Delete your account and associated data

Use the in-app deletion process

1. Open Hitpoints and sign in to the account you want to delete.
2. Open Profile, find Account, and choose Delete account.
3. Review the consequences, authenticate again, and confirm deletion.

When the request is accepted, Hitpoints signs you out and starts resumable clearing of account data from that device. Connected Apple authorisation or Google access is revoked or disconnected as part of the request.

Your account and private cloud data remain during a seven-day cancellation period. Sign in during that period to cancel deletion. After the period, a scheduled service deletes your Firebase Authentication account, private account database, and backup objects. Failures can delay completion and, after five unsuccessful attempts, require operator attention.

External request route

If you cannot use the app, email support@hitpoints.gg and request deletion of your Hitpoints account and associated data. State the sign-in method you used and the account email or Apple private-relay address, and provide a contact address where you can receive a reply.

If you have lost access to the original or relay address, support will use the approved provider-backed account recovery route if one exists. If ownership cannot be proven, the request is escalated and deletion is not executed until an authorised decision is recorded.

The owner has approved this evidence boundary and is the sole initial authorised operator and escalation owner.

What is deleted or cleared

• the Firebase Authentication account;
• the private account database tree and cloud snapshot objects;
• managed local account, profile, progress, workout, sync, and telemetry-consent state on the requesting device; and
• connected Apple or Google authorisation handled by the deletion request.

Device clearing first confirms sign-out. If sign-out cannot finish, cleanup remains pending and account entry is blocked until you retry. After sign-out, managed account data is cleared before the final Lock in cleanup. On iOS, that final step releases restrictions, stops the failsafe, and clears saved Lock in selections and activity state. If it fails, native data or restrictions may remain; Hitpoints keeps the cleanup pending, blocks account entry, and offers Retry cleanup. An interrupted cleanup also resumes on the next launch. A failed attempt is not reported as complete removal.

Current device clearing also cancels Hitpoints reminders and attempts to remove Hitpoints-owned calendar events. Native cleanup failure can require a later retry. The operating system or calendar provider controls its own records and synchronised copies, so Hitpoints cannot promise that account deletion removes every provider-held calendar record.

What may remain temporarily or separately

• Firestore database history can remain recoverable for one hour after deletion in the staging service.
• Deleted Storage backup objects can remain recoverable for a further seven days under soft-delete controls.
• Default service logs are configured for 30 days and required audit logs for 400 days.
• UID-free deletion completion receipts and HMAC-addressed tombstones become eligible for automatic deletion 90 days after deletion completes. Firestore expiry is asynchronous, so an expired record can remain temporarily after that date.
• Minimal support cases, ownership-verification records, and related correspondence become eligible for deletion 90 days after the case closes.
• Provider-controlled TestFlight and other service records follow provider schedules.

Health and calendar information written to Apple, Google, or another platform is controlled through that platform and your device settings. Deleting Hitpoints does not promise deletion of those platform-owned copies, previously delivered optional telemetry, or TestFlight reports. It does not delete support messages immediately; retained support messages follow the approved 90-day schedule measured from case closure and any separately disclosed provider limits.

More information

See the Privacy Policy for the full data inventory, access, optional telemetry, and retention disclosures, and the Terms of Service for the account rules.