Data Processing Agreement (DPA)
Agreement under Art. 28 GDPR between each clinic (controller) and Mag Vision Ltd. (processor).
Last updated:
Data Processing Agreement
under Art. 28(3) of Regulation (EU) 2016/679 (the “GDPR”) between:
- Controller: the Clinic — the healthcare establishment holding a DentaFlow account (the “Controller”);
- Processor: Mag Vision Ltd. („Маг Вижън“ ЕООД), UIC 203220345, Gotse Delchev, Bulgaria (the “Processor”).
Section I. Conclusion, Subject Matter and Hierarchy
Art. 1. (1) This agreement (the “DPA”) is an integral part of the Terms of Service and is deemed concluded in electronic form (Art. 28(9) GDPR) upon their acceptance. Upon request, the Processor provides a copy (PDF) of the accepted version signed by it, for counter-signature by the Controller.
(2) Subject matter: processing of personal data of patients and related persons on behalf of the Controller, necessary for the provision of the DentaFlow service, with the scope set out in Annex 1.
(3) In the event of a conflict between this DPA and the Terms of Service on data protection matters, the DPA prevails.
Art. 2. Duration: for the term of the service contract, plus the period under Art. 9 until the deletion/return of the data.
Section II. Obligations of the Processor
Art. 3. The Processor processes the personal data only on documented instructions from the Controller, including with regard to transfers of data to a third country, unless required to do so by EU or Member State law — in which case the Processor informs the Controller of that legal requirement before processing, unless that law prohibits such notification. The Controller’s use of the Platform’s functionality constitutes a documented instruction.
Art. 4. The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or another data protection provision.
Art. 5. The persons authorised to process the data have committed themselves to confidentiality. For health data, the Processor additionally ensures an obligation of professional secrecy equivalent to that owed by medical personnel.
Art. 6. The Processor implements the technical and organisational measures set out in Annex 2 (Art. 32 GDPR) and keeps them up to date relative to the level of risk.
Art. 7. Assistance. The Processor, taking into account the nature of the processing:
- assists the Controller by appropriate technical and organisational measures in fulfilling the Controller’s obligation to respond to requests from data subjects (Arts. 12–23 GDPR);
- assists the Controller with the obligations under Arts. 32–36 GDPR (security, breach notification, data protection impact assessments, prior consultations), taking into account the information available to the Processor;
- if a data subject sends a request directly to the Processor, forwards it to the Controller without undue delay and does not answer it on the merits without the Controller’s instruction. For such requests the Controller has, in the Platform, the export of the clinic’s data (Art. 9(1)) and the editing and deletion of records.
Art. 8. Security breaches. The Processor notifies the Controller without undue delay after becoming aware of a personal data breach affecting the Controller’s data, and in any event no later than 72 hours, to the account email address (and to a designated alternative contact). Where it is not possible to provide all information at the same time, it is provided in phases without undue delay. The notification includes: the nature of the breach; the categories affected and the approximate number of data subjects and records; the likely consequences; the measures taken and proposed; recommendations to the Controller.
Notifying the Bulgarian DPA (CPDP, Art. 33(1) GDPR) and the affected data subjects (Art. 34 GDPR) is the Controller’s obligation; the Processor assists with the information available to it and does not notify the CPDP or the data subjects on the Controller’s behalf without its instruction.
Art. 9. End of processing. (1) Until termination and until deletion under para. 2, an administrator of the clinic can download its data using the “Data export” function (Settings → Subscription) — a ZIP archive of JSON files of the records. The export does not include uploaded files (images, documents) or signed PDF documents; the Processor provides these on the Controller’s written request.
(2) The Controller can request deletion of the clinic’s account from the Platform. The request can be withdrawn within 30 days. When that period ends, an operator of the Processor confirms and carries out the deletion of the Controller’s personal data and of its staff’s user accounts; the action is recorded in the Processor’s log of administrative actions.
(3) Where the service ends without a deletion request (e.g. on non-payment or expiry of the subscription), the Processor does not delete the data automatically; it remains available for export under para. 1 until the Controller requests its deletion.
(4) Paras. 2 and 3 do not apply to the extent that EU or Bulgarian law requires retention (e.g. the rules on medical and accounting records) — the Processor informs the Controller of the duration and scope of any such retention. Copies of the database in backups lapse when their retention period ends.
Art. 10. Audits. The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR and allows for and contributes to audits, including inspections, conducted by the Controller or an auditor mandated by the Controller — subject to reasonable notice, during business hours, no more than once per year (except following a breach), under confidentiality undertakings and at the Controller’s expense.
Section III. Sub-processors
Art. 11. (1) The Controller gives a general written authorisation for the engagement of the sub-processors listed in Annex 3 (current public list: /en/subprocessors).
(2) The Processor notifies the Controller at least 30 days before adding or replacing a sub-processor. The Controller may object on reasonable, data-protection-related grounds; in the absence of an acceptable alternative, the Controller may terminate the service with a pro-rata refund of the prepaid amount.
(3) The Processor concludes with each sub-processor a data processing agreement under Art. 28(4) GDPR (the provider’s standard DPA, accepted with the service contract) and remains fully liable to the Controller for the performance of the sub-processor’s obligations.
Section IV. Transfers outside the EU/EEA
Art. 12. (1) Primary storage (database, files, backups) and the execution of the Platform’s server functions take place in the EU (Ireland region, eu-west-1).
(2) Individual sub-processors process data outside the EU/EEA (mainly in the USA) only under a mechanism pursuant to Chapter V GDPR — an adequacy decision (EU-US Data Privacy Framework) for certified sub-processors and/or standard contractual clauses (Decision (EU) 2021/914), as specified per sub-processor in Annex 3. As at the date of this version this covers the AI features (Anthropic), the metadata and logs of sent emails (Resend), bot checks on forms (hCaptcha), font loading in the app (Google Fonts) and the database provider’s support and telemetry (Supabase).
(3) AI features: the staff AI assistant and the AI chat on the online booking page are off by default and are switched on explicitly by the Controller, each separately, in Settings → Modules; while the AI chat is off, the booking page shows the form only. AI column suggestions when importing patients from a CSV file (sends the column headers and up to 5 sample rows) are triggered by a staff member during the import. AI wording in treatment-plan documents is off by default and is enabled by the Processor for a specific clinic.
Section V. Final Provisions
Art. 13. The clauses of this DPA may not be amended unilaterally to the detriment of data protection; amendments follow the procedure of the Terms of Service, Section XI, with the 30-day notice period applying to material amendments of the DPA.
Art. 14. Matters not settled herein are governed by the GDPR, the Bulgarian Personal Data Protection Act (ЗЗЛД) and Bulgarian law.
Contact for this DPA: contact@dentaflow.bg, subject “DPA — [clinic name]”.
Annex 1 — Description of the Processing
| Subject matter | Processing of personal data necessary for the functionality of DentaFlow (electronic health record, scheduling, documents, invoicing, patient communication) |
| Duration | The subscription term + the period under Art. 9 |
| Nature and purposes | Storage, structuring, retrieval, look-ups, preparation of documents, sending of messages — on the Controller’s instructions |
| Categories of data subjects | Patients; legal representatives of minor patients; emergency contacts; persons who request an appointment or send an inquiry through the clinic’s booking page or website; dental-lab staff using the lab portal; clinic staff (as users) |
| Categories of data | Identification data (ЕГН/ЛНЧ (Bulgarian personal identification numbers for citizens/foreign residents), names, date of birth, sex); contact data (address, phone, email); health data — special category under Art. 9 GDPR (diagnoses, dental status, treatments, prescriptions, images, signed consents incl. electronic signatures from a signature pad); financial data (invoices, payments, outstanding balances); notes and documents entered by the doctor; documents submitted to and responses from НЗИС (the national health information system); health-insurance status checks (ЕГН) with the National Revenue Agency (НАП); hashed IP addresses for abuse protection |
| Recipients that are not sub-processors | Public authorities to which the Platform sends data on the Controller’s instructions: НЗИС (НЗОК/Ministry of Health) — medical documents; НАП — health-insurance status check by ЕГН; НЗОК ПИС — through the local DentaFlow Bridge component on the Controller’s computer |
Annex 2 — Technical and Organisational Measures (Art. 32 GDPR)
Access and isolation: isolation between clinics via Row Level Security in the database for access from the application; server functions that run with a service key restrict every query to the user’s clinic in their code; role-based access model; mandatory two-factor authentication (TOTP) for clinic staff users: the application does not allow work without an enrolled second factor, and once it is enrolled the database refuses access to the clinic’s data without second-factor confirmation.
Change log: creating, changing and deleting clinical, scheduling and billing records is logged; the log is kept 365 days by default, and the clinic can choose from 90 days to 5 years. Views (reads) of records are not logged.
Access by the Processor’s staff: to the Controller’s data — only where necessary for support, troubleshooting, fulfilling a request of the Controller or as required by law. Signing in “as the clinic” from the admin panel gives full access (read and write) as the clinic owner, requires a stated reason and is recorded in the Processor’s log, which the clinic cannot see; the application ends such a session automatically after 30 minutes. On request the Processor provides the Controller with an extract of that log. The Processor also has technical access to the production database (service key and administrator access), used for support and troubleshooting; reading data through such access is not logged.
Encryption: data at rest, incl. backups — AES-256 (managed by the database provider); data in transit between the browser, the Platform and sub-processors — HTTPS (TLS).
Backups: backups of the database made and kept by its provider (Supabase) in the project region (Ireland). Uploaded files (images, PDFs) are kept in storage in the same region.
Personnel: confidentiality and professional secrecy obligations (Art. 5); access restricted on a need-to-know basis.
КЕП (qualified electronic signature) specifics: the private key of the doctor’s qualified electronic signature stays on the Controller’s computer — signing takes place locally through the DentaFlow Bridge component. Signed documents are sent through the Platform to НЗИС and stored as part of the records; the Platform also keeps the short-lived НЗИС access tokens.
The measures are reviewed periodically; their current public description is available at /en/security. The Processor lists here only measures that are actually implemented.
Annex 3 — Sub-processors
The current, dated list is maintained at /en/subprocessors and forms an integral part of this annex. As at 19 October 2026 it includes:
| Sub-processor | Role | Region | Health data? | Transfer mechanism |
|---|---|---|---|---|
| Supabase Pte. Ltd. (infrastructure: AWS) | Database, auth, storage, server functions, backups | Ireland (eu-west-1); provider support and account data also outside the EU | Yes | Supabase DPA + SCCs 2021/914 (Module 3) |
| Stripe Payments Europe, Ltd. | Subscription payments and invoicing of clinics. Patient deposits and instalments go through the clinic’s own Stripe account. | Ireland (EU); Stripe, LLC (US) | No | Stripe DPA + SCCs; Stripe, LLC — EU-US DPF |
| Plus Five Five, Inc. (“Resend”) | Emails to patients and staff: reminders (appointments, overdue items, amounts), messages between clinic and patient and the patient’s replies, portal invites, links to documents | Sending from Ireland (eu-west-1); logs and metadata stored in the US | Yes (the content shows the link to the clinic; messages may contain health information) | Resend DPA + SCCs 2021/914; EU-US DPF |
| Vercel Inc. | Hosting of the app, the website and managed clinic websites | Global CDN; mainly US | No (static files; technical request logs) | Vercel DPA + SCCs; EU-US DPF |
| Cloudflare, Inc. | DNS for managed clinic websites | Global | No | Cloudflare DPA + SCCs; EU-US DPF |
| Anthropic Ireland, Limited | Staff assistant and AI chat on the booking page (off by default; switched on by the Controller); AI column suggestions in patient CSV import (sends up to 5 sample rows); AI wording in treatment-plan documents (only for clinics the Processor has enabled); translation of service names | US (no EU processing option) | Yes — names, phone numbers, visit and procedure types, messages, CSV sample rows, treatment-plan document text | Anthropic DPA + SCCs 2021/914 (Module 2/3); no training on the data (Anthropic Commercial Terms); requests kept up to 30 days under Anthropic’s public terms |
| Intuition Machines, Inc. (“hCaptcha”) | Bot protection on booking, intake, sign-in and invite forms | US | No (IP address and browser technical data) | |
| Google Ireland Ltd. / Google LLC (“Google Fonts”) | Font delivery in the app, the patient portal and the booking page | Global | No (IP address) |
Google Calendar sync is not a sub-processor — a doctor connects it, and Google processes the events under the terms of the doctor’s Google account (see /en/subprocessors, “Integrations you connect yourself”).
Version: 1.3 Effective from: 7 November 2026 Last updated: 7 November 2026
Other legal documents