Back to PierDo

Privacy Policy — Digit Span Trainer

Effective date: September 11, 2026

Public policy: https://pierdo.net/digit-span-trainer/privacy/. The separate authenticated cloud-deletion page is https://digit-span-coach-worker.pierdo-dev.workers.dev/account-deletion#digit-span-data-deletion.

Scope

This policy covers the Digit Span Trainer Android app and the backend services it uses (AI Coach and billing).

Contact

Questions: pierdo.dev@gmail.com

Local-only data

Training rounds, preferences, skin unlocks, tutorial progress, saved Digit Span Lab programs, local goals, active Lab drill progress, and the last generated Lab report snapshot are stored on your device using IndexedDB. They do not leave the device on their own.

The app keeps two separate duplicate-charge safeguards. A Coach Pack safeguard contains the signed-in Coach account identifier, product identifier, known pre-purchase Coach balance, verification status, and timestamps. The Digit Span Lab control record contains the exact Lab product, verification timestamps, generation/revision fences, and a purchase-owner binding made by applying a Digit Span Lab-specific SHA-256 namespace to RevenueCat's original app-user ID. The Lab record never stores the raw RevenueCat or Google identifier. Neither record contains payment-card or Google Play transaction data.

If a Coach cloud deletion response is interrupted or ambiguous, the app keeps a local pending-deletion safety marker containing the Google account identifier, request state, and timestamp. The marker survives relaunch and Reset All Progress, blocks Coach generation and account or purchase mutations, and is cleared only after the same authenticated account receives confirmed deletion proof and Coach sign-out completes.

Sign-in

If you sign in with Google, Google may provide a stable account identifier, email address, and display name. The app uses the identifier to recognize you across devices and associate purchases with your account. Your email address and display name are used locally to show your signed-in state; they are not sent to the AI Coach backend or included in Coach Pack measurement.

Google sign-in inside Digit Span Trainer is optional for Free Core training, Stats, themes, CSV, and the Digit Span Lab purchase and restore controls. A Google Play account is still required by Google Play to buy or restore Lab. Coach Google sign-in is required only to use AI Coach so lifetime samples and purchased Coach insights can be protected and associated with the correct account. The app sends a short-lived Google identity token to the Coach backend, which verifies its signature, intended audience, issuer, expiration, and account identifier.

The backend never sends the raw Google account identifier to Fireworks AI. When the required Worker secret is configured, it derives a Fireworks-specific HMAC reference for request affinity; that value cannot be joined to the separate HMAC reference used in sampled operational logs. If the secret is unavailable, the optional Fireworks affinity field is omitted.

AI Coach

When you tap an AI Coach button, a digest of your recent training stats (best span, recent accuracy per mode, weekly round counts, journey progress) is sent over HTTPS to our backend to generate a personalized response. Signed-in accounts receive 10 lifetime sample insights, which can be used at any pace. A one-time Coach Pack adds 365 non-expiring purchased insights. Existing subscribers retain the Coach service they purchased. Failed, unavailable, not-ready, cached, and deterministic-fallback requests do not use a sample or purchased insight. We do not share this data with advertisers and we do not sell it.

While an account deletion is pending or in progress, the app blocks new Coach generation, sign-in owner changes, and purchase or restore mutations. The backend independently serializes deletion against all per-account writes so a late request cannot recreate deleted Coach records or consume a credit after a successful deletion.

Digit Span Lab

Digit Span Lab is a separate, permanent local-feature unlock. It adds saved custom programs, advanced local drills, serial-position and response-time analysis, deeper comparisons, local goals, and a shareable local report. It does not include AI Coach samples or purchased Coach insights and does not send Lab analytics or reports to the AI Coach backend.

The verified Lab grant remains on the device when a person signs out of Coach, deletes Coach cloud memory, or changes the optional Coach account. When current RevenueCat information is unavailable or belongs to a different purchase owner, the app preserves an already verified grant. Authoritative inactive information for the same original purchase owner, such as a refund or revocation, relocks Lab creation, editing, and drills. It does not delete saved programs or the last saved report: those remain locally readable and the report remains shareable. Free Core remains usable. Premium analytics are not recomputed while Lab is relocked.

Billing

Digit Span Lab and Coach Pack purchases are processed by Google Play and their status is managed through RevenueCat. Lab uses the fresh non-consumable product digit_span_lab_lifetime and entitlement digit_span_lab; it is not inferred from an older lifetime or subscription product. Its localized price is supplied at runtime by Google Play through RevenueCat. Coach Pack remains the separate, repeatable 365-insight product, and purchased insights do not expire. An existing legacy Coach subscription remains managed by Google Play and RevenueCat on the terms already purchased.

Before opening Google Play, the app records the current authoritative Coach balance. It reports a Coach Pack as added only after RevenueCat returns a higher balance. If the purchase result or balance refresh is uncertain, the saved verification record blocks another Coach Pack purchase until the same signed-in account checks again and RevenueCat confirms the increase. If the Google or RevenueCat account changes during verification, the stale result is ignored and the original account's local purchase lock is retained.

Before opening Google Play for Lab, the app durably saves an exact-product, hashed-owner pending record. It reports Lab as owned only after RevenueCat returns the exact active entitlement and the owner-bound grant is saved and read back. Explicit cancellation clears the guard. Network errors, timeouts, account changes, or uncertain results retain it and block another purchase until an authoritative same-owner check or Restore Lab purchase resolves it. Lab purchase and restore do not require Coach Google sign-in.

