# Schedule 3 — Sub-processors **Version:** 1.2. This Schedule is versioned separately from the Master Agreement and changes under clause 7. The current list is always at dentalx.studio/legal/subprocessors. | # | Sub-processor (contracting entity) | Service | Clinic Data it receives | Location of processing | Transfer basis for non-US clinics | Notes | |---|---|---|---|---|---|---| | 1 | Google Cloud / Firebase (Google LLC) [[TO CONFIRM: Google contracting entity on VstreamX's Google Cloud account, e.g. Google LLC or Google Cloud Canada Corporation]] | Hosting, database, file storage, sign-in (including text messages that carry a second-factor code), server functions, backups, server logs | All Clinic Data | United States: database in the US multi-region (nam5); files, functions and backups in us-central1 (Iowa) | Google Cloud Data Processing Addendum, with the SCCs and the EU-US / UK-US Data Privacy Framework certification of Google LLC [[TO CONFIRM: DPF listing verified live, with a dated record]] | Firestore, Cloud Storage and Cloud Functions are covered by the Google Cloud Business Associate Agreement. | | 2 | Google Vertex AI (Gemini) (Google LLC) | Administrative AI and support reply drafts | The text, image or document sent with each AI request | United States: Vertex AI US multi-region (`us`). [[BLOCKING TO CONFIRM: verify deployed routing matches the US multi-region configuration before publication]] | As row 1 | AI is limited to administrative and operational tasks: office drafts, identity and insurance card entry, and supply invoice extraction. It does not generate clinical notes, patient summaries, medical advice, treatment recommendations or radiograph interpretations. Existing saved AI findings remain historical Clinic Data. Staff review every draft and extracted field before use. | | 3 | Google Workspace (Gmail) (Google LLC) [[BLOCKING TO CONFIRM: the sending account is a Google Workspace account (not consumer Gmail) with Google's Cloud Data Processing Addendum accepted for it; a consumer Gmail account cannot be a Sub-processor]] | Reminders, recall notices, consent links, prescriptions and treatment plans sent by email | The recipient's email address and the message, with its PDF attachment where there is one | United States and the other countries where Google stores Workspace data, as Google's Workspace sub-processor and data-location pages state | Google Cloud Data Processing Addendum as it applies to Google Workspace, with the SCCs and Google LLC's DPF certification | One DentalX sender address sends for every clinic. | | 4 | Meta (WhatsApp Business Platform) (Meta Platforms, Inc. / WhatsApp LLC) [[TO CONFIRM: Meta contracting entity on DentalX's WhatsApp Business account, and the data-processing terms accepted]] | Reminders, recall notices and the two-way inbox over WhatsApp, for clinics that send through DentalX's own WhatsApp Business account | The patient's phone number, the messages sent and received, and the files a patient sends | United States and other countries where Meta operates | Meta's WhatsApp Business data-processing terms, with SCCs and Meta Platforms, Inc.'s DPF certification [[TO CONFIRM]] | Not available to US clinics. A clinic that connects its own WhatsApp Business account does so under its own agreement with Meta; that account is not a Sub-processor. | | 5 | Google reCAPTCHA (Google LLC) | Checking that a person is at the browser when a User sets up or uses a text-message second factor | Browser and device information sent by the browser; **no patient data** | United States and other countries where Google operates | As row 1 | Loaded only on the screens where a text-message second factor is set up or used. | **Transfer Instruments.** Where a Transfer Instrument governs the Clinic's transfers (TM-BR for Brazil, TM-AR for Argentina), each onward transfer to a Sub-processor is also made under that Instrument, as the Country Annex states. **Not Sub-processors:** - **Paddle** resells Clinic software subscriptions as merchant of record and handles billing information as an independent controller. VstreamX remains the DentalX supplier. No Patient Data or special-category health data is shared with Paddle, and Paddle does not collect patient treatment payments. - **Services the Clinic connects itself** are governed by the Clinic's own agreement with their provider. These are its own Google Calendar and its own WhatsApp Business account. - **OpenAI** is not called by the Service. If VstreamX ever enables it, clause 7.3 applies first. --- # Annex Index ### Part A — Documents in every bundle (non-US) | ID | Document | |---|---| | `MDPA` | This Master Data Processing Agreement, with Schedules 1–3 | ### Part B — Country Annexes and Transfer Instruments | Clinic's country / province | Documents added to the MDPA | File | |---|---|---| | EEA: all 30 states offered | TM-EEA: EEA Transfer Module (EU SCCs 2021/914, Modules 2 and 3) | `annex-eu-scc.md` | | Spain | TM-EEA + ANX-ES | `annex-es.md` | | Italy | TM-EEA + ANX-IT (with the art. 1341 approval) | `annex-it.md` | | Belgium | TM-EEA + ANX-BE | `annex-be.md` | | Austria | TM-EEA + ANX-AT | `annex-at.md` | | Poland | TM-EEA + ANX-PL | `annex-pl.md` | | Sweden | TM-EEA + ANX-SE | `annex-se.md` | | Norway | TM-EEA + ANX-NO | `annex-no.md` | | Netherlands | TM-EEA + ANX-NL | `annex-nl.md` | | United Kingdom | TM-UK + ANX-UK | `annex-uk.md` | | Canada: British Columbia | none | — | | Canada: Ontario | ANX-CA-ON | `annex-ca-on.md` | | Canada: Quebec | ANX-CA-QC (French controls) | `annex-ca-qc.md`, `fr/annex-ca-qc.md` | | Canada: Alberta | ANX-CA-AB | `annex-ca-ab.md` | | Canada: Manitoba, Saskatchewan, Nova Scotia, New Brunswick | ANX-CA-MB / -SK / -NS / -NB | `annex-ca-mb-sk-ns-nb.md` | | Mexico | ANX-MX | `annex-mx.md`, `es/annex-mx.md` | | Colombia | ANX-CO | `annex-co.md`, `es/annex-co.md` | | Peru | ANX-PE | `annex-pe.md`, `es/annex-pe.md` | | Chile | ANX-CL | `annex-cl.md`, `es/annex-cl.md` | | Argentina | ANX-AR + TM-AR | `annex-ar.md`, `es/annex-ar.md` | | Brazil | TM-BR + ANX-BR (Portuguese controls) | `annex-br.md`, `pt/annex-br.md` | | Ecuador (when opened) | ANX-EC | `annex-ec.md`, `es/annex-ec.md` | | Guatemala | none (MDPA in Spanish) | — | | Costa Rica | ANX-CAC §CR | `annex-cr.md`, `es/annex-cr.md` | | Panama | ANX-CAC §PA | `annex-pa.md`, `es/annex-pa.md` | | Dominican Republic | ANX-CAC §DO | `annex-do.md`, `es/annex-do.md` | | Other country | ATT-OTHER (attestation); SCC addendum on request | `annex-other.md` | ### Part C — United States US Clinics accept the DentalX Business Associate Agreement (`baa.md`) instead of this Agreement. ### Part D — Countries not offered DentalX is not offered at this time to Clinics in France, Finland or Germany, or in the Canadian provinces and territories not listed in Part B (Newfoundland and Labrador, Prince Edward Island, Yukon, the Northwest Territories and Nunavut). The reasons are in the country matrix. --- ## Items to confirm before publication (MDPA) 1. Publication date of v1.0 (Effective date). 2. Automatic removal of non-current file versions at the deletion date (clause 14.5(b)). 3. A clinic-scoped WhatsApp opt-out list, deleted with the Clinic Data (clause 14.5(d)). 4. Dedicated privacy address and the external privacy office (EU DPO, Brazil encarregado, Panama Oficial, Peru Oficial) (clause 24.1). 5. Name and address of the EU Article 27 representative (clause 24.2). 6. Name and address of the UK Article 27 representative (clause 24.2). 7. The date phase B′ (field encryption of new consents and prescriptions) went live, stated as 2026-10-06 (Schedule 2, A.3). 8. Completion date of the sealing sweep for earlier consents and prescriptions (Schedule 2, A.3). 9. The owner's confirmation that the off-platform sealed copy of the encryption key exists (Schedule 2, A.4). 10. Whether key custody moves to Cloud EKM/HSM under external control (Schedule 2, A.4). 11. That every Google Cloud project administrator account enforces 2-step verification (Schedule 2, B.11). 12. A roadmap date for read-access logging of every patient-data view (Schedule 2, C.12). 13. That written confidentiality undertakings and annual training cover everyone with production access (Schedule 2, G.22). 14. That VstreamX holds no independent certification today (Schedule 2, G.25). 15. The Google contracting entity on VstreamX's Google Cloud account (Schedule 3, row 1). 16. The live DPF listings for Google LLC and Meta Platforms, Inc., with a dated record (Schedule 3, rows 1 and 4). 17. **Blocking:** the Vertex AI regional endpoint live for every tenant, and named (Schedule 3, row 2; clause 13.1). 18. **Blocking:** the email sender on a Google Workspace account with the Cloud Data Processing Addendum accepted (Schedule 3, row 3). 19. The Meta contracting entity and the data-processing terms accepted for DentalX's WhatsApp Business account (Schedule 3, row 4). 20. The mapping of each Sub-processor's terms against GDPR Article 28(3)(a)–(h) and the ANPD clauses, recorded in Schedule 3 (clause 7.2). 21. Deletion or anonymisation of the audit trail at the deletion date (clause 14.5(c)).