Privacy notice

Data controller

Hosting and DNS

The website, its server services and the associated operational data are hosted by Hetzner in Germany. AI processing for ANNA takes place in Lower Bavaria, as described in the section on the AI assistant. DNS is managed through INWX in Germany. No CDN or external diagnostic service for usage or error data is used. Hosting and DNS providers process the technical connection data needed to provide their respective services. Map data sources and external services that you choose to open are described separately in the relevant sections.

Using the website, search and map

When you make a request, the server processes technically necessary connection data, particularly your IP address and the requested URL, to deliver the page or API response. The front-end web server keeps access and error logs; the application writes operational and diagnostic messages to the system journal. Access logs may contain the client address, the complete request including search text or coordinates, response status, referrer and user agent.

Search and routing requests are processed to provide the requested function. Map tiles, search and routing are generally delivered through karte.bayern itself. Usage is not used to create advertising profiles and is not passed from the browser to Google Maps, Apple Maps or comparable global map services.

The logs are used exclusively for necessary operation and security. No additional profiling or deliberate association of these search and routing logs with user accounts takes place. The IP address and request details described above may nevertheless be included.

Operational statistics

Usage counts are aggregated for a technical overview of operations. These include coarse spatial counts of requested places and routes. A requested place does not necessarily represent your actual location. To estimate the number of distinct accesses each day, the server processes the IP address and a broad browser category using a key that changes daily. Neither these inputs nor their HMAC values are stored in the statistical registers. Daily aggregates are cleaned up when the statistics store is opened and at the start of each UTC day: daily registers and spatial usage aggregates dated before the UTC cutoff of “today minus 32 calendar days” are deleted. The cutoff date itself is retained. Daily keys older than the previous UTC day are also removed. This does not mean that other logs or backups are deleted after the same period. This processing serves operational planning and security (Article 6(1)(f) GDPR); it does not use statistics cookies.

Cookies and technically necessary storage

Karte.Bayern does not set marketing or tracking cookies or embed external analytics, font or advertising scripts. Where information is stored in the browser, it supports functions you use, such as settings, navigation, offline maps, debug exports or form drafts. Technically necessary session or access-token cookies may be set for login and WorkOps functions. Section 25(2), point 2, of the German TDDDG applies to access that is strictly necessary for a service you have explicitly requested. Non-essential access requires prior consent; not using marketing does not in itself create an exemption. The home page at https://karte.bayern/ does not initialise cookies, a service worker or local browser storage. Additional app storage functions begin only within the applications themselves or after a function is invoked.

Accounts, organisations and municipal contributions

When you use account, organisation, WorkOps or editorial functions, the server processes the submitted profile and contact details, memberships, permissions, credentials, and associated content and activities. Access and changes may be logged for access control and traceability. Processing serves the requested function and its security (Article 6(1)(b) or (f) GDPR, depending on the specific relationship).

Municipal change proposals are stored for review. Approved content may be displayed publicly; submitting a proposal does not immediately publish it. Requests for erasure or access can be made using the contact details below.

The login cookie kb_identity_token is limited to 30 days and is removed when you log out. Server-side account, session and activity data are separate. Deleting local browser data does not automatically delete those server-side records.

Fuel-price demo

When you explicitly request the price demo, a short-lived signed cookie (kb_fuel_price_view, 15 minutes by default) protects access against automated bulk retrieval. To enforce a limited access allowance, the server retains HMAC-derived values of the IP address and requested targets (for 24 hours by default). These pseudonymous data are used to prevent abuse, not for advertising or recognition across providers (Article 6(1)(f) GDPR).

Local browser storage

The applications may use localStorage, sessionStorage, IndexedDB, Cache Storage and service workers. Stored information may include map styles, navigation options, recent inputs, offline map data, route caches, incident-response/WorkOps data, debug logs or diagnostic information. These data remain on the device until deleted by the application or through the browser settings.

Traffic reports and Mobilithek

