Privacy policy

Who this document is for

It covers two different parties: a subscribing clinic and its staff, and a visitor to this website. What is held in the two cases is not the same, so the document keeps them apart instead of folding both into one sentence.

The patient record belongs to the clinic

The clinic collects its patients' details and the clinic is responsible for them. We hold and run that data so the clinic can work its day with it.

We do not sell a patient's data, we do not use it to train any model, and nobody on our team opens a clinic's data except for a technical reason the clinic itself has asked us to look at.

What the clinic enters into the system

Patient names and contact details, visits, diagnoses, prescriptions and treatment plans, scan and lab attachments, invoices, payments and expenses, and the clinic's own staff accounts and their permissions.

That data is separated at the database by row-level policies, and the attachments sit in a store that is not public. Each control and the place it is enforced is set out on the security page.

This website does not track you

There is no analytics tool on these pages: no Google Analytics and no substitute for it, no advertising pixel, no click map, no tracking library of any kind. We do not know who read this page or how long they stayed, and we have not built anything that could know.

When you write to support

A support ticket holds your name and email, your phone number if you write one, the subject and text of your message, the language you wrote in, and a tracking code stored hashed, from which the code itself cannot be recovered.

Because we do not run an email provider yet, no mail is sent and your address is not handed to any sending service; the reply appears on the ticket page itself.

When you ask for a tailored subscription

The request form holds your name, mobile, email, clinic name and city, the contact method you choose, and your notes if you write any.

Stored with them is a copy of the subscription lines you selected and their price at the moment you sent it, so our reply is about the same figures you saw and not different ones.

Your IP address is not stored

To stop the forms being flooded we store a digital fingerprint derived from your address together with the page path — not the address itself, and the fingerprint cannot be turned back into one. Those fingerprints are swept after two days.

Who processes the data with us

One party: Supabase, which runs the database, the file store and sign-in. No advertising network, no analytics service, and no external AI model provider today — the clinic assistant reads and writes inside your clinic's own database.

If we add an external provider later, we will write its name and what it sees on this page before it runs, not after.

How long the data stays

As long as the subscription does. When a subscription ends the system erases nothing by itself: there is no scheduled job that deletes a clinic's data, and it stays as it is until the clinic owner asks in writing for it to be exported or deleted, which we then carry out.

Support tickets are kept as a record of what was asked and when it was answered, being correspondence rather than a patient's file.

A patient's request goes to their clinic

If a patient wants a copy of their file, a correction to it, or its deletion, the request goes to the clinic treating them, which owns the file and is responsible for it. We help that clinic technically with whatever it decides.

Changes to this document, and who to ask

The date of the last change is printed in the margin of this page and comes from the text itself rather than being typed by hand, so it cannot claim a review that did not happen. If we change something that affects data already held, we tell subscribing clinics before the change takes effect.

The operating party's commercial details and registration are sent in writing on request from the support page.