Privacy policy

Last updated: 20 October 2026

This is an English translation for your convenience. Only the German version is legally binding.

1. Controller

EDV-Technik Dennis Weimer
Owner: Dennis Weimer
Franz-Rector-Straße 1
55411 Bingen
Germany
E-mail: support@glowcamp.de

You can find further details about the provider in the legal notice.

2. Basic principle: local instead of cloud

GlowCamp is deliberately built so that your travel data leaves your device as little as possible, ideally not at all. There is no GlowCamp user account; the app can be used entirely without an account. As long as you do not share a trip, we store on our servers neither your location nor your route nor your photos; we store your diary entries only if, when sharing, you expressly select an individual entry for this (section 6b). All of this data is held exclusively locally in a database on your smartphone.

From version 1.10.0 you can voluntarily share individual trips via a private link (section 6b), without an account. Only for trips that you expressly share do we store the places, the route and the photos that you select for this, and, if you wish, your current position while driving. Everything you do not share stays only on your device. A voluntary user account, sharing with friends, public trips, the "Campfire" and sharing information about pitches, petrol stations and sights are available from version 1.12.0; route calculation via our own server from version 1.11.0, and the printed travel book from version 1.12.0. They are described in section 18. In older versions of the app, no data is processed for these.

For individual features, the app nevertheless queries public third-party services (place search, route calculation, map tiles as a fallback) or our own server (map tiles, campsite data). In addition, you can voluntarily, and only when you tap, report how full a campsite or motorhome pitch is (occupancy report, from version 1.4.0) — only the identifier of the site is transmitted, not your location. Likewise, only when you tap can you look up an address for a stop or for your home location; in doing so, the coordinate of this one point is sent to a public map service (sections 3 and 5). Only if you switch on weather notices (consent, new from app version 1.10.0) does the app query the weather service Open-Meteo for the weather at a position rounded to approx. 10 km (sections 3 and 5). With the same consent, the app also loads the official severe weather warnings for the country you are currently in from MeteoAlarm; no position is sent for this, only the country (section 5). Unless you switch off the "Severe weather push", the app, when you are at a place to stay, also reports the country, the warning area and a push identifier to our server so that warnings arrive even when the app is idle (section 5, again no position). The data transmitted in each case is listed individually below. For the Google Maps list import, the app does not require you to sign in to Google: it retrieves publicly shared lists without signing in (see section 5). The optional sign-in in an embedded Google window included in version 1.3.0 has been switched off since version 1.3.1 and completely removed from the app from version 1.6.0.

3. Location data (core feature of the app)

GlowCamp records your position when you start a trip — including in the background if you allow this ("Always" permission), so that the route is recorded completely even when the screen is locked. This location data is stored and processed exclusively locally on your device (stage detection, fog-of-war map reveal, trip review, statistics). Your location and your route are not transmitted to us or to any other server unless you expressly share a trip via a private link (from version 1.10.0, section 6b). If you share a trip "live" via a link, the app sends your current position to our server about every 5 minutes while driving; for this it takes the position from the recording that is already running and does not switch on any additional location tracking. Apart from that, the exceptions always concern only a single point and never happen automatically, but only when you expressly tap (for the weather, which only works with a rounded position, see below): if you tap "Search address" for a stop (from version 1.5.0) or the GPS symbol for your home location, the coordinate of exactly this one point (without route, photos or diary) is sent to Nominatim of the OpenStreetMap Foundation in order to suggest an address to you (see section 5). The place suggestions for stops (e.g. campsites, petrol stations or previous places nearby), by contrast, come exclusively from data on your device. If you voluntarily report the occupancy of a known site (see section 5), only the identifier of this site is transmitted, not your coordinates and not your route.

Weather (only with your consent): If you have agreed to the weather notices, the app sends a rounded position to the weather service Open-Meteo without any further tap: the coordinate is first rounded to 0.1 degrees (approx. 10 km; more precisely, approx. 11 km in the north-south direction and, in Central Europe, approx. 7 km in the east-west direction). This happens during a recorded trip at a detected stop, for the weather of the current day and, when you open an ongoing trip, for the daily forecast at the place of your last overnight stay; weather for past days is not retrieved. Because the query is triggered at your stop, the rounded position is close to where you are. Your exact position, your route and your trip are not transmitted. For the official severe weather warnings (MeteoAlarm), no position at all is sent: the app loads the warning list for the whole country and checks on your device whether a warning affects your site; it also determines the country on the device. Details in section 5.

The home-arrival detection ("End trip?" when you reach your home location) and the "My location" option for the dart also evaluate your position exclusively locally. For "My location", the position is determined only once when you tap; no additional continuous location tracking runs for this.

If you tap "Navigate" (e.g. "Navigate to next stop" or for a campsite or a petrol station), GlowCamp passes the coordinate and the name of this one destination to the map or navigation app of your choice on your device (e.g. Apple Maps, Google Maps, Waze or Sygic). GlowCamp itself does not transmit anything to a server in doing so; what the chosen app does with the destination is governed by its own privacy policy.

The legal basis is your consent (Art. 6(1)(a) GDPR), which you give via the system permission dialogue — preceded in the app by a separate information screen explaining background use. You can revoke the permission at any time in the device settings; the app will then only record while it is open, or not at all if you withdraw access completely.

4. Cloud backup (optional)

If you activate cloud backup in the app settings (opt-in, deactivated by default), a backup copy of your local data is regularly written to your own cloud storage — depending on the operating system, in iCloud (Apple) or Google Drive (Google), in each case in the "app data" area of your own account, which is not visible to you. From version 1.6.0, the app points out this option once after your first completed trip; the backup remains deactivated until you switch it on yourself in the settings.

This is your own Apple or Google account — we ourselves have no access to these backup copies. The privacy provisions of Apple or Google also apply. The backup copy includes your trip data (including location history), diary (including noted diary destinations and your markings on sights such as "Visited" or "Don't suggest again", each with the name and location of the place), your saved home location, the places noted for the morning outing ideas (name and location, from version 1.10.0), app settings, photos and documents; videos are not included in the backup. From version 1.10.0, it also includes your travel companions under "My people" (name, role, for pets the species, emoji, and if you wish a photo and a year of birth; including for children), your own ratings of sights (stars, "Suitable for", private note) and your weather corrections. This information is held only on your device and, if you have switched on the backup, in your own cloud backup; it is never sent to us or to any other service and never shared. If you have switched on weather notices, the backup also contains the locally stored weather values (temperature and weather conditions per rounded position and day or hour, see section 5). Your weather consent, the most recently retrieved forecast and scheduled weather notifications, by contrast, are reset when restoring: on the new device, the app asks again before retrieving weather. Likewise, the registration for the severe weather push is not restored. From version 1.10.0, the backup also includes your sharing settings (which trips, places and photos you share via a link), the secret key of private links and the list of deletion requests not yet carried out (section 6b). GlowCamp does not additionally encrypt the copy itself — protection is provided by the encryption of your Apple or Google account (during transmission and on their servers).

The legal basis is your consent (Art. 6(1)(a) GDPR); you can deactivate cloud backup again at any time in the app settings. With "Delete all data" in the app, you can choose whether only the data on your device or also the backup copy in your cloud is deleted. If you choose "This device only", the backup copy initially remains and is replaced by the (then empty) state during the next backup run; it can also be deleted at any time in your Apple or Google account.

5. External services to which data is transmitted

The following features send requests to public third-party services or to our own server. In each case, only the information needed for the request leaves your device (search text, map section, route coordinates, vehicle dimensions or a rounded position for the weather) — none of your saved trips, photos or diary entries. The only exceptions are sharing a trip via a private link (section 6b), the occupancy report and the severe weather push (in each case only after your consent or after you switch it on, see table). Account, friends, public trips, Campfire and community information (from version 1.12.0) as well as the further features from version 1.11.0 and 1.12.0 are covered in section 18 and in the table at the end of this policy.

For the row on sharing via a link, the legal basis in section 6b applies; for weather, severe weather warnings and severe weather push, consent applies (see below), as it also does for the occupancy report. For all other rows, including delivery of the link page to its viewers, the legal basis is our legitimate interest in a working map and search function (Art. 6(1)(f) GDPR). The services named are also subject to their own privacy provisions, in particular those of MapTiler, those of the OpenStreetMap Foundation, those of openrouteservice (HeiGIT) and, if you use the list import or the severe weather push on Android, those of Google or, for the severe weather push on iOS, those of Apple; as well as those of Open-Meteo and MeteoAlarm.

Weather (Open-Meteo): The legal basis is your consent (Art. 6(1)(a) GDPR). The app asks for it once, at the first stop during a recorded trip or when you switch on the weather notices yourself. A "Yes" covers both, the severe weather notice and the weather in the diary and at stops. Without your "Yes", no weather is retrieved and none is displayed; "Not now" does not ask again. You can withdraw your consent at any time: Profile → Notices & features → Notifications → "Turn off weather data completely". After that, the app no longer retrieves or displays any weather; the most recently stored forecast and scheduled weather notifications are deleted. The withdrawal does not affect the lawfulness of the processing carried out up to that point. The app stores the retrieved weather values only locally on your device (and in your own cloud backup, if activated, see section 4); "Delete all data" removes them completely. Open-Meteo is based in Switzerland; there is an adequacy decision of the EU Commission for Switzerland (Art. 45 GDPR). The terms of use and privacy provisions of Open-Meteo also apply. The forecast is a notice without guarantee and does not replace official severe weather warnings.

Official severe weather warnings (MeteoAlarm): The legal basis is the same consent as for the weather (Art. 6(1)(a) GDPR); a "Yes" to the weather notices also covers the official warnings, and with "Turn off weather data completely" you withdraw both. No position is sent to MeteoAlarm, only the retrieval of a country's warning list and your IP address. MeteoAlarm is operated by GeoSphere Austria in Vienna, so the data remains in the EU. MeteoAlarm does not state separately how long its servers store IP addresses when the warning lists are retrieved; for its programming interfaces, GeoSphere Austria states a retention period for server log files of 180 days. The terms of use of MeteoAlarm also apply. The warnings come from the national weather services; delays are possible between the app and meteoalarm.org; the warnings there and from the weather services are authoritative.

