Security & privacy, on one page.
GotIt Guides doesn't change your clinical advice. It takes the discharge notes your clinic already writes and transforms them into a clearer, easier-to-follow digital guide that your team reviews before sending. The clinician stays in control; we handle presentation and delivery. Here's how the information is looked after, in plain English — with the full data processing summary behind it.
Safer than the email you'd have sent.
Your discharge notes are encrypted on your own computer before they reach us, with a code only your clinic sets. We can't read them. Neither can anyone who gets hold of the link, because the code that opens it never travels with the link. It goes home on the paperwork.
- No readable copy sitting in an inbox
- No wrong address moment you can't take back
- Nothing a search engine can ever find
One thing worth knowing: to turn your notes into a guide, they pass through our AI provider in the United States. Transiently, never stored there, never used to train anything. Everything else stays on AWS in Sydney. The detail is below.
Where is the data stored?
On Amazon Web Services in Sydney, Australia — the same infrastructure most Australian practice-management and pathology systems run on. Encrypted in transit and at rest.
Who can read a guide?
Discharge guides are locked by default and encrypted on the device before they're stored, using a guide code your front desk writes on the discharge paperwork. We store unreadable ciphertext: GotIt Guides staff cannot read a locked guide, and neither can anyone else without the code. Guide links are randomly generated and never appear in Google or anywhere on our site.
What does the AI actually do?
It reformats. The AI reads your existing notes and restructures them into sections — it is specifically instructed never to invent, infer or "fill in" a clinical detail. Anything missing or ambiguous becomes a visible "⚠️ Check with your clinic" flag, and publishing is gated behind your team confirming medications, warning signs, follow-up and contact details against the paperwork.
Is AI training on our information?
No. Guide content is processed by Anthropic's Claude API, which does not use API data to train models. Processing is transient — what persists is the guide your team publishes, nothing else. No document content is ever written to our server logs.
Does data leave Australia?
Storage stays in Sydney. The one exception is the AI step itself: notes are transiently processed through the AI provider in the United States (not retained long-term, never used for training) — the same pattern as most cloud healthcare software your clinic already uses.
Whose data is it, and can it be deleted?
Yours. The clinic (or the owner) controls the guide, can edit or unpublish it at any time, and can have it permanently deleted on request — email hello@gotitguides.com with the link, no questions asked. We use the information solely to generate and serve the guide: no advertising, no data resale, and anonymous first-party analytics only.
What about consent?
The workflow builds it in: before a clinic-created guide can be published, the person publishing confirms they have the owner's consent to create and send it. A sentence at discharge is all it takes — "Would you like your discharge instructions as a digital guide? We'll securely process today's notes into an easier-to-follow format."
Questions we haven't answered here? A real person reads hello@gotitguides.com — usually within a day. The fine print lives in the data processing summary and the privacy policy. There's also a printable one-page summary if it's easier to hand your practice manager a sheet of paper.