While that Lab record is unresolved or unreadable, the app temporarily prevents RevenueCat owner changes, including Coach purchase linking, Coach restore, and Coach sign-out. This keeps the ambiguous result attached to the owner that began it. The app directs the user to Check or Restore Lab first; a mismatched record remains blocked with support guidance rather than being cleared from another owner.

Optional tips

Optional tips are repeatable Google Play purchases with preset localized amounts. They add no Lab access, Coach requests or other app features. RevenueCat processes tip transactions using the same purchase data described above. A separate local record stores the product, purchase-owner identifier, pre-purchase transaction identifiers and pending status so an uncertain result cannot start a duplicate payment. Tips are separate from Coach balances and Lab ownership.

Coach Pack measurement

To understand whether the free Coach experience leads people to a Coach Pack, we measure only four milestones: a sample insight succeeded, the Coach Pack screen was viewed, a purchase was started, and a purchase was completed. Reports contain event counts grouped by UTC ISO week and a small allowlist of entry sources. They do not contain Coach prompts or responses, training statistics, product prices, transaction identifiers, Google profile data, or advertising data.

The app sends the Coach Pack view and purchase-start milestones with its RevenueCat app identifier and a random event identifier used to prevent duplicate counting. The backend records sample-insight success after generation, and records purchase completion only from an authenticated production RevenueCat event. Short-lived hashed markers retain the latest paywall source long enough to attribute a completed purchase; the weekly reports contain no account identifiers. These directional counts are used only to improve the app and are not sold or shared with advertisers.

Sub-processors

The following third-party services receive limited data when you use billing, AI Coach, or sign in:

Device features

The app uses your device's text-to-speech engine to read digits aloud. The app does not request microphone permission and does not record voice input.

Permissions

Data export

The CSV feature imports and exports training rounds only. It never imports or exports the Lab grant, purchase guard, programs, goals, sessions, or report snapshot. CSV export writes a temporary file to your device's cache directory and opens the system share sheet. The Lab report share action similarly opens the system share sheet with the locally saved report text. Neither action uploads data to our servers.

Android cloud backup and device-to-device transfer are disabled for this app so the local Lab grant/control record cannot unlock a different device by being copied. On a new or cleared device, use Restore Lab purchase so Google Play and RevenueCat can verify ownership again.

Children

This app is intended for general audiences, including students. We do not knowingly collect personal data from children.

Data retention and deletion

To permanently delete off-device Span Coach account data in the app, sign in with the Google account used for Coach and open More > Settings > Account > Delete Coach cloud account. If you do not have the app installed, open the Google-authenticated public deletion page at https://digit-span-coach-worker.pierdo-dev.workers.dev/account-deletion#digit-span-data-deletion. That page works without opening or reinstalling the app. Both paths require a final confirmation and send a short-lived Google identity token over HTTPS to the same Coach backend. The backend verifies the token and derives the same internal account key used for Coach access. The deletion request body contains no Google subject identifier, email address, display name, or support lookup reference. An email-only support request cannot safely identify this pseudonymous account; support will direct you to one of these authenticated paths.

After authenticated deletion, the backend immediately removes from service access and sweeps that account's Coach memory, short-lived completed-response and replay state, generated-response caches, free-allowance and per-account spend records, entitlement cache, short-lived purchase-source attribution, and Coach request state. The operation is idempotent and fenced against other per-account writes, so an interrupted or ambiguous request can be retried safely. The app keeps its pending marker and blocks Coach/account mutations until the backend confirms deletion, then signs out of Coach.

The backend's strongly consistent account record advances a deletion epoch before it confirms the request. All later account-addressable KV reads and writes are resolved only in the new epoch, so an obsolete value cannot be returned even if a Cloudflare KV list, delete, or edge cache has not yet converged. The backend also maintains a strongly consistent exact-key cleanup index for active account-addressable reads and writes, and sweeps that index, the complete legacy key inventory, and all older epoch namespaces. Physical deletion/cache propagation follows Cloudflare's infrastructure timing, while the old namespace is logically inaccessible to every Coach endpoint immediately after confirmation.

To prevent repeated deletion and sign-in from issuing the same ten lifetime samples again, the backend retains a minimal opaque anti-regrant tombstone for the lifetime of that grant. It contains only a zero sample balance, a retired-grant flag, and a deletion epoch used to reject stale writes. It contains no raw Google subject, email, display name, Coach prompt or response, training content, or purchase balance. The Durable Object is addressed through the backend's internal account mapping; the tombstone is not exposed as a support lookup identifier.

This deletion does not remove training or Lab data stored on the device; use Reset all progress separately for that data. It also does not delete Google Play or RevenueCat purchase records, entitlements, purchased insight balances, or the independent local Lab grant. Identifier-free aggregate service metrics and the bounded HMAC-pseudonymized operational logs described above remain; those logs follow the infrastructure provider's retention controls and contain no Coach content or raw Google identifier. Google Play or RevenueCat purchase deletion and refund requests follow those providers' processes.

What we never collect or transmit

Contacts, photos, location, microphone, camera, browsing activity, or contents of other apps.

Changes to this policy

We may update this Privacy Policy from time to time. Material changes will be reflected with an updated "Effective date".

Contact

Email: pierdo.dev@gmail.com