Traffic reports such as roadworks, closures and congestion may be retrieved on the server from Mobilithek/DATEX II feeds, normalised and stored for map layers and route calculation. These reports describe traffic conditions and road sections; they are not used to profile individual users.

Location data

The browser shares your location only with your permission. Your current position is used to provide nearby maps, search or navigation. In debug mode, location, device status, console messages and navigation announcements may be logged locally and exported as a debug file. These debug data are not uploaded automatically.

Online search may send search text and a geographical reference to the Karte.Bayern server; route planning may send the starting point, destination and selected options. Recalculation may use your current location as the starting point. Map tile requests reveal the area being viewed. Prepared offline data allow certain functions to work without ongoing server requests; downloads and updates require a connection and transmit the areas requested.

If you share a location or route progress, a time-limited sharing link is created. Depending on the selected mode, it shows only estimated arrival time and status, progress along the route, an approximate position or an exact position. Public and update tokens are stored on the server only as hashes. Expired or ended shares are automatically deleted after a short retention period.

Native iPhone and iPad app

This section describes the App Store edition of Karte.Bayern for iPhone and iPad: map, place search, local favourites, route planning, navigation, free driving (“Freie Fahrt”), saved routes, offline street maps and optional destination and route history. These functions do not require a Karte.Bayern account. Location access is optional; starting points and destinations can also be selected manually.

Online requests and location processing

Online search transmits search text and, where applicable, the selected geographical reference, such as the map centre or your permitted location. Route planning transmits the starting point, destination, travel profile and route options. When a route is recalculated or alternatives are updated, your current location may again be transmitted as the starting point. Requests for maps, road data and optional traffic information describe a map area or route corridor. They may allow inferences about your surroundings. The server receives connection data and may log requests as described in the server logging section. Not having an app account therefore does not make server requests anonymous.

Additional map layers and place information are retrieved through Karte.Bayern servers after you select them. Official geographic areas, historical maps, water supply points, and weather and elevation information relate to the selected place, map area or planned route. Elevation requests may transmit selected points along the route. These requests are also subject to the server logging described above. External source links are opened only after you select them.

During car navigation that you have deliberately started, the app may send the remaining compact road path, trip progress and estimated remaining travel time to the routing service to detect new disruptions. The routing service evaluates these without storing a trip or server navigation session; connection and operational logs remain separate. Any necessary recalculation transmits the starting point and destination like an ordinary routing request.

Deliberately started trips in the background

The app processes GPS progress, speed and turn instructions on the device. Background navigation is on by default: navigation or free driving that you have deliberately started continues when the screen is locked or you switch to another app. The setting alone does not start location tracking. If you turn it off, the trip pauses when you leave the app and background location tracking stops. Returning to the app does not automatically resume the trip. You can end the trip at any time or revoke location permission in the iOS settings.

Widgets and Live Activities

The App Store edition's widgets open search, saved content, offline maps or settings. They do not request location themselves or start network requests, a trip or a download. During navigation or free driving, the app may display local Live Activities with turn instructions, distance, remaining route distance and speed on the lock screen and in the Dynamic Island. These details may be visible there; you can manage Live Activities in the iOS settings. Updates originate from the device and do not use an operator-provided push service.

Favourites, history and offline buffers

Favourites, explicitly saved routes and settings stay on the device and are not synchronised with a Karte.Bayern account. Destination and route history can be enabled separately and are off by default. History stores selected destinations and route summaries, not a sequence of individual GPS positions. Retention can be set to 7, 30, 90 or 365 days; the default is 30 days. Cleanup occurs when history is loaded and updated. You can delete individual entries or all history and deliberately export it to another app.

When you deliberately start navigation, the app buffers the complete route with turn instructions for 24 hours. Expired route data are removed on the next access. It also downloads street maps along the route and, when driving, public road data for local detours, including over mobile networks. The requests relate to the planned route and do not create a GPS history. You can disable and clear the automatic buffer; maps already stored can be removed separately. Within the storage budget, maps are retained until removed or automatically rotated; explicitly prepared areas remain until removed. Road data for detours are valid for 24 hours.

