Back to the app Deck & Dine

● Legal

Privacy policy

Last updated 6 October 2026

The app sends no statistics unless you say yes. If you do, it sends information about how your challenge is going, linked to a random ID for your install. It never sends your name or your allergies.

The short version. Your challenge, your pantry, your calendar and your collection are written to storage on your own phone, and the app never sends them anywhere. Separately, the app asks once whether it may send usage statistics about how far you get, linked to a random ID that resets when you turn them off. Saying no changes nothing about the app, and the switch in Settings (the gear at the top right of the Challenge tab) changes your answer at any time.

What is stored on your device

The app saves your progress locally so it is still there when you reopen it:

  • Your current challenge — which day you are on and how each day was signed off.
  • Your pantry and card collection.
  • Your difficulty settings and completed-challenge history.
  • Your diet: which track you are on, whether you eat gluten, and any allergens you excluded.

This data stays in the app’s private storage on your phone. Uninstalling the app deletes it. You can also clear it from your device’s app settings at any time. The app never sends any of it anywhere, including everything in the analytics section below.

If backup is on in your phone’s settings, Android’s own backup may copy the app’s storage, this data included, to your Google account and restore it on a new phone. On iPhone, iCloud Backup may do the same, copying the app’s data to your Apple Account and bringing it back when a phone is set up from that backup, though not on a reinstall. That is between your phone and Google or Apple. We never see it.

Analytics, if you agree to it

The app asks once whether it may send usage statistics. They’re off until you say yes. The measurement library is switched off when the app is built, and only your yes turns it on, so until then it doesn’t send even the automatic events it would otherwise collect on its own. The iPhone app works the same way: off until you say yes, and it sends the same events.

If you agree, the app sends these events:

  • When a challenge starts: which challenge it is, the difficulty, how many rest days and cheat meals it allows, whether the app picks your packs, whether you started with empty pantry slots, and your diet track.
  • When you commit to a set for the day, and which set it was.
  • When you sign a day off — which day, whether it was cooked, rested, a cheat meal or a failure, and how long your streak was.
  • When the app resolves a day you did not answer, and what it decided.
  • When you buy the unlock of every pack. Restoring it on a new phone sends nothing.
  • When you change a pantry slot: which day, which slot, the card you put in and the card it replaced.
  • When you finish a thirty-day challenge — how many cards and Legendaries you had, and at what difficulty.
  • If you change your diet, which track you moved from and to.

Alongside those it records four things about you: your diet track, your difficulty tier, how many challenges you have completed, and which day you are on.

Google’s measurement library also sends its own standard events once it’s on, such as when the app is first opened, when a session starts, which screen is showing and how long the app is in use. Each event carries basic facts about the phone and the app, like the app version, the version of Android or iOS and the language.

There’s no account, so none of it is tied to your name or email address. It’s tied to a random ID that the measurement library makes for this install of the app. Every event from your phone carries that ID until you turn analytics off, which replaces it with a new one. What was sent before then stays with Google under the old ID, and the old ID is gone from your phone.

What is never sent

These are not choices made carefully each time. The app is built so that they cannot be sent at all — every piece of information above is declared in advance, and anything undeclared is discarded before it can leave:

  • Your allergies and dietary restrictions. A list of allergies is health information, and the app never sends it. The app knows it because the cards have to; the statistics do not, and cannot.
  • Your birthday, in any form.
  • Anything you typed. There is no free text in what is sent — the app has no way to represent it.
  • Your name, email address or contacts. The app never asks for them.
  • Your signature. The signature you draw when you sign a day off is not saved on your phone or sent anywhere, and it is gone as soon as you press Submit.
  • Your location. The app requests no location permission. Note that any internet service can tell roughly which country a connection comes from, and Google’s analytics does derive an approximate region that way — city-level at most, never a position.

Who processes it

Google Analytics for Firebase, provided by Google, acting as our data processor. The data is transmitted encrypted and is held under Google’s terms for that service. We do not sell it, share it with anyone else, or use it for advertising.

Event-level data is kept for up to 14 months and then deleted automatically. Totals worked out from it, such as how many people reached day 7, are kept longer.

Your choices

  • Say no. No statistics are sent, and the app works the same. You lose no feature, and the app doesn’t ask again.
  • Change your mind, either way. The switch is in Settings.
  • Unlink it, or have it deleted. Turning analytics off gives your install a new random ID, so what was already sent is no longer linked to your phone. That doesn’t delete it. To have it deleted, email the contact address below. Because the statistics aren’t linked to a name, we can’t pick out yours, so we ask Google to delete everything the app collected over the period, yours included. You don’t need to tell us anything to identify it.

Our lawful basis for this processing is your consent, and you may withdraw it at any time.

Buying packs

The base sets are free. One purchase, for a one-off price shown in the app, unlocks every other pack, including packs released later. The purchase is made through Google Play on Android, or the App Store on iPhone, which takes the payment under its own terms. We never see your card, your payment details, your Google account or your Apple Account; the store tells the app only that the unlock is owned.

The app keeps that on your phone, and asks the store again when it starts, so the unlock comes back after a reinstall or on a new phone signed in to the same Google account or Apple Account. A purchase does not carry over between Android and iPhone, because there are no accounts. If you share usage statistics, buying it is one of the events sent (see the list above). Restoring it sends nothing.

Advertising

There are no adverts in this app. There is no advertising SDK, and the advertising identifier is not collected — the permissions that would allow it are removed from the app before it is built, and the measurement library is configured not to request it. On iPhone the app never reads the advertising identifier and never asks permission to track.

Permissions

The app does not use the camera, microphone, location or contacts. It uses the internet, and reads whether the phone is online, which is what sending statistics requires. It asks once whether it may show notifications, for an optional daily reminder to sign your day. The reminders are scheduled on your phone; nothing is sent to us to make them. On iPhone, tapping Save Image asks once to add photos; that permission can only add pictures and cannot see existing photos.

Children

The app is for a general audience and is not directed at children. We do not knowingly collect information from children. If you believe a child has agreed to analytics on a device you’re responsible for, turn off Share usage statistics in Settings to stop it, and contact us to have what was sent deleted.

What the app does not do yet

Some of these are planned. None are in the app today, and none collect anything from you at present:

  • User accounts and cloud sync
  • Crash reporting
  • Advertising
  • Friends, guilds, shared households, and photo sharing
  • Notifications sent from a server (the daily reminder is scheduled on your phone)

They are listed here so you can see the direction of travel, not because they are active.

Changes

This policy is updated before any version that changes the answers above is released, together with the Data safety disclosure on Google Play and the App Privacy details on the App Store — not afterwards. If a future release collects something new, it will say so here first: what is collected, why, who processes it, and how to have it deleted.

The date at the foot of this page shows when it was last revised.

Contact

Deck & Dine is made by Luke Pillar, trading as Faulty Compass Studio, who is responsible for the data described in this policy.

Questions about this policy, or a request to delete your data, can be sent to Luke@faultycompassstudio.com. You do not need an account and you do not need to give a reason.