Data retention
Effective date: October 12, 2026
Handyman Puzzle keeps information only for as long as reasonably needed to run the game, provide purchases and rewards, support players, prevent fraud and abuse, meet legal obligations, and comply with app-store requirements.
This page summarizes the retention periods used for Handyman Puzzle. It should be read together with the Handyman Puzzle Privacy Policy.
Requesting deletion hides public rankings and starts the 30-day cancellation period. Confirming continuation does not shorten it. After the deadline the worker removes active data in batches; an irreversible fence prevents recreation. A pending recovery job keeps the account identifier until Firebase Auth deletion succeeds, then only the hashed fence remains. Offline installations reconcile when they reconnect. Store records, backups and sign-in-provider accounts follow their own lifecycles. Deleting the app or game account does not cancel an Apple subscription. Cancel renewal separately in your Apple subscriptions to stop future charges. Active subscription status is removed with the profile; necessary purchase identifiers follow the separate purchase-record retention described below.
Only the two founders have company access to support and privacy requests. Gmail, Linear and Codex records are managed separately under the support retention policy; the game-account deletion worker does not automatically delete those provider records.
| Data category | Retention |
|---|---|
| Active account and backend profile data | Kept while the account is active. A deletion request starts a 30-day cancellation period; the worker then removes active game data and retries Firebase Auth deletion until successful. Processing may take longer if a provider is unavailable. |
| Active inventory and entitlements | Kept while the account is active. Removed from the active profile when the deletion period completes. |
| Public leaderboard scores | Available for the current and two previous periods. Supporting correctness and security records follow their applicable retention schedules. Leaving leaderboards removes public visibility immediately. |
| Nickname reports and moderation audit records | 90 days; expired reports are not used for review. |
| Personal nickname blocks and active nickname restrictions | Account preferences kept until changed or account deletion; appeals do not require retaining expired reports. |
| Mission progress | Kept while the account is active. Deleted or anonymized when the account is deleted. |
| Purchase, reward, spend, fraud-prevention, tax/accounting, and dispute records | Retained as long as reasonably needed for purchase restoration, duplicate-grant prevention, fraud prevention, support, disputes, tax/accounting, legal obligations, and app-store obligations. |
| Minimized purchase archives and deletion fences | No automatic expiry in the current system. Store transaction identifiers, necessary purchase tokens and hashed former account references are retained for restoration, duplicate-grant prevention and preventing deleted-account recreation. These are separate from active profiles. |
| Purchase usage and optional Apple refund-sharing consent | Per-purchase usage counters and the versioned sharing choice are kept with the active account and removed during account erasure. They are not copied into retained minimized purchase archives. Withdrawal stops further reports but does not remove inventory accounting needed to fulfill purchases and reconcile refunds. |
| Apple refund-report delivery jobs | Reports may be sent within Apple’s 12-hour request window. Completed, skipped, failed and expired delivery records become eligible for automatic deletion after 30 days; physical cleanup may follow later. Account erasure removes remaining jobs. Apple independently retains any information already received under its own policy. |
| Support messages | 24 months, unless a longer period is needed for an unresolved issue, dispute, legal obligation, security issue, or fraud-prevention reason. |
| Firebase/Google Analytics user-level and event-level data | Collection is disabled in this release. Historical data follows provider settings; the retention policy is two months. |
| Normal backend application/request logs | 30 days. |
| Application security, fraud and abuse-prevention records | 90 days, unless a longer legal, dispute, security, or fraud-prevention hold is needed. |
| Google Cloud mandatory administrative audit logs | 400 days in Google Cloud’s locked audit bucket. These provider-managed administrative and system audit records have a separate retention period from normal application logs. |
| Push choices, consent records and delivery tokens | Consent records contain the two choices, notice version and consent/withdrawal times, linked to an account and random app-installation identifier. Kept until account erasure or replacement by a different account on that installation. Successful choice changes remove the delivery token; re-registration requires an enabled category and device permission. Turning both categories off removes the active token, rotation replaces it, and sign-out disconnects it. Tokens not refreshed for 30 days are suppressed from delivery but are not automatically erased on that schedule. Legacy tokens never establish consent and are removed with account erasure. Provider-managed identifiers follow provider retention; disabling push does not delete a shared Firebase installation identifier. |
| Local device data | Audio and haptic preferences, account caches, broad age-check status/timing, ad pacing and pending-ad state, and purchase replay-protection keys remain until cleared by the app, app-data reset, uninstall or operating-system cleanup. Unfinished current-session boards are discarded on leave or app termination. Completed online results awaiting delivery remain until acknowledged or removed by the app; offline Classic results are never queued for leaderboard submission. Account-derived local caches are cleared when leaving or erasing the account. Device-wide preferences and ad pacing can remain independent of account sign-in. |
Handyman Puzzle provides an in-app account deletion option from the Profile screen. The app asks for confirmation before sending the deletion request.
A deletion request starts a 30-day deletion period and hides public ranking entries. Normal game entry is blocked for that account. Sign in again before the scheduled deletion date to cancel, or continue as a fresh guest while deletion remains scheduled. Once irreversible deletion starts, it cannot be cancelled.
When the deletion period completes, Handyman Puzzle deletes or anonymizes active backend data tied to the account, including:
The app clears account-derived local caches as it leaves or erases the account. A fresh guest is separate and does not inherit the deleted account's inventory. Other offline installations reconcile when they reconnect.
Deleting an account removes remaining active consumable inventory and active entitlements from that backend profile. Remaining consumable inventory is not transferred to a new account.
Some purchase and transaction records may still be retained in minimized form where needed for:
Where technically feasible, retained records are detached from the active player profile and minimized so they do not preserve gameplay benefits for the deleted account.
Behavioral Firebase Analytics collection is disabled in this release. Historical data follows the provider's settings; our retention policy for that data is two months.
Advertising data may also be processed by Google AdMob and related advertising services under their own retention settings and policies. Handyman Puzzle uses Google's consent tools and non-personalized ad requests as described in the Privacy Policy.
Support messages are retained for 24 months. We may keep a support message longer if it is needed for an unresolved issue, purchase dispute, legal obligation, fraud-prevention review, security issue, or similar reason.
Support requests should not include passwords, full payment card details, government ID numbers, private keys, or other sensitive information that is not needed to resolve the request.
Some records may be kept longer than the periods listed above if required for:
When a longer hold is no longer needed, the data is deleted, anonymized, or minimized according to the relevant retention category.
For privacy questions, data requests, or account deletion help, contact:
You can also use the StackWiz Labs contact page.