How ForLife protects your information
What we hold, and for how long
ForLife keeps the minimum needed to show you a screening status: the result lines from a pathology report, where they came from, and an audit record. Reports from My Health Record are checked in memory and not stored — the original stays in My Health Record. Anyone you share with sees a single signed Yes or No, nothing else.
Where it lives
Information derived from My Health Record is stored and processed only in Australia, encrypted with Australian-region keys. The service refuses to store it anywhere else.
How it is protected
- Encrypted at rest (AES-256-GCM) and in transit (TLS 1.2+, HSTS); API responses are never cached.
- App lock on by default (Face ID / Touch ID / passcode), locks again after 15 minutes without use, wipes after 10 failed unlocks; app data is kept out of cloud backups.
- myGov sign-in happens in your phone's own browser — ForLife never sees your password. Access tokens stay on our server, encrypted, and stop being used after 45 days of inactivity.
- Sign-in lockout after repeated failures; single-use refresh tokens; every access recorded in a tamper-evident audit log kept for at least 12 months.
- Insurers, employers and underwriters are blocked from receiving any answer.
- Every change passes automated checks (tests, dependency audit, secret scanning) before it is merged, and the hosted service is scanned with OWASP ZAP after each update.
If something goes wrong
We run an incident process that notifies affected people, the Australian Digital Health Agency and the OAIC as required. Report a security concern to security@forlifeglobal.health; responsible disclosure is welcome.
Your control
You can stop sharing, revoke any proof, disconnect My Health Record or delete your account at any time from the app or at /delete-account. Withdrawal revokes our access token, deletes your records and cancels every live proof and partner grant.