Privacy Policy

Effective date: 21 August 2026
Last updated: 28 September 2026

This Privacy Policy explains how the developer of Slowmap ("we", "us", "our") collects, uses, and protects your information when you use Slowmap (the "App"). We are the data controller responsible for your personal data; our full name and postal address are in Section 12.

Contact: support@slowmap.app

If you are in the European Union / European Economic Area, this Policy is intended to meet the requirements of the General Data Protection Regulation (GDPR).

1. Summary

• You need an account to use the App. We collect the email or Apple ID you sign in with.
• When you plan a trip, the details you enter (destination, dates, preferences, accommodation names, your own ideas for the trip, notes) are sent to our AI provider to generate your itinerary.
• We store your saved trips so you can access them across devices, and on your device so they open instantly, so your reminders keep working without a connection, and, on Pro, so you can read them with no connection at all.
• We count how many plans you generate, because that is what the free and subscription allowances and our own cost controls are based on. We also keep anonymous notes on how each plan turned out, with nothing about you in them, to fix mistakes that keep coming back. We do not use analytics or crash-reporting tools.
• We do not sell your personal data.
• Some links in a trip, to somewhere to stay, to tickets and to an eSIM, are partner links: if you book through one, the partner pays us a commission and your price stays the same. A link carries the trip's destination, dates and party size, never who you are (Section 2).
• You have rights over your data, including access and deletion; see Section 9.

2. Information we collect

Account information. When you create an account we collect an identifier from your chosen sign-in method: your Apple ID (via Sign in with Apple), your Google account (via Google sign-in), or your email address (via a magic link / one-time code). We assign you an internal user ID. You can use the same account on our app and, in the future, on our website.

If you sign in with Google, Google also passes us your name and the link to your profile picture, which our authentication provider stores alongside your account. The App does not display either, and we do not use them. Signing in with Apple or with an email address does not give us a name.

