Privacy Policy for Ritual Descent

Last updated: 19 September 2026

Ritual Descent ("the game") is a single-player dungeon game. This policy explains what data the game collects, why, and what you can do about it.

The game is playable offline and without an account. You are never asked to sign in, and you are never asked for your name, email address, or any other personal detail.

Who is responsible: Mzeva Dust
Contact: mzevadust@gmail.com


The short version


What the game collects

1. Player identity and scores

When you complete a run, the game sends it to our leaderboard server so scores can be recorded and ranked.

What is stored:

DataWhy
A random player IDAttributes runs to the same player across sessions. Generated on your device; it is not derived from any device identifier and is not linked to your identity.
A display nameShown on the leaderboard. Generated at random on your device, not chosen by you and not derived from any personal detail.
A secret, stored only as a one-way hashProves a later submission comes from the same device that claimed the ID, so nobody can submit scores as you. The secret itself never leaves your device in a readable form.
Your run resultsScore, completion time, remaining light, times hit, whether a companion was present, floor number or daily date, and the time the run completed.
TimestampsWhen the player record was created and last seen.

Your display name is public. It is stored so it can be shown on a leaderboard alongside your scores. It is generated at random on your device and identifies nobody.

When the leaderboard is switched on you will be able to change it. If you do, choose a name that is not your real name, your email address, or anything else that identifies you. Names are checked automatically, and names that are offensive or that impersonate the developer are rejected.

At the time of writing, the in-game global leaderboard is not switched on, so no player sees another player's name inside the game. Scores are still collected and stored so the leaderboard is populated when it is enabled. This policy will be updated before that changes.

This data is stored by Supabase, our database and server provider, acting on our behalf. Supabase's own systems log technical request information, including IP addresses, as part of operating the service. We do not store your IP address in the game's own tables and do not use it.

2. Crash and error reports

If the game crashes or hits an error, a report is sent so the bug can be fixed. This uses Firebase Crashlytics, provided by Google.

A report contains the error and where in the code it happened, plus a small amount of game context: the floor you were on, the game and difficulty state, and how long the session had been running. Crashlytics also collects standard device information such as the device model, operating system version, and a Crashlytics-generated installation identifier.

Crash reports deliberately contain no player ID and no display name. Your leaderboard identity is not connected to crash data.

Reports are stored on your device if you are offline and sent later when a connection is available.

3. Advertising

The game shows ads, provided by Google AdMob. Ads appear between runs, and you may optionally choose to watch an ad in exchange for an in-game reward.

To serve ads, Google may access your device's advertising ID and related technical information. Google may use this to show personalised ads, depending on your consent and your device settings.

In the European Economic Area, the United Kingdom, and Switzerland, you are shown a consent form before personalised ads are used, using Google's official consent tool. You can change your choice at any time from the game's settings menu, under Privacy Options.

You can also reset or delete your advertising ID at any time in your device's Android settings, under Settings → Privacy → Ads.

Google's own handling of this data is described at https://policies.google.com/technologies/partner-sites.

4. Data stored only on your device

Your settings, local records, progress and the identity described above are stored on your device. If you have Android Backup enabled, Android may include this in your Google account backup so a new device restores your progress. That backup is controlled by you and Google, not by us, and can be turned off in your device settings.


What the game does not do


Children

The game is not directed at young children and is not part of Google Play's Families programme. We never ask for an age or a date of birth.

Ads are the one place age makes a difference, and that is handled by Google rather than by us: the ads shown depend on the age signals attached to the Google account and device, including any Family Link supervision.

If you are a parent or guardian and want a child's data removed, delete it in the game under Records → My Data, or email mzevadust@gmail.com with the display name they played under.


Your rights and how to delete your data

The reliable way: delete it from inside the game. Open Records and use Delete my data. This removes your display name and every stored run from our server, and stops anything further being uploaded, so you are opted out of the leaderboard completely. Your records on your own device are kept, and you can start uploading again later if you want to.

If you have already uninstalled, email mzevadust@gmail.com with the display name you played under and we will remove the record.

Uninstalling the game stops all collection and removes the identity stored on your device, but it does not delete scores already sent to the server.

Data is kept for as long as the leaderboard operates, or until you ask us to delete it.


Third parties

ProviderPurposeTheir policy
SupabaseLeaderboard database and serverhttps://supabase.com/privacy
Google (AdMob)Advertisinghttps://policies.google.com/privacy
Google (Firebase Crashlytics)Crash reportinghttps://firebase.google.com/support/privacy
Google PlayApp distributionhttps://policies.google.com/privacy

Changes

If this policy changes materially, the "last updated" date above will change and, where the change is significant, the game will say so.

Contact

mzevadust@gmail.com