Re:Visit beta privacy policy
Re:Visit is an app that tells you the history of the places around you. It is in a test (beta) phase run by its founder. This policy explains what we collect, why, who we share it with, how long we keep it and what you can do about it. When the app launches publicly it will be run by a UK company and this policy will be replaced. We will tell you in the app before that happens.
Who is responsible
Christopher Gorman
Burgauerstr. 68, 81929 Munich, Germany
Email: chris.w.gorman@gmail.com
During the beta, Christopher Gorman decides how your data is used (the "controller").
What we collect and why
| What | Why | Legal basis |
|---|---|---|
| Account: email address, password (stored only as a secure hash) or your Sign in with Apple identity | To create your account and let you sign in | Needed to provide the app (contract) |
| Your location while you use the app, if you allow it | To find historical places near you, plan journeys and confirm a check-in at a place | Contract. You can turn location off in iOS Settings at any time. |
| Places you open or check in at, saved journeys and story sessions | To keep your history and journeys in the app | Contract |
| Chats and questions you write to the AI guide | To answer you and keep your conversation | Contract |
| Photos you take with "Identify" | To recognise the building or place in the photo. The photo is used to answer and is not stored in your account. | Contract |
| City pack requests: the city (and country) you ask for, linked to your account and its email address | To decide which city packs to build next and email you when the city you asked for is ready. The founders review requests, with your email, on a password-protected page on our server. | Contract, as you asked us to tell you, and legitimate interest in building the cities people want |
| Interests and optional profile notes | To pick stories that suit you | Contract |
| Optional feedback in the app or through TestFlight | To fix mistakes and improve the app | Legitimate interest in a working, accurate app |
| App usage and performance, linked to your account: the days you used the app, your app version, and for each AI request its type, how long it took, how much text it processed (tokens) and what it cost. No content. | To keep the beta fast and affordable, find features that are slow or failing, and see who needs to update | Legitimate interest in a working, affordable app |
| Response times for features such as nearby places, chat and stories, with the result (for example, worked or timed out) | To find and fix slow features. These records are not linked to your account. | Legitimate interest |
| Crash and error reports when the app or our server fails: the error and where in the code it happened, the app and iOS version, the device model, and recent app activity such as the app opening or closing. We remove account details and email addresses and do not include location, chats or screenshots. | To find and fix crashes and errors. These reports are not linked to your account and are stored only on our own server. | Legitimate interest in a working app |
| IP address and technical request data | To keep the service secure and stop abuse | Legitimate interest |
About location. We do not record a continuous location track. We keep the places you opened, checked in at or saved in a journey. Together that is a rough history of where you have been, linked to your account. Journey positions are stored to about 11 metres.
We use app usage and performance data only to run and improve Re:Visit. We don't use it to track you across other apps or websites, and we don't share it with other companies.
We don't sell your data, and we don't use your chats to train AI models.
About ads. The beta has no ads. We plan to show ads in the future. Before that starts, we will update this policy, tell you in the app, and ask for your consent where the law requires it.
AI in Re:Visit
An AI guide writes stories, chat replies and summaries from the sources shown with them, and illustrations are AI-generated. AI can be wrong, so check the sources. See Settings › AI and your data in the app.
Please keep chats about history. Re:Visit is a history app, not a place for private matters. Don't tell the AI guide about your health, money, religion, politics, sex life or other sensitive topics, and don't share details that identify you or other people, such as full names, addresses or phone numbers. Your chats are stored with your account and sent to AI providers to write an answer.
Where your data is stored
The app's server and database run on a computer at the founder's home in Germany. Traffic reaches it through Cloudflare's secure network. Backups are kept on a private storage device, also in Germany.
Who we share data with
| Provider | What they receive | Where |
|---|---|---|
| OpenRouter, which passes requests to AI model providers such as Google (Gemma) | Place details and your question or photo, to write an answer. Requests use OpenRouter's zero-data-retention routing. | USA |
| Brave Search, Parallel | Search queries about places (no account details) | USA |
| Wikipedia / Wikimedia | Requests for public articles about places | USA |
| Brevo | Your email address, to send sign-in and password emails | EU (France) |
| Cloudflare | All app traffic passes through Cloudflare's network | Global |
| Apple | Sign in with Apple, TestFlight and feedback you send through TestFlight | USA |
Where data goes outside the EU, we rely on the provider's data protection agreement with standard contractual clauses, or the EU–US Data Privacy Framework where the provider is certified. We share data with authorities only where the law requires it.
How long we keep it
| Data | How long |
|---|---|
| Account, places, journeys, chats, interests | Until you delete your account |
| City pack requests | Until you withdraw the request in the app or delete your account |
| App usage and AI usage records linked to your account | Until you delete your account |
| Response times (not linked to your account) | 90 days |
| Crash and error reports (not linked to your account) | 90 days |
| IP-based rate-limit counters | 8 days |
| Server logs | Rotated automatically and cleared each time the server is updated |
| Database backups | Up to about 3 months. A separate offsite disaster-recovery copy is kept longer. |
When you delete your account, everything linked to it is deleted from the live database straight away. Backups are only used to recover from a system failure, never to restore a deleted account.
Your rights
You can ask to see, correct, delete or export your data, to object to or restrict how we use it, and to withdraw consent where we rely on it. You can delete your account yourself in Settings › Profile & interests. For anything else, email chris.w.gorman@gmail.com. We answer within one month.
You can also complain to a data protection authority, for example the one where you live, or the one responsible for the operator: Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Ansbach. In the UK, you can contact the Information Commissioner's Office.
Children
The beta is not meant for anyone under 16.
Security
Passwords are stored as secure hashes, traffic is encrypted, and only the founders can access the server.
Changes
If we change this policy in a way that matters, we will tell you in the app before the change applies.