#1. Parties and scope
This DPA is between the Clinic (the “Controller”) and [Company Name] (Private) Limited (“Enamela”, the “Processor”). It applies to all Patient Data that Enamela processes for the Clinic through the Service, and it forms part of the Terms of Service. Capitalised terms not defined here have the meaning in the Terms.
#2. Details of the processing
| Item | Description |
|---|---|
| Subject matter | Providing the Enamela dental practice management service to the Clinic. |
| Duration | The term of the Clinic's account, plus the retention period in section 11. |
| Nature and purpose | Storing, organising, displaying, transmitting, backing up and deleting Patient Data so the Clinic can schedule, chart, bill, message and manage its patients. |
| Data subjects | The Clinic's patients and prospective patients, their guardians or emergency contacts, and people who book through the Clinic's booking page. |
| Personal data | Identity and contact details; appointment history; dental charts, treatment notes, plans, prescriptions, images and files; billing and payment records; messages sent through the Service; consent records. |
| Special categories | Health data, which the parties treat as sensitive and protect accordingly. |
#3. Controller's responsibilities
- Have a lawful basis, and any patient consent required, for the processing it instructs.
- Provide patients with the privacy information the law requires.
- Make sure its instructions comply with applicable law, including health-record and data protection rules where it operates.
- Manage its Users, roles and access within the Service.
#4. Processing on instructions
Enamela processes Patient Data only on the Clinic's documented instructions. The Terms, this DPA and the Clinic's use and configuration of the Service are the Clinic's complete instructions. Enamela will tell the Clinic if it believes an instruction breaks the law, and will not process Patient Data for its own purposes, sell it, or use it for advertising or to train AI models.
#5. Confidentiality of personnel
Enamela allows access to Patient Data only to personnel who need it to provide or support the Service, who are bound by confidentiality obligations, and who are trained on data protection. Support access to a Clinic's account requires the Clinic's permission and is recorded in its audit log.
#6. Security measures
| Area | Measure |
|---|---|
| Encryption | TLS for all data in transit; encryption at rest for databases, backups and file storage. |
| Tenant isolation | Every record is tied to a Clinic, and every query is limited to the signed-in Clinic. |
| Access control | Role-based permissions in the Service; least-privilege access for Enamela staff. |
| Logging | An audit log of access to and changes in patient records, visible to the Clinic. |
| Backups and recovery | Automated daily backups by our database provider, kept for a rolling retention window. |
| Application security | Code review, dependency monitoring, input validation, rate limiting and bot protection on public forms. |
| Monitoring | Error and uptime monitoring configured to avoid collecting Patient Data; alerts to the engineering team. |
| Certifications | Enamela does not yet hold SOC 2, ISO 27001 or HIPAA certification. Our providers hold their own certifications, listed on their websites. |
Enamela may update these measures over time, provided the overall level of protection does not decrease.
#7. Subprocessors
The Clinic gives general authorisation for Enamela to use subprocessors. The current list is on the Subprocessors page. Enamela will give at least 30 days' notice before adding or replacing a subprocessor that processes Patient Data. If the Clinic objects on reasonable data protection grounds and the parties cannot agree a solution, the Clinic may terminate the affected part of the Service and receive a refund of prepaid fees for the unused period. Enamela imposes data protection terms on each subprocessor no less protective than this DPA and remains responsible for them.
#8. Assistance to the Controller
- Data subject requests: the Service lets the Clinic access, correct, export and delete patient records. If a patient contacts Enamela directly, Enamela will refer them to the Clinic and will not respond itself unless the Clinic instructs it to.
- Enamela will provide reasonable help with the Clinic's data protection impact assessments and consultations with regulators, where they relate to the Service.
#9. Personal data breaches
Enamela will notify the Clinic without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting the Clinic's Patient Data. The notice will describe, as far as then known, what happened, the data and patients likely affected, the likely consequences, and the steps taken or proposed. Enamela will update the Clinic as it learns more and will help it meet its own notification duties. Notifying the Clinic is not an admission of fault.
#10. International transfers
Patient Data is stored in Singapore (ap-southeast-1). Enamela will transfer Patient Data to another country only where the transfer complies with the law that applies to the Clinic, using appropriate safeguards such as standard contractual clauses or the transfer mechanisms set out in that law. Where a country requires health data to stay inside the country, the country addendum describes the arrangements, and Enamela will not move the data without first agreeing a compliant option with the Clinic.
#11. Return and deletion
During the term, the Clinic can download bills and reports from the Service and can request a complete export of its Patient Data, which Enamela provides within 14 days. When the Clinic's account ends, Enamela keeps Patient Data for 90 days so the Clinic can export it, then deletes it from live systems; deleted data is removed from backups as they expire within a further 35 days. Enamela will confirm deletion in writing on request. Enamela may keep data only where the law requires it to, and then protects it under this DPA.
#12. Audits
Enamela will provide the information reasonably needed to show compliance with this DPA, including answers to security questionnaires and summaries of its controls. If that is not enough, or a regulator requires it, the Clinic may carry out an audit once per year, at its own cost, with 30 days' notice, during business hours, through an auditor bound by confidentiality, and in a way that does not compromise other clinics' data or the security of the Service.
#13. Liability and precedence
Each party's liability under this DPA is subject to the limitations in the Terms of Service, except where the law does not allow such a limit. If this DPA conflicts with the Terms about Patient Data, this DPA prevails; if a country addendum imposes stricter requirements, the addendum prevails for Clinics in that country.
#14. Contact
Data protection questions, and requests for a countersigned copy of this DPA: privacy@enamela.app.
Questions about this document? Email legal@enamela.app.