Privacy Policy
This page is for the Diomap app (iOS and Android) and the website at diomap.com. The product was also called Local Guide and Magnus Guide. Same app.
I built this. I am not a large company. This policy is meant to be true, not impressive.
Who is responsible
Magnus Kyneb, Denmark, is the data controller. Questions and privacy requests: hello@diomap.com.
What we collect
Account
You sign in with Google or Apple. We store an account id from that provider, your email if they send us one, and the display name you choose (for example Magnus#2847).
Location
The map needs your location while you use the app. You grant that in the system permission dialog. We use it to show nearby places, load content for your area, and check that you are close enough to crack a stone, claim a place, or pick something up.
Precise coordinates are sent to our servers for those actions. We do not keep a GPS track of where you walk. We do store which map cells we have delivered to you, and coarse location cells on some activity logs (about neighborhood size, not your exact pin).
We only ask for location while you use the app. We do not request Always or background location.
Your progress
Tied to your account we store discoveries and claims, journal history, quiz answers, collectibles, gems, friends, trades, and purchases. That is how the game syncs between sessions.
Feedback
If you send story ratings, app feedback, or a quiz report, we store what you wrote.
Public map notes
You can leave a public note on the map. Those notes are emoji only — no typed sentences. People nearby can see the emoji and your display name. Journal notes are only for you.
On your device
The app caches map and story data locally so the map is faster and works with a worse connection.
Usage on our servers
We log some actions with your account id: loading a map area, cracking a stone, opening a story, playing voiceover, and submitting feedback. Those rows can include a coarse map cell, a place id, and a story id.
We have not set an automatic delete-after-X-days job for those logs yet. If you delete your account, those rows go with it.
Crashes
In release builds, Firebase Crashlytics receives crash reports (stack traces and basic device info) so we can fix bugs. Crash collection is off in debug builds.
What we do not do
- We do not record your microphone. The app plays story audio. We do not ask for microphone permission.
- We do not sell your personal information.
- We do not collect age, gender, or other demographic profile data.
- We do not currently sell location analytics to partners. If that ever happens, this page will say so first.
When you crack a stone
We send information about that place (name, location, public map data) to Google Gemini and a web-search provider so we can research it and write the story and voiceover. We do not send your email or display name to those services for that.
Why we use it
- Sign-in and keeping your account
- Showing the map and stories near you
- Saving progress, friends, and purchases
- Writing stories about places you crack
- Finding crashes
- Understanding how the app is used, from logs on our own servers
- Answering support and privacy requests
Legal basis (EEA / UK)
- Contract. Account, progress, purchases, and running the map and stories you asked for.
- Consent. Location permission on your phone.
- Legitimate interest. Crash reports, security, usage logs on our servers, and keeping the service running.
Who else sees data
We use other companies to run the product:
- Hetzner (Helsinki, EU). Our API, database, and app servers.
- Cloudflare. Website hosting and R2 storage for story audio and images.
- Google. Sign-in (if you choose Google), Gemini for stories and voice, and Crashlytics. Google’s privacy policy.
- Apple. Sign-in (if you choose Apple), App Store, and TestFlight if you install a beta.
- Mapbox. Map tiles and map requests. Mapbox privacy.
- RevenueCat, plus Apple or Google. Subscriptions and in-app purchases.
- Serper. Web search used while researching a place, not to profile you.
Some of those companies are in the United States. Our own database is in the EU.
The website
diomap.com has no advertising pixels and no analytics cookies. We store your language choice in the browser. The main site may guess your country from IP (via Cloudflare or a country lookup) only to pick a default language. The landing page loads icon fonts from Google.
How long we keep it
Account and progress stay until you delete the account, or until you ask us to delete it.
If you delete your account in the app, we delete you and your progress. Places and stories on the map stay. Your discoverer claims become free again. Open trades with you are cancelled. Apple or Google keep their own purchase records. Cancel a subscription in the App Store or Google Play. Deleting the account does not stop billing.
Backups can hold a copy for a short time after deletion. Server usage logs currently have no separate expiry clock besides account deletion.
Your choices
- Turn location off in iOS or Android settings (the map will not work fully)
- Sign out
- Delete your account in Settings. You will have to type your display name to confirm.
- Email hello@diomap.com for a copy of your data, a correction, or deletion if you cannot use the in-app flow
If you are in the EU/EEA you can also complain to your data protection authority. In Denmark that is Datatilsynet.
Children
The app is not aimed at children under 13, or under the minimum age in your country if that is higher. We do not knowingly collect personal data from children.
Changes
If this page changes, the date at the top will change. The new text applies from then. This is not “keep using the app and you agree to whatever we write later”. If a change is large, we will try to say so in the app.
Contact
Magnus Kyneb · hello@diomap.com