Effective: August 31, 2026
Privacy policy
This policy explains local game data, age-gated Google/Firebase Analytics, contextual Google Mobile Ads, and the choices available to you.
Revealscape is a general-audience family game positioned for players aged 13 and older; its content is also suitable for younger family members. It has no player accounts and game progress stays on the device. Google Analytics for Firebase remains off for an under-13 or unknown choice. For a 13+ choice, limited product and gameplay metrics are on by default and can be turned off at any time. Store builds use Google Mobile Ads to fund the game. Every ad request is child-directed, General-rated and non-personalized, while Google's consent flow is marked under-age for every player. The two targeting flags are not enabled together in one request, and the local age-band choice is never sent to ads. On iOS, Revealscape also requests Google's Limited Ads mode before the ads SDK starts.
1. Who is responsible
Revealscape is operated by an independent developer, who is responsible for information handled directly by Revealscape, including support correspondence. Google, Proton, and Cloudflare process certain information under their own terms and privacy policies. For privacy questions or requests, use the support.revealscape@proton.me.
2. Data stored on your device
The game stores the following information locally so it can work:
- progress, unlocked levels, scores, records, and collectibles;
- language, audio, motion, vibration, accessibility, tutorial, and audience preferences;
- optional reminder settings and local notification schedules;
- temporary game state needed to resume normal play.
Revealscape does not upload the saved progress record itself. When limited game metrics are enabled, selected catalog IDs, outcomes, and numeric totals derived from current play are sent under the separate rules in section 3. You can remove local progress by deleting the app and its data. Store builds exclude this local Preferences container from cloud backup and device transfer so a restored 13+ choice cannot silently re-enable Analytics. As a result, local progress does not automatically migrate to another installation.
3. Limited product and gameplay metrics
On first opening, the game asks for one broad age band. The answer is stored only on the device and is never sent to Google. An under-13 or unknown choice keeps Analytics off. A 13+ choice turns limited metrics on by default so the developer can improve levels, questions, difficulty, and collection balance. You can turn them off at any time from Settings → Audience & Privacy. Browser and developer QA modes do not send these metrics.
The allowed metrics are limited to:
- platform and app language;
- app and screen opens;
- catalog level and city IDs, attempt and result, score, duration, coverage, and bounded gameplay totals;
- question format and outcome, but never the answer selected or question text;
- collectible category, rarity, source, and aggregate counts.
Revealscape does not send a name, email, age band, exact age, birth date, account or player ID, user ID, advertising ID, contact, free text, precise location, question text, or raw answer. Google Signals, user-provided data, granular city location and device collection, and ads personalization are disabled. Analytics data is not sold or used by Revealscape for advertising or cross-service tracking.
Google Analytics for Firebase automatically assigns an app-instance identifier so it can count unique installations and retention. Google also processes product interactions, app and platform metadata, and country or region inferred from a masked IP address. The app does not request location permission. These identifiers are not advertising IDs, but stores may classify the app-instance identifier as a device identifier. See Privacy and Security in Firebase and the Google Privacy Policy.
Firebase keeps events locally while the device is offline and uploads them when a connection returns. The Analytics property is configured with two-month event and user data retention, no reset of that period on new activity, device-based reporting, no Google Ads links, and no BigQuery export. Standard aggregated reports and Google service or security records may follow Google's separate retention rules.
4. Contextual advertising
Store builds include Google Mobile Ads (AdMob) as Revealscape's source of revenue. The only placements are an optional rewarded video to continue after a failed attempt and an occasional interstitial before every third attempt in a session. There are no banners or app-open ads, ads never interrupt active gameplay, and an ad is never required to retry, use the map, or continue to the next level.
Every ad request is tagged child-directed, limited to Google's General content rating, and requested as non-personalized; Google's UMP consent flow is separately marked under the age of consent. High-engagement formats that add closing steps or viewing time are disabled. Revealscape does not send the local age band or gameplay Analytics profile to AdMob, does not request precise location, IDFA, AAID, or App Tracking Transparency, and disables Google's publisher first-party ID on iOS. On iOS, the app also signals Limited Ads before Google Mobile Ads starts, disabling personalization and features that require a local identifier.
Google Mobile Ads and its consent service may still process network-derived coarse location, IP address, device or app identifiers, advertising data, ad interactions, performance, crash, and other diagnostic information to deliver and measure contextual ads, prevent fraud, and operate the service. “Non-personalized” does not mean “no data.” Google processes this information under the Google Privacy Policy.
5. Consent and privacy choices
The first opening presents Under 13, 13+, and a non-blocking Not now choice. Under 13 and Not now keep Analytics off. A 13+ selection enables limited metrics by default with an immediate opt-out in Settings → Audience & Privacy. Changing the band to Under 13 or turning metrics off disables collection and asks Firebase to reset local Analytics data and its app-instance identifier. It cannot recall data already processed by Google.
This choice never blocks levels, retries, the map, collectibles, or any other core feature. The game also continues normally when offline or when Analytics is unavailable. The age-band control governs Analytics only. Ads use the same conservative treatment for everyone; where Google's consent platform requires a privacy-options form, it is available from Settings. With no consent, network, or inventory, the game continues and simply skips the ad.
6. Messages you send us
If you email support, we receive your email address, message, and any attachment you choose to send. We use that information only to answer you, troubleshoot the game, or investigate a technical or privacy issue.
Support email is hosted by Proton, which processes email under its privacy policy. Please do not include sensitive personal information.
7. Age bands and families
Revealscape is a general-audience family game positioned for players aged 13 and older, while its content may be suitable from age eight. It is not listed in Apple's Kids Category. A person under 13 can still play the complete game. The broad first-opening choice configures metrics only; it is not age verification.
The game does not collect or transmit a birth date, exact age, the locally selected age band, name, email from gameplay, account, precise location, contacts, photos, or microphone access. Analytics stays off for under-13 and unknown choices. A parent or guardian can change the local band or analytics option in Settings and can contact us about any privacy concern involving a child.
Advertising does not switch to a more invasive mode for a 13+ choice. All players receive the same child-directed, General-rated, non-personalized requests and under-age UMP flow. The iOS build additionally requests Limited Ads for every player.
8. Retention and deletion
- Local game data remains until the app data is removed. Store builds exclude it from backup and device transfer to avoid restoring a stale audience choice.
- Google Analytics event-level and user-level data is configured for two-month retention. Standard aggregated reports and Google service or security records may be retained under Google's own rules.
- Support correspondence is kept only as long as reasonably necessary to answer the request, troubleshoot, maintain security, comply with law, or resolve a dispute. It is deleted or anonymized when it is no longer needed for those purposes.
To request deletion of a support conversation, use the support.revealscape@proton.me. You may also contact us about Analytics data; the app does not have an account or developer-assigned user ID that reliably identifies one person in Google's processed reports. Limited information may be retained where required by law or necessary to protect legal rights.
9. Regional rights and international processing
Depending on where you live, you may have rights to access, correct, delete, restrict, or object to processing of personal information. Contact us for support information we control. Use the in-game metrics option to object to future Analytics collection. Google, Cloudflare, and Proton may process service data in other countries as described in their policies.
10. This website
The public legal and support pages have no account, contact form, advertising, or web analytics. Visiting a public page does not activate the app's Firebase Analytics. Cloudflare delivers and protects this website and may process an IP address, browser or device information, request metadata, and security events under the Cloudflare Privacy Policy.
11. Security and policy changes
Revealscape minimizes collection by keeping progress local and operating without player accounts, developer user IDs, precise location permission, or requested IDFA/AAID. Analytics access is limited to the developer's Google account, and the event contract allows only bounded game data. No system is completely risk-free, but we restrict the data, retention, and access and use established service providers.
This policy may be updated when the game, its data practices, or legal requirements change. The effective date at the top identifies the current version.