Privacy Policy

Last Updated: November 19, 2026

This Privacy Policy describes how the MapReveal mobile application ("App") collects, uses, stores and shares personal data. MapReveal is a game: you walk around and the fog over the map clears where you have been. Because the game is built on your location, we have designed it so that your location stays on your device unless you choose to create an account, and even then it is visible only to you.

By installing or using the App, you agree to this Privacy Policy. If you do not agree, do not use the App.


1. Who We Are

1.1 Controller The App is owned and operated by Spiridonov Nikolai Aleksandrovich, IP ("we," “us,” “our”). We are responsible for the personal data described in this Privacy Policy. You can reach us at mapreveal@nickswift.dev (see Section 12).

1.2 Scope This Privacy Policy applies to the MapReveal App for iPhone. It does not apply to third-party services or websites that we do not control, even if the App links to them.


2. Summary

  • You can play without an account. Without one, we do not receive your location, your map or your walks.
  • Your location is processed on your iPhone to clear the fog. It is never sent to our analytics or crash reporting. The App asks only for “While Using the App” location access; with MapReveal Pro, a walk you started keeps recording while the App is in the background, and iOS shows its location indicator while it does.
  • Without an account, your map is stored on your device and, if you keep the setting on, in your own iCloud account, which we cannot access.
  • If you create an account, your map and walk history are also stored in Google Firebase (data centers in the United States) so that you can use them on other devices. Only you can read them.
  • Nicknames are not public: your nickname is shown to your friends, to people who open your invite link and to players you send a friend request to.
  • Friends see your nickname, your totals (explored area, distance, number of walks, completed districts such as “3 of 33”, level and streak), your figures for the week, a list of up to 30 of your districts with their names and how much of each you have explored, and, unless you hide it, your collection. They never see your map, your routes, your walk history, your heatmap or your position.
  • Anyone with your invite link sees your invite card: your nickname, explored area, distance walked and number of completed districts.
  • We do not use the Advertising Identifier (IDFA), we do not track you across other companies’ apps or websites, and we do not sell your personal data.
  • You can turn analytics off in Settings and delete your account in the App at any time.

3. Information We Process

3.1 Location With your permission (“While Using the App”; the App does not ask for “Always” access), the App uses your device’s precise location to clear the fog where you walk, to measure distances, to work out which district you are in and to detect when you pass a collectible place. This processing happens on your device. When you first allow location, the App also sends your current position once to Apple Maps to build a short demo walk on real streets near you. Location access is optional: without it you can still watch a built-in demo walk, but the fog will not clear. You can change the permission at any time in iOS Settings.

Background recording (MapReveal Pro): if you have MapReveal Pro and the “Background recording” setting is on (Settings, Recording section; on by default for Pro), a walk that you started in the App keeps recording when you leave the App or lock your iPhone, with the same “While Using the App” permission. It records only a walk you started yourself, and only until you stop it, until it stops by itself after 30 minutes without movement, until you turn the setting off, or until your MapReveal Pro ends. If iOS closes the App while it is in the background, the walk ends at its last saved point and does not continue. While it records, iOS shows the location indicator in the status bar. The location is processed on your device in the same way as when the App is open. Without Pro, or with the setting off, the App does not record your location while it is in the background.

3.2 Your Map, Walks and Collection From your location the App creates and stores on your device:

  • Your map: which areas you have explored, district progress and completed districts.
  • Your walk history: for each walk, its start and end time, time zone, distance, duration, speed, the area you revealed, the cities and districts you walked in, the places you collected and a simplified line of your route.
  • Your collection: the places you have collected, with their name, type, rarity, coordinates and the date you found them.
  • Your stats and achievements: totals, level, streak and badges, calculated from the above.

This data stays on your device unless you use iCloud (3.3) or an account (3.4). If you allow Motion & Fitness access in a version of the App that asks for it, step counts and elevation gain from your device may be added to your walks; they are stored the same way.

