Security & trust
Security & trust, in plain language.
What we do, what we deliberately don't claim, and how to check us.
Don't take our word for it
Three free, public scanners grade how foveal.in is secured. Click any seal to run the test yourself, right now.
Graded by independent scanners
Mozilla ObservatoryWeb securityRe-run test ↗
A+
Security Headerssecurityheaders.comRe-run test ↗
A+
SSL LabsEncryption · QualysRe-run test ↗
How Foveal is built and hosted
Hosted on SOC 2 Type II infrastructureFoveal runs on Amazon Web Services (AWS) in Mumbai,
independently audited to SOC 2 Type II.
The three seals are graded by third parties. The cards below them describe how Foveal is built and hosted.
Where your data lives
All clinic and patient data is stored in a professional data centre in Mumbai, India (AWS ap-south-1). Connections are encrypted with TLS; storage is encrypted at rest. Nightly backups are encrypted before they leave the database and are kept off-site, which may be outside India. Voice dictation, if your clinic switches it on, is processed outside India. Every provider is named in our privacy policy.
Who can see it
Only your clinic's staff, signed in with their own accounts. Isolation between clinics is enforced inside the database engine itself (row-level security), not just in the application — a bug in a screen cannot leak another clinic's records. Foveal's own platform administrators are structurally excluded from reading patient data: the database policies deny it, and our automated test suite proves that denial on every code change. Direct database access, for maintenance, is limited to one operator and logged.
DPDP, by design
- Consent is captured at patient registration — with timestamp and the staff member who recorded it.
- Every clinically significant action is written to an audit log scoped to your clinic.
- Your full clinic data is exportable as CSV by your clinic owner, anytime — including if you leave, and including during the 30-day money-back window.
- We act as a data processor on your clinic's behalf; your clinic remains the data fiduciary. Our privacy policy says this without fine print.
What we don't claim: there is no such thing as a "DPDP certificate", so we won't wave one at you. We build to the Act's obligations and put the mechanisms above in writing instead.
ABDM / ABHA
ABHA integration is on our roadmap — planned, not yet certified. When Foveal completes ABDM integration it will be announced here; until then we won't call ourselves ABHA-compliant, and we'd encourage you to ask any vendor who does for their certification details.
Backups & the boring discipline
- Automatic nightly backups, encrypted before they leave the database and stored off-site.
- Restores are tested, not assumed: a full backup has been restored end to end and checked. A backup that's never been restored is a rumour, not a backup.
- Error monitoring configured so we usually know about a problem before you message us.
Your notes are sacred
A design rule enforced across the product: nothing you typed is ever silently overwritten. Templates and "mark normal" fill only blank fields. Drafts autosave locally and survive power cuts, and local drafts are wiped when you sign out.
Honest limits
- Foveal works best online. If the internet drops, registrations, check-ins and payments are saved on the machine for up to 72 hours and sync on their own, and consultation drafts are kept on the machine too. It is not a full offline system.
- Foveal is a record-keeping tool. It does not make clinical decisions and never replaces clinical judgment.
- Patient-data encryption where even our infrastructure cannot technically read records (client-side encryption) is on the roadmap, not shipped today. We say "encrypted in transit and at rest" because that is exactly what is true.