Severe weather push (from version 1.10.0)

Purpose: Official severe weather warnings should reach you even when your phone is lying still at the site and the app is idle in the background (it then hardly checks by itself any more). That is why our server queries the warnings from MeteoAlarm and sends you a notification as soon as a new warning applies to your warning area.

What data: If you arrive at a stop or overnight pitch during a recorded trip, the app reports only the following to our server (glowcamp.de): the country, the identifier(s) of the MeteoAlarm warning area (e.g. "Kreis Friesland – Küste", at most 10), a push identifier of your device with the platform (iOS/Android), the app language and your time zone together with the setting that at night (10 pm–7 am) only warnings of level orange or red come through. The app determines the warning area on your device from the area outlines included in the app; your position does not leave the device in the process. No trip, no route, no account and no device or advertising identifier is transmitted; the registration is not linked to shared trips or to the occupancy report. For changing and deleting, the app receives a random identifier and a secret key; on the server, the key is stored only as a check value (hash). Our server also remembers which warnings it has already sent for this registration, so that each warning only arrives once (again only if the level rises).

Delivery: Our server sends the notification (level of the warning, heading and issuer of the warning, e.g. "Official WARNING of STORM GUSTS – Deutscher Wetterdienst") with the push identifier to the delivery service of Apple (Apple Push Notification Service) or Google (Firebase Cloud Messaging), which deliver it to your device. In doing so, Apple and Google receive the push identifier and the text of the notification, but no warning area and no position. From version 1.12.0 (currently not active), the notification also names the site to which the warning applies (e.g. "At your caravan (Campsite X)"). The app only inserts this name into the notification on your device (on the iPhone via an extension of the app that runs when the notification is received); the site name never goes to our server, nor to Apple or Google. Apple and Google are recipients of this data and operate their delivery services as independent services under their own privacy provisions. On Android, we use Firebase Cloud Messaging only as a delivery service, without automatic registration when the app starts and without analytics; the identifier is only requested when you are at a stop and the conditions above are met. Apple and Google may process the data in the USA. Such a transfer is based on the adequacy decision of the EU Commission for the EU-US Data Privacy Framework, insofar as the respective provider is certified under it, and otherwise on standard contractual clauses of the EU Commission.

Legal basis: your consent (Art. 6(1)(a) GDPR), the same as for the weather; the consent dialogue expressly mentions the severe weather push. Without consent, with the notification type "Severe weather at site" switched off, during a notification pause or without permission for notifications in the operating system, the app does not register anything. The app never asks specifically for notification permission for this; it only uses permission that has already been granted.

Deletion: If you only drive from the overnight pitch on an outing (e.g. shopping, a sight) and stay within a radius of 10 km, the registration remains in place (the awning and chairs are still at the site, after all); the app checks the distance on your device, and it stores the coordinate of the site only there. The app deletes the registration on our server as soon as you are more than 10 km away from the site, a new overnight pitch takes its place, you end or delete the trip, switch off "Severe weather at site", pause notifications, withdraw the weather consent ("Turn off weather data completely") or choose "Delete all data". Irrespective of this, our server deletes every registration no later than 24 hours after the last registration or extension (if you stay longer at the same site, the app extends it). We delete the list of warnings already sent together with the registration, no later than 12 hours after the end of the respective warning. There is no history. The IP address is held only in memory for rate limiting (at most 1 hour); no access log is kept for this address. If the severe weather push is not available (e.g. in countries without area outlines such as Switzerland, or if our server has switched it off), the app generates the notifications itself on your device as before.

Occupancy report: The legal basis is your consent (Art. 6(1)(a) GDPR), which you give in the app's explanation dialogue; data is only sent after each individual tap on an answer. If you choose "No, thanks", the report stays only on your device. You can withdraw your consent at any time in the app: Profile → Notices & features → Report occupancy → "Withdraw consent to sending" switch. The withdrawal does not affect the lawfulness of the processing carried out up to that point. Reports already sent are deleted after 2 days at the latest; individually, they can no longer be attributed to you (see section 12).

In order to detect and remove misuse (e.g. deliberate false reports), the operator can see the stored individual reports from the last 48 hours (site, level, source, hour, time of receipt) in a protected administration area and can delete individual reports. The hash and the IP address are not displayed there; even the operator cannot attribute a report to you. The legal basis for this is our legitimate interest in reliable occupancy information (Art. 6(1)(f) GDPR).

6. Photos and journal

GlowCamp stores trip photos and journal entries locally in the app directory on your device. Journal entries are only uploaded if you share a trip by link and, for an individual entry, explicitly choose “Yes, highlight” or “Yes, whole entry” (section 6b). Photos are only uploaded if you select them individually when sharing a trip (from version 1.10.0, section 6b); without this selection they are not shared with us and not transferred to third parties. Photos you take with the camera in GlowCamp (of petrol stations and pitches) and photos you add from your media library remain on your device. The app evaluates photo suggestions from your camera roll (only if you switch them on) and places from photos (where they were taken) exclusively locally. Likewise locally, from version 1.12.0, the app searches your media library for the original full-resolution photos for your travel book (based on capture time and image dimensions) and chooses the image crop; nothing is transferred in the process.

My people (from version 1.10.0): Under Profile → “My people” you can add travel companions (partner, children, friends, family, pets) with a name, emoji or photo and, if you wish, a year of birth. In addition, there are your own ratings of sights and weather corrections. This information is stored exclusively locally on your device (and, if enabled, in your own cloud backup, section 4); it is never transferred to us or third parties. When sharing by link, only the number and, if you switch it on, the first names of your travel companions are uploaded (section 6b), never photos or years of birth. Please only add information about children and other people if they agree or their parents or guardians agree. Using “Export data” (Profile → My data) you can save your trips (GPX, journal as HTML or PDF) as a file.

6b. Sharing a trip via a private link (voluntary, from version 1.10.0, without an account)

Anyone who sees your shared trip can tell that you are or were away travelling. You decide for each trip individually whether to share it; nothing is uploaded unless you explicitly switch it on. Anyone who has the link sees the trip on a glowcamp.de web page in their browser, without the app and without an account. The page cannot be found by searching and can only be reached via the secret link. Default setting: live (with a notice, see below). Sharing with friends and sharing publicly are available from version 1.12.0 with an account (section 18b).

For each trip you choose which places and which photos are included; photos are never preselected. Identifiers from your device’s database never leave it in the process; the server receives new, random keys for each share.

• What can be shared: everything you select, including your own places, wild camping spots and private addresses with the name you have given them, and, if you wish, the complete route including the drive from home and back. Anyone who has the link will then also see where you set off from. In addition, the day of arrival at each place (for times, see below), the month in which the trip began and, if you wish, the trip name. Places and route are rounded to about 10 metres, and the route is simplified and transferred without timestamps.
• Departure and kilometres: The app additionally uploads the time of your departure (start of the trip with time of day) and the kilometres driven so far (rounded to whole km, as in the trip review). The page shows them, for example, as “Set off Mon 08:12 · 312 km”: with “live” immediately, otherwise only after the end of the trip. After the end of the trip it only shows kilometres and duration in days (e.g. “312 km · 5 days”), no departure time. This is on by default; you can switch it off for each trip and level with the switch “Show departure, times and km” in the “Who can see it?” step; then neither is uploaded any more.
• Times at places and end of trip (from app version 1.10.0): For each shared place, the app additionally uploads the arrival and departure times, together with the time zone offset of your local time, so that the page shows, for example, “12:05–15:33 Leipzig” in your local time. It also uploads the planned end of the trip, if you have entered one, and, after the end of the trip, the end date. The times never appear before the place itself; the departure time and end date are only uploaded after the set delay. The times and the end date are tied to the same switch as departure and kilometres: if you switch it off for a trip and level, they are not uploaded either.
• Travel companions (from app version 1.10.0): If you have entered travel companions for the trip, the app only uploads their number (people and pets); with the switch “Show travel companions’ names” (off by default) it additionally uploads their first names, with pets shown as a symbol. Roles, years of birth, ages and photos of travel companions are never uploaded.
• Planned excursions (from app version 1.10.0): With the switch “Show planned excursions” (off by default), the app uploads for today and the coming days (at most 14) only the names of the planned excursion destinations (at most 5 per day), without location and without time. Past days are never uploaded.
• Parked status update with Live (from app version 1.10.0): While you are sharing your trip live (private link) and your vehicle is parked at a stop, the app sends a parked status update at most about every 45 minutes with the stored position of this stop (rounded to approx. 10 m) and the time you arrived there, without determining your location again; the page then shows “Now: <place> · parked since <time>”. Only the latest update is stored; it is replaced by the next position, a pause or the end of the trip and is no longer displayed 36 hours after the last update at the latest.
• Special journeys (from app version 1.10.0): If you have marked a journey in the journal as a special journey (e.g. a city tour by bus) or assigned photos to it, the app uploads this journey with its means of transport and name; as long as “Show departure, times and km” is switched on, it also uploads km and times. Photos you assign to a journey appear there. Normal journeys in your own vehicle are not transferred individually.
• Weather at the places (from app version 1.10.0): If you have consented to weather notices (section 5), the app uploads for each shared place the weather at the hour of your arrival: only the temperature and a code for the weather conditions (e.g. sunny, rain). The value comes from your device’s storage; no additional weather data is retrieved for sharing and nothing is sent to Open-Meteo. If a value is missing, the place is shown without weather. Without weather consent, weather is never uploaded.
• Journal (from app version 1.10.0): If sharing by link is switched on for a trip, the app asks when you save the evening journal whether the entry should appear on the trip page. The default is “No”. Only if you choose it for this entry does the app upload the highlight of the day (“Yes, highlight”) or the whole entry with highlight, detailed text and mood (“Yes, whole entry”), in each case with the day. The texts are only displayed as plain text. The entry appears with the same delay as the places of that day and never before the first visible place; on days without a shared place it is not uploaded. You can change your choice in the entry at any time; “No” removes it from the page the next time content is uploaded.
• Photos: at most 5 per day of the trip, only those you select individually. Before uploading, the app removes all metadata (e.g. location and camera) and reduces the size of the image; our server does this a second time. Please do not share photos in which people or vehicle number plates can be recognised. By uploading, you confirm that you hold the rights to the photo. The photos remain on our server until the link expires or until you withdraw them, and are visible to anyone who has the link. From version 1.12.0 (currently not active): Instead of at most 5 photos per day of the trip, there is an allowance of 5 photos per day that builds up if you share fewer on a given day; with GlowCamp Pro (section 9) it is 50 photos per day. There is no upper limit per trip. So that the server checks the correct allowance, the app only sends the indication “Pro” when uploading; we do not store it. For public trips (section 18b) the limit remains at most 5 photos per day. In the app itself, photos remain unlimited. If storage space on our server runs low, it temporarily accepts no new photos; the app then shows you that there is a technical problem, and we receive a notification e-mail with the storage level, without any information about you or your photos.
• Timing: You choose when a place becomes visible on the page: 2, 5, 12, 24 or 48 hours after you arrive there, or immediately (“live”, default). The waiting time counts from arrival, even if you are still at the pitch. A section of the route only appears once the place at its end is visible.
• Stops entered by you with the link: A stop that you enter yourself in the app is uploaded by the app immediately. On the link page it appears after the chosen waiting time from the arrival time you entered, so with “live” immediately. Unlike automatically detected stops, there is no minimum length of stay for this (with “live” otherwise about 30 minutes).
• Uploading and holding back: The app uploads the selected content straight away as soon as you reach a place. Our server stores it until the chosen time, shows it to no one until then and enforces the waiting time itself. Our server therefore knows a place even before it is released. It publishes every 15 minutes; a place therefore appears at the next full quarter-hour after the waiting time has expired (a few minutes later under high load). In the app you can see roughly when a place will become visible.
• “Live” with the link: Here the page additionally shows where you are at the moment: while you are driving, the app sends your current position together with the time and the route since the last visible place to our server about every 5 minutes. The position comes from the recording that is running anyway; no additional location tracking takes place for this. What is stored is the latest position in each case and the route since the last visible place (points without timestamps, at most 2000). The page shows a position that is older than 15 minutes as “last known position”, for at most 12 hours (a parked status update for at most 36 hours); at places you do not share, the position is paused, and after the end of the trip there is no live position any more. All of this is deleted together with the link at the latest. Before you share by link for the first time, the app informs you of this and asks for your confirmation.
• Please note: Anyone who sees your trip can tell that you are away and that your home may be empty, and with “live” also where you are currently parked or driving.

