Daily Tactics — Privacy Policy

Draft for Play Store submission (STORY-016). Founder review required before it goes live at a public URL and is linked in the Play listing — see the checklist at the bottom. Two variants below; ship the one matching the build that goes to Play.

STORY-017 has shipped (2026-07-13): the app now bundles Firebase Crashlytics + Google Analytics, default-on with a Settings opt-out. Variant B is therefore the operative policy for any build off main. Variant A is retained only as the record of the pre-telemetry codebase (and would apply again to a hypothetical analytics-free build).

Last updated: (fill on publish)

Summary

Daily Tactics is an offline-first, single-player Android app. You do not create an account, and the app works with no network connection. This is a deliberate product decision (infrastructure "rung 0" per DDEF Studios' ddef-planning/blueprints/infrastructure-decisions.md): the daily tactic is generated on your device from the calendar date, so there is no server that needs to know who you are or what you did.

Variant A — Launch build (no analytics)

Historical: accurate for the pre-STORY-017 codebase, when no telemetry SDK was present. Superseded by Variant B on 2026-07-13 — see the note at the top.

What we collect

Nothing that leaves your device. Daily Tactics has no account system, no login, no advertising SDK, and no analytics SDK. We do not collect, transmit, or sell any personal data.

What is stored on your device

The app saves, in local on-device storage (Android DataStore), only:

your progress on each day's tactic (the position, your moves so far, lives left);
which days you have solved, to compute your streak;
your theme preference (system / light / dark).

This data never leaves your device, is not readable by us, and is removed if you uninstall the app or clear its data from Android settings.

Children

The app is suitable for all ages and collects no data, so it does not knowingly collect information from children under 13 (or the equivalent age in your region).

Changes

If a future version adds any data collection, this policy will be updated and the change described in the release notes before that version ships.

Contact

[email protected]

Variant B — With optional analytics (operative since STORY-017, 2026-07-13)

This is the truthful policy for the current codebase: it bundles Crashlytics + Google Analytics, default-on with a Settings opt-out.

Everything in Variant A applies, plus:

Diagnostics & usage data (optional, on by default, can be turned off)

To find crashes and understand which features are used, the app includes Firebase Crashlytics and Google Analytics for Firebase. When enabled, these may collect:

crash reports and technical diagnostics (stack traces, device model, OS version, an app-generated install identifier);
anonymous usage events (e.g. "a tactic was opened", "a tactic was solved") — never the content of a position or your personal identity.

This is optional and you control it. Settings → "Share crash & usage data" turns both off; with it off, nothing is transmitted and the app remains fully functional. No advertising ID is used and no data is sold. Google processes this data as our data processor; see Google's own privacy terms for their handling.

If you are in the EEA, the UK or Switzerland (or your device's country can't be determined), nothing is collected until you answer a one-time question on first launch; declining — or dismissing the question — keeps collection off. Your answer can be changed anytime in Settings.

Data deletion

Uninstalling the app stops all collection. To request deletion of previously collected diagnostics tied to your install identifier, contact us at the address above.

Founder review checklist (delete this section before publishing)

[ ] Choose the variant matching the build being submitted (B since STORY-017 shipped).
[ ] Fill the contact email and the "last updated" date.
[ ] Host at a stable public URL (GitHub Pages / studio site) and paste that URL into the Play Console listing's Privacy Policy field.
[ ] Confirm the "what is stored on your device" list still matches app/.../progress/ + settings/ (update if the save format changed).
[ ] Cross-check every claim here against play-data-safety.md — the two must agree.