Legal

Standard Contractual Clauses

The transfer instruments that attach to the Data Processing Agreement when a clinic is in the EEA, the UK or Switzerland — which one applies, the options we have resolved, and the completed annexes.

Last updated 10 August 2026

01When these clauses apply to you

They apply automatically, and only where they are needed. Your clinic tells us which country it operates in when it sets up, and that answer decides which instrument attaches to your Data Processing Agreement. Nothing here is a separate signature or a separate negotiation.

Where your clinic isWhat attaches
European Economic AreaThe EU Standard Contractual Clauses, Module Two.
United KingdomThe same clauses, plus the UK International Data Transfer Addendum (section 8).
SwitzerlandThe same clauses, read with the Swiss amendments (section 9).
Everywhere elseNothing on this page. Your own regime may still restrict the transfer — see the note at the end.

The transfer being covered is real rather than theoretical. Your clinical records are stored in Belgium, but we are a United States company and our own staff administer the service from outside Europe, and transactional email is delivered by a provider in the United States. Either of those is enough on its own.

02What is incorporated, and what is not

Incorporated: the Standard Contractual Clauses set out in the Annex to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, Module Two (transfer from controller to processor), as completed by the annexes on this page.

Not reproduced: the clause text itself. It is the Commission's, it is published in the Official Journal, and a copy pasted into a marketing site is a copy that can silently fall out of date. The authoritative text governs; the completed annexes are what we owe you.

Where the Clauses and the Data Processing Agreement disagree, the Clauses win. That is not generosity — Clause 5 requires it.

03The options, resolved

The Clauses leave several choices to the parties. Leaving them unstated is the most common way a set of clauses turns out not to work, so here they are.

ClauseOur position
Clause 7 — DockingIncluded. A further party can accede later without re-papering everything.
Clause 9 — Sub-processorsOption 2, general written authorisation. We give 30 days’ notice before adding or replacing one, matching the DPA.
Clause 11 — RedressThe optional independent dispute-resolution body is not adopted. Your right to lodge a complaint with your own supervisory authority and to go to court is unaffected.
Clause 13 — Supervisory authorityThe authority of the country your clinic operates in. See Annex I.C.
Clause 17 — Governing lawOption 2: the law of the EU Member State in which your clinic is established. For clinics in Iceland, Liechtenstein or Norway, the law of Ireland.
Clause 18 — ForumThe courts of that same Member State, so a dispute about these clauses is heard where you are, not where we are.

Two consequences worth naming. First, the Delaware governing law in our Terms does not reach these clauses; a dispute about the transfer is heard under your own Member State's law. Second, because every one of these resolves from your country rather than from a negotiation, there is no per-customer edition of this document — which is exactly what makes it possible to have it ready before a customer arrives rather than after.

04Annex I.A — Parties

Data exporter — controller. The clinic that holds the account: its registered name, address and contact details as entered in the panel, and the account owner as contact person. Activities relevant to the transfer: use of Clinic+ to schedule appointments, keep clinical records, bill patients, manage stock and answer patients through the assistant. Signature and date: recorded at acceptance, as described in section 10.

Data importer — processor. Pull House LLC, 8 The Green, Suite 23111, Dover, DE 19901, United States, trading as Clinic+. Contact: hello@clinicplus.io. Activities relevant to the transfer: hosting and operating the Clinic+ practice management service on the exporter's instructions.

05Annex I.B — Description of the transfer

Data subjectsCategories of personal data
PatientsIdentity and contact details, appointment history, clinical records (examinations, tooth charts, prescriptions, vaccinations, measurements), consent records, documents and clinical photographs, financial entries and balances, conversations with the assistant.
Clinic personnelName, email address, role and permissions, actions recorded in the audit log.
Website visitors of the clinicMessages sent to the assistant before any booking, and whatever contact details they volunteer in order to book.

Sensitive data. Clinical records are data concerning health under GDPR art. 9. The restrictions applied to them are the measures in Annex II, and in particular: tenant isolation enforced in the database rules rather than in application code, role-based access with clinical records and sensitive financial fields as separately grantable modules, exports gated by their own permission and written to an audit log, and a confidentiality obligation on everyone with access.

ItemDescription
FrequencyContinuous, for as long as the account is open.
Nature of processingStorage, retrieval, structuring, display, transmission of reminders and confirmations, generation of assistant replies, and erasure.
PurposeProvision of the Clinic+ practice management service to the exporter.
RetentionFor the duration of the account, then 90 days after termination, after which the data is deleted from live systems. Backups age out on their own cycle and are not selectively restored.
Transfers to sub-processorsAs set out in Annex III: hosting and storage for the duration of the account; transactional email for the time needed to deliver each message.

06Annex I.C — Competent supervisory authority

The supervisory authority of the EEA state in which your clinic is established. For clinics in Iceland, Liechtenstein or Norway, the Irish Data Protection Commission acts as competent authority under Clause 13, consistent with the governing law chosen in section 3. Nothing here limits your right to complain to your own national authority.

