Security
How we protect data — verifiable facts only.
Last updated:
Principle
This page contains only things that are true today — no “in-progress” certifications, no promises. When we add something, we add it here too.
Infrastructure and location
- Database and storage: Supabase, Ireland region (EU, eu-west-1), on AWS infrastructure. Data is stored in the EU (Ireland). Server (edge) functions run in the same region (eu-west-1) — requests from the app, our websites, webhooks and scheduled jobs are pinned to it.
- Processing outside the EU happens for: the AI features (Anthropic, US — under a DPA and standard contractual clauses; the staff assistant and the AI chat on the booking page are off by default and switched on by the clinic); the metadata and logs of sent emails (Resend, US); bot checks on forms (hCaptcha); font loading in the app (Google Fonts). Google Calendar sync sends events to Google only if a doctor connects their calendar. The full list is on Sub-processors.
- App and site: Vercel (global CDN; serves static files only and processes technical request logs).
Encryption
- At rest: AES-256, incl. backups (Supabase/AWS managed).
- In transit: HTTPS (TLS) between the browser and the platform and between the platform and sub-processors.
Access and isolation
- Every clinic is isolated via Row Level Security in the database. Server functions that run with a service key restrict every query to the user’s clinic in their code.
- Mandatory two-factor authentication (TOTP) for clinic staff — the app requires an enrolled second factor, and the database refuses data access without confirming it.
- Change log of records (create, update, delete) — kept 365 days by default, configurable from 90 days to 5 years. Views (reads) of records are not logged.
- Our team accesses a clinic’s data only when needed for support or at the clinic’s request. Signing in “as the clinic” gives full access as the clinic owner, requires a stated reason, is recorded in our log, and the app ends it automatically after 30 minutes; we give the clinic an extract of the log on request. We also have technical access to the production database for support; reads through it are not logged.
- The private key of the doctor’s qualified signature (КЕП) never leaves their machine — НЗИС signing happens locally through our Windows bridge.
Backups
- Database backups (Supabase), kept in the project region (Ireland).
Incidents
- On a suspected incident — internal escalation; we notify affected clinics without undue delay and no later than 72 hours so that they, as controllers, can notify the Bulgarian DPA (CPDP). For data where we are the controller (accounts, website), we notify the CPDP ourselves. Process described in the DPA.
Responsible disclosure
Found a vulnerability? Write to contact@dentaflow.bg — we respond with priority and take no action against good-faith researchers.
Other legal documents