Last updated 10 November 2026
Privacy
Guided Tours needs to know where you are in order to work — that is the whole product. This page explains exactly what that means in practice, what leaves your phone, and how to stop it.
Who is responsible
Guided Tours is operated by Krzysztof Kałamarski, a business registered in Poland. For any question about this policy or your data, contact hello@guidedtours.app.
What is collected
Your account
There are two ways to sign in, and neither uses a password.
- Sign in with Apple. We store the stable identifier Apple gives us for you, which lets us recognise you across sessions and devices. Apple may also share your name and email address with us, the first time you sign in. You can choose Apple’s private relay address instead of your real one.
- Email. You enter your email address and we send you a 6-digit code to type in. We store the address so we can recognise you the next time you sign in.
If you have a display name, it is shown publicly as the credit on a photo you contributed, once that photo has been accepted into the catalogue (see “Photo contributions” below). If you have none, a default credit is shown instead.
Location
The app asks for background (“Always”) access to your precise location. This is what lets narration begin on its own as you arrive at a stop, with the app closed and your phone in your pocket.
Your position is evaluated on the device. Guided Tours does not stream a continuous location trail to its servers. What is recorded on the server is the start point of a walk you build, and which stop you reached and when — not a track of everywhere you went.
Free roam. If you turn on Free roam, the app watches your position in the background and asks the server for places with a story near you, so it can notify you when you pass one. The server uses your position only to answer that request. It is not saved to your account and it is not kept as a location history.
If you decline background access, the app still works: you trigger each stop’s narration yourself instead of it starting automatically.
How you use a tour
The app records events about tour playback — stops reached, narration played, skipped, or abandoned, and how far through a tour you got. This exists for one reason: to find out where tours lose people, so they can be made better.
You can turn this off. There is an analytics opt-out in the app’s settings. With it enabled, these events are no longer collected.
Problem reports and walk ratings
If you report a problem, we store your note (free text), the walk and stop it was about, and when it happened. You can also attach a photo: you pick it yourself in the system photo picker, and the app never browses your photo library. An attached photo is kept privately for review and is not shown to anyone else. After a walk you can rate it, and add a short optional note about what was off. These are linked to your account and are used to fix the catalogue.
City requests
If you ask for a city that is not covered yet, what you typed is stored with your account, so we can decide which cities to add next and let you know when one opens.
Photo contributions
If you choose to, you can photograph a place that has no picture yet and submit it to the catalogue. Apart from the optional photo in a problem report (above), this is the only camera or photo-library access the app has, and it only happens when you deliberately start a submission — the app never reads your photo library or camera roll on its own.
A submitted photo is reviewed before it is shown to anyone else. If it is accepted, it becomes part of the public catalogue for that place under the rights grant you agree to at the moment you submit — the same screen tells you what that grant covers. An accepted photo stays in the catalogue even after you delete your account (see “Your rights” below): it was contributed under that explicit grant specifically so the catalogue could keep relying on it, and removing it would silently take a picture away from every other person using the app. What changes is that the photo’s link to you, as its contributor, is removed.
Beta waitlist signups
The website at guidedtours.app has a form to join the TestFlight beta waitlist. If you use it:
- What is stored: the email address you submit, lowercased, and the page path you submitted it from (for example, which city page led you here). Alongside it: which signup form you used (for example, the one at the top of the home page or the one at the bottom), the page you first arrived on during that visit together with the name of the site that referred you and any campaign tags in the link you followed, your device type (iPhone, Android or computer, worked out from the browser identification your browser sends, which is not stored), and the random page code described under “Website pageviews and interactions” below, which links your signup to that day’s record of your visit. Once linked, that record is pseudonymous rather than anonymous: it does not name you, but it can be connected to the address you gave.
- Rejected attempts: submissions caught by the form’s spam checks, and repeat submissions of an address that is already on the list, are counted so we can see how often they happen. The address itself is not stored for them. What is kept is the reason, the form used, the page path, the daily one-way visitor code and the random page code described below. Those two codes link the attempt to that day’s record of your visit.
- Why: to contact you when TestFlight beta access opens, and to understand which pages on the site lead people to sign up.
- Where: in the project’s own Postgres database, on its own server. When we email you, the message is delivered through Resend (see “Services that process data” below). The list itself is not kept with a third-party mailing-list provider.
- Marketing email only if you ask for it. The form has an unticked box for occasional news about new tours and features. Marketing email goes only to people who ticked it, and every such email can be unsubscribed from. Email that is essential to the beta you signed up for, such as your invite, still arrives.
- Removal: to have your submitted address removed, contact us at the address above.
Website account and beta city choices
You can sign in on the website’s account page with the same email code as in the app (Sign in with Apple is not offered on the website). Signing in with an email creates the same account the app would. Invitation emails can carry a one-time sign-in link instead of a code. If you sign in:
- The sign-in cookie: the account page is the only part of the site that uses a cookie. After you sign in, the project’s server at api.guidedtours.app sets one sign-in cookie that the page itself cannot read. It is used only to keep you signed in to your account (other pages of the site ask the server whether you are signed in, so they can show “My account” and stop offering the beta waitlist to someone already on it), lasts at most 30 days, and is removed when you sign out or delete your account. It is never used for analytics or advertising. The rest of the site still sets no cookie.
- What is stored: the cities you are willing to test the beta in and, if you give it, when you plan to be there; whether you have an iPhone; the email address you want your TestFlight invite sent to, if it differs from your account email; your preferred language (English or Polish); and your email choices. A city you suggest is stored as a city request (see “City requests” above). If your email is already on the beta waitlist, your waitlist signup is linked to your account.
- One-time sign-in links: only a one-way fingerprint of each link is stored, never the link itself. A link works once and expires after 7 days.
- Why: to invite people to the TestFlight beta in the cities they chose, and to see which cities to prepare next.
- Removal: the account page has a “Delete my account” link, which removes your account, your city choices and your sign-in sessions.
Website pageviews and interactions
The website at guidedtours.app also keeps a simple record of which pages people visit and how they use them. It does not identify you on its own. If you sign up for the beta, your signup is linked to that day’s record of your visit, so that record becomes pseudonymous data connected to your email address (see “Beta waitlist signups” above). Every page you view on this site, including a page reached without a full page reload:
- What is stored: the page path you viewed, the name of the site that referred you here (if any), any campaign tags carried in the link you followed, an approximate screen width, the approximate country the visit appears to come from (a two-letter country code, worked out from your IP address), and a one-way code that stands in for “one visitor”, rebuilt from a new secret every day. Also your device type (iPhone, Android or computer) and whether the page opened inside an app’s built-in browser, such as Instagram’s or Facebook’s. Both are worked out from the browser identification your browser sends with every request; that identification itself is not stored.
- How you use the page: how far down the page you scroll, in steps (a quarter, half, three quarters and so on); which sections and signup forms came into view; how long you were active on the page (counted only while the page is visible and you have recently scrolled, tapped or typed); which marked buttons and links you used, recorded as fixed labels we chose, never as text from the page or anything you typed; the site name of any external link you followed; repeated rapid clicks in one spot; whether you focused a signup form, started typing in it, submitted it and what the outcome was (never what you typed); the choices you made in the sample tour builder; and which questions you opened in the FAQ.
- The page code: all of this is tied together by a random code made up for each page you view. It is held only in your browser’s memory while the page is open and disappears when you leave; it is never saved on your device.
- What is NOT stored: no cookie (the only cookie on the site is the sign-in cookie of the account page, described above, and it is never used for this), no browser storage of any kind, no IP address, and no full referring URL — only the referring site’s name. Nothing you type is recorded, there is no screen recording, and no third-party analytics service is used: all of it goes to the project’s own server. The country is as specific as it gets: never a city, a region, or a location on a map.
- Why: to see which pages and which parts of the site lead people to sign up for the beta waitlist, where people lose interest, and roughly where in the world visitors are coming from.
- The daily code: because that one-way code is rebuilt from a new secret each day, the same person cannot be followed from one day to the next.
- How long: the records of how you used a page (scrolling, sections, clicks, form steps and rejected signup attempts) are deleted after 180 days. The pageview records themselves have no fixed retention period.
- How the country is worked out: your IP address is looked up against a locally-held country database at the moment the visit is recorded, and the address is discarded immediately afterwards — it is never saved.
The web server that hosts this site also keeps its own short-lived access logs, the way most web servers do, with the visitor’s address partially masked.
Place pages also embed a small map showing where the place is. Loading one of those pages fetches map tiles directly from the OpenStreetMap Foundation’s tile servers, so those servers receive the same request any image load produces — your IP address and the address of the page you’re viewing. How the OpenStreetMap Foundation handles that is described in its own privacy policy.
What is not collected
- No advertising identifiers, and no third-party ad or tracking SDKs.
- No contacts or microphone access, and no camera or photo-library access beyond the deliberate photo-contribution flow described above.
- No continuous background location history.
- Your data is never sold.
How narration is made
Tour narration is written and voiced in advance from public, openly licensed sources — see the attribution page. Generating it uses third-party AI services, but they receive only that public source material about places. Your personal data is not sent to them.
Services that process data
- OpenAI writes the stories and voices the English narration. It receives only public source material about places, never personal data.
- Google Cloud voices the Polish narration. It also receives only public source material about places, never personal data.
- Resend delivers email: sign-in codes, and any other email the service sends you. It receives your email address and the message.
- Apple WeatherKit supplies the weather on the home screen. Your phone asks Apple for the weather at the city’s centre, not at your own position.
Where data is held
Data is stored on servers operated for Guided Tours in the European Union. Access is limited to the operator.
Legal basis and retention
- Your account — necessary to provide the service you asked for. Kept until you delete your account.
- Location — processed with your consent, which you give through the iOS permission prompt and can withdraw at any time in iOS Settings.
- Usage events — our legitimate interest in improving tours, subject to the opt-out described above.
- Problem reports, walk ratings and city requests — our legitimate interest in fixing the catalogue and choosing which cities to add. We have not fixed a specific retention period for them: the honest answer today is that they are kept until you delete your account or ask for removal.
- Website analytics — our legitimate interest in understanding which parts of the site lead people to join the beta. Records of how a page was used are deleted after 180 days; pageview records have no fixed retention period.
- Beta waitlist email — your consent, given by submitting the form. We have not fixed a specific retention period beyond it: the honest answer today is that it is stored until beta access opens or you ask for removal.
Your rights
Under the GDPR you can request access to your data, correction, a portable copy, or object to processing. To exercise any of these, contact us at the address above.
Account deletion is available directly in the app, from the Account screen — it does not require contacting us. Deletion is immediate: the moment you confirm it, your account record, your saved items, your usage events, and your tour history are gone, and any photo submission you had pending review is withdrawn. If you had signed in with Apple, we also ask Apple to revoke the sign-in grant you gave us. Two things are not removed, deliberately: a photo you contributed that had already been accepted into the catalogue stays there, with only your link to it removed (see “Photo contributions” above); and your credit history keeps its record of what was earned, with only the link to you removed, so the ledger’s own totals stay accurate. Signing in again afterwards creates a new account, never your old one restored.
Children
Guided Tours is not directed at children under 13, and we do not knowingly collect their data.
Changes
If this policy changes in a way that affects what is collected or why, the date at the top will change and the update will be noted in the app.