CephNinja Data Processing Agreement

Last updated: 9 November 2026.

Between the dental practice or clinician accepting it (“Clinician”, the controller) and Cyncronus LLC, operating CephNinja (“CephNinja”, the processor).

This DPA is part of the CephNinja Terms of Service and applies whenever the Clinician uses the Service to process Patient Data. It is written to meet Article 28 GDPR and UK GDPR, the fiduciary–processor contract required by India’s DPDP Act 2023, and similar laws elsewhere.

1. Definitions

2. Roles and scope

2.1 For Patient Data, the Clinician is the controller (Data Fiduciary) and CephNinja is the processor (Data Processor).

2.2 CephNinja processes Patient Data only (a) to provide the features the Clinician sets up and uses — storage, organisation, cephalometric analysis, a requested written analysis summary and export — and (b) on the Clinician’s other documented instructions, unless the law requires otherwise, in which case CephNinja tells the Clinician unless the law forbids it.

2.3 Nature and duration: hosting, organising, automated analysis and retrieval of Patient Data for as long as the Clinician uses the Service, plus the deletion periods in Section 9.

3. Clinician responsibilities

The Clinician warrants that:

3.1 it has, and will keep, a lawful basis for all Patient Data it processes in the Service, and has given patients every notice the law requires;

3.2 for patients who are minors, it has obtained and recorded verifiable parental or guardian consent where required (including under Section 9 of the DPDP Act and the DPDP Rules) before uploading that patient’s data;

3.3 it will use the Service’s tools (deletion, correction, export) to act on patient requests, and remains its patients’ main contact;

3.4 it will not upload identifiable data of US patients unless a Business Associate Agreement with CephNinja is in force (Section 12).

4. CephNinja obligations

CephNinja will:

4.1 process Patient Data only as set out in Section 2 — never sell it, never use it for advertising or marketing, and never use it, identifiable or de-identified, to train or improve AI models;

4.2 make sure everyone authorised to process Patient Data is bound by confidentiality, and that staff access it only to provide support the Clinician asks for, keep the Service secure, or meet a legal requirement — with that access logged;

4.3 keep the security measures in Annex A in place;

4.4 help the Clinician, as far as reasonably possible, to answer patient requests and meet its duties on security, breach notification and impact assessments;

4.5 provide the information reasonably needed to show compliance with this DPA, and allow audits (including through summary reports of independent assessments) on reasonable request, once a year unless a regulator requires more or a breach has occurred;

4.6 tell the Clinician promptly about any legal demand for Patient Data, unless the law forbids it, and challenge demands that are unlawful or too broad.

5. Data minimisation for automated analysis

5.1 CephNinja processes a radiograph for automated analysis only when the Clinician requests that analysis. CephNinja Zen removes detected visible text and reduces the image on the Clinician’s computer before sending the resulting copy for tracing. Because automated text detection may miss unusual or faint text, the Clinician must review the prepared image and avoid submitting unnecessary identifiers.

5.2 When the Clinician requests an AI-generated written analysis summary, CephNinja sends the analysis name, patient age and gender, bone-structure category and cephalometric measurements to OpenAI. The provider payload excludes the patient name, notes and date and does not send the radiograph. OpenAI states that API data is not used to train its models by default and that abuse-monitoring logs may be retained for up to 30 days, subject to its published exceptions.

6. Sub-processors

6.1 The Clinician authorises the sub-processors listed on the Legal Center page.

6.2 CephNinja gives at least 30 days’ notice before adding or replacing a sub-processor that handles Patient Data. The Clinician may object on reasonable data-protection grounds; if the objection can’t be resolved, the Clinician may end the affected service and CephNinja deletes the Patient Data under Section 9.

6.3 CephNinja binds each sub-processor to data-protection terms at least as protective as this DPA and remains responsible for their performance.

7. Personal data breach

7.1 CephNinja notifies the Clinician without undue delay and within 72 hours of becoming aware of a breach affecting Patient Data, with the information the Clinician needs for its own notifications, and helps put it right.

7.2 Where a Data Protection Law puts a duty to notify directly on CephNinja (for example, to the Data Protection Board of India, or to a covered entity under HIPAA), CephNinja meets it.

8. International transfers

CephNinja uses Amazon Web Services and Microsoft Azure. Current processing locations are available on request. CephNinja will not transfer Patient Data across borders except as Data Protection Laws allow and will use an applicable lawful transfer mechanism where one is required.

9. Deletion and return

9.1 The Clinician can delete any cloud patient record at any time in the Service. A deleted record leaves the Clinician’s view at once. A record that remains deleted for 30 days becomes eligible for permanent erasure from the live database and referenced object storage through CephNinja’s deletion process. Independent infrastructure backups are not erased by that live-system process; they age out under the applicable backup-retention settings and are not used as active records. Current backup-retention details are available on request.

9.2 When the Clinician stops using the Service, CephNinja will, at the Clinician’s choice, return Patient Data in a common format and/or delete it on the schedule above, and confirm deletion in writing on request — except data the law requires CephNinja to keep, which is set apart and deleted when that requirement ends.

10. Liability

Liability under this DPA follows the limits in the Terms of Service, except where Data Protection Laws do not allow those limits.

11. Precedence

If this DPA conflicts with the Terms of Service about Patient Data, this DPA wins. Where mandatory clauses for a particular country (such as the SCCs or a BAA) conflict with this DPA, those clauses win for the data they cover.

12. US practices — HIPAA

For Clinicians that are HIPAA covered entities, the parties will sign CephNinja’s Business Associate Agreement, which governs protected health information alongside this DPA. Identifiable US patient data must not be uploaded until the BAA is in force.

Annex A — Security measures

  1. Transport security: HTTPS/TLS protects data in transit; stored data is protected by the configured security controls of CephNinja’s cloud providers.
  2. Access control: individual sign-ins, role-based permissions, two-factor sign-in available.
  3. Separation: each practice’s data is logically separated, with no access path between practices.
  4. Logging: the cloud application records audit events for supported Patient Data access routes.
  5. De-identification: CephNinja Zen removes detected visible text and sends only a reduced copy for tracing; the Clinician reviews the result because automated detection may miss text.
  6. Backups: independent infrastructure backups follow the applicable provider retention settings described in Section 9.
  7. Incident response: a written plan and the 72-hour notification commitment.
  8. People: confidentiality undertakings and least-privilege access.
  9. Review: these measures are reviewed regularly against current risks.