3.3 iCloud If the “Save Map to iCloud” setting is on, the App stores a copy of your map, walk history and collection in the private iCloud database of your own Apple account (Apple CloudKit). This copy belongs to you: it counts toward your iCloud storage and we cannot see or access it. Apple’s handling of iCloud data is described in Apple’s Privacy Policy: https://www.apple.com/legal/privacy/. You can turn the setting off in the App. If you create an account or sign in, your map is kept in your account instead (Section 3.4): the iCloud setting no longer applies, and the guest copy in your iCloud is deleted once your account holds the whole map. When you sign out, the account’s map stays on your iPhone, hidden, and is deleted from the iPhone after 30 days if it is fully saved in your account.

3.4 Account (Optional) You can create an account with Sign in with Apple or with an email address and password. Accounts are provided by Google Firebase Authentication.

  • With Sign in with Apple, we receive a unique user identifier from Apple. We do not ask Apple for your name or email address.
  • With email and password, we process your email address and a securely stored password (handled by Firebase; we cannot see your password). Firebase sends emails such as password reset messages to that address.
  • Firebase Authentication may also process technical data such as your IP address and device information to keep accounts secure and prevent abuse.

When you have an account, the App stores the following in Google Cloud Firestore, in the United States multi-region (nam5): your account’s map, walk history (including the simplified route lines) and collection, your profile (nickname, creation date, the time of your last nickname change, your invite code and whether your collection is hidden from friends), and, for friends features, the data described in Section 3.5. Security rules allow only you to read and write your map and walk history. We have technical access to the database as its operator, but we do not look at your map or walks except where needed to investigate a problem you report to us, or where required by law.

3.5 Nicknames, Friends and Reports

  • Nickname: every account starts with a generated nickname (such as “Explorer_7K3Q9D”). You can replace it, and after that change it at most once every 7 days. Nicknames are not public and there is no public list of them: your nickname is shown only to your friends, to people who open your invite link and to players you send a friend request to. When you change your nickname, your previous nickname is held for you for 30 days so that no one else can take it. To enforce the 7-day limit, the time of your last nickname change is stored together with your account identifier, separately from your profile.
  • Checking nicknames: so that the App can tell you whether a nickname is free, any signed-in player can check whether a specific nickname is taken; the check also returns the internal account identifier of the nickname’s owner. It does not reveal any of your other data, and it cannot be used to find a player’s nickname from their account identifier.
  • Invites: you can invite friends with a link or a QR code that contains your invite code. To show it, the App stores an invite card in Firestore. Anyone who has your link or code can see that card, with your nickname, explored area, distance walked and number of completed districts, and can send you a friend request, so share it only with people you know.
  • Friend requests: a player who receives your friend request sees your nickname and explored area. The request stores both players’ account identifiers and nicknames, your explored area, the invite code used and the time, until it is accepted, declined or cancelled.
  • Friends: your friends can see your nickname; your totals: explored area, distance, number of walks, completed districts as “x of y” (for example “3 of 33”), level and weekly streak; your figures for the current week (new area and number of walks, used for the weekly friends leaderboard); a list of up to 30 of your districts, by name, with the percentage of each you have explored; and, unless you turn on the option to hide it, your collection: legendary and notable places by name, sets with your progress, and the number of common places. Friends never see your map, routes, walk history, heatmap or current position. To show this, the App stores a summary of these figures in Firestore while you have friends or friend requests.
  • Blocking and removing: you can remove or block a friend. Your block list (the account identifiers of the players you blocked, their nicknames at that time and when you blocked them) is stored in your account. Blocked players are no longer your friends, can no longer see your figures or your invite card, and cannot send you requests; they are not told.
  • Reports: you can report a player’s nickname. The report stores your account identifier, the reported player’s account identifier, the reported nickname, the reason you chose and the time, so that we can review it. You can report the same player once; you can report them again only after they change their nickname. We aim to review reports within 48 hours and may change or remove nicknames that break our Terms of Use. Reports are kept after either account is deleted (Section 7.3).

