We keep one small database on Google Firebase for the public leaderboard and bug reports, nothing else. Your saves, your run history, and your settings live on your device. The leaderboard runs through the in-game Compete setting, which is on by default and which you can turn off at any time (what Compete off does). A bug reportleaves your phone only if you write one and tap Send.
Who this covers
This policy applies to the mobile apps published by Darktier Studios, LLC on Google Play — currentlyDelve, Die, Repeat (package com.darktierstudios.delvedierepeat). Our website and browser-based tools are covered separately by thewebsite privacy policy.
Data we collect
Darktier Studios, LLC runs the one small database described above, and nothing else. The only personal information involved is the Google Play Games name you chose in Google Play Games, which appears on the leaderboard beside your runs (next section). Beyond that, our apps do not collect, transmit, sell, or share:
- Your real name, email address, phone number, or address (we never ask Google for them)
- Location data, precise or approximate
- Financial or payment information
- Contacts, calendar, photos, videos, audio, or files
- Gameplay analytics, or automatic crash and diagnostic reports from our own code
- Device identifiers or the Android Advertising ID
The game sends data in only two cases: the leaderboard data described in the next section, only while Compete is on; and a bug report you write yourself, only when you tap Send, described underBug reports. Achievements, with Compete on and you signed in, go to Google Play Games, which is Google's service and not ours, under your own Play Games account. Google's own Play Games software, which runs while Compete is on, also collects a little data of its own. Both are described under Google Play Games.
Our leaderboard (Compete)
Delve, Die, Repeat posts your finished runs to a public leaderboard — deepest descent, longest-lived, most kills, and fattest purse — so you can see where you placed against everyone playing, under yourGoogle Play Games name. This runs through the in-game Competesetting, which is on by default, needs you to be signed in to Google Play Games, and which you can turn off at any time.
- Your Google Play Games name: the gamer name, a nickname, that you chose in Google Play Games. It appears publicly beside each of your runs on the leaderboard. You change it in Google Play Games, not in our game, and the board shows the new one after you sign in again. If a name contains a word from our safety list, the board shows a neutral placeholder instead, and we can hide a run. We never ask for the real name or email of your Google account.
- Your game ID: a random Firebase account ID the game creates for you, which Firebase Authentication links to your Google Play Games player ID when you sign in with Compete on. The player ID is never shown to anyone else. The ID carries no email, phone number, device identifier, or advertising ID. It's created when Compete is on and you send your first run, or anonymously, with no link, when you send a bug report.
- How the name gets onto the board: when you sign in, a Google Cloud Function in our one small Firebase project asks Google's sign-in service to confirm your Google Play Games name, and records it next to your game ID, so the board's names stay current and cannot be faked from a phone.
- The run details we send: for each run that ends while Compete is on, we send your game ID, your Google Play Games name, and the run's own details:
- the season
- your adventurer's name (rolled by the game, not yours), race, class, and sub-class
- level, the floor you reached, the days you survived, the squares you walked, your kills, the wilmst you carried, and your experience
- your cause of death, what killed you, and your epitaph
- the time of death, the app version, the dungeon's random seed, and the turn count
- a fingerprint of the run, and the ranking numbers worked out from the fields above — not new information
- When it's sent: as each run ends, while Compete is on — queued on your phone and sent the next time you're online, and held until you are signed in to Google Play Games. Once only, the first time Delve, Die, Repeat 2.3 starts with Compete on, the game also re-sends runs from your own list of runs sent with Compete on that never reached the board, and your earlier 2.2.0 runs move under your Google Play Games name.
- Who sees it: the leaderboard is public. Any other player can see your Google Play Games name and your runs, including the epitaph and the cause of death.
- Where it goes: our one small database on Google Firebase, which stores it for us as our service provider. We never sell it.
- With Compete off: Nothing is sent. The Play Games software never starts when you open the game, so no Google Play Games sign-in is asked for and no game ID is created. Any runs still waiting to be sent are thrown away, and runs you finish while Compete is off are never uploaded later, even if you turn Compete back on. If you turn Compete off while the game is open, it takes full effect the next time you open the game: Play Games stays signed in until the app closes, and nothing reaches the board. Compete must be on to reach the board, and so to erase anything already sitting there.
- Erasing your runs: ERASE MY RUNS, in the account block, deletes every run of yours on the board, in every season, deletes the board name we recorded for you, and deletes your game account together with its Google Play Games link. Your local run history stays on your phone. Signing in again and sending a run later starts a new game account under your Google Play Games name. To cut Google's side too, disconnect the game in Google Play Games settings.
- Forged runs: we remove runs that look forged or tampered with, and we can stop a game ID from posting again.
- Retention: your runs stay on the board until you erase them or we remove them. Runs from past seasons stay in our database after a season ends, unless you erase them.
- Finding the account block: in the dungeon, open the ☰ menu; on the title screen, tap the corner chip. From there: COMPETE, SIGN IN (when you are not signed in to Google Play Games), and ERASE MY RUNS.
Versions before 2.2 posted scores to Google's own game leaderboards, which are being retired and deleted. Version 2.2.0 showed a rolled @name instead of a Google Play Games name; those runs stay on the board under that name until their owner updates and signs in, and then they move.
Google Play Games
With Compete on, the game signs you in with Google Play Games. From version 2.5, with Compete on and you signed in, the game also sends your achievement unlocks, reveals, and progress counts (for example, 37 of 50) to Google Play Games, which shows them in your Play Games profile under your own Play Games account. Achievements you earn while Compete is off, while you are signed out, or while you are offline wait on your phone and are sent the next time Compete is on and you are signed in. We do not use Google leaderboards or saved games. Google's own Play Games software runs inside the app while Compete is on and collects data automatically: your gamer identity (gamertag and avatar, which our game never reads or shows), plus analytics and diagnostics data that Google uses to keep its software stable. That data goes to Google, not to us, under Google's own terms and privacy policy; Google describes it atdeveloper.android.com/games/pgs/data-collection. With Compete off, the Play Games software does not start, so it collects nothing (details). ERASE MY RUNS does not remove achievements held in Google Play Games, which are Google's data: you can delete your Play Games account and its data, achievements included, in your Play Games profile or Google MyAccount.
Bug reports
Delve, Die, Repeat has a REPORT A BUG option in its ☰ menu. Nothing is sent unless you type a report and tap Send. A report contains what you typed, the game's in-run log (the Oracle, which may include your adventurer's randomly generated name), the app version and build, your device model and Android version, and a summary of the current run (floor, class, race, level and turn count). It carries no account, email address, or other contact detail.
Sending a report uses your anonymous game ID only as the key of a small limit record — the time of your last report, the day, and a count — that enforces a short cooldown and a daily cap on reports; that record is deleted automatically about 2 days after your last report. The report itself does not carry the game ID.
Reports are stored in the game's Google Firebase project and posted publicly as issues on the game's GitHub repository (github.com/sheibeck/ddr), where anyone can read them, so please leave out anything private. A report is deleted from our database once it's filed (30 days at most either way), and the public GitHub issue is deleted on request — follow the steps on our delete your datapage or contact us.
Data stored on your device
The game keeps a small amount of data on your phone so it works: your current run, your local run history (YOUR DEAD), your personal best records, your settings (including Compete), your game ID and Google Play Games name, your achievements record with the short list of what has already reached Google Play Games, and, while you are offline, the short list of runs waiting to be sent to the leaderboard. None of it is sent to us except as described above, and it is removed when you uninstall the app — except runs already on the leaderboard, which stay there until you erase them (see delete your data).
One small database, no ads, no analytics
Our apps require no account of our own and play fully offline. They contain no advertising, analytics, or crash-reporting SDKs of our own. The only network calls our code makes reach Google Firebase over plain HTTPS — with no Firebase SDK bundled in the app — for the leaderboard, your board name, and bug reports, all described above; Google's Play Games software makes its own, including the achievement updates described above, only while Compete is on. Google Play handles your purchase and installation underGoogle's privacy policy.
Permissions
Our apps do not request access to your location, contacts, camera, microphone, storage, or any other permission-gated data. The one permission is internet access, used only for the leaderboard and achievements while Compete is on (Play Games sign-in, the board, and achievement updates), and for sending a bug report when you tap Send.
Children
Our apps are suitable for general audiences. We collect no email addresses or other contact details from anyone, including children under 13. The only name the board shows is the gamer name a player chose in Google Play Games, which Google governs, including its supervised accounts, whose names Google generates; there is no chat or messaging of any kind. The game needs no sign-in to be played, and Compete, which is the only thing that uses Google Play Games (sign-in, the board, and achievements), can be turned off at any time.
Your rights
We hold the runs you sent to the leaderboard while Compete was on, and any bug report you chose to send. ERASE MY RUNS, in the game, removes your leaderboard runs, your board name, and your game account yourself. It does not remove achievements held in Google Play Games; those are Google's data, deleted in your Play Games profile. Or email us with your Google Play Games name and we will delete them and confirm. Uninstalling the app deletes everything stored on your device. If a future app ever changes any of this, this policy will change first.
Data safety summary
For the Google Play Data safety section, Delve, Die, Repeat declares: Name (your Google Play Games name, shown publicly beside your runs) — collected, not shared, optional (turn Compete off), used for App functionality, encrypted in transit, and deletable with ERASE MY RUNS. User IDs (the game's Firebase account ID, linked to your Google Play Games player ID when you sign in with Compete on; the player ID is never shown) — collected, not shared, optional (created only when Compete is on and a run is sent, or when you send a bug report), App functionality, encrypted in transit, and deletable with ERASE MY RUNS.App activity (your Google Play Games name and the run details listed above, sent for each run while Compete is on, plus achievement unlocks, reveals, and progress counts sent to Google Play Games while Compete is on and you are signed in) — collected, not shared, optional (turn Compete off), App functionality, encrypted in transit, deletable, and public on the leaderboard.Diagnostics and Photos collected by Google's own Play Games software while Compete is on (the data Google's page lists: analytics, diagnostics, and the avatar half of your gamer identity; our game never reads the avatar) — optional, because Compete can be turned off (what that does). Other user-generated content (the bug report you type, sent only when you tap Send) — collected, not shared, posted publicly on GitHub, deleted from our database once filed. Diagnostics (the Oracle log, app version and build, device model and Android version, and a summary of the run, attached to a bug report only) — collected, not shared, deleted on request. None of it is sold.
Changes to this policy
If we update this policy, the new version will be posted at this address with a new effective date. Material changes to what an app collects will also be reflected in that app's Google Play listing.
Contact
Questions about this policy: sheibeck@gmail.com
Darktier Studios, LLC · Grand Rapids, MI