Link page: You send the link yourself, e.g. via a messenger or e-mail; only give it to people you trust, because anyone who has it can pass it on. If you send the link e.g. in WhatsApp, the messenger loads a preview from glowcamp.de. This preview is the same for all links (“A trip has been shared with you” and the GlowCamp lettering) and contains no trip data: no place, no map, no trip name. The page itself only shows what is currently released and refreshes about every 5 minutes while it is visible. What the viewer’s browser transfers to glowcamp.de and tiles.glowcamp.de in the process is set out in section 5 (row “Link page in the browser”): the page sets no cookies, stores nothing in the browser, uses no analytics or tracking services and loads nothing from third-party servers; we do not log the requests and do not find out who views the page. We only count how many links are created and trip pages are opened per day – without reference to people, devices or individual links.

Link without an account: When you share, your app receives a secret key with which only you can change or delete the trip. It is stored in the protected keystore of your device and additionally in your cloud backup, if you have enabled it (section 4), so that you can still delete the trip even after changing devices. On the server we store the key only as a hash value, and we store no device or account identifier and no IP address with it. If you lose your device without a backup, you can no longer delete the link yourself; it then expires automatically like any other link.

Expiry: Links expire 30 days after the end of the trip (without an end of trip, 30 days after the last upload); after that the page can no longer be reached with immediate effect and we delete the content during the next 15-minute run.

• Withdrawing: You can withdraw individual places, photos or the whole trip, or switch sharing off, at any time, including during the waiting time, and likewise with “Stop all sharing” in your profile. With the link, they disappear from the server immediately (as soon as your device is online); a link page that is already open shows the old state until it next refreshes (about every 5 minutes).
• Deletion requests: If you delete a shared trip, a share or, with “Delete all data”, everything on your device, the app remembers a deletion request for the server (only the identifier of the share on the server, the level, the time and, for the link, the deletion key) and sends it; if there is no connection, it does so as soon as a connection is available again. This list is therefore retained even after “Delete all data” and after a restore from backup, until the server has confirmed the deletion.
• Notifications on your own device: see section 8; they are purely local.

Reporting and moderation: You can report content that violates the law or our Terms of Use to us via “Report” at the bottom of the link page (opens an e-mail to us) or directly at support@glowcamp.de. We review reports manually and remove unlawful content. We only use an e-mail address provided voluntarily in this context to respond to that report. For the link page, we are a hosting service within the meaning of the Digital Services Act (DSA). The single point of contact for users and for authorities is support@glowcamp.de (German or English). To process a report, we process the reported link, the reasons given and, if provided, your contact details. There is no general monitoring of shared content. The link page refers to the legal notice, this privacy policy and the Terms of Use.

The legal basis for sharing by link (including the live position) is your consent (Art. 6(1)(a) GDPR), which you give for each trip and can withdraw at any time by withdrawing the trip or switching sharing off; withdrawal does not affect the lawfulness of processing carried out up to that point. For protection against misuse (rate limiting), we rely on our legitimate interest in a secure service (Art. 6(1)(f) GDPR), and for legal obligations to process reports on Art. 6(1)(c) GDPR.

7. Feedback form

Using the feedback form on this website and the corresponding function in the app itself, you can report bugs or submit requests without creating an account. What is transmitted is the category, title and description you enter; from the app, also the app version and the platform including the operating system version (e.g. “Android 14”). If you report a bug via “Report a bug”, the app pre-fills the description with the error message; you can see the text and change it before sending. We deliberately do not ask for a name or an e-mail address. If you yourself include personal data in the description (e.g. your name in the message), this is voluntary.

The information is transmitted to our own server (glowcamp.de) and recorded there as a ticket (issue) in the GitHub issue tracking system (GitHub Inc., USA, a Microsoft company) in a non-public repository for processing. The transfer to the USA takes place on the basis of standard contractual clauses of the EU Commission (Art. 46(2)(c) GDPR). Please do not include names or contact details of third parties in the text. To protect against misuse/spam, your IP address is briefly (for a maximum of one hour) held exclusively in the server’s working memory in order to detect too many requests from the same address — it is not stored permanently and is not stored linked to the content of your feedback.

The legal basis is our legitimate interest in receiving and processing feedback in order to improve the app (Art. 6(1)(f) GDPR).

8. Notifications

Reminders (e.g. about checklists or the evening journal) and the notice “Welcome home – end trip?” (from version 1.3.0) are notifications generated locally on your device. Apart from the severe weather push (see below), there is no push delivery via a server and no third-party push service (planned additionally from version 1.12.0: notifications about an ordered travel book, section 18e).

Sharing trips (from version 1.10.0): These notices are also generated purely locally on your device; nothing is sent to a server for this and no additional location tracking is switched on:

• once at the start, “You are sharing your trip” with the levels you have switched on (link, live or with waiting time);
• on Android, the addition “Shared live” in the notification about the ongoing recording, which is visible anyway, as long as you are sharing live;
• “Newly visible” as soon as a shared place becomes visible via the link. The app schedules this notice in advance for the release time, combines several places and does not mention any place name or trip name. You can switch it off under Profile → Notices & features.

The question “How full is this site?” is generated locally on your device as soon as the app detects that you are at a known campsite or motorhome pitch. Nothing is sent to a server for this; only your tap on an answer and your consent trigger a report (see section 5). The question can be switched off in the app.

The notice “Would you like to write something about this place in your journal?” (from version 1.6.0) is also generated locally on your device when the app detects that you are at a known campsite or motorhome pitch and the trip’s evening journal is active. Nothing is sent to a server for this. The site name is not included in the notification text. You switch the notice off by switching off the trip’s evening reminder.

Severe weather notices at your pitch (e.g. “Thunderstorms possible”) and the weather line in the morning notification are also generated and scheduled locally on your device, from the forecast previously retrieved from Open-Meteo or the official warnings loaded from MeteoAlarm (only with your consent, see section 5). The app also shows official warnings of level orange or red at night. The content of these local notifications is not sent to any server. Severe weather push (from version 1.10.0): If the app is idle at the pitch, our server sends official warnings for your warning area to your device via Apple or Google; as long as this is registered, the app does not generate its own notification for official warnings (for data, delivery and deletion, see section 5, “Severe weather push”). You switch them off under Profile → Notices & features → Notifications (“Severe weather at the pitch” or “Switch off weather data completely”).

Year in review (from version 1.12.0, currently not active): From 15 December, the app creates on your device a review of your trips of the year (a reel with photos, route and figures) and can point you to it with a local notification. The review and notification are created only on your device; nothing is sent to a server for this. The reel is only shared if you pass it on yourself via your device’s share menu. The map in the reel and the region badges (e.g. German federal states) use boundary data contained in the app; your position does not leave the device for this.

9. In-app purchases

Up to and including version 1.11.0, GlowCamp does not offer any in-app purchases.

GlowCamp Pro (from version 1.12.0, currently not active): Pro is a voluntary subscription with additional features relating to reels (e.g. a reel while the trip is still under way, longer reels, reels without end credits, further variants) and more photos when sharing (section 6b). Everything that has been free until now remains free. You take out the subscription via Apple’s App Store or Google Play (€2.99 per month or €24.99 per year); Apple or Google process the payment and, for this purpose, receive your payment details in accordance with their own terms. We do not see your payment details.