3.6 Purchases Purchases and subscriptions are processed by Apple through the App Store. We do not receive or store your payment card details. We receive information about your purchase (such as which plan you bought, whether it is a trial, and its status) to unlock MapReveal Pro. We may use Adapty (Section 5) to validate purchases and manage subscription status.

3.7 Analytics and Crash Reports If “Share Analytics” is on (Settings, Privacy section; on by default), the App sends usage events and crash reports so that we can understand how the App is used and fix problems:

  • Usage events: for example, that onboarding was completed, a fog style was changed, the paywall was opened or a walk was finished, with details such as durations, distances and counts. Some counts are grouped into ranges; other durations, distances and counts (for example a walk’s duration and distance, the number of newly revealed map tiles, or the size of a completed district) are sent as exact numbers. Events never contain your coordinates, map tiles, or the names of the districts or places you visited.
  • Device and app information: device model, iOS version, app version, language, approximate country or region, and a random app-instance identifier.
  • Crash reports: technical information about the state of the App and device when a crash happens.

We do not use the Advertising Identifier (IDFA) and the App does not ask for permission to track you. When you turn “Share Analytics” off, the App stops sending usage events and crash reports from that moment; events that happen while it is off are not sent later.

3.8 Remote Configuration The App downloads configuration values (for example, game settings) from Firebase Remote Config. To do this, Firebase processes a random app-instance identifier and basic device information.

3.9 Support If you email or message us, we receive your email address or messaging handle and whatever you choose to include in your message.

3.10 Sharing Cards and Exports When you share a walk card or export your walks (GPX or CSV), the App creates the file on your device and passes it to the iOS share sheet. It is sent only where you choose to send it. Check what a card or file shows (for example, a district name or your routes) before you share it.


PurposeDataLegal basis (where GDPR / UK GDPR applies)
Run the game on your device (clear the fog, progress, collection, stats)Location, map, walks, collectionPerformance of our contract with you (the Terms of Use)
Keep your map across devices and provide accountsAccount data, map, walks, collection in FirestorePerformance of contract
Friends features and nickname moderationNickname and nickname checks, invite card, friend requests, friends, summaries, block list, reportsPerformance of contract; our legitimate interest in a safe community
Unlock and restore purchasesPurchase informationPerformance of contract
Analytics, crash reports and improving the AppUsage events, device information, crash reportsOur legitimate interest in a working, improving App; you can opt out at any time
Remote configurationApp-instance identifier, device informationLegitimate interest in operating the App
Support and legal complianceMessages, data needed to answer requestsLegitimate interest; legal obligation

We do not use your data for advertising, we do not sell or rent it, and we do not “share” it for cross-context behavioral advertising (as those terms are used in California law).


5. Service Providers

We use the following service providers, which process data on our behalf and only for the purposes above:

ProviderWhat it doesMore information
AppleApp Store purchases; iCloud (your private database, which we cannot access); Sign in with Apple; Apple Maps for the base map and walking routes for the demo walkapple.com/legal/privacy
Google Firebase (Authentication, Cloud Firestore, Analytics, Crashlytics, Remote Config)Accounts, account data storage (United States), analytics, crash reports, configurationpolicies.google.com/privacy, firebase.google.com/support/privacy
Amplitude (planned)Product analytics, used only after it is enabled in an App update and only if “Share Analytics” is onamplitude.com/privacy
Adapty (planned)Purchase validation and subscription status, used only after it is enabled in an App update; it receives App Store transaction information and a random profile identifieradapty.io/privacy

When the App shows the map, Apple Maps receives the map area being displayed, as with any app that uses Apple Maps. We may disclose information if required by law, to protect the rights and safety of our users or others, or as part of a transfer of the App to a new owner who continues to be bound by this Privacy Policy.