07Annex II — Technical and organisational measures

These are the measures the importer has implemented, described in the categories Annex II asks for. They are the same measures set out in the Data Processing Agreement, not a more flattering version written for this document.

MeasureImplementation
EncryptionData encrypted in transit (TLS) and at rest by the platform. Authentication sessions carried in a signed, HTTP-only cookie.
Access controlTenant isolation enforced in the database access rules, checked against a signed membership claim on every read and write — a query that omits or forges a clinic scope fails rather than returning another clinic’s rows. Role-based permissions set per member, with clinical records and sensitive financial fields as separately grantable modules.
Confidentiality of personnelEveryone with access is bound by a confidentiality obligation. Production access by our staff is limited to operating the service and answering support requests.
Integrity and availabilityManaged infrastructure with platform-level replication. Exports are a separate permission and are written to an audit log, so a bulk read is visible after the fact.
RestorationPlatform-managed backups, restored as a whole rather than selectively.
Data minimisation and qualityThe controller decides what is recorded; the product asks for what a practice management system needs and no more. Records are editable by the clinic, which is what makes correction a self-service action rather than a support ticket.
ErasureThe clinic can delete a patient record directly. On termination, deletion from live systems after 90 days.
PortabilityExport available to the clinic at any time while the account is open, and throughout any billing dispute.
Sub-processor measuresEach sub-processor is bound by terms no less protective than these, and is selected on the basis of its own published security posture.

We do not claim a certification we do not hold. Where a clinic needs assurance beyond this description, section 11 of the Data Processing Agreement sets out how audits work.

08Annex III — Sub-processors

Authorised under Clause 9, Option 2, with 30 days' notice before any addition or replacement.

Sub-processorProcessingLocation
Google Cloud / FirebaseDatabase, file storage, authentication, application hosting. Duration: the life of the account.europe-west1 — St. Ghislain, Belgium
ResendTransactional email: confirmations, reminders, magic links. Duration: the time needed to deliver each message.us-east-1 — United States

09The UK Addendum

UK GDPR does not accept the EU clauses on their own. For a clinic in the United Kingdom, the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the Information Commissioner under s.119A of the Data Protection Act 2018 (version B1.0) is incorporated on top of them.

Addendum tableCompleted as
Table 1 — PartiesAs Annex I.A above. Start date: the date of acceptance recorded under section 10.
Table 2 — Selected SCCsModule Two, with the options as resolved in section 3 of this page.
Table 3 — Appendix informationAnnexes I.A, I.B, I.C, II and III above.
Table 4 — Ending the AddendumThe data exporter — your clinic — may end this Addendum if the ICO revises the Approved Addendum in a way that reduces protection.

Where the Addendum and the EU clauses conflict, the Addendum governs the UK transfer. The competent authority is the Information Commissioner's Office, and Clauses 17 and 18 read as the law and courts of England and Wales.

10The Swiss amendments

For a clinic established in Switzerland, the same clauses apply with the amendments the Federal Data Protection and Information Commissioner requires: the FDPIC is the competent supervisory authority, references to the GDPR are read as references to the Federal Act on Data Protection, references to EU Member States are read so that a data subject in Switzerland may bring proceedings in Switzerland, and — for as long as Swiss law continues to protect them — the Clauses are read as covering the data of legal entities as well as of individuals.

11How these are executed

By acceptance rather than by signature. When your clinic is created you accept the Terms, the Privacy policy and the Data Processing Agreement in one act, and these clauses come with the agreement wherever your country calls for them.

What we record at that moment is deliberately more than a boolean: the version of the document set, the timestamp, who accepted and under which email address, the country given, the instruments that attached because of it, and the IP address and browser the acceptance came from. The record is written in the same operation that creates the clinic, so a clinic cannot exist without one, and it is stored where the clinic's own administrators can read it but cannot alter it.

One honest limit. A clinic that skips the setup questions has not told us where it operates, so no instrument attaches at that moment and the record says so rather than guessing. It attaches when the country is set in Settings. If you are in the EEA, the UK or Switzerland, fill the country in before you enter patient data.

12If you are somewhere else

An empty row in section 1 means these particular instruments are not the ones that apply to you. It does not mean your regime is silent on the transfer.

The clearest case is Türkiye. A Turkish clinic transfers health data abroad the moment it uses the service, KVKK art. 9 requires its own mechanism, and Türkiye has issued no adequacy decision for any country — so the practical route is a standard contract notified to the Board within five business days, or an undertaking. That is a separate instrument with a separate filing, and the clauses on this page do not stand in for it. Write to hello@clinicplus.io and we will handle it with you.

13Getting a countersigned copy

Some clinics need paper: a copy of the clauses with both parties' signatures on it, for their own file or their own regulator. Write to hello@clinicplus.io and we will send one. Asking for it does not change what is already in force — the acceptance did that.