So that the app knows whether you have Pro, we use the billing service provider RevenueCat, Inc. (USA) as a processor. RevenueCat receives the purchase receipt from Apple or Google (product, purchase and expiry date, subscription status), a random, pseudonymous app identifier generated by the RevenueCat SDK on first launch, as well as technical information (app version, operating system, store country) and the IP address at the time of the request. RevenueCat does not receive any trips, any positions, any photos or any journal entries. We do not link the identifier to a GlowCamp account (section 18a) and do not store it on our server; it only reaches our server in the cases described below (Pro discount on the travel book, thank-you year for beta testers). RevenueCat processes the data in the USA; the transfer takes place on the basis of the EU standard contractual clauses or the EU-US Data Privacy Framework, insofar as RevenueCat is certified under it. The legal basis is the performance of the subscription contract (Art. 6(1)(b) GDPR). Apple, Google and RevenueCat retain the purchase data for as long as is necessary for the subscription and statutory retention obligations; you cancel the subscription in your device’s subscription settings.

Even without a purchase: The RevenueCat SDK has been included since the first versions of the app (September 2026) and contacts RevenueCat every time the app starts, even if you never buy anything and never open the Pro screen. Only the pseudonymous app identifier, the technical information (app version, operating system, store country) and the IP address go to RevenueCat; without a purchase there is no purchase receipt. In this way the app finds out at startup whether a Pro subscription exists on this device, and purchases can be restored. The legal basis is our legitimate interest in reliably recognising purchases (Art. 6(1)(f) GDPR). The identifier is random and is generated anew when the app is deleted.

Pro discount on the travel book (from version 1.13.0): With GlowCamp Pro you permanently receive a discount on the printed travel book (section 18e). So that we can grant it, the app sends your pseudonymous RevenueCat app identifier (see above) to our server glowcamp.de when retrieving the book price and when ordering or reordering a travel book. Our server uses it to query RevenueCat once as to whether GlowCamp Pro is currently active for this identifier, and only receives this information back. The query does not create a new customer record at RevenueCat; RevenueCat only learns that our server queried the identifier, not what for. Our server does not store the identifier and does not log it (not even in error messages), does not cache it and does not pass it on to Stripe or Peecho. Only the discount granted is stored in the travel book order (percentage and “Pro”), so that a payment page that is opened again shows the same price. If RevenueCat cannot be reached, there is no Pro discount; other discounts remain. The legal basis is determining the price at your request or the performance of the purchase contract (Art. 6(1)(b) GDPR).

Thank-you year for beta testers on Android: Instead of a code, you can send us an e-mail to support@glowcamp.de from the app’s thank-you card. It contains your pseudonymous RevenueCat app identifier (see above) and the request for activation; you see the text before sending, and no other device data is included. We only use the identifier to activate one year of GlowCamp Pro for it in RevenueCat (without renewal, free of charge), and do not link it to trips or a GlowCamp account. We treat the e-mail itself like any other message to us (section 13). The legal basis is your request (Art. 6(1)(b) GDPR).

The printed travel book (from version 1.12.0, in test mode in the beta, section 18e) is not an in-app purchase: it is a physical product that you buy from us on a Stripe payment page in your browser (Stripe Checkout). No payment is made via Apple or Google, and the app itself sees neither your payment details nor your delivery address.

10. No advertising, no tracking

The GlowCamp app does not show any advertising and does not include any third-party analytics or tracking SDKs. The RevenueCat SDK (section 9) serves only for billing GlowCamp Pro, not for analysing your behaviour or for advertising. There is no profiling and no disclosure of your data for advertising purposes. This also applies to shared trips and push identifiers: we do not evaluate them for advertising, do not create profiles from them and do not sell them; we only use push identifiers for the severe weather push, and from version 1.12.0 also for notifications from friends and from the Campfire (sections 18b and 18d) and for notifications about an ordered travel book (section 18e). For this website, section 14 applies (audience measurement only with your consent); the link page of shared trips contains no audience measurement.

11. Storage period

All locally stored data (trips, stages, photos, journal, vehicle file, settings, retrieved weather values) remains on your device until you delete it in the app or uninstall the app. Uninstalling completely removes all data on the device; a backup copy you have enabled in iCloud or Google Drive is not affected by this — delete it before uninstalling via “Delete all data” → “Device + cloud backup” or afterwards in your Apple or Google account (see section 4).

Occupancy reports stored on our server (section 5) are deleted after 2 days, and the hash derived from them after just 24 hours. Only an aggregated summary per site for the last 6 hours is published; it is continuously replaced by more recent data. The IP address is held in working memory for at most 1 hour.

We delete registrations for the severe weather push (section 5, “Severe weather push”) as soon as the app deregisters them (e.g. when you are more than 10 km from the pitch), but at the latest 24 hours after the last registration or renewal; the list of warnings already sent for them is deleted together with the registration, at the latest 12 hours after the end of the respective warning. The IP address is held in working memory for at most 1 hour.

Trips shared by link (from version 1.10.0, section 6b):

• Links expire 30 days after the end of the trip (without an end of trip, 30 days after the last activity); after that the page can no longer be reached and we delete the content (places, route, photos, journal excerpts, live position) during the next 15-minute run. Of the live position, we store the latest one in each case and the route since the last visible place; these are overwritten or deleted together with the link.
• We delete a share to which nothing has yet been uploaded after 24 hours.
• Content that is still waiting to be released remains unpublished on our server until then and is deleted like all shared content.
• Deleted data may still be contained in our server backups for some time and is overwritten after 30 days at the latest.
• The list of pending deletion requests (section 6b) is stored only on your device (and in your cloud backup) and is cleared as soon as the server has confirmed the deletion.
• We count per day how many links were created and trip pages were opened; these counters have no reference to people, devices or individual links.

Account and community (from version 1.12.0, sections 18a–18d):

• We delete your account and everything linked to it immediately when you delete it. We delete an account that you have not signed in to for 24 months; if we have an e-mail address, we warn you beforehand (after 23 months) and delete it no earlier than 25 days after the warning.
• Sign-in codes sent by e-mail are valid for 15 minutes; we store the number of attempts and the related IP address for at most 7 days.
• Trips shared with friends expire like links 30 days after the end of the trip (without an end of trip, 30 days after the last upload) and are then deleted. Publicly shared tours remain until you withdraw them, delete the trip in the app or your account is deleted (including after 24 months without signing in, see above).
• We delete closed reports 180 days after they have been dealt with; voluntary information on the reason for deleting an account (without reference to the account) after 12 months.
• We delete the delivery list for notifications from friends and from the Campfire after 14 days; with “Live for friends” we only store the latest position in each case.
• Your shared information about sites, petrol stations and sights remains stored until you withdraw it or delete your account.

Details can be found in sections 18a–18d.

Travel book (from version 1.12.0, in test mode in the beta: nothing is printed and nothing is charged; section 18e):

• We delete the uploaded photos and the book document (texts, places, map data) as soon as the print file has been created, at the latest 7 days after the order was created.
• We delete the preview images at the latest 7 days after the order was created, and immediately after dispatch.
• Without payment, we delete all content, including the print file, 7 days after creation; an empty entry (only the status, without a title) remains for a further 7 days.
• After payment, we keep the print file until the book has been dispatched, and thereafter for a further 60 days for complaints and a possible reprint. Upon dispatch, the download link for Peecho becomes invalid; during these 60 days only the operator can retrieve the print file in the admin area. After that we delete it. The status, title, shipment tracking and the order and payment identifiers from Peecho and Stripe remain until the end of this period.
• We delete the push identifier for notifications about the book after the last notification, at the latest together with the order. We delete identifiers of Stripe events that have already been processed after 30 days.
• We store the discount granted (from version 1.13.0, only the percentage and type: first book or Pro) with the order and delete it together with the order. We do not store the RevenueCat app identifier used for the Pro discount.
• If you delete an order that has not yet been paid in the app, or if it fails or is refunded, we immediately delete all content except the empty entry. If you delete a paid order in the app, we immediately delete the photos, preview images, book document and push identifier; the print file and the order identifiers remain so that your paid book can be printed and delivered, and are deleted as described above.
• We do not store your name, delivery address or e-mail address on our server. Stripe and we (copy by e-mail) retain the invoice for as long as tax law requires (currently generally 8 years, for some documents 10 years). How long Stripe and Peecho store further data is governed by their terms (section 18e).
• If you order the same book again before dispatch, we copy the print file into a new order with its own payment; it is valid at most until the first order expires and is then deleted like that order. After dispatch this is no longer possible.
• For troubleshooting, the server writes a short line without an IP address (order identifier, result, duration) each time Peecho retrieves the print file. We delete these lines after 14 days.
• Order data may be contained in our server’s daily backups; these backups are overwritten after 7 days.

Route calculation via glowcamp.de (planned from version 1.11.0, section 18f): We store nothing; the IP address is held in working memory for only a few minutes.

Periods at a glance: Links to shared trips expire 30 days after the end of the trip (without an end of trip, 30 days after the last activity) and are then deleted, as are trips shared with friends; public tours remain until they are withdrawn or the trip or the account is deleted; of the live position we only keep the latest state in each case, which is overwritten or deleted together with the link; we delete empty shares after 24 hours. We delete occupancy reports after 2 days, and the associated hash after 24 hours. We delete registrations for the severe weather push at the latest 24 hours after the last registration or renewal. For these services we hold IP addresses in working memory for at most 1 hour. Server backups are overwritten after 30 days at the latest. Statutory retention obligations remain unaffected; in such cases we restrict processing of the data instead of deleting it, and delete it once the obligation has expired.

12. Your rights

Under the GDPR you have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). As long as you do not share a trip and do not use the severe weather push, GlowCamp does not store any trip data on our servers; your trip data is then kept exclusively by you on your device — you exercise access, rectification and erasure for it directly in the app or by uninstalling it. You can view and delete your shared trips in the app (section 6b), and with “Stop all sharing” in your profile you can also delete them all at once. If you have a GlowCamp account (from version 1.12.0, section 18a), you delete it together with all shared content in the app (Profile → Account → “Delete account”) or on the Delete account page; you can view and change your profile name, profile picture, friends and signed-in devices in the app. For all other matters, including access to the data stored for your account, you can reach us at the e-mail address given above.