6. International Transfers

Account data is stored in the United States, and our service providers may process data in other countries. Where data from the European Economic Area, the United Kingdom or Switzerland is transferred, our providers rely on recognized transfer mechanisms such as the Standard Contractual Clauses or the EU-U.S. Data Privacy Framework.


7. Retention and Deletion

7.1 On Your Device and in iCloud Your map, walks and collection stay on your device and in your iCloud until you erase them. Settings → Data → Erase Map deletes the map, walk history and collection from your device and from your iCloud copy. A map saved in your account is removed from our servers when you delete the account (7.2). Deleting the App removes its data from your device; your iCloud copy stays in your iCloud account until you erase the map in the App or delete it in iOS Settings (iCloud storage).

7.2 Account You can delete your account at any time in the App: Profile → Delete Account. Deleting your account permanently deletes your map, walk history and collection stored in Firestore, your profile and nickname, and your account in Firebase Authentication; for Sign in with Apple accounts, the App also revokes the App’s access to your Apple ID. You choose whether the map on your iPhone is kept as a local map or erased too. Deleting your account also deletes your friendships, the friend requests you sent and received, your invite card, the summary your friends see, your block list and the earlier nicknames held for you.

  • Your current nickname stays reserved for 30 days after deletion, without any link to your account, so that no one can take it at once; after that, anyone may choose it.
  • If you changed your nickname less than 7 days before deleting your account, the record of the time of that change (your account identifier and the time, without the nickname) remains, so that deleting an account cannot be used to get around the 7-day limit. It is not needed after those 7 days, and we may delete it at any time after that.
  • Reports that you sent or that were made about your nickname are kept (Section 7.3).

7.3 Analytics and Reports Analytics data is kept for as long as needed for the purposes above, for a limited period set in Google Analytics, no longer than 14 months for event-level data; Crashlytics keeps crash reports for up to 90 days. Nickname reports are kept for as long as needed to handle them and to prevent repeated abuse, also after the reporter’s or the reported player’s account is deleted. Aggregated statistics that do not identify you may be kept longer.


8. Your Rights and Choices

  • Location: allow or deny location access in iOS Settings at any time.
  • Background recording (MapReveal Pro): turn “Background recording” off in Settings, or stop the walk.
  • iCloud: turn “Save Map to iCloud” off in the App.
  • Analytics: turn “Share Analytics” off in Settings.
  • Collection visibility: hide your collection from friends in your Profile.
  • Account: change your nickname (once every 7 days), remove, block and unblock players, and delete your account in the App.
  • Export: with MapReveal Pro you can export your walks (GPX) and statistics (CSV).

Depending on where you live (for example under the GDPR, UK GDPR, the California Consumer Privacy Act or the Australian Privacy Act), you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict certain processing, and to withdraw consent. To exercise these rights, contact us (Section 12). We will not discriminate against you for exercising them. You also have the right to complain to your local data protection authority.

Because accounts are anonymous apart from your sign-in method, we may ask you to send your request from the email address of your account, or to perform it in the App, so that we can verify it is you.


9. Children

The App is not directed to children under 13. Accounts and friends features are intended for users who are at least 13 years old, or older where the law of your country requires a higher age to use such services without parental consent (for example, up to 16 in some EU countries). We do not knowingly collect personal data from children below these ages through accounts. If you believe that a child has created an account or provided personal data to us, please contact us and we will delete it.


10. Security

We protect data with encrypted connections (HTTPS/TLS) and with database security rules that limit access to your own data. Data on your device is protected by iOS. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.


11. Changes to This Privacy Policy

We may update this Privacy Policy, for example when we add a feature or a service provider. We will change the “Last Updated” date above, and for material changes we will let you know in the App before they take effect.


12. Contact

For questions or requests about this Privacy Policy or your data, please contact us:

This Privacy Policy is provided for information about our practices and is not legal advice.