Notice version: 30 October 2026. Responsible contact: Dr Pramod G Kulkarni, +91 9561394341.
With permission documented by the doctor, a coded trend history can be stored for reviewing measurements across visits and devices. It contains a generated patient code, dates/times, entered measurements, any entered notes, revisions and the permission record. The new cloud-save flow sends the generated code instead of the local display name. Please avoid names, phone numbers and addresses in notes. A code does not make medical data anonymous.
Cloud histories are available through the clinic owner’s authenticated account. Vercel runs the website backend; Supabase stores the history in the configured project. The storage region is determined by that project’s settings and is not asserted in this notice. Local browser copies and exported files are separate. Research agents and public article pages are not authorised to read these records. This notice is not permission to share a patient history with an AI provider.
The doctor should explain this notice in a language you understand, discuss alternatives and document permission before the first upload. You can ask for correction or withdrawal of permission by contacting the doctor. If a guardian gives permission, the doctor must check their authority. A checkbox records the doctor’s attestation; it does not independently verify consent or satisfy every clinical/legal requirement.
Contact the doctor to request correction or deletion. The owner can delete the current cloud trend copy after confirming its patient code and revision. Required clinical retention obligations must be checked first. Deletion does not automatically remove other device copies, downloaded PDFs, recipient copies or provider backups. Minimal audit metadata, such as code, event and timestamp, may remain; provider backups follow their retention settings. No universal retention duration or instant erasure from every backup is promised.
Older cloud records may have been uploaded before this notice and may contain a name. The doctor must review and convert them using the new coded save flow; no past consent is assumed. HTTPS and access controls reduce risk but do not establish complete regulatory compliance. Avoid shared browser profiles and protect downloaded files.