Legal
Data Processing Agreement
In short
- This agreement is made between the Practice (controller) and Simbions Kft. (processor) when the Practice stores scans and patient data in Sinus3D.
- Simbions Kft. processes patient data only on the Practice's instructions and only to provide the Service. It does not use, sell or analyse the data for its own purposes.
- The data is kept on Simbions Kft.'s own servers in Hungary and is not transferred outside the EEA.
- Simbions Kft. notifies the Practice of a personal data breach without undue delay and no later than 48 hours.
The User acting on behalf of the Practice accepts this agreement when creating the Practice. The Service records the time, the version and the User who accepted it.
1. Parties
- Controller
- the dental practice registered in Sinus3D (the "Practice"), with the details given at registration and in its billing details.
- Processor
- Simbions Korlátolt Felelősségű Társaság (Simbions Kft.), registered office: Nagymező utca 23. I. em. 3., 1065 Budapest, Hungary, tax number: 23802834-2-42, company registration number: 01-09-978543 (the "Processor").
This agreement is a contract under Article 28(3) of the General Data Protection Regulation (GDPR) and forms an integral part of the Sinus3D Terms of Use. If they conflict, this agreement prevails as regards the processing of personal data.
2. Subject-matter, duration, nature and purpose
- Subject-matter: storing and displaying dental imaging and related documents uploaded by the Practice, and sharing them with dentists the Practice designates.
- Duration: for as long as the Practice's subscription is active, plus the return and deletion period in section 11.
- Nature: storage, organisation, retrieval, display, transmission (sharing on the Practice's instructions), backup and erasure.
- Purpose: solely to provide the Service to the Practice.
3. Data subjects and categories of data
- Data subjects: the Practice's patients; the Practice's staff and the dentists connected with it (at user account and log level).
- Data: the patient's name and date of birth; imaging and the metadata it contains (for example further identifiers, acquisition time, device details); the content of documents uploaded by the Practice; logs of sharing and access.
- Special categories: scans and documents are data concerning health (GDPR Article 9).
4. Rights and obligations of the Practice
As controller, the Practice is responsible for having a valid legal basis for the processing (typically GDPR Article 9(2)(h)), for informing its patients, and for uploading and sharing only data it is entitled to. The Practice is responsible for the security of its own workstations (screen lock, up-to-date software, malware protection), and for granting access only to authorised staff and revoking it when they leave. It gives instructions by using the functions of the Service (upload, share, revoke, delete) or in writing.
5. Obligations of the Processor
The Processor:
- processes personal data only on documented instructions from the Practice, including with regard to transfers outside the EEA, and informs the Practice without delay if it considers an instruction to infringe the law;
- ensures that persons with access to the data have committed to confidentiality or are under a statutory obligation of confidentiality;
- takes the security measures described in section 7 and Annex 1 (GDPR Article 32);
- engages sub-processors only in accordance with section 8;
- assists the Practice, by appropriate technical and organisational measures, in responding to requests from data subjects (GDPR Chapter III);
- assists the Practice in meeting its obligations under GDPR Articles 32 to 36 (security, breach notification, data protection impact assessment, prior consultation);
- makes available to the Practice all information necessary to demonstrate compliance with these obligations and allows audits under section 10.
The Processor does not use, sell or analyse patient data for its own purposes and does not create statistics or other products from it. It may process technical data needed to operate the Service that does not contain personal data (for example, the amount of storage used).
6. Operator access
The Service is built so that the Processor's operator interface shows practices, users and storage, but not patient data or scans. The Processor's staff access patient data only where this is essential to troubleshooting requested by the Practice or to comply with a legal obligation. Any such access is documented.
7. Security
The Processor applies technical and organisational measures appropriate to the risk. They are listed in Annex 1. The Processor may improve the measures as technology evolves but may not lower the level of protection.
8. Sub-processors
The Practice gives general authorisation for the engagement of sub-processors. The Processor informs the Practice at least 30 days in advance of any new or replaced sub-processor, and the Practice may object. If the objection cannot be resolved, the Practice may terminate this agreement and its subscription with a refund. The Processor imposes on each sub-processor the same data protection obligations as set out in this agreement and remains liable for their performance.
The current list of sub-processors is in Annex 2.
9. Personal data breaches
The Processor notifies the Practice of a personal data breach without undue delay and no later than 48 hours after becoming aware of it. Where available, the notification describes the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Information may be provided in phases if it is not all available at once. The Processor assists the Practice in notifying the supervisory authority (GDPR Article 33) and data subjects (GDPR Article 34).
10. Audits
The Practice, or an auditor it appoints who is bound by confidentiality, may audit compliance with this agreement by prior arrangement, at most once a year, and additionally after a breach or at the request of a supervisory authority. The Processor demonstrates compliance primarily through written documentation (description of measures, log extracts, certifications where available). An audit must not compromise the security of other practices' data.
11. End of processing
When the subscription ends, the Processor allows the Practice to download its scans and documents for 60 days. If the subscription ends because of cancellation or a failed payment, partner dentists and the links sent to patients can still access the scans the Practice shared during this grace period; if the Practice closes its account itself, this access ends immediately. After that, the Processor deletes the Practice's personal data unless the law requires further storage. Data is removed from backups through their normal rotation, no later than a further 90 days. The Processor confirms deletion in writing on request.
Meeting statutory retention obligations (for example, under Hungarian law, 10 years for imaging and 30 years for reports) is the responsibility of the Practice as controller. If the Practice wishes to meet them in Sinus3D, it must keep its subscription active or download the data before the subscription ends.
12. International transfers
The Processor processes personal data within the European Economic Area, in Hungary, and does not transfer it to third countries. The exception is when the Practice itself shares a scan with a dentist outside the EEA; the Practice is responsible for the lawfulness of that transfer.
13. Liability, term and changes
Liability is governed by GDPR Article 82 and the liability provisions of the Terms of Use. This agreement takes effect when the Practice is created and remains in force until processing ends under section 11. The Processor gives at least 30 days' notice of any change and asks the Practice to accept the new version. This agreement is governed by Hungarian law.
Annex 1 · Technical and organisational measures
- Encrypted connections: HTTPS only (TLS 1.2 or later) between browser and server.
- Separation of practices: row-level access control in the database (PostgreSQL Row-Level Security). A user of one Practice cannot technically access another Practice's data. Automated tests verify the separation.
- Access control: personal accounts confirmed by email; passwords stored in a form that cannot be reversed; limits on sign-in attempts; two-step sign-in (passkey or authenticator app), mandatory for the Practice's owners and administrators; automatic sign-out after 12 hours of inactivity; roles (admin, uploader, viewer).
- Sharing: only through mutually approved connections or through share links that expire and can be revoked; every view and download is logged, and the log cannot be altered.
- Notifications: email notifications about sharing contain no patient data (only the sharing Practice's name and a sign-in link); the scan can only be opened after signing in.
- Limited operator access: the operator interface does not display patient data.
- Malware scanning: every uploaded file is scanned for viruses on the Processor's own server before it is saved (ClamAV, signatures updated daily); the file does not leave the server for this. Infected files are not saved. Uploads are also checked for a match between content and file extension, and executable file types cannot be uploaded.
- Client-side processing: the DICOM viewer and document previews run in the browser; scan content is never sent to third-party services.
- Infrastructure: the Processor's own server in a locked room in Hungary; firewall; only required services reachable from outside; the application runs under an isolated, unprivileged system user; regular security updates.
- Organisational measures: confidentiality obligations for staff with access; changes are made under version control and are traceable.
- Encryption at rest: scans and the database are stored on AES-256-GCM encrypted storage (ZFS native encryption); the encryption key exists only on the server and in the encrypted backup.
- Availability and backups: data on mirrored disk pairs (ZFS mirror, across two separate disk enclosures and two separate controllers), the system disk is also mirrored (RAID1) — the failure of one disk, enclosure or controller causes no data loss; two power supplies; automatic restart and self-check after a power cut; daily encrypted backup (AES-256) of the database, scans and settings to a separate physical medium and to an off-site storage within the European Union (Annex 2); backups are kept for at most 90 days; restoration is verified by an automatic monthly test.
- Monitoring and incident response: automatic monitoring of the server, disks, backups and services with immediate alerts; a written incident response procedure; the Processor notifies the Controller of a personal data breach without undue delay and at the latest within 48 hours (Section 9).
Annex 2 · Sub-processors
Patient data are stored and processed on the Processor's own server in Hungary. The Processor uses the following sub-processors:
Off-site backup (since 2 October 2026): Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany — storage for backups in a German data centre. The provider receives only data already encrypted by the Processor; it has no access to the encryption key and therefore cannot learn the content of patient data.
Email delivery: Websupport Magyarország Kft., Fehérvári út 97–99, 1119 Budapest, Hungary — delivery of the Service's notification emails through the info@sinus3d.com mailbox. Messages contain the recipient's email address and the notification text; no patient data (a scan can only be opened after signing in).
A data processing agreement with Hetzner Online GmbH under Art. 28(4) GDPR was concluded on 2 October 2026 (covering the backups encrypted in advance by the Processor, including health data); the technical and organisational measures of its data centres were audited by TÜV Rheinland, and Hetzner holds ISO/IEC 27001 certification. The agreement is available to the Controller on request.