Privacy & Data Handling

The fewer places sensitive data lives, the fewer things to worry about

Most platforms store what you send them indefinitely. This one is built specifically not to, down to where identity ever exists at all.

The core design

Your server never receives a patient's identity: not even briefly

This isn't a retention policy layered on top of a normal upload. Identity is stripped in your browser before the first byte is ever sent.

What's stripped, before anything uploads

Name, date of birth, date of test, time of test: every date field, not just the obvious ones. Only age and gender remain, plus an opaque case reference that is never linked to a patient name anywhere on our servers.

Hosted in Sydney

All infrastructure (application, database, file storage) runs on a single Australian server. Nothing crosses a border to be processed.

Encrypted end to end

In transit and at rest, for as long as anything exists on the platform at all, which, by design, is not long.

Purged the moment you download

QEEG, TOVA, checklist, and report are all deleted the instant your download completes. No fixed retention window, and no scheduled cleanup job you have to trust.

Re-identification happens on your machine

At download, you confirm the patient's identity yourself. That is the only point identity and clinical content ever meet, and it never touches our servers.

What we can't do, as a result

Because we never hold the identity mapping, we can't recover it if you lose track of a case reference, and we can't verify what you enter at download time. That trade-off is the whole point: the alternative is us holding data we do not need to.

Reports themselves

Even the report addresses your client only by age and gender

“The client is a 39-year-old female.” That is the extent of it: nothing else identifying ever appears in a generated report.

Questions about how your data is handled?

Check the FAQ or read our full legal terms.