Regarding links without an account: we do not store any information about you for these (no name, no e-mail address, no device identifier, no IP address). You can only change and delete such a link with the secret key in your app (section 6b). Without it, we generally cannot attribute a link to you; access, rectification or erasure are then only possible under Art. 11 GDPR if you provide us with information that enables us to attribute the link. Every link expires no later than 30 days after the end of the trip.

Regarding occupancy reports: reports that have been sent contain no information that would allow us to attribute them to you (the pseudonymous identifier is deleted after 24 hours, the report after 2 days). We therefore generally can no longer trace an individual report back to you; access, rectification or erasure in respect of an individual report are then not possible under Art. 11 GDPR unless you provide us with additional information that would allow us to identify you. You can prevent further reports by withdrawing your consent in the app (see section 5).

You also have the right to lodge a complaint with a data protection supervisory authority, e.g. with the authority responsible for Rhineland-Palatinate, the Landesbeauftragte für den Datenschutz und die Informationsfreiheit (State Commissioner for Data Protection and Freedom of Information).

13. Visiting this website

When you access the pages of glowcamp.de, the web server, for technical reasons, writes access data to a log file: IP address, date and time, page accessed, status code, amount of data transferred, browser identifier (user agent) and, where applicable, the page you came from (referrer). The purpose is the secure and stable operation of the website and the prevention of misuse. The legal basis is our legitimate interest (Art. 6(1)(f) GDPR). The log files are kept for 10 days and then deleted.

Excluded from this logging are requests from the app and the feedback form (map tiles, campsite, petrol station and sights data, occupancy, feature query, feedback, severe weather push, from version 1.10.0 also sharing and retrieving trips via link, from version 1.11.0 (planned) also route calculation, from version 1.12.0 the travel book including the return page after payment, as well as the account and the community features (sign-in, account, profile, account deletion, friends, campfire, public trips, reports, information about places; see sections 5, 6b, 7, 18a–18f). For sharing and the severe weather push, see section 5 (IP address briefly, to protect against misuse).

Link page for shared trips (from version 1.10.0): If you open a link that someone has sent you, your browser loads the page and the currently released trip data from glowcamp.de and the map tiles from tiles.glowcamp.de (also our server). In doing so, for technical reasons, it transmits your IP address, your browser identifier (user agent) and your preferred language, and to glowcamp.de also the secret link; only the tile identifier, not the link, is sent to tiles.glowcamp.de. We do not log these requests; the IP address is held only briefly in memory in order to detect too many requests. The page sets no cookies, stores nothing in your browser, loads nothing from third-party servers and contains no Google Analytics and no consent banner. The legal basis is our legitimate interest in delivering the page (Art. 6(1)(f) GDPR).

Hosting: the website runs on a server of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, in the Falkenstein data centre (Germany). Hetzner processes the data on our behalf.

Without your consent, this website sets no cookies, uses no analytics or tracking services and loads no fonts, scripts or images from third-party servers (for audience measurement, see section 14). If you send us an e-mail at support@glowcamp.de, we process your sender address and your message in order to reply to you (Art. 6(1)(b) or (f) GDPR).

14. Audience measurement with Google Analytics (only with consent)

On your first visit, a banner asks you whether we may use Google Analytics 4, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google). The purpose is audience measurement: we want to understand how the website is found and used in order to improve it. Without your consent, Google Analytics is not loaded: no connection is made to Google servers and no cookies are set by Google. "Decline" and "Accept" are given equal prominence.

If you consent, Google Analytics sets cookies (_ga and _ga_<identifier>, stored for up to 2 years) and collects usage data, for example pages accessed, time, length of visit, referring page (referrer), browser and operating system (with versions), device type, device model and brand, screen size, language and your approximate location (country, region and city, derived from the IP address, not your precise location). For technical reasons the IP address is transmitted to Google when the request is made; according to Google, Google Analytics 4 does not store individual IP addresses. The advertising features (Google Signals, personalised advertising) are switched off. Event data is kept for 2 months. User data linked to cookies is kept for 14 months; the period starts again on a new visit. The data is then deleted.

In this process, data may be transferred to Google LLC in the USA. Google LLC is certified under the EU-US Data Privacy Framework; standard contractual clauses also apply. We have a data processing agreement with Google (Art. 28 GDPR).

The legal basis is your consent (Art. 6(1)(a) GDPR and § 25(1) TDDDG). We store your choice in your browser (local storage, not a cookie) for 12 months; after that we ask again. Withdrawal: at any time via "Statistics settings" in the footer of every page. If you choose "Decline", the Google cookies are deleted and nothing more is measured. More on this in Google's privacy policy. The app is not affected by this measurement.

15. Beta test (TestFlight and Google Play)

The beta runs via Apple TestFlight (iOS) and a closed test on Google Play (Android; access is via a Google group). For this you need an Apple ID or a Google account. Apple and Google process your account data as independent controllers; their privacy policies apply. If you submit feedback in TestFlight, we receive it via Apple.

As the operator of the test group, we see the e-mail addresses of the group members. We use them exclusively for running the beta (Art. 6(1)(f) GDPR) and delete them after the beta ends.

16. Links to other providers

On our website we link to services of Apple (App Store) and Google (Google Groups, Google Play). The App Store badge is hosted on our own server. No content from these providers is embedded; data is only transmitted when you click a link. From then on, the privacy policy of the respective provider applies. If you open our website in Safari on an iPhone or iPad, Safari may display a notice about the app in the App Store at the top (Smart App Banner). Safari retrieves the information for this from Apple itself, not from our website.