Trip content you provide. To generate a plan, you enter: destination, number of days, dates, when you arrive and leave and when your days start, who is travelling (how many adults, teenagers and children, and whether older travellers, a pushchair or a dog come along), whether you have been there before, transport, pace and how much you like to walk, interests and activities, an occasion if there is one, food and drink preferences, budget, the must-see/hidden-gems setting, what you have already booked, per-night accommodation names or areas and, if you give it, what you pay for each (kept as one of the trip's costs, never sent to our AI provider), and your own ideas for the trip (what you want to see, do and eat, and any special wishes). We do not ask about health or religion. We also store the plans generated for you and the modification requests you make.

What you add to a saved trip. What you add or change once a plan is made is stored with the trip, so it follows you to another device: your own entries (flights, bookings and the like), the costs you add, your notes and marks on stops, the stops you add by hand and the changes you make to the plan yourself. The ticks in a trip's Checklist are kept only on your phone.

Reports about a plan. If you tell us that something about a stop is wrong, we store the report against your account and that trip: which stop, the reason you chose, the note you write if you write one, and the language of the plan. We read reports only to make plans better. A report is deleted when its trip is, and so when you delete your account.

Settings you choose. The currency you read figures in is kept with your account rather than on the phone, so signing in on a new device does not mean saying it again. It is a three-letter code and nothing else. Your notification choices (which reminders you want, how early they come and the trips you have silenced) are kept with your account for the same reason.

Purchase information. If you subscribe, our subscription provider and the App Store process the transaction and tell us your subscription status (active/expired) and the date it began, which is the day a subscription's plan allowance is counted from. We do not receive or store your full payment card details: the App Store handles payment.

Generation counts. We record when a plan is generated, modified, or translated, and what it cost us to produce, against your internal user ID. This is how the free allowance and a subscription's allowances (its plans, and the changes to each trip) are counted, how abuse is spotted, and how we keep our own AI spending inside a daily limit. It is not used to profile you and it is not shared with advertisers.

How plans turn out. Before you see a plan, a change, a translation or a read in Discover, our server checks it for mistakes that can be found automatically (for example, prices in two different currencies or a place listed twice) and asks the AI once more if it finds one. For each of these we keep a short technical note: which checks failed, whether asking again fixed it, the language and number of days of the plan, the AI model, how long it took and what it cost us. The note is not linked to your account or to the trip, and holds nothing you typed, no destination and no part of the plan. We use these notes only to find mistakes that keep coming back and fix them, and delete them after two years.

We do not use analytics or crash-reporting tools. The App contains no analytics SDK and no crash-reporting SDK, and we do not collect your device model, operating system version, or crash reports. If that ever changes, this Policy changes first.

Abuse prevention. To stop the free allowance being used repeatedly through new accounts, we use Apple's DeviceCheck service, which lets us record a minimal flag against your device (managed by Apple) indicating that the free trip has been used. It does not identify you and is not used for advertising or analytics.

Advertising data (free tier only). If you use the free version, we show ads through Google AdMob. AdMob may access your device's advertising identifier, your IP address (from which it estimates an approximate location), what you tap in the app and technical reports on how its own software ran, in order to show and measure ads. That data goes to Google, not to us. With your consent, ads may be personalized; if you decline tracking, you will see non-personalized ads instead. We also record on your account how many full-screen ads you have been shown today and when the last one appeared, so that we can limit how often they are shown to you; this is used for that limit and nothing else. Paid (Pro) users see no ads and the ad system is not activated for them. See Section 4a for consent.

Trips you choose to share. The App can create a link to one of your trips. Anyone who has that link can read the itinerary (the days, places, times, tips and the estimated budget) without an account and without our knowing who they are. Your own additions are never included: flights, accommodation, reservations, the places you sleep, your notes and marks on stops, the stops you added by hand, and the answers you typed while planning stay out of the shared copy. The itinerary itself is shared as it was written for you, though: a stop planned around something you booked or asked for appears like any other, and the plan's text may mention it. Shared pages are marked so that search engines do not list them, but a link can be forwarded by whoever receives it, so treat sharing as making that itinerary public. You can turn a link off at any time in the App, and sharing again afterwards creates a new link while the old one stops working permanently. Links also stop working on their own if your subscription ends, so nothing you shared stays readable once you stop paying.

Trips shared with you. When you open a link somebody sent you while signed in, the App remembers that link so the trip appears on your list without you having to keep the message. We store the link itself and a short summary of the trip (its name, the destination, the number of days and the start date) against your account. We do not store a copy of the itinerary. Every time you open it, it is read from the sharer's own trip, which is why it disappears from your list the moment they turn the link off or their subscription ends. You can remove it yourself at any time by deleting your account, and it is removed automatically when the link stops working. We do not tell the person who shared it that you saved it, and we do not tell you who else has.

Destination suggestions. As you type a destination, the App shows suggestions. Most come from a list built into the App itself, which needs no connection and tells us nothing. Beyond that list, what you have typed so far is sent to Apple's map search so it can suggest places we do not carry: the same search that powers Maps on your device. It is sent to Apple, not to us; we do not receive, store or log what you type there. It happens while you are typing in that field, and when the App needs to find a trip saved before we began keeping a destination's coordinates, for its card on your list of trips or for its Weather tab; see below.

Weather. The App shows what it is like at each destination now (on your list of trips and in the Weather tab), together with the forecast for the days of your trip and, for days further ahead than any forecast reaches, what those dates are usually like there. To fetch it, the destination's coordinates are sent to Apple's weather service, along with your trip's dates when the usual weather for them is asked for; the destination's time zone is looked up from the same coordinates, so that hours and sunrise are shown on its own clock; and for a trip saved before we began keeping coordinates, its name is looked up first, as described above. All of it goes to Apple, not to us: we do not receive, store or log it, and it happens only while your list of trips or that tab is on screen. The forecast is then kept on your device for an hour, and the usual weather for a trip's dates for thirty days, so that coming back does not ask again. Apple requires us to name them as the source, which is what the mark under your list of trips and at the bottom of the tab is.

Files you attach to a trip stay on your phone. With a Pro subscription you can keep tickets, bookings and other documents (PDFs, Word files, photos) alongside a trip. We never receive them. They are not uploaded, not synced, not included in a shared link, and not readable by us in any circumstance: they are written into the App's own private storage on your device, which no other app can read, and marked so that they are left out of iCloud and iTunes backups. Three consequences follow, and the App says all three on the screen where you add them: they are gone if you lose the phone or delete the App, they are not restored when you set up a new phone, and anyone who can unlock your phone can open them. Deleting a trip deletes the files kept with it, deleting your account deletes all of them, and you can delete any of them individually at any time.

We do not collect your precise device location. The App shows your itinerary on a map using coordinates in the plan; it does not track your GPS location in this version. If we add an optional location-based feature in the future, we will ask for your permission and update this Policy first.

Notifications. With your permission, the App sends reminders about your trips (for example, an upcoming trip, a flight or reservation you entered, or the start of your day's plan). You choose which notification types you receive in the App, and you can turn them off in the App or in your device settings at any time. Most reminders are scheduled on your device from your trip details. One notification comes from our server rather than your device: if you allow notifications and leave the App while a trip is being planned, we tell you when it is ready. For that, the App sends your device's push token with the request for the trip; we use it once, through Apple's push notification service, and do not store it. The notification says only that a trip is ready, never where to.

Partner links. On some trips the App offers somewhere to stay and tickets for places in your plan, each marked "Partner link". If you book through one, the partner pays us a commission; the price you pay is the same. When you tap one, the App asks our server for the link. The server builds it from the trip itself: for a stay, from the destination, your dates and how many adults and children are travelling; for tickets, from the name of the place, its city and the day of your visit. For tickets, our server first sends that address to Travelpayouts, which turns it into a partner link. The link then opens in Safari inside the App, at Stay22, which passes you on to a booking site such as Booking.com, Expedia, Hotels.com, Agoda or Vrbo, or at GetYourGuide. From then on you are on their sites: they receive what the link carries and what any website receives, such as your IP address. Their own privacy policies apply. Nothing in a link says who you are: not your account, not your email address, nothing you typed on the planning form. We keep no record of the links you open. A stay is offered only if you did not name your own accommodation when planning; that is checked on our server and sent nowhere. On a trip abroad where roaming usually costs extra, the Checklist also offers an eSIM from Saily for the trip's country. To decide whether to offer it, the App works out the destination's country with Apple from the plan's own coordinates and sends our server that country and the region your phone is set to; the server answers and keeps neither. Travelpayouts makes the eSIM link a partner link, as it does for tickets.

3. How we use your information and our legal bases (GDPR)

Where we rely on your consent (for example, personalised advertising on the free tier), you can withdraw it at any time.

4. AI processing of your trip details

To create your itinerary, the trip details you enter and your modification requests are sent to our AI provider, Anthropic (the Claude API), which generates the plan on our behalf. Anthropic acts as our service provider (processor) for this purpose. We send only what is needed to produce your plan (the preferences and inputs described in Section 2), associated with a request, not with your name. Before your first plan, the App asks whether you agree to this. The time you agree is kept with your account; without your agreement, no plan is made.

When you ask for a change to a plan or for a translation, the plan as it stands goes with the request, including your own notes on its stops, your marks on them and the stops you added by hand. Your own entries (flights, bookings and the like) and the files you attach to a trip are never sent.

A plan made from answers in which you named no accommodation and wrote nothing of your own (no notes and no ideas for the trip) may also be kept for up to thirty days with no link to you or your account, and given to anyone who later gives exactly the same answers. A plan for which you named a stay or wrote notes or ideas of your own is never kept this way. From time to time we also read a small random sample of these copies, to find mistakes in plans and make them better; they hold nothing you typed and are linked to no one.

Plans are generated by AI and may contain inaccuracies (for example, incorrect opening hours, prices, or occasionally places that are out of date). Itineraries are a starting point to verify, not a guarantee. Please confirm details before relying on them. For how Anthropic handles data submitted through its API, see Anthropic's terms and privacy documentation.

4a. Advertising and your consent (free tier)

The free version shows ads via Google AdMob. Before serving personalized ads, we ask for your consent using Google's consent prompt and, on iOS, Apple's App Tracking Transparency prompt. You can decline; you will then see non-personalized ads, and you can change your choice later in your device settings. Subscribing to Pro removes all ads. For how Google handles ad data, see Google's privacy policy.

5. Who we share information with

We share data only with service providers that help us run the App, each acting on our instructions:

• Apple: Sign in with Apple, App Store subscription and payment processing, map search for destination suggestions and for a destination's time zone and country, weather and delivering the notification that a trip is ready.
• Google: Google sign-in, and (free tier) advertising via AdMob.
• Supabase: cloud hosting, database, and authentication (stores your account and saved trips).
• Anthropic: AI generation of itineraries (see Section 4).
• RevenueCat: subscription management.
• Google AdMob: advertising on the free tier (not used for Pro users). (Google is also listed above for sign-in.)

Partners you choose to visit. When you open a partner link, Stay22, GetYourGuide, Saily and the booking site you land on receive what that link carries and decide for themselves what to do with it, under their own privacy policies; they do not act on our instructions. Travelpayouts receives from our server only the address of the GetYourGuide or Saily page, to make it a partner link (Section 2, Partner links).

We may also disclose information if required by law, to protect our rights, or in connection with a business transfer. We do not sell your personal data, and we do not share it with advertisers to target you.

6. International data transfers

Some of our service providers are located outside your country, including in the United States. Where we transfer personal data outside the EEA, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses. You can request more information using the contact details above.

7. Data retention

• Account and saved trips: kept until you delete a trip, delete your account, or ask us to erase your data.
• Files you attached to a trip: never held by us at all. They are removed from your device when you delete the file, the trip it belongs to, your account, or the App.
• Generation counts: kept as long as the account exists, and afterwards without your user ID, so the totals still add up but no longer point at anyone.
• Notes on how plans turn out: hold nothing about you; each is deleted after two years.
• Reusable copies of plans (Section 4): carry no link to you, so deleting your account does not touch them; each is deleted automatically after thirty days.
• Partner links: not kept. Each is built when you tap it, and we store nothing about it.
• Purchase records: kept as required for accounting and legal purposes.

When you delete your account, we delete or anonymize your personal data within a reasonable period, except where we must retain it to meet a legal obligation.

8. Security

We use technical and organizational measures to protect your data, including encryption in transit, access controls, and storing our AI provider credentials only on our server (never in the App). No method of transmission or storage is completely secure, but we work to protect your information.

9. Your rights

Depending on where you live, you have the right to: access your data; correct inaccurate data; delete your data; restrict or object to certain processing; data portability; and withdraw consent where processing is based on consent. You will not be treated differently for exercising these rights.

To exercise any of these, contact us at support@slowmap.app. You can also delete saved trips and your account within the App.

If you are in the EEA and believe we have not handled your data properly, you have the right to lodge a complaint with your local supervisory authority. In Poland, this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO).

10. Children

The App is not directed to children under 16. We do not knowingly collect personal data from children under that age. If you believe a child has provided us data, contact us and we will delete it.

11. Changes to this Policy

We may update this Policy as the App changes or as required by law. When we make material changes, we will update the "Last updated" date and, where appropriate, notify you in the App. Please review it periodically.

12. Contact

Questions about this Policy or your data:
Filip Jantos
support@slowmap.app
ul. Puławska 424 skr. 69, 02-800 Warszawa, Poland