Privacy Policy
What data we collect about you, why, and what rights you have under GDPR.
Last updated:
At a glance
- What data? The minimum needed — email, name, clinic name, IP for security, cookieless visit statistics for dentaflow.bg.
- What for? To deliver the platform, bill correctly, and improve the product.
- Who sees it? Our team and our sub-processors, each only for its specific function (full list in 4.2 and on the Subprocessors page).
- How long? Active data: while the clinic has an account; after a deletion request, a 30-day window to cancel, then the data is deleted. Accounting records: for the periods set by the Bulgarian Accountancy Act.
- Your rights? Access, rectification, erasure, restriction, portability, objection. Details below.
1. Who we are
The data controller is Mag Vision Ltd. (UIC 203220345, VAT No. BG203220345), Gotse Delchev, Bulgaria.
Data-protection contact: contact@dentaflow.bg.
Important for clinics: For patient data your clinic stores in DentaFlow, the clinic is the controller and we are the processor. Details in our DPA.
1a. If you are a clinic’s patient
When you use the patient portal, the online booking page (/book) or the /intake form of a clinic that works with DentaFlow, your data controller is the clinic. We process the data on its behalf and on its instructions as a processor (DPA). Send your GDPR requests to the clinic.
- If the clinic has switched on the AI chat, the booking page opens a chat whose replies are generated by an Anthropic AI model (US); you can choose the plain form instead.
- Sign-in, booking and the /intake form are protected from bots by hCaptcha.
2. What data we collect (clinic users)
2.1 Data you give us
- First and last name
- Phone (optional)
- Position/specialty at the clinic
- Clinic name and EIK (tax ID)
- Payment data (processed via Stripe — we never see card numbers)
2.2 Data generated automatically
- Access logs (IP, time, action)
- Technical data (browser, OS)
- Product usage patterns (which features you use, how often)
2.3 Data we do NOT collect
- No third-party tracking cookies
- No ad-network data sharing
- No fingerprinting for tracking or advertising. For bot protection hCaptcha checks browser signals at sign-in, sign-up, invite acceptance and on the patient forms; the site statistics recognise a visitor for 24 hours only, through a hash of the request.
3. Why we process this data
| Purpose | What we process | Legal basis |
|---|---|---|
| Service delivery | Name, email, phone, company data | Performance of contract |
| Invoicing | Payment data, company data | Contract + legal obligation |
| Security | IP, access logs | Legitimate interest |
| Product improvement | Clinic-level usage data (action counts, timings, no clinical content) | Legitimate interest |
| Usage review for refund requests (30-day guarantee) | Access logs, number of patient records created, scheduled appointments, active doctor profiles, days of activity | Legitimate interest (GDPR Art. 6(1)(f)) — fraud prevention and contract enforcement |
| Answering inquiries and demo requests from dentaflow.bg | Email, name, clinic, clinic type, inquiry text and follow-up messages, page, UTM parameters from the URL, salted hashed IP | Pre-contractual steps (Art. 6(1)(b) GDPR) + legitimate interest; the database deletes them automatically after 12 months (spam after 30 days). The inquiry is also forwarded by email to contact@dentaflow.bg. |
| Visit statistics for dentaflow.bg (Vercel Web Analytics) | Pages viewed, referrer, country, device and browser type, events such as a sent demo request. No cookies. A visitor is recognised through a hash of the request, which Vercel discards after 24 hours; no emails or names are collected | Legitimate interest (Art. 6(1)(f) GDPR) |
| Legal compliance | Accounting records (invoices) | Legal obligation |
The usage review for the 30-day money-back guarantee is only triggered if a clinic submits a refund request under Terms, Art. 9. It is limited to aggregate usage signals (record counts, days of activity, scheduled appointments) — we don’t open the clinical content of patient files. The balancing test: our legitimate interest in preventing bad-faith refund claims and in protecting our product from feature-copying attempts outweighs the minimal intrusion into usage data needed to determine whether the clinic actually tried the platform.
4. Who sees your data
4.1 Our team
Need-to-know access only. In-app actions are recorded in an audit log. For support, a team member can sign in to the clinic’s account (“sign in as clinic”) with the full rights of its owner; every such sign-in is recorded in our internal log, which the clinic cannot see. The platform administrators also have direct database access; it is not recorded in the app’s audit log.
4.2 Sub-processors
- Supabase (database and files; Supabase Pte. Ltd., Singapore) — AWS infrastructure, region eu-west-1, Ireland
- Stripe (payments; Stripe Payments Europe, Ltd., Ireland, with Stripe, LLC in the US) — under Stripe’s DPA
- Resend (transactional email, incl. patient reminders; Plus Five Five, Inc.) — sends from region eu-west-1, logs and metadata are stored in the US; under Resend’s DPA
- Vercel (site and app hosting; visit statistics for dentaflow.bg) — Vercel Inc., US; global CDN; under Vercel’s DPA
- Cloudflare (DNS for managed clinic websites) — Cloudflare, Inc., US/global
- Anthropic (AI models; US, no EU processing option) — used by: the AI assistant for the clinic team and the booking chat on /book (both off by default; the clinic switches them on in Settings → Modules); help with importing patients from CSV (the column headers and up to 5 sample rows, which can include ЕГН/personal ID numbers, allergies and notes); translation of service names (names only); wording of treatment-plan documents (off by default, enabled by us for a specific clinic). Under Anthropic’s public commercial terms the data is not used to train models and is kept for up to 30 days.
- hCaptcha (Intuition Machines, Inc.; bot protection at sign-in, sign-up, invite acceptance, /book and /intake; receives the IP address and browser signals) — US
- Google (Google Fonts, loaded from Google’s servers on dentaflow.bg and app.dentaflow.bg — the visitor’s IP reaches Google) — US/global
Integrations you connect yourself. Google Calendar sync works only if you connect your own Google account; Google LLC then processes the data under your Google account terms, not as our sub-processor.
Transfers outside the EU/EEA. Anthropic, Resend, Stripe, Vercel, Cloudflare, hCaptcha and Google also process data in the US — under each provider’s DPA with Standard Contractual Clauses, or under the EU-US Data Privacy Framework where the provider is certified.
Cookies and local storage — see the Cookie Policy. Full list with locations and what data each sub-processor sees — on the Subprocessors page and in the DPA.
4.3 Government bodies
Only on legal demand (court order, NAP/tax authority inspection, etc.). We notify you when allowed.
The information systems to which the clinic submits data through DentaFlow (NHIS/НЗИС; NHIF/НЗОК reports, for which DentaFlow generates the XML file that the clinic uploads) are not our sub-processors — the data is submitted on the clinic’s instructions.
5. How long we keep data
- Active account — while the clinic has an account. After a clinic deletion request there is a 30-day window in which it can be cancelled; after that our team carries out the final deletion. Data is not deleted automatically when a subscription ends.
- Accounting records (invoices) — for the periods set by Art. 12 of the Bulgarian Accountancy Act (up to 10 years)
- Audit log and security logs — 12 months (365 days) by default; the clinic can set another period, no shorter than 90 days; records of deleted clinics — 2 years
- AI usage counters and rate-limit records for the booking page (with a hashed IP address) —
After these periods the data is deleted; copies in automatic backups expire when the backup retention period ends.
6. Your rights (GDPR Articles 15–22)
- Right of access — get a copy of the data we hold about you
- Right of rectification — correct inaccurate data
- Right of erasure — request deletion (“right to be forgotten”)
- Right to restriction — pause processing temporarily
- Right to portability — get data in a machine-readable format. The clinic admin downloads the clinic’s data as a ZIP of JSON files from Settings → Subscription → “Data export”; the archive does not include uploaded files or signed PDF documents.
- Right to object — object to processing based on legitimate interest
- Right to withdraw consent — for consent-based processing
Send requests to contact@dentaflow.bg. We reply without undue delay and within one month at the latest (Art. 12(3) GDPR); for complex requests this can be extended by two further months, and we will tell you if so.
7. Filing a complaint
If you believe we’re mishandling your data, you can file a complaint with the Commission for Personal Data Protection (CPDP), 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria, cpdp.bg (Art. 77 GDPR).
8. Changes to this policy
We email registered users about material changes at least 30 days in advance. The current version and its date are always on this page.
Version: 1.0 Effective: 7 November 2026 Last updated: 7 November 2026
Other legal documents