Account access
Firebase Authentication supports email, Apple, and Google sign-in. Account and patient identifiers are used to scope access to records.
HealthTracker
A plain-language overview of the safeguards used to protect accounts and health records. This page describes current practices, not a security certification or guarantee of absolute protection.
Firebase Authentication supports email, Apple, and Google sign-in. Account and patient identifiers are used to scope access to records.
Firebase and Google Cloud provide encryption in transit and at rest for supported database and file-storage services.
Automatic inactivity locking and your device or browser security controls help protect access on shared or unattended devices.
Encrypted database backups are created daily and retained for up to seven days for disaster recovery.
Reports are downloaded or handed to your browser and operating system sharing tools. You review the destination and decide whether to send.
HealthTracker has no ads and does not sell personal data. Service providers are used to operate the app, subscriptions, and support.
HealthTracker relies on Firebase and Google Cloud for account, database, file, analytics, and crash-reporting services, and RevenueCat for subscription management.
Apple and Google process sign-in requests when those optional providers are used. Your browser and operating system process downloads, reports, messages, email, calendar events, notifications, and sharing actions that you initiate.
Once you send or save an exported report, the destination service and recipient control that copy.
Send enough detail for us to investigate, but do not include passwords or unnecessary health information. We will assess reports and notify affected people or authorities when required by applicable law.
healthtrackersupport@ntc.com.au