On our page with guides and tips (glowcamp.de/anleitungen.html or glowcamp.de/en/guides.html, from version 1.12.0 also linked from the app) we refer to our Facebook group (https://www.facebook.com/groups/campinginsider) and to GlowCamp on Instagram (https://www.instagram.com/glowcampapp/). These are plain links: we do not embed any content, buttons ("Like") or scripts from Meta. Only when you click one of these links is data transmitted to Meta Platforms Ireland Ltd.; from then on, its privacy policy applies.

17. Changes to this privacy policy

We update this policy as soon as data processing in the app changes — in particular before introducing paid offerings such as the printed travel book (section 18e). We mark features that are still in preparation in section 18 as “in preparation”; before they are released, we review the description and publish it with a new “last updated” date. The current version is always available at this address.

18. Account, community and other features from versions 1.11.0, 1.12.0 and 1.13.0

The following features are available from version 1.11.0, 1.12.0 or 1.13.0; each section states the version from which it applies. In older versions of the app we do not process any data for them. The features requiring an account (sections 18a–18d) are enabled on our server with version 1.12.0. Sections marked “in preparation” describe features that we will only enable later; until then we do not process any data for them.

These are: a voluntary account (section 18a), sharing with friends and publicly (18b), sharing information about campsites, petrol stations and sights (18c), the “Campfire” with a diary for friends (18d), a printed travel book without an account (18e), route calculation via our own server (18f), “Search in my photos”, which runs only on your device (18g), weather via our own server instead of Open-Meteo (18h), an anonymous trip counter only with your consent (18i), photo suggestions on Android (18j), in preparation, fellow travellers contributing to a trip (18k), and from version 1.13.0 the recommendation link for places (18l).

18a. GlowCamp account (voluntary, from version 1.12.0)

The account is voluntary. You only need it to share trips with friends or publicly, for the Campfire and to share information about places, petrol stations and sights; sharing via link also works without an account (section 6b). All other features, including cloud backup (section 4), work without an account. You sign in with Apple, with Google or with a code sent by e-mail; there is no password. When creating the account, you confirm that you are at least 16 years old.

We store: a random account identifier; the sign-in method and, as an irreversible hash value, the Apple or Google identifier or your e-mail address (so that we recognise you the next time you sign in); (where we have one; with Apple without e-mail sharing there is none) your e-mail address additionally in encrypted form, so that we can warn you before an inactive account is deleted; a profile name; the time of your age confirmation; your language (for our e-mails); the creation date and the time of your last sign-in; a note if the account is blocked; for sign-in with Apple, an encrypted token with which we can revoke the link with Apple upon deletion. For each signed-in device we store a session: a device identifier that the app generates randomly for this purpose (not a hardware or advertising identifier), a device name, the times of sign-in and last use, and a hash value of the sign-in key. You can see the list of your signed-in devices in the app and sign out individual devices there.

Profile name: the app suggests a random name (e.g. “NightOwl_85”), which you can change; your real name is not required. Each profile name exists only once. A name that becomes free (after renaming or deleting the account) remains blocked for 30 days and only then becomes available to others again. Your profile name is visible to everyone who views your shared trips, and to everyone to whom you send your invitation link; do not choose your real name if you do not want to be recognised. We never display your e-mail address.

Profile picture (optional): without a picture of your own, the app shows your initials; nothing is uploaded for this. If you upload a photo, the app crops it to a square, reduces it to 256 pixels and removes metadata such as the location where it was taken and camera data; our server checks the image and removes metadata once again. We store it with your account. Only your confirmed friends can see it (section 18d). You can replace or remove it at any time; it is deleted together with the account. Do not upload a picture in which other people can be recognised without their consent.

The data is stored on our server at Hetzner in Germany (section 13). On your device, the sign-in data is kept only in the operating system's protected keystore, not in the app database and not in the cloud backup.

For moderation and support, the operator sees the account data in a protected admin area (profile name, sign-in method, creation date and last sign-in, status, shared content and its quantity); he has your e-mail address displayed there only in individual cases where this is necessary.

Changing devices: after restoring from a backup or on a new device, you sign in again. Your shared trips, friends and your profile name are tied to the account and will be back afterwards. You can sign out the old device in the device list.

Signing out: when you sign out, your shared trips remain online until you withdraw them or delete your account; we only send new changes after you sign in again. If you want to remove something, withdraw the sharing beforehand or delete the account. When you sign out, we delete the push identifier of this device.

Occupancy reports (section 5) remain separate from the account: we never link reports to your account.

Deleting your account: in the app under Profile → Account → “Delete account” (after signing in again if your last sign-in was some time ago) or on the Delete account page. There you enter the e-mail address with which you signed in. If you signed in with Apple, we do not have an address: in that case you delete the account in the app (Profile → Account) or via the form on that page. If the address belongs to an account, we send a code to exactly that address; after you enter and confirm it, the account is deleted automatically and immediately. We only receive a notification of this, without your profile name and without your e-mail address. If, exceptionally, no address is available, you can request deletion via the form there or write to us at support@glowcamp.de; we will do this within 30 days. When deleting, you can voluntarily tick a reason and write what you would have wished for. We store this without reference to your account (only with the day and language) in order to improve the app, and delete it after 12 months. With this we immediately delete your account, all sessions and push identifiers, your friendships and all trips and photos you have shared, including your links, your shared information about places, petrol stations and sights (section 18c), your profile picture, your hearts and comments in the Campfire, and the hearts and comments of others under your entries (section 18d). For sign-in with Apple, we also revoke the link with Apple. The data on your device and your cloud backup are retained.

Inactive accounts: if you have not signed in for 24 months, we delete your account as described above. If we have your e-mail address, we write to you beforehand (after 23 months) and delete it no earlier than 25 days later; if you sign in during that time, the account remains.

The legal basis is the performance of the terms of use contract for the account (Art. 6(1)(b) GDPR). The minimum age for an account is 16 years. Our Terms of Use apply.

18b. Sharing with friends and publicly (from version 1.12.0, only with an account)

In addition to the private link (section 6b), from version 1.12.0 there are two further levels, both only with a GlowCamp account: Friends (your confirmed friends see the trip in the app and receive a notification if they wish) and Public (tours that everyone can see in the app under “Other people's trips”, not on our website). The same principles apply to link, friends and public: for each trip, place and photo, you choose what is shared; photos without metadata, at most 5 per day of travel; you can withdraw everything.

• What can be shared publicly: only known public campsites, motorhome pitches, car parks and sights from OpenStreetMap, with their name from OpenStreetMap and the day of arrival without the time, as well as the simplified route between them, without times. The journey from home to the first place and from the last place back home is always omitted. Wild camping spots, your own places, private addresses and your home location are never shared publicly; our server only allows such places for “public”. If you leave out a place, the route ends there so that the stop cannot be identified.
• “Live” for friends and public: always switched off until you expressly switch it on for a trip and confirm a warning. A place then only appears after a stay of about 30 minutes; publicly, your position while driving is never shown. While “live” is running, the app shows this to you visibly, and you can switch it off with one tap.
• “Live for friends”: if you switch it on for a trip (default: off, with a warning), your confirmed friends see your position while driving, as with the link (section 18d). Named stops (e.g. a campsite) then appear after about 15 minutes, other places after about 30 minutes.
• Who sees it: public trips are visible to everyone, but only in the app (not on our website), together with your profile name. They are delivered as tiles for broad regions; we cannot track who views which trip (the tiles also contain the month, places and photo references of the trips; there is no individual retrieval per trip; the app only loads photos when you open a trip, without an access log and without attribution to you). Trips at the “Friends” level are seen only by your confirmed friends, trips at the “Link” level only by people with the link. Anything that was once visible may have been copied or saved as a screenshot by someone; we have no control over this.

Friends: you invite friends with a secret invitation link, e.g. via WhatsApp. It is valid for 7 days and can be withdrawn at any time; no one can find you via your profile name. Whoever opens the link in the app sends you a friend request; only when you accept it are you friends (mutually). Friends see your trips at the “Friends” level with the delay chosen for them and the diary entries released for them in the Campfire (section 18d). For this purpose we store on our server who has sent whom a request and who is friends with whom, as well as your “notifications on/off” setting for each friend. You can remove friends at any time.

Notifications to friends (push): if you receive a friend request or there is something new at the Campfire (a new diary entry by a friend, the arrival of a friend who shares “Live for friends” and to which you have agreed, a heart or a comment under your entry; details in section 18d), our server sends a notification to your device, provided you have allowed notifications in GlowCamp and in the operating system. For this we store, for each device, a push identifier assigned by Apple or Google for GlowCamp. We send the notification directly to the delivery service of Apple (Apple Push Notification Service, iOS) or Google (Firebase Cloud Messaging, Android), without any other service provider in between. Apple or Google receive the push identifier and the text of the notification (e.g. “NightOwl_85 has arrived: Camping Landidyll” with the name of the trip, or “NightOwl_85 today: Swimming in the sea”). The text never states a time and contains no photos. With the setting “Notifications without content”, each of these notifications reads only “Something new at the Campfire”, without names, places or text. Notifications about places and diary entries are sent by the server with its 15-minute runs, hearts and comments shortly afterwards; at night (10 pm–7 am in your time zone) it holds them back until the morning. You can switch them off per friend, per trip and altogether in the app. In this process, data may go to Apple Inc. or Google LLC in the USA. We delete the push identifier of a device when you sign it out or delete your account, when you switch off notifications from friends altogether, or when Apple or Google report it as invalid.

Reporting and moderation: any shared content can be reported in the app; you can also reach us at support@glowcamp.de. We use an e-mail address voluntarily provided in this context only to respond to that report. We review reports manually and remove unlawful content or content that violates our Terms of Use; in the event of repeated violations we block the account. Anyone who has published content is informed by e-mail why it was removed, and can object by replying to that e-mail; we then review it again. We delete closed reports 180 days after they have been processed. In an emergency we can immediately suspend all publications to friends and public publications; links are not affected by this.

How long: we delete trips shared with friends 30 days after the end of the trip (if there is no trip end, 30 days after the last upload), together with photos, diary entries and live position. Public tours remain visible without a fixed period until you withdraw them, delete the trip in the app (the app then withdraws the sharing, at the latest at the next internet connection) or your account is deleted, including as an inactive account after 24 months without signing in.

The legal basis for sharing (link, friends, public, including the live position for the link and for “Live for friends”) is your consent (Art. 6(1)(a) GDPR), which you give for each trip and level and can withdraw at any time by withdrawing the sharing or switching it off; withdrawal does not affect the lawfulness of processing carried out up to that point. For friendships and notifications to friends, the legal basis is the performance of the terms of use contract for the account (Art. 6(1)(b) GDPR); you only receive notifications if you have allowed them in the operating system. For protection against misuse and moderation we rely on our legitimate interest in a secure service (Art. 6(1)(f) GDPR), and for legal obligations to process reports on Art. 6(1)(c) GDPR.

18c. Sharing information on campsites, petrol stations and sights (voluntary, from version 1.12.0, with an account)

When saving your own rating of a campsite, a petrol station or a sight, instead of “Save for me” (for sights the rating is automatically saved only on your device) you can also choose “Save & share with community”. Only then do we send to our server (glowcamp.de): the OpenStreetMap ID and the coordinates of the place (not your position), the features you have ticked (e.g. “Electricity”, “Suitable for car and caravan”, for sights “Suitable for” and “Practical info”; no free text), and, where applicable, stars (1–5) and, for a site, a price level (cheap/OK/expensive). We never share your private note or details from “My people” (e.g. years of birth). Stars and price level are only sent if your app has determined locally from your own recording that you were there (a stop or overnight stay at the site, at the petrol station a stop of a few minutes or a refuelling stop, at a sight a stay of at least 10 minutes within a radius of about 200 m, including on foot; places added afterwards never count). For this, only the flag “confirmed on site” is transmitted — never your position, your route or a date. The information is stored pseudonymously together with your account ID, so that there is only one entry per account and place and you can change or withdraw it; we also store when it was created and last changed.

What others see: only totals across all campers, without names or account, e.g. “Motorhome-friendly · 3 campers”. Stars only appear once there are 4 on-site-confirmed ratings from different accounts, the price level only once there are 10. We deliver the totals as static files for areas of 1 × 1 degree; when they are retrieved, only this area ID and the IP address (for technical reasons) are transmitted, without an access log. There is no query for an individual place, so we do not find out which site you are looking at. The app only loads these files when you open a site or a petrol station or a sight or plan refuelling stops. We only show stars in the detail view, not on the map and not in lists. Reading also works without an account.

Withdrawing and deleting: With “Stop sharing” we immediately delete your entry for this place; the totals are recalculated within a few minutes. If you delete your account, we delete all your entries (they disappear from all totals within one hour at the latest). Your own rating remains on your device. On the device, the app only remembers which places you have shared (for “Update community” and badges).

Reporting: You can report the totals for a place — even without an account — (reason: wrong, fake, offensive, other). We then store the place, the reason, the time and, if you are signed in, your account ID; we delete closed reports, like other reports, 180 days after they have been dealt with (section 18b). We can hide the totals for a place and block accounts in the event of misuse; entries from blocked accounts do not count.

Photos for this information (from version 1.12.0): For a shared place, with an account you can share up to 3 photos that you choose yourself (from your photos of this place or from your photo library). The app re-encodes each photo before sending it (long edge at most 1280 pixels); this removes all metadata, including the location (GPS) and time the photo was taken. Our server re-encodes the image once more. Only the image, the OpenStreetMap ID and the coordinates of the place are sent; the photo is stored together with your account ID, the place and the time. Please do not photograph people or number plates. Others only see a photo after we have checked and approved it; until then, only the operator can see it in the protected admin area. Approved photos appear in the place information without your name; their IDs are listed in the area files, and the app only loads the image when the place information is viewed (without an access log). If we reject a photo or remove it following a report, we delete the image immediately and send you the reason by e-mail; the app then shows “Rejected” with the reason (we delete this entry, which has no image, after 30 days). We delete photos that we do not check within 14 days. You can remove any photo at any time; when your account is deleted, we delete all your photos. You can report photos — even without an account. The legal basis is your consent (Art. 6(1)(a) GDPR), which you give by selecting a photo and can withdraw by removing it.

The legal basis for sharing is your consent (Art. 6(1)(a) GDPR), which you give by tapping “Save & share with community” and can withdraw at any time with “Stop sharing”; for protection against misuse (rate limiting, moderation), our legitimate interest in a secure service (Art. 6(1)(f) GDPR). We only use IP addresses for this in memory for rate limiting (for at most 1 hour).

18d. Campfire: diary with friends, hearts, comments, Live for friends, profile picture (voluntary, from version 1.12.0, with an account)

The Campfire is a menu item in the app that only appears if you have at least one confirmed friend. It shows only diary entries that your friends have individually selected for sharing (“Yes, highlight” or “Yes, whole entry”, section 18b), and only from trips that they share with friends. An entry appears with the same delay as the places and photos of that day, at the earliest together with the first visible place of the day. The following are shown: profile name and profile picture, trip name, date, highlight, for a whole entry also text and mood, at most 5 photos from that day, the place with its country flag and the weather there. Arrival, departure or end of the trip do not appear in the Campfire. No new data is created for this: the Campfire shows what you already share with friends. So that the flag is correct, the app sends the country (two-letter country code) with every shared place.

Hearts and comments: Under an entry, the author and their confirmed friends can give a heart and write short comments (plain text, at most 500 characters). For this we store the entry, your account ID, the time and, for a comment, the text. Hearts (as a number) and comments with profile name are only visible to the author of the entry and their friends; your comment and your profile name are therefore also visible to friends of the author with whom you yourself are not friends (you only see their profile picture for your own friends). You can delete your comments and hearts at any time; the author of an entry can delete any comment under it. Comments and hearts are deleted when the author stops sharing the entry or withdraws the trip, when one of you ends the friendship (then everything between the two of you), and with the account. Content can be reported in the app (section 18b, “Reporting and moderation”); for a reported comment, we see its text in order to review it.

Live for friends: If you switch it on for a trip (see section 18b), the app sends, while you are driving and as with the link, about every 5 minutes your current position with the time and the route since the last visible place to our server, taken from the recording that is running anyway (no additional location tracking). Only the most recent position is stored; your confirmed friends see it in the app for as long as the trip is ongoing. We no longer show positions older than 12 hours, and after the end of the trip there is no live position. You can switch it off at any time with one tap; the position is then deleted.

Notifications and your settings: As the recipient, you decide whether you receive notifications: per friend (on/off), per trip (“Mute trip”: no more notifications, the trip remains in the Campfire and on the map; “new diary entry” and “arrival” can be chosen separately) and for your account (“Hearts and comments” under your entries, “Notifications without content”). Arrival notifications are only available with “Live for friends” and only if you agreed when you first opened the trip. At most one notification per entry, place, heart or comment. We store these settings on our server because it sends the notifications. Together with the push token, we store your time zone (e.g. “Europe/Berlin”), so that nothing is delivered at night (10 pm–7 am). To send them, the server remembers for each notification the recipient, the occasion (e.g. ID of the entry) and the time; we delete this list after 14 days.

Profile picture: see section 18a. In the Campfire and in the friends list, only your confirmed friends can see it.

Please note: The diary, photos and “Live for friends” show your friends that you are travelling and where you have been or are currently driving. Anything that was visible at some point may have been copied or saved by someone as a screenshot.

The legal basis for sharing entries, comments, hearts, profile picture and “Live for friends” is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time by deleting, withdrawing or switching off; for displaying the Campfire, the notifications and the stored settings, the performance of the user agreement for the account (Art. 6(1)(b) GDPR).

18e. Having a travel book printed (voluntary, from version 1.12.0, without an account)

From a completed trip you can order a printed photo book (hardcover). We sell the book ourselves: the controller and your contractual partner is EDV-Technik Dennis Weimer (section 1). Payment is made via Stripe, and the book is printed and shipped by our printing company Peecho. You do not need an account for this. Our General Terms and Conditions apply.

When data is transmitted: At first you put the book together only on your device. When you open it, the app only asks our server for the price; for this it sends the number of pages and the delivery country (from your device's region), for technical reasons together with your IP address. From version 1.13.0 it also sends whether this is your first travel book, and your pseudonymous app ID from RevenueCat for the Pro discount (see “Discounts” below). Everything else is only transmitted when you expressly tap “Print book” and choose “Upload and continue” in the explanation dialogue that follows. With “Cancel” nothing is sent.

What goes to our server (glowcamp.de):

• the photos you have selected for the book, as recalculated JPEG files in print resolution (long side at most 4000 pixels). In doing so, the app removes all metadata such as location (GPS), date and camera; our server recalculates the photos once more on receipt and additionally removes metadata in the process;
• the book document: title and period of the trip, a heading for each day, the date and the timeline with names of the places (e.g. campsites, sights, overnight stays) and times, the diary texts you keep in the book, captions, a sentence from the diary for the back cover, the trip's figures (kilometres, days, countries, number of places) and the page layout with book language and chosen style, plus the image crop for each photo (chosen by the app on your device or moved by you). From version 1.12.0 also: figures per day and overnight site (kilometres, departure, arrival, driving time, nights), the weather of the day only if you have agreed to the weather query, the location of the overnight site rounded to about 1 km for the dot in the country outline, in the “Roadbook” style the simplified daily route without the area around your home (15 km), as well as the distance of the site furthest from home together with its name – your home itself (name or location) is never included;
• the data for the map in the book: the simplified route (at most 1500 points), the overnight places, the countries visited and the map section. As long as the switch “Leave out outward and return journey” is on (default setting), the journey from home to the first place and from the last place back home is omitted;
• if you allow notifications, a push token for your device with platform and app language, only for two notifications about this order (“Your travel book is ready to order” and “Your travel book is on its way”, with the trip title). They are delivered via Apple Push Notification Service or Firebase Cloud Messaging (as with the severe weather push, section 5).

The sole purpose is to generate the preview and the print file (PDF) of your book from this, to have it printed and to handle complaints. We do not analyse the content and do not use it for anything else, in particular not for advertising. Access to your order is via a random order ID and a secret key that only your app knows; on the server, the key is only held as a check value (hash). We do not store any device or account ID. We do not keep an access log for this area. We only hold the IP address in memory: to limit requests, for at most about one hour and, so that nobody creates more than two orders at the same time, together with the order ID until the order is ready for payment (at most 7 days). For troubleshooting, the server writes a short line without IP address each time Peecho retrieves the print file (order ID, result, duration), which we delete after 14 days. Order data may be contained in the daily backups of our server, which are overwritten after 7 days.

Payment via Stripe: Once the print file is ready, the app opens a Stripe payment page in your browser (Stripe Checkout). The payment service provider is Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. On this page you enter your payment details, your e-mail address, your name and your delivery address directly with Stripe; no telephone number is requested. From us, Stripe receives the product name with the title of your book, the price (from version 1.13.0, where applicable, with a note on the discount granted), the book language and the order ID. Stripe creates the invoice and sends it to you by e-mail; we receive a copy (e-mail with links to the invoice at Stripe). According to its own statements, Stripe processes the payment data as an independent controller, among other things to process the payment, to prevent fraud and to fulfil legal obligations, and in doing so also processes information about your device and browser. For other services, such as creating the invoice, Stripe acts on our behalf. According to Stripe, data may also be transferred to Stripe, Inc. in the USA; according to its own statements, Stripe bases this on the EU-US Data Privacy Framework or the European Commission's standard contractual clauses. If, in the Stripe checkout, you choose a payment method from another provider (e.g. PayPal or Klarna), that provider also receives the data it needs for this under its own terms. For details, see the Stripe privacy policy. Our server does not store any payment details, name, e-mail address or delivery address; it only remembers the IDs of the payment session and of the payment at Stripe. After payment, Stripe redirects you to a page on glowcamp.de, which takes you back to the app; there is no access log for this either.

Printing and shipping by Peecho: After your payment, we order the printing from Peecho B.V., Herengracht 340, Amsterdam, Netherlands (part of the Prodigi group). For this, Peecho receives the print file, which Peecho collects from our server via a link with a secret key (valid from payment until shipping, at most until the end of the retention period, see section 11), as well as your name, your delivery address and your e-mail address. For this purpose, our server reads these details from your payment session at Stripe and passes them on to Peecho only in memory; they are not stored on our server. Peecho prints and ships the book and sends us the shipping status with tracking. Peecho sends the shipping confirmation with the tracking number directly to your e-mail address. If you have questions about printing or delivery, Peecho's customer service may also contact you directly. Peecho may use printing partners and other service providers for this; according to Peecho's privacy policy, data may also be processed outside the EU in the process (the USA and New Zealand are named). How long Peecho keeps print files and order data is governed by Peecho's privacy policy. If you order the same book again before it is shipped, we copy the print file into a new order with its own payment (time limits in section 11). We ourselves keep the print file for a further 60 days after shipping for complaints and a possible reprint; during this time it can only be retrieved by the operator (section 11). For details, see the Peecho privacy policy.

Discounts (from version 1.13.0): The price is calculated by our server alone; the app only sends information for this, never amounts. For your first travel book there is a first-book discount (15%). Whether it is your first book is remembered locally by the app on your device (this flag is included in your backup if you use the cloud backup, section 4), and it only sends “first book: yes/no” when retrieving the price and when ordering; nothing is stored on our server for this. With GlowCamp Pro there is instead a permanent Pro discount (20%, also for repeat orders); for this our server asks RevenueCat once whether Pro is active, without storing or logging the ID (section 9). Only the higher discount ever applies; in delivery countries with high printing and shipping costs it may be lower. In the order we only store the discount granted (percentage and type: first book or Pro), so that a reopened payment page shows the same price; it is deleted together with the order (section 11). Stripe receives the discounted price and a note such as “incl. 15% first-book discount” in the product description, but never your app ID.

Photos with other people: You are responsible for the photos you include in your book. If other people can be seen in them (or e.g. number plates), please make sure that they agree to this.

Deleting: You can delete an order in the app at any time; any payment page that is still open is then closed. If the book has already been paid for, the print file and order IDs remain until it has been printed and shipped and the complaints period has expired. How long we keep what is set out in section 11. The photos on your device are not affected by this.

Legal basis: For creating the preview and print file, payment, printing, shipping and the notifications about the order, the performance of the purchase contract or pre-contractual measures at your request (Art. 6(1)(b) GDPR); for retaining the invoice, our legal obligation (Art. 6(1)(c) GDPR); for limiting requests to protect against misuse, our legitimate interest in a secure service (Art. 6(1)(f) GDPR). The explanation dialogue before uploading is there so that you know beforehand what goes where; without the data named there, we cannot produce the book.

18f. Route calculation via our own server (from version 1.11.0)

From version 1.11.0, the app has routes (kilometres and driving time) calculated by our own server instead of by public third-party services; from this version onwards it no longer queries the OSRM demo server. For this purpose we operate our own routing service on glowcamp.de (Valhalla, with map data from OpenStreetMap). The requests (addresses “/route” and “/route/matrix”) only go to this service on our server, not to any third party.

When: in trip planning when calculating the route, when you tap “Calculate route” for a trip added afterwards, and automatically when you open a trip added afterwards without kilometres for which a home location and places are known (at most once per trip and app session). In the day plan, while you have it open: road km and driving times from the site to the day's planned destinations and back, and on the day of departure also the journey home (home location rounded, see below). Also for the dart: when you tap (“Go” or “Again”), the app requests the driving distance and driving time for the suggestions found, so that the set radius applies as driving distance (at most three requests per throw). From version 1.12.0, on the Today map on travel days (departure, change of site, while driving) automatically: road km and driving time to the next site or home, at most once per travel day and destination in one app session. The app only uses our server if it offers the function (feature query, section 5). If it does not offer it or is not reachable, the app estimates the distance on the device (straight line); only the route suitable for car and caravan in trip planning can then, as before, be calculated by openrouteservice (section 5), when you tap, never automatically.

Which data: the waypoints of the route (2 to 25 coordinates, e.g. home location, sites, overnight and excursion destinations), the profile (car or motorhome/car and caravan), for a motorhome or car and caravan the known vehicle dimensions (height, width, length, weight) and, for technical reasons, your IP address. For the dart, it is the starting point (home location, chosen place or, if you choose “My location”, your current location) and up to 50 coordinates of public sites from OpenStreetMap per request. On the Today map, the starting point is the most recently recorded position of your trip (no additional location query), likewise rounded to 0.01 degrees; the destination is the next site or your rounded home location. The app rounds your home location and the starting point of the dart to 0.01 degrees (approx. 1 km) before each request, regardless of whether the request goes to our server or to openrouteservice; your exact address does not leave the device for this. No recorded route, no trip, device or account ID.

Storage: none. Our server does not store the requests, does not write them to logs (not even in error messages) and does not keep an access log for this address. The IP address is held in memory for only a few minutes in order to detect too many requests.

The legal basis is our legitimate interest in route calculation that works and is data-minimising (Art. 6(1)(f) GDPR).

18g. “Search my photos” (iPhone from version 1.11.0, Android from version 1.12.0)

On the iPhone, you can have past trips found from your photo library. Only when you tap does the app read the date and location of the photos from the last 3 years (at most 30,000 photos) and suggest trips from them. This happens exclusively on your device, in the foreground and can be cancelled at any time: nothing is sent to us or to third parties, no location tracking runs, and photos that are only stored in iCloud are not downloaded for this. The search uses the photo access you have granted the app in the operating system. Trips that you create from the suggestions are stored by the app, like other trips added afterwards, only on your device (and, if activated, in your own cloud backup, section 4). If you open such a trip later, the app can calculate its kilometres as described in section 18f. On Android, this function is also available from version 1.12.0, with the permissions named in section 18j.

18h. Weather via our own server (from version 1.11.0)

From version 1.11.0, the app no longer requests the weather (section 5: severe weather alert at a stop, weather for the current day, daily forecast) from Open-Meteo in Switzerland, but from our own weather server on glowcamp.de (address “/wetter”). What is sent and when remains unchanged: a position rounded to 0.1 degrees (approx. 10 km), the weather values requested and, for technical reasons, your IP address, only with your weather consent. No device, trip or account ID.

Storage: none. Our server does not store the requests, does not keep an access log for this address, and the weather service itself does not write any request logs. Your request does not go to any third party. Our server loads the weather data, independently of individual users, from the open database of Open-Meteo (provided via the Amazon Web Services Open Data programme); only data blocks requested by our server are retrieved, never your position or IP address. Weather data: Open-Meteo.com, licence CC BY 4.0.

As before, the legal basis is your consent (Art. 6(1)(a) GDPR); you can withdraw it at any time in the app (section 5). With our own server, the transfer to Switzerland no longer takes place.

18i. Anonymous trip counter (voluntary, off by default, from version 1.12.0)

On our website, we would like to show how many trips have already been recorded with GlowCamp (e.g. “Over 1,000 trips with GlowCamp already”). For this, the app asks you once after your first trip recorded with GPS (“Count your trips?”); without an answer and with “No, thanks”, nothing is sent. You can also find the “Count trips” switch under Profile → My data. Only if you agree does the app report to our server (glowcamp.de) once at the end of each trip recorded with GPS “one more trip” and the kilometres driven on this trip, rounded to the nearest 100 km. If you agree when asked after a trip, that trip is counted; older trips are not reported retrospectively, and trips added afterwards never count. No ID, no position, no route, no destination, no country and no date are transmitted. If there is no connection at the end of the trip, the app sends the report once later.

Our server only adds up the reports into daily totals (number of trips and kilometres per day) and does not store any individual report. The IP address is only held briefly in memory in order to detect too many requests (at most 24 hours); no access log is kept for this address. Publicly, we only show rounded overall figures. We keep the daily totals for as long as we use them for this purpose; they do not allow any conclusions to be drawn about individual persons or trips.

The legal basis is your consent (Art. 6(1)(a) GDPR; for sending from the app, § 25(1) TDDDG). You can withdraw it at any time under Profile → My data → “Count trips”; after that, the app no longer reports anything, and reports not yet sent are discarded. Withdrawal does not affect the lawfulness of the processing carried out up to that point. Reports already counted have been merged into the daily totals and cannot be attributed to any person.

18j. Photo suggestions on Android (from version 1.12.0)

On Android, from version 1.12.0 and with your permission, GlowCamp can read photos from your library in order to suggest photos for your travel days and to find past trips (as on the iPhone, section 18g). For this, the app asks the operating system for the permissions “Read photos” and “Read location of photos”. The app evaluates the date and location the photos were taken (EXIF data) exclusively on your device. Photos are not uploaded unless you expressly share them (section 6b). You can revoke the permissions at any time in the Android settings.

18k. Fellow travellers contribute (voluntary, with an account, from version 1.12.0) – in preparation, not yet active

You can invite people to a trip (from among your friends or via a one-time, expiring invitation link), who can then contribute diary entries and photos to this trip. To accept, the invited person needs an account (section 18a). The trip continues to be recorded only on the device of the person to whom it belongs.

End-to-end encrypted: Contributions (texts, photos, changes to places) are encrypted on the devices before they go to our server (glowcamp.de). Our server only stores encrypted data and cannot read it. It can only see what it needs for delivery: who belongs to which trip, when something was uploaded and how large it is. When there is contact with our server, we process your IP address, for technical reasons, to protect against misuse.

Deleting: If the owner of the trip withdraws an invitation, if someone leaves the trip or deletes their account, we remove the associated encrypted data from our server. The legal basis is the performance of the user agreement (Art. 6(1)(b) GDPR). Details (e.g. what happens to the keys if a device is lost) will follow before launch.

18l. Recommendation link for places (voluntary, without an account, from version 1.13.0)

On the page of a campsite, motorhome pitch or car park, a sight or a petrol station from OpenStreetMap, you can share a link with “Recommend”. For this, the app opens your phone's share menu; you decide where you send the link (e.g. messenger, e-mail). The app itself does not send anything to us in the process. The link has the form https://glowcamp.de/o/<type>/<OSM type>/<OSM ID>#n=<name>&la=<latitude>&lo=<longitude>. It only contains information about the place: the type (site, sight, petrol station), the OpenStreetMap ID, the name and the location of the place rounded to two decimal places (about 1 km) – never your position, your route, a date or an ID of you or your device.

Messengers and link preview: The provider of the service via which you share the link processes it under its own responsibility in accordance with its privacy policy. The preview of the link (title, image) is generated by the messenger itself by retrieving the page from us. This preview is deliberately generic (“A place tip from GlowCamp”) and does not contain a place name.

When the link is opened: If GlowCamp is installed, the link opens the place page directly in the app (via Apple's or Google's operating systems); we receive nothing in the process. Otherwise, a web page on glowcamp.de opens. When it is called up, the path of the link (type, OSM type and OSM ID) and the IP address reach our server for technical reasons, plus, as with any web page request, the browser identifier (user agent) and preferred language. We do not store or log any of this: we do not keep an access log for this page, and the IP address is only held in memory for the duration of the connection. The server does not evaluate the path and delivers the same page for every link. The part of the link after “#” (name and location) is not transmitted to our server by your browser; it is only read by a small script on the page in your browser in order to display the name.

Information from GlowCamp users: Using the rounded location, the page in your browser loads the public area file of the community information (1 × 1 degree, at degree boundaries also the neighbouring one), exactly like the app (section 18c). Only the area ID and the IP address are transmitted, without an access log; we therefore do not find out which place is being viewed. From this, the page only shows stars for this place (only once there are 4 on-site-confirmed ratings) and ticked features, without names and without photos.

Source and links: Place data comes from OpenStreetMap (© OpenStreetMap contributors, licence ODbL). The page links to the place's page on openstreetmap.org as well as to the App Store and Google Play; only when you tap one of these links do you leave our page (section 16).

No tracking, not in search engines: The page does not use cookies or any analytics or advertising services, and does not load any content from other providers. It does not send a referrer and is blocked for search engines (noindex).

The legal basis for delivering the page and the area files is our legitimate interest in being able to display recommended places even without the app (Art. 6(1)(f) GDPR).

Data flows from version 1.11.0, 1.12.0 or 1.13.0

Rows marked “in preparation” concern functions that have not yet been activated.