Privacy Policy

Doldari Do

This app has no accounts. Records stay on your device, and on iPhone in your iCloud too. Two things leave the app: the device information Google's ad SDK sends when it fetches the rewarded ad, and a few counts that tell us what to fix. This website counts visits with Google Analytics — which page was opened, how often. None of it is tied to what you do in the app.

What the app sends out

The ad

Tapping the coin slab on the end screen plays an ad that doubles that run's coins. To have one ready, the app asks Google AdMob for one when it launches. What the ad SDK sends to Google at that point is roughly:

How Google handles this is described in How Google uses information from sites or apps that use our services and the Google Privacy Policy. In the European Economic Area and the UK a consent form appears once before the first screen (Google User Messaging Platform). Decline and the app won't request ads and the slab won't appear; the game runs the same. You can change your choice in Settings at any time.

There is no server of ours. The ad SDK and Firebase may send diagnostic information such as crashes or performance to Google on their own, but the app collects and sends no crash reports of its own. There is no name, email or account to begin with.

How often things happen

To know what to fix, the app counts things with Google Analytics for Firebase. What goes out is a mark saying something happened plus a few numbers with it. Nothing in it points to a person.

Your scores, coins and characters themselves are never sent. Those stay on your device (and in your iCloud on iPhone). No name, no list of records, no record of which stone you stepped on. Firebase sends along one per-device mark, which disappears when you delete the app and is not linked to any other app. On iPhone the app never asks to track you, so the advertising identifier (IDFA) is not used here either. On Android, Firebase may also receive the advertising ID mentioned above.

What the app keeps on the device

These live in the app's own storage and are deleted with the app.

iCloud and backups

On iPhone, records, coins, characters and settings sync across devices on the same Apple account through Apple's iCloud key-value store. That storage is between you and Apple; we can't read it. Turn iCloud off on the device and the app works locally only. If you back up your device, the app's storage may be part of that backup, which is likewise between you and Apple.

On Android there is no syncing between devices yet. Records live only on that device and are not included in device backups, so deleting the app deletes them too.

Sharing and Photos

On iPhone, the end screen can turn your run into a card, a single image. It's made on the device and handed to the iOS share sheet, and you choose where it goes. The app doesn't know where it went. If you choose to save it to Photos, the app asks once for permission to add to your photo library; that permission only lets it add, not read.

On Android, the share button only copies your run as a line of text. No image is made and no photo permission is asked for. You choose where to paste it.

Children

This app is not made for children, and it never asks for or infers your age.

Changes

If this policy changes, this page changes with it, along with the date below. If in-app purchases are added later, a section on Apple's and Google's payment handling will be added then.

Contact

deepheart.app@gmail.com