Hitpoints account
Privacy Policy
This policy explains what information Hitpoints handles, why it is used, who can process it, how long it may remain, and the choices available to you.
1. Scope and contact
This policy applies to the Hitpoints mobile application, Hitpoints account services, cloud backup and restore, and the support and authentication pages at auth.hitpoints.gg.
“Hitpoints”, “we”, “us”, and “our” refer to HITPOINTS.GG PTY LTD, the developer and publisher of the Hitpoints app. Our public business address is L 7, 140 St Georges Terrace, PERTH WA 6000.
Privacy questions and requests can be sent to support@hitpoints.gg.
2. Information we handle
Account, authentication, and required acceptance
We handle your email address, Firebase account identifier, sign-in provider, email-verification status, account lifecycle state, security and session metadata, adult attestation, and the versions and acceptance times of required terms and notices. Firebase Authentication processes sign-in credentials. Plaintext passwords are not stored in Hitpoints app data or cloud snapshots.
Profile, progress, training, and workouts
When account cloud backup is enabled, backups can include your display name, age, fitness goal, trainer and equipment choices, onboarding and placement results, skill progress, Hit Points, preferences, workout plans, schedules, active and completed workouts, adaptation and statistics. Workout records can include pain or discomfort level, body location, form-quality feedback, skipped or paused activity details, and notes you enter.
Cloud backup, device, and health-export metadata
Supported snapshots include app and Unity versions, account environment, an app-generated source-device identifier, snapshot identifiers, sizes, integrity hashes, and operation times. Backups can also include your health-sync preference, related Hitpoints workout identifiers, export and repair status, failure categories, and match counts. They exclude authentication tokens, native health authority, and raw dashboard readings. The service can download and decompress snapshots to validate them; the backups are not end-to-end encrypted against the service operator.
Calendar, reminders, and Lock in
If you enable calendar integration, Hitpoints reads and writes through the device calendar provider. On Android this includes writable calendar account and display metadata and lookup of Hitpoints-owned events. The app creates generic “Hitpoints Workout” events with scheduled time, duration, and time zone. A connected calendar provider may sync its own copy. Native calendar event identifiers are not uploaded in Hitpoints account snapshots.
If you enable workout reminders, Hitpoints schedules local notifications containing generic workout text, internal identifiers, and timing data. Android can restore pending reminders after device restart. No Hitpoints product integration for remote push notifications is present in the reviewed source.
If you enable Lock in on iOS, your selected Screen Time app, category, and web-domain tokens are stored in the shared App Group used by the Hitpoints app and its extensions. Unity receives selection counts and status. The selection tokens are excluded from Hitpoints account snapshots.
Security, diagnostics, service, and support data
App Check and authentication signals, installation and app metadata, request metadata such as network address and user agent, error categories, operational and audit events, and information you choose to include in a support request may be processed to operate and secure the service. This necessary service processing is separate from optional product analytics and Crash diagnostics.
3. How we use information
We use the information described above to:
- create, verify, secure, and support your account;
- provide onboarding, training, workout, progress, and health-related features;
- back up, validate, restore, repair, and reconcile supported app data;
- prevent account confusion, fraud, abuse, and unauthorised access;
- diagnose failures, protect the service, and respond to support;
- comply with law and enforce applicable terms; and
- provide analytics or crash reporting only when the separate choice permits it.
Where applicable law requires a legal basis, we rely on performance of our agreement with you, consent, compliance with law, and legitimate interests such as operating, securing, and improving the service, as appropriate to the specific processing.
4. Health-platform information
With your permission, Hitpoints reads supported Apple Health or Health Connect information for health dashboards: steps, heart rate, and active energy or active calories. Raw dashboard readings are held in runtime memory for the requested dashboard windows and are not included in Hitpoints account backups.
If you separately enable workout export, Hitpoints writes supported workout or exercise-session information to your chosen health platform. On Android it can read bounded exercise-session information to review and repair its prior exports. Export may continue for future completed workouts while sync remains enabled. The app does not import these readings into skill progression. The platform controls its own copy under your device settings, terms, and privacy policy.
6. Optional product analytics and Crash diagnostics
Product analytics and Crash diagnostics are separate choices in Profile. Both are off by default. Accepting account terms, this policy, or the 18+ requirement does not enable either choice. Hitpoints applies a choice only while it has trusted consent for the same account, environment, and current telemetry policy.
Turning a choice off stops future authorised collection or delivery through that feature. It does not retroactively erase records already delivered to a provider, and disabling Crash diagnostics does not promise that no local diagnostic record can exist. Authentication, App Check, security logging, and other necessary service processing continue independently where needed to provide and secure the account service.
When Product analytics is enabled, Firebase Analytics can collect automatically generated app-interaction events and SDK installation, app, and device identifiers. When Crash diagnostics is enabled, delivered reports can contain crash data, diagnostic context, and identifiers. These identifiers must not be treated as anonymous or necessarily unlinked to an account or device.
7. TestFlight testing data
If you install a beta through Apple TestFlight, Apple separately provides the developer with tester and beta-service information such as contact or invitation details, installed build and device or operating-system details, session and crash information, and feedback you submit through TestFlight. Apple controls this TestFlight service data under its terms and privacy practices. Hitpoints' in-app analytics and Crash diagnostics choices do not control Apple's separate TestFlight processing.
8. Storage, operator access, and security
Some information is stored locally on your device. Eligible account data and backups are stored in private Firebase and Google Cloud resources configured in Sydney, Australia. Other authentication, security, support, telemetry, vendor, or testing data may be processed elsewhere.
Authorised Hitpoints operators and service providers can process account information, private backups, and technical records as needed to operate, secure, troubleshoot, and support the service. Hitpoints uses access controls, encrypted network transport, platform application-integrity checks, server-controlled lifecycle state, integrity validation, and mobile file-protection and backup boundaries. No system can guarantee absolute security.
9. Retention and deletion timing
Active account information and backups are retained while needed to provide and secure the account service. Hitpoints does not currently promise a fixed number of retained backups. Account deletion has a seven-day cancellation period. After it expires, scheduled processing deletes the Firebase Authentication account, private account database, and backup objects.
- Staging Firestore database history can remain recoverable for one hour after deletion.
- Deleted Storage backup objects can remain recoverable for a further seven days under soft-delete controls.
- The configured default Cloud Logging bucket retains logs for 30 days.
- The required audit-log bucket retains logs for 400 days.
- UID-free deletion completion receipts and HMAC-addressed security tombstones become eligible for automatic deletion 90 days after deletion completes. Firestore's asynchronous expiry process can leave an expired record temporarily present after that date.
- Minimal support cases, ownership-verification records, and related correspondence become eligible for deletion 90 days after the case closes.
- Other vendor and TestFlight service records follow provider-controlled schedules.
Processing failures may delay deletion and can require operator attention after automatic retries stop. We may retain information where required by law or while it remains needed for an approved security, dispute, or compliance purpose.
10. Your choices and rights
Depending on your location, you may have rights to access, correct, obtain a copy of, restrict, object to, or delete personal information, withdraw consent, or complain to a privacy regulator. Contact support@hitpoints.gg. We may need to verify account ownership before acting on a request.
Support-assisted deletion requires either a fresh authenticated Hitpoints session or an approved provider-backed account recovery result; email-address matching, including an Apple private-relay address, is contact evidence only; never send passwords, one-time or other authentication codes, provider tokens, recovery keys, identity documents, or unrelated health or workout content at any stage — we will never ask for them.
Delete your account and associated data
In the app, open Profile, find Account, and choose Delete account. Recent authentication is required. The request signs you out, starts resumable clearing on that device, and schedules final cloud deletion after the seven-day cancellation period. Sign in during that period to cancel. See the account-deletion page for the external support route and detailed limits.
Device cleanup confirms sign-out before clearing managed account data. On iOS, Lock in restrictions, its failsafe, saved selections, and activity state are cleared as the final step. If cleanup cannot finish, Hitpoints blocks account entry and offers Retry cleanup; interrupted cleanup also resumes on launch. Native data or restrictions can remain until that step succeeds. A failed attempt does not count as complete removal.
Current device clearing cancels Hitpoints reminders and attempts to remove Hitpoints-owned calendar events. A failed native cleanup can require a later retry. Calendar records held or synchronised by an operating-system or calendar provider remain under that provider's controls; deleting the Hitpoints account does not give Hitpoints authority over every provider copy.
11. Age restriction
Hitpoints accounts are intended only for people aged 18 or older. If you believe a person under 18 has created an account, contact support@hitpoints.gg.
12. Changes and privacy complaints
Material updates use a new policy ID and effective date. When required, the app asks account holders to review and accept the updated policy before continuing with account-backed features.
Send privacy questions, access or correction requests, and complaints to support@hitpoints.gg.