Privacy Policy

Data We Use

An account and completed detective profile are required to play. Ultra Murdle uses account email, authentication identifiers, the selected private profile, gameplay progress, badges, completed cases and focused timing, optional recommendation activity, Firebase-synced Hint Token wallet records and paid reveal history, opt-in public leaderboard summaries, and remote puzzle pack status.

If you separately consent to usage analytics, Ultra Murdle links your Firebase account identifier to screen and allowlisted action identifiers, case and volume identifiers, difficulty, locale, foreground engagement time, assistance counts, purchase and wallet outcomes, and allowlisted reliability codes. The app owner can view this activity with the current email and username from your account profile. Analytics never contains private notes, clue or story text, solutions, deduction-grid content, accusation selections, passwords, authentication tokens, receipts, transaction identifiers, support text, raw error messages, or tap coordinates.

If you contact support, your message may include the support category, your written comment, optional screenshots you choose to attach, app version, platform, locale, text-size setting, active case identifier, account email, and account user ID if signed in.

Services

Firebase provides authentication, Firestore database storage, remote content delivery, Analytics, and an owner-only administration service. Google Analytics 4 and BigQuery process consented usage events. RevenueCat manages purchase validation and restore state for Apple and Google in-app purchases. Apple App Store and Google Play process mobile purchases and refunds according to their own systems.

Usage analytics is not used for advertising or cross-app tracking. Ultra Murdle does not collect IDFA for analytics and does not use heatmaps, session replay, or raw tap capture. Advertising consent remains denied even when usage analytics is enabled.

Personalized recommendation activity is optional and is sent only after the signed-in player enables it in Settings. Events contain compact identifiers, difficulty, locale, timing, completion, failed-submission, and assistance metadata. They do not contain private notes, clue or story text, solutions, deduction grids, manual marks, accusation content, email, or purchase identifiers.

Hint Token balances, paid clue unlocks, and full-answer reveal history are synchronized to the signed-in account through Firebase and cached on the device for offline use. RevenueCat validates store purchases. The leaderboard is off by default and publishes only after explicit confirmation. A public entry contains a stable system-issued alias, solved cases, badge totals, streaks, collection points, focused solve times, and ranking metadata. It never contains a Firebase UID, email, private display name, username, or selected profile.

Deletion And Retention

Raw account-linked usage events are retained for no more than 90 days. Turning “Share usage analytics” off stops future collection; previously collected events remain until they expire within that period. Anonymous, irreversible daily aggregates that do not contain a user identifier may be retained for up to 24 months.

Account deletion can be started inside the app from Settings. It revokes Sign in with Apple when applicable and deletes the RevenueCat subscriber, Firebase Auth account, progress, badges, wallet, paid clue and full-answer history, support attachments, public ranking, remote sync data, and linked analytics identity. BigQuery analytics deletion is processed within 24 hours. Unused Hint Tokens are permanently forfeited and cannot be restored.

A non-reversible HMAC deletion tombstone is retained for 90 days only to prevent delayed or retried purchase webhooks from recreating a deleted wallet. Store processors may retain transaction, refund, tax, dispute, fraud, or security records when legally or operationally required.

Contact

For privacy questions or data requests, contact support@ultramurdle.com.