The route library, temporary route buffer, history and local detour data are excluded from device backups. Other app data, such as favourites and settings, may be included in device backups depending on iOS and backup settings. Deleting data on the device does not remove older backups. iOS may manage cached map resources independently.

Sharing a place or trip

Sharing a place (“Ort teilen”) opens the iOS share sheet with a map link containing the selected place's name and coordinates. You choose the destination app and recipient. Sharing a trip (“Fahrt teilen” or “Unterwegs teilen”) instead starts a time-limited share on the Karte.Bayern server only after your deliberate selection. Anyone with the link can view the shared information.

By default, the route, trip status, progress, remaining distance and arrival time are shared, not current GPS coordinates. Alternatively, you can share only arrival time or an approximate or exact location. Approximate-location coordinates are rounded before transmission. Sharing is limited to 15, 30, 60 or 120 minutes. You can end it earlier. Updates pause without a connection; a revocation that has not yet been acknowledged may leave the link accessible until it expires. Expired or ended shares are subject to the server-side deletion routine described in the section on temporary sharing.

To retry revocation, the app temporarily retains a device-bound Keychain entry containing the sharing link, expiry time and revocation data. It contains no GPS history and is not synchronised through iCloud. Public and update tokens are stored on the server only as hashes. External information, telephone and email links open after you select them; the destination app and recipient have their own privacy notices.

The app's API requests to Karte.Bayern use no cookie, credential or URLCache storage. MapLibre Native also maintains its own persistent map tile cache for offline functions. The App Store edition contains no advertising or analytics SDK of its own. Server-side logging and operational statistics are separate from this.

ANNA AI assistant

ANNA is designed as a data-minimising assistant for questions about maps, routing and points of interest. Requests are processed to provide the current response and the requested map functions. AI processing takes place in Lower Bavaria. Karte.Bayern does not use ANNA conversations to profile users.

In addition to your question, selected place and route context may be transmitted to this AI service in Lower Bavaria. When diagnostic logging is enabled, the question, answer, context including any coordinates, and technical connection details are stored in separate files on the server. Please do not submit confidential information or personal data that are unnecessary for your question.

External services and links

External links, for example to OpenStreetMap, Wikidata, Wikipedia, BayernAtlas or project websites, are opened only when you click them. Map and source content is mainly delivered through Karte.Bayern's own endpoints. Depending on the data source, the server may retrieve external services, such as aerial imagery or Wikimedia content. An endpoint operated by Karte.Bayern therefore does not mean that all data are produced without external processing. Source and rights information is provided in the relevant view and in the source and licence notices.

Place-data enrichment through Google Places or Google Geocoding is disabled. Other external data sources are independent of this.

Contact and data submissions

If you contact karte.bayern by email or submit data, the information provided is processed to handle your request. It may include your name, email address, organisation, message and submitted geographic data.

Legal bases and retention periods

Depending on the function, processing provides the requested website or map function, serves legitimate interests in secure and stable operation, or relies on voluntary consent, for example for location access. The legal bases are, in particular, Article 6(1)(b), (f) and, where consent is given, (a) GDPR. Under the verified operational configuration, the system journal is limited to 28 days and 512 MB. Web server logs are rotated daily, with 14 archive generations provided for. These limits apply to the respective storage systems, not automatically to the active log file, other recipients or backup copies. You can delete local browser and app data yourself.

No separate backups of server or database data, or provider snapshots used as backups, are currently retained. Device backups through iOS or iCloud are governed independently by the device settings.

Separate AI and API diagnostic files are not covered by these journal limits. No automatic deletion period is configured for those files; their retention and deletion must be managed separately in operations. Deleting data locally in the browser does not remove server logs already stored.

Your rights

Data subjects may request access, rectification, erasure, restriction of processing and data portability, and may object to processing, within the limits of applicable law. Where processing is based on consent, consent may be withdrawn for future processing. For privacy requests, simply email karte.bayern@simon.waldherr.eu. You also have the right to lodge a complaint with a data protection supervisory authority, in particular the Bavarian State Office for Data Protection Supervision.