App privacy policy

This is a convenience translation. The German version is legally binding. German version as of 26 October 2026.

This policy applies to the mobile app “TravelMaster Go” (iOS & Android) and to its web version at app.travelmaster-go.app (section 3a). The separate website privacy policy applies to this information website at travelmaster-go.app.

1. Controller

The controller for the processing of personal data in this app within the meaning of the General Data Protection Regulation (GDPR) is:

Thomas Althaus
In der Rötelgrube 2
74243 Langenbrettach, Germany
Email: service@travelmaster-go.app

No data protection officer is appointed. There is no obligation to appoint one: we employ fewer than 20 people who are permanently engaged in the automated processing of personal data (§ 38(1) sentence 1 BDSG), and, according to our assessment, our processing is not subject to a mandatory data protection impact assessment (§ 38(1) sentence 2 BDSG). We have nevertheless carried out a data protection impact assessment under Art. 35 GDPR voluntarily.

This privacy policy applies to the mobile app “TravelMaster Go” (iOS & Android) and to its web version at app.travelmaster-go.app (section 3a).

1a. Legal bases at a glance

We process your data on the following legal bases. Each section below states which one applies.

No automated decision-making, including profiling, producing legal effects concerning you takes place. Providing your data is voluntary; without it, individual features cannot be used or can only be used to a limited extent.

2. Data we process

TravelMaster Go processes the following data to the extent you provide it voluntarily:

Smart Filing and tickets stay on your device. A till receipt can contain particularly sensitive details – a pharmacy receipt names the medicine. Neither is therefore transferred to the cloud, not even when synchronisation is switched on, and neither is sent to AI services. Uninstalling the app removes this data.

Health details in the emergency section (Art. 9 GDPR): Blood group, allergies, medication, pre-existing conditions and a note for emergencies are special categories of personal data. We store them only if you have first given explicit consent in a separate dialogue (Art. 9(2)(a) GDPR). The details are kept exclusively in encrypted form in your device’s protected storage (iOS Keychain or Android Keystore). They are not transferred to the cloud, not included in device backups, not transmitted to AI services or third parties, and are lost when you change device. You can withdraw your consent at any time under Settings → Privacy; the details are then deleted immediately. An SOS message sent in an emergency contains only your optional location, none of these details. The same applies to the accessibility profile under Settings → Accessible travel: whether you travel with a wheelchair or with a mobility, visual or hearing impairment is stored only with your explicit consent and likewise only in encrypted form on your device; you can remove it at any time with “Delete profile”.

What the accessibility profile does: it works on your device only. In “Discover”, places with documented accessibility are ranked higher; a matching packing list template is suggested; and before flights a local notification reminds you to request airport assistance. No data leaves your device for that reminder — it is scheduled on the phone. Each of these three effects can be switched off individually. The profile does not enter usage analytics or crash diagnostics.

Health-related documents in the vault: with cloud sync switched on, the document vault otherwise transfers details such as a document’s title and category, never the image files. Documents in the categories medication, prescriptions, vaccination record, disability ID card, EU parking card and medical certificate are excluded from this entirely and remain on your device; they therefore do not appear on a second device.

Photo library for the Photo Memory game: In the “Photo Memory” game, you play with photos from your own device. To do this, the app reads your photo library with your permission and selects images for the game at random; screenshots are excluded. This processing happens exclusively locally on your device – the photos are not uploaded, not transmitted to us or third parties and not stored permanently; they remain in the app’s memory only for the duration of the game. You can restrict or revoke this access at any time in your device settings; without access the game cannot be started.

Voice dictation (optional): In the diary, the packing list, community contributions and the Coco assistant, you can dictate text instead of typing. Speech is converted to text by your operating system’s speech recognition (Apple or Google); depending on the device and its settings, this may transfer the recording to the respective provider for recognition. The app itself does not store audio recordings and does not transmit them to us; only the recognised text is used. Without microphone permission, the keyboard remains available as usual.

Importing bookings by email (optional): In the settings you can generate a personal forwarding address. If you forward a booking confirmation to that address, we automatically extract the travel details (such as flight, hotel, rental car or train) and offer to assign them to a trip. The feature is voluntary and unused by default: as long as you do not forward an email, no data is processed. Extraction requires that you have enabled the AI features (section 4); otherwise we do not read the message and discard it, and the app tells you so. Receipt is handled by our processor Brevo (Sendinblue GmbH) with data centres in the EU; the message is not stored there but passed on directly to our processing. To extract the details, the text and any PDF attachments are transferred to Anthropic (USA) – see section 4. Only the result is stored, i.e. the recognised trip and booking data; the email itself, its attachments and the sender address are not stored permanently. Results you do not import are deleted automatically after 30 days.

Information about other people: Forwarded booking confirmations may contain information about other people, for example fellow travellers. Please only forward messages where this is acceptable to you. We use such information solely to create the booking in question in your trip – it is not evaluated for other purposes and not used to train AI models. For group votes we do not ask for names; we only store the chosen answer with a random identifier, and other participants only see the overall result (details in section 5a).

2b. Minors

The app is intended for people aged 16 years and over. Consent to the processing of personal data — for example to the optional AI features or to usage statistics — can be given independently from that age in Germany (Art. 8 GDPR). Younger people may use the app only with the consent of a person with parental responsibility; that person’s approval is also required for paid services and for the younger person’s own community contributions.

We do not collect age separately and cannot verify it technically. If we become aware that an account is being run by a younger person contrary to this requirement, we will delete it together with the associated data. The age rating in the app stores assesses the suitability of the content and is independent of this rule.

2c. Community contributions: photos and tips on places

Voluntary — and, unlike the rest of your data, visible to everyone. You can contribute a photo or write a note about a place, such as a restaurant or a sight: an insider tip, a description, opening hours or details of the facilities. Unlike your trips, diary entries and private photos, such a contribution is not private: once reviewed, it is shown to all users of the app at that place — in the case of photos, immediately after the automatic check. An approved photo may replace the previous symbol image as the place’s cover image. The feature is voluntary and unused by default — nothing is transmitted unless you act.

A human sees free-form texts before publication. Insider tips and descriptions are never released automatically, but only after a visual review by us. Until then the contribution is visible only to you and to us; if it is rejected, it does not appear. Photos without text, by contrast, are checked automatically and appear immediately afterwards — details in the next paragraph.

Automatic preliminary check. Before a human sees the photo, Google Cloud Vision checks it automatically — for offensive content and for whether faces or vehicle number plates are recognisable. For this purpose the image is transferred to Google LLC in the USA; this transfer is safeguarded as described in section 7. If a photo fails this check, it does not appear; if the procedure detects faces or number plates, the photo is held back for editing. If it passes the check, it appears immediately. If the service does not respond, the photo remains invisible. A human review takes place on a case-by-case basis, in particular after a report; a reported photo is immediately no longer visible.

No attribution by name. Published contributions appear without your name — others do not learn who a photo or a tip comes from. Internally the contribution remains linked to your account so that you can find it again and delete it.

Location data in image files is removed. Every photo is re-encoded on upload. In the process, all metadata of the original file is lost, including the GPS coordinates and the capture time embedded by many cameras.

Coordinates you set yourself. For some contributions there is no suitable map point – on a beach, for example. In that case we store the position you adopt or have determined by GPS as part of your contribution. That is something other than the image file’s metadata: those are still removed in full.

Photos from the scavenger hunt. If you submit a photo for a scavenger hunt station, we additionally store the time it was taken and the position where you took it. We use these to check that you really were at the station; without this proof, points and badges would be worthless. The position is not published and cannot be retrieved by other users; it is deleted together with the photo. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR).

People in photos. Please do not upload images in which other people are recognisable without their agreement — in a restaurant, for example, guests at the next table. You are responsible for the content of your contribution. If you yourself appear in a published photo and do not want this, report the image to us via the report function in the app or at service@travelmaster-go.app; we will remove it.

Legal basis and withdrawal of publication. Processing is based on the performance of our user agreement (Art. 6(1)(b) GDPR) in so far as it serves to provide the community features; publication itself rests on your decision to submit the contribution. You can withdraw the publication at any time: under “Profile → My contributions” you delete a contribution, and it then disappears from the app. We cannot recall copies that other devices have already stored in their image cache.

2d. Founder campaign

If you take out a Premium yearly subscription during the Founder campaign (§ 5c of the Terms), our service provider RevenueCat notifies us of the purchase. If you receive a Founder spot, we store the following for your account on the servers of our processor Supabase in the EU: the Founder number, the time of purchase and assignment, the identifier of the store product purchased and of the purchase event, and your settings for displaying the Founder badge.

The purpose is to assign Founder status, to evidence the order of assignment and to display the status in the app. The legal basis is performance of the contract (Art. 6(1)(b) GDPR). No new recipients are added as a result.

Only the number of assigned spots and, on the Founder page in the app, the assigned Founder numbers are publicly visible, in each case without reference to any person. We store and publish a name for the Founder page only if you enter it yourself and consent (Art. 6(1)(a) GDPR); for this purpose we store the time of your consent. Before the name appears, a person reviews it; we do not publish a name that violates the Terms. You withdraw your consent by removing the name; it then disappears from the Founder page immediately.

We store this information for as long as your account exists. If you delete your account, we remove the link to you and any name you entered; the number remains assigned without personal reference so that it is not assigned again.

2e. Reminder before your subscription renews

If you have a subscription that renews automatically (Premium or Premium+), we send you an email seven days before each renewal with the date and how to cancel; for a free trial, before it ends. For this we use your email address, your plan, the end of the term as reported to us by RevenueCat from the App Store or Google Play, and – if synced – your app language.

So that no reminder reaches you after you have cancelled, we store on the servers of our processor Supabase in the EU whether and when you cancelled and for which end of term we last sent a reminder. The email is sent via Resend, Inc. (USA; delivery via servers in Ireland), safeguarded by the EU-US Data Privacy Framework and EU standard contractual clauses. Opens and clicks are not tracked.

The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). The reminder is contract information and therefore cannot be unsubscribed from. If you delete your account, we delete this information too.

3. Cloud synchronisation

If you enable cloud sync, your trip data and your app settings (such as units, display options, travel pace and travel styles) are transmitted over an encrypted connection and stored encrypted on servers operated by our processor Supabase within the EU (AWS region Ireland). A data processing agreement under Art. 28 GDPR is in place with Supabase. As Supabase Inc. is a US company, US authorities may demand the disclosure of data under US law (including the CLOUD Act) even when it is stored in the EU; where required, processing is additionally based on the EU Standard Contractual Clauses (Art. 46 GDPR). The document vault is additionally encrypted on the device.

Without signing in. Even if you do not sign in, the app creates a pseudonymous guest account with Supabase (EU) on first launch: a random identifier with technical sign-in data (by Supabase standard also the IP address and device/browser identifier of the session) and a profile with basic settings (such as plan tier and whether you have allowed the AI features). This is technically necessary so that features such as weather, places and purchases work without an account (§ 25(2) no. 2 Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz (TDDDG, Telecommunications Digital Services Data Protection Act); Art. 6(1)(b) GDPR). Before this guest sign-in, Cloudflare Turnstile automatically checks whether the request comes from a human (section 6). RevenueCat receives the identifier only when you open the purchase page, buy something or restore a purchase. Without signing in, your content – trips, diary, photos, documents, points and settings – is stored exclusively locally on your device and is not synchronised with the server. The only exceptions are what you send to us yourself, such as feedback (text and optional contact address), and queries for weather and map data with an approximate location, which are cached without reference to you as a person. A guest account without content is deleted automatically if it has not been used for 30 days; if you sign in later, it is carried over into your account.

3a. Web version in the browser

At app.travelmaster-go.app you can also use TravelMaster Go in your browser. The web version is only available with an account; there is no guest access as in the app. It accesses the same data as the app through your account with Supabase (section 3). Unless this section states otherwise, the other sections of this policy apply to the web version accordingly.

The pages of the web version are provided by IONOS SE (Montabaur, Germany) as our hosting provider. With every request, IONOS processes, for technical reasons, your IP address, the time, the requested address and information about your browser in server logs. The legal basis is our legitimate interest in providing the pages securely and reliably (Art. 6(1)(f) GDPR). If you sign in with an email code, Cloudflare Turnstile checks, as in the app, whether the sign-in comes from a human (section 6).

The web version does not set cookies. Usage analytics via PostHog are not available in the browser; like the app, the web version sends error reports via Sentry only with your consent (section 6). It stores your sign-in and a copy of your data in your browser's storage (localStorage) so that pages load quickly. This is strictly necessary for the use you request (§ 25(2) no. 2 TDDDG; Art. 6(1)(b) GDPR). When you sign out, the web version deletes this storage completely; everything remains in your account. For this reason, always sign out on a shared computer or one that belongs to someone else.

Without Premium, the web version only transfers your trips to your account. Bookings, packing lists, tasks, expenses and day plans that you create in the browser without Premium stay in this browser only and are deleted when you sign out. The web version points this out to you the first time.

Files that you drag or paste into the web version are read by your browser itself. Calendar entries, wallet passes, spreadsheets, place files and GPX files do not leave your browser. PDF files, photos, emails and pasted texts are only sent to the AI features for analysis (section 4) if you have enabled them; without this consent, none of it is sent to our server. If you paste a link, our server retrieves the page as described in section 7.

The assistant "Coco", the document vault and the health information from the emergency area are not available in the browser; the web version does not retrieve this data. The web version only asks for your location if you start the nearby search and grant permission in your browser (section 5). Purchases are currently not possible in the browser.

4. AI features & transfers to third countries

For AI-assisted features (including diary enhancement, trip and day planning, receipt/document scanning, analysis of booking confirmations forwarded by email, photo/place recognition, translations and the “Coco” assistant), the content required for this – such as diary text, uploaded receipts/photos, the contents of forwarded booking emails including their PDF attachments, trip data or location details – is transferred to and processed by the following processors:

Because the primary model used for text and dialogue (Anthropic/Claude) is operated in the USA, using these AI features transfers the relevant content to a third country (USA). This transfer is based on the EU Standard Contractual Clauses (Art. 46 GDPR). Under the contractual terms of the providers used (Google Cloud/Vertex AI, Anthropic), your inputs are not used to train the AI models. AI features are optional and disabled by default: you can turn them on or off at any time under Settings → AI. As long as you do not use them, no transfer takes place. If you report an AI output (using the report function on the output itself), we store the reported output verbatim (up to 2,000 characters), the reason you selected, an optional explanation, the feature concerned and your user ID. Your input is not stored with it. The purpose is to improve filtering and moderation; the legal basis is our legitimate interest in a safe and reliable service (Art. 6(1)(f) GDPR). If you delete your account, the report is detached from your ID and evaluated anonymously only.

5. Location data

Nearby search: The Discover feature requests your location to show places near you. This request itself is not stored and is not passed on to unrelated third parties. We store location references only where you create them yourself: when you mark a place as visited (the place and the time are stored), when you record your travel route or an activity, when you save a favourite place with its position, or when you submit a community contribution with coordinates. You can delete each of these entries individually; the following paragraphs describe them in detail.

Nearby places from OpenStreetMap: if the app knows only a few places in an area, it fetches more from OpenStreetMap without you having to tap anything. This only happens while the app is open, and you can cancel it at any time. For this, the app does not send your location but only the centre of a grid cell of about 11 kilometres per side and the category being searched to our server (Supabase, EU), without your user ID. Our server queries the OpenStreetMap Overpass interface and stores the result in a shared cache for all users; the operator of the interface does not learn your IP address. The app stores the places found (name, category, location and, where available, opening hours and operator) on your device for 14 days, for at most twelve grid cells. These stored cells give a rough indication of the areas your device has been in; they do not leave your device and are removed when you delete your local data or uninstall the app. The legal basis is performance of the user contract (Art. 6(1)(b) GDPR).

Live location sharing in shared trips: If you enable it, your position is visible, together with your display name, to the other members of that trip for as long as sharing is active. You can stop it at any time or revoke it in your device settings.

Recording your travel route (optional, off by default): If you enable this under Settings → Privacy, the app records your path during an ongoing trip. Recording runs only while the app is open and in the foreground – it stops as soon as you leave the app. At most one point every 500 metres is stored, up to 500 points per trip. These points remain exclusively on your device and are not transferred to the cloud. You can switch recording off again at any time; the points are removed when you delete the corresponding trip or your local data, and they are included in your data export.

Activity recordings (hiking, skiing, motorcycling): When you start such a recording, the route covered is stored as a sequence of coordinates, along with duration and distance, plus elevation gain depending on the activity. Unlike the travel route, these recordings are synchronised to the cloud with your account so that they are available on multiple devices and are preserved when you reinstall. The legal basis is performance of the user agreement (Art. 6(1)(b) GDPR): cross-device availability is precisely the service you request with cloud synchronisation. They are visible only to you and are not passed on to third parties. You can delete individual recordings; deleting your account removes them as well.

Maximum speed stays on your device: For ski and motorcycle recordings the app also determines the highest measured speed. This value is stored exclusively locally and is not transferred to the cloud, because it could allow conclusions to be drawn about your driving behaviour. It is therefore not shown on a second device.

Visited places and favourite places: If you mark a place as visited or planned, we store that assignment together with the time in your account. The same applies to a favourite place you save with a position. These entries are visible only to you and can be deleted individually; deleting your account removes them as well.

5a. Sharing with others

Some features make content visible to others – always only when you trigger it yourself. Anyone who knows such a link can see the content without signing in; so pass it on only to people it is meant for. You can revoke every link in the app.

The web pages through which such links are opened are hosted on GitHub Pages (GitHub, Inc., USA); GitHub receives the IP address of the person opening the link. The transfer is covered by GitHub’s contractual safeguards (EU Standard Contractual Clauses). The legal basis is performance of the user agreement (Art. 6(1)(b) GDPR): sharing is the service you request.

Details of other people: if you enter details of other people, such as the names and PayPal.me handles of fellow travellers in the travel fund, we process them only for that feature. The legal basis is our legitimate interest and that of the travel group in organising the trip together (Art. 6(1)(f) GDPR). Only enter them if the person agrees, and tell them that their details are stored here. Data subjects can exercise their rights under section 8 directly with us, even without the app.

If you open a shared link: the pages can be reached without the app and without an account. When you open one, GitHub, as the host of the web pages, technically receives your IP address and details about your browser. The page loads the content from our server (Supabase, EU); your IP address is processed in the process but not stored together with the content. Anything you enter there yourself — a vote, an expense in the travel fund or an itinerary item — is stored with the shared trip or vote until the person who shared it deletes it or the periods under section 9 expire. The legal basis is our legitimate interest and that of the sharing person in providing the shared content (Art. 6(1)(f) GDPR). The pages use no cookies and no analytics tools; only the voting page stores a random identifier and your own choice in your browser’s storage so that you can change your vote. You can exercise your rights under section 8 at service@travelmaster-go.app.

6. Analytics, stability & security

If you enable anonymous usage analytics, pseudonymised technical events (e.g. feature usage) are collected via our service provider PostHog (EU region). Analytics is disabled by default, active only with your consent and can be switched off at any time under Settings → Privacy. To improve stability, we process crash and error diagnostics in the store version via Sentry. The provider is Functional Software, Inc. (USA); processing and storage take place in the service’s EU region. What is transmitted are technical details about the error: stack trace, app version, operating system and device type. Content from your trips, diary entries or documents is not transmitted; user identifiers, requested addresses and network traces are already removed on your device before a report is sent.

Error diagnostics are tied to the same consent as usage analytics — if that is switched off, no report is sent. The legal basis is your consent (Art. 6(1)(a) GDPR); you can withdraw it at any time under Settings → Privacy.

Access to your device (§ 25 TDDDG). Usage analytics and error diagnostics store or read information on your device solely with your consent (§ 25(1) TDDDG). Storing your trip data, settings and sign-in data on the device does not require separate consent: it is strictly necessary to provide the features you have expressly requested — in particular offline use (§ 25(2) no. 2 TDDDG).

Protection against automated abuse (bot protection): To protect our sign-in – in particular the anonymous first sign-in at app start and sign-in by email – against automated access (bots), we use the service Cloudflare Turnstile by Cloudflare, Inc. (USA). Turnstile checks in the background whether a sign-in request comes from a human and, for this purpose, processes technical information such as your IP address and characteristics of your device and browser. Contents of your trips, your email address or other account data are not transmitted to Cloudflare in the process. The check is for the most part invisible; only in exceptional cases is a brief confirmation shown. The legal basis is our legitimate interest in preventing abuse and in the security of our systems (Art. 6(1)(f) GDPR). Further information can be found in Cloudflare’s Turnstile Privacy Addendum.

6a. Notifications

Reminders on your device. Most of the app’s notices – such as for check-in times, planned schedule items, your packing list or trip preparation – are created by the app directly on your device and shown there at the right moment. No data leaves your device in the process, and no server and no third party is involved.

Push notifications (flight alerts). If you have a flight monitored (paid access only), we need to be able to reach you even when the app is not open – for example on a gate change or a delay. For this, your operating system assigns the app a device identifier (push token), which we store together with the details of the job. When setting up, the app obtains the token from the Expo Push Service (650 Industries, Inc., USA); the device token and the app identifier go to Expo in the process. We use Expo as a processor for this. When a change occurs, we transmit the identifier and the notification text to Expo, which delivers the message to your device via Apple’s or Google’s delivery services. No content from your trips is transmitted in the process.

The legal basis is your consent, which you give when you allow notifications and set up the monitoring (Art. 6(1)(a) GDPR). You can withdraw it at any time – in your device settings or by ending the monitoring; the device identifier is then no longer used and is deleted along with the entry. As the service is operated in the USA, this constitutes a transfer to a third country. Sending messages via Expo is currently switched off on the server side and will only be switched on once the EU Standard Contractual Clauses (Art. 46 GDPR), on which we base the transfer, have been agreed with Expo; until then, notices appear only inside the app itself.

7. Recipients of your data

We use carefully selected service providers, mostly as processors (Art. 28 GDPR); the map and content services further below, by contrast, are independent controllers. We do not pass on your data for advertising purposes and we do not sell it. In detail:

Where recipients process personal data outside the EU/EEA – in particular in the USA – the transfer is safeguarded as follows:

Gelato (Norway) processes data as a processor within the EU/EEA; no separate instrument for third-country transfers is required for this. Gelato usually has production carried out by local print partners in the country of delivery (i.e. within the EEA); should a production partner outside the EEA be involved in an individual case, the transfer is safeguarded by EU Standard Contractual Clauses or – for US recipients – the EU-US Data Privacy Framework. Even where data is stored in the EU by US companies (e.g. Supabase), US authorities may demand access under US law (including the CLOUD Act) (see section 3).

7b. Referrals to partners (affiliate links)

In some places the app refers to offers from third-party providers, for example for accommodation, activities or eSIM data packages. Some of these references are affiliate links: they contain an identifier by which the provider recognises that the visit came via TravelMaster Go. If a booking is made via such a link, we may receive a commission. Your price does not change as a result. Affiliate links are labelled directly at the respective link.

What happens: The link is opened in your external browser — not in the app. We transmit no data from your account, no trip data and no identifier that identifies you. Only our partner identifier is passed on. Once the provider’s page has loaded, the provider processes your data (including IP address, browser details and cookies it sets) under its own responsibility in accordance with its privacy policy. We have no influence on this processing.

Together with you, we are the starting point for opening the link, but we are not a processor or joint controller for what happens afterwards at the provider. The legal basis for the referral is our legitimate interest in financing the app (Art. 6(1)(f) GDPR); the referral takes place only when you activate the link. In the reports we receive from the partner network, we see only aggregated figures (clicks, bookings, commissions) — no details about individual people.

Active partners: GetYourGuide (GetYourGuide Deutschland GmbH, Berlin). Further providers will be added here as soon as a partnership exists.

8. Your rights

You have the right of access to the data stored about you (Art. 15 GDPR), to rectification of inaccurate data (Art. 16), to erasure (Art. 17), to restriction of processing (Art. 18), to data portability (Art. 20) and to object to processing (Art. 21).

Right to object: Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you have the right to object at any time on grounds relating to your particular situation. We will then no longer process the data concerned unless we can demonstrate compelling legitimate grounds which override your interests.

You can withdraw any consent you have given at any time with effect for the future (Art. 7(3) GDPR) – in the app under Settings → Privacy or informally by email. The lawfulness of processing carried out until the withdrawal remains unaffected.

An informal message to service@travelmaster-go.app is sufficient to exercise these rights.

Irrespective of this, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart. You can also contact the supervisory authority at your place of residence.

9. Retention periods and data deletion

How long we keep what. Where no fixed period is stated, the following applies: the data remains for as long as your account exists and is deleted along with it.

You can delete your account and all associated cloud data directly in the app (Settings → Account → Delete account, or Settings → Privacy). You can additionally remove local data by uninstalling the app. When your account is deleted, we also revoke any Sign in with Apple authorisation at Apple and delete your customer record at RevenueCat; purchase records kept by the app stores themselves are not affected.

Without the app installed: The full procedure — including without the app — is described on the Delete account and data page.

How long deletion takes. In the database your data is removed immediately upon the deletion request, at the latest within 30 days. Two technically unavoidable follow-up periods apply in addition:

This does not affect data that we are required by law to retain — in particular invoice data for purchases made, for the duration of the tax retention periods (§ 147 AO).

Deleting without the app: You do not need to have the app installed. Email us at service@travelmaster-go.app with the subject “Delete account” from the email address you registered with. We will delete your account within 30 days and confirm the deletion by email.

What is deleted: account and sign-in data, trips, diary entries, bookings, budgets, photos and documents, community contributions, and points and badges — completely and irreversibly.
What remains: invoice data for purchases made, for as long as the tax retention periods run (§ 147 AO), as well as anonymised evaluations without reference to you.
Important: Deleting your account does not end an active subscription. You manage and cancel subscriptions in the settings of your app store account (Apple App Store or Google Play).

As of: 27 October 2026