Schedule 3: Sub-processors

MDPA-S3 · Draft of November 18, 2026 · revision 1 · version 4.0

Part of Master Data Processing Agreement

English and Spanish wording approved for conditional publication on November 18, 2026 under delegated owner instruction. Unexecuted template: approval does not establish signatures, filings, provider contracts or operational security and does not activate countries.

Which language controls depends on the clinic's country: English, Español.

Read in: English · Español

SHA-256 of this text: 6c4b489c8bc8ee89d2a177a2ba097afd84ab4064f203bb9566219390479eecb6

Schedule 3 — Providers and connected services

Wording approved under delegated owner instruction; unsigned and subject to activation conditions.

Review edition: 18 November 2026. proposed version 4.0; not in effect. Provider names identify services. The contracting legal entities, executed terms, covered services and required transfer safeguards must be verified against VstreamX's actual accounts before activation. No current Data Privacy Framework listing or signed supplier agreement is assumed from a brand name.

ServicePurpose and dataProcessing location and conditions
Google Cloud / FirebaseHosting, database, files, sign-in (including text messages carrying sign-in verification codes to Users), server functions, backups and operational logs; Clinic Data needed by those servicesDatabase, its backups and point-in-time recovery in the US multi-region nam5; files (including earlier file versions) and functions in Iowa us-central1. Google gives 30 days' notice of its own new sub-processors and may take up to 180 days to complete deletion from its systems. Google's Cloud Data Processing Addendum offers no transfer mechanism for the laws of the countries in scope; the onward transfer relies on this Agreement and the Country Annex. Evidence that VstreamX accepted that Addendum, and the Google Cloud BAA for US clinics, is pending; coverage is not represented as established. Review access.
Google Vertex AIAdministrative drafting, permitted identity/insurance-card entry, supply-invoice extraction and reviewed support drafts; the content submitted to that featureUS multi-region us. Verify deployed routing and contractual coverage. No clinical notes, patient summaries, medical advice, treatment recommendations or radiograph interpretation.
DentalX's shared Google email senderRecipient address, messages and document attachments sent for a clinic; optional owner summariesGoogle account locations may include countries outside the US. Verify the sending account's actual Google contract. US patient email remains unavailable unless the required agreement and location conditions are satisfied.
DentalX's WhatsApp Business Platform (Meta)Phone numbers, sent/received messages and patient-supplied filesUS and other Meta processing locations. Verify actual contracting entity and processing terms. Unavailable for US clinics and unreviewed countries.
Google reCAPTCHA / Firebase App CheckApplication integrity, abuse protection and SMS second factor; browser/device/application and page-use metadata; DentalX does not intentionally submit patient-record contentsCan load on public and application pages. Assess actual URL/action metadata, configuration and contractual coverage before PHI; loading it is not evidence that App Check operates successfully.

Services connected by the Clinic

The Clinic chooses and contracts for its own Google/Meta accounts. That does not remove VstreamX's obligations for DentalX's own processing or change the classification of an actual recipient under mandatory law.

  • Clinic or clinician Gmail/Google Workspace: account identity and assignment, encrypted authorization grant, recipients, subjects, message bodies, thread identifiers and attachments used to send mail or retrieve replies to DentalX-initiated threads. The whole mailbox is not imported. Clinic access follows staff Messages permissions; clinician access is limited to that clinician and owners/managers. Imported records are stored in DentalX's US database. Google account copies remain under that account's rules. Disconnect removes DentalX's stored mailbox grant, not imported records or every Google permission. Google-wide revocation can also affect Calendar.
  • Google Calendar: appointment times, treatments, dentist and patient name are sent to the selected account; no phone numbers or clinical notes. Review authority, agreement coverage and locations before connecting.
  • Clinic WhatsApp Business account: the messages, phone numbers and files needed for the selected messaging feature, under the Clinic's Meta agreement and the same country restrictions.

Google API data is used only for disclosed connected features and handled under Google's API Services User Data Policy, including Limited Use. No advertising, sale of mailbox contents or general-purpose AI training is authorized. Personal Gmail authorization is not evidence of a BAA. Third-party provider approval/security assessment and any required clinic consent remain independent conditions.

Billing and other recipients

Stripe processes payments for the clinic software subscriptions that VstreamX bills directly. The contracting entity is expected to be the Stripe entity for a Canadian merchant, likely Stripe Payments Canada, Ltd., and must be verified against VstreamX's Stripe account. Stripe receives only clinic billing contacts, invoice details and card or other payment details, which are Account Data, never Patient Data or patient treatment payments. OpenAI is not a provider: DentalX's code path to it is switched off, and it could be used only after being added as a new Sub-processor under clause 7. A new recipient cannot be introduced by changing this draft alone; clause 7's applicable notice, approval and routing conditions remain.

Annex index and scope

The non-US bundle comprises the MDPA and Schedules 1–3, plus the country or province annexes and transfer instruments listed below for the Clinic's country. The US bundle uses the BAA and applicable state schedules instead. Current documents and languages are at the agreement index; previous texts are historical copies.

The launch begins with El Salvador, subject to the activation conditions of the MDPA and ANX-CAC-SV. Selected US states follow under the BAA and its state schedules, not the MDPA, and selected Canadian provinces follow under the MDPA. Every other annex listed below is a saved draft: it applies only once VstreamX, by decision of its owner, approves that country (or province) for launch and the country's conditions are met.

  • First launch: El Salvador, ANX-CAC-SV.
  • Selected Canadian provinces (to follow): the annex for the Clinic's province where one exists (ANX-CA-ON, ANX-CA-AB, ANX-CA-MB, ANX-CA-SK, ANX-CA-NS or ANX-CA-NB); Quebec is excluded.
  • Saved drafts, Central America: Belize, ANX-CAC-BZ; Guatemala, ANX-CAC-GT; Honduras, ANX-CAC-HN; Costa Rica, ANX-CAC-CR; Panama, ANX-CAC-PA and, once completed and published, the RIPD model clauses (TM-PA).
  • Saved drafts, South America: Argentina, ANX-AR and TM-AR; Bolivia, ANX-BO; Chile, ANX-CL and, once completed and published, the RIPD model clauses (TM-CL); Colombia, ANX-CO; Ecuador, ANX-EC; Guyana, ANX-GY; Paraguay, ANX-PY; Peru, ANX-PE; Suriname, ANX-SR; Uruguay, ANX-UY and, once completed and published, the Council of Europe model clauses (TM-UY).
  • Saved drafts, other: Mexico, ANX-MX; the Dominican Republic, ANX-CAC-DO.

An annex or transfer instrument that is not listed for the Clinic's country (or province) does not apply to the Clinic. ATT-OTHER applies only where a validly executed bundle expressly includes it.

Nicaragua and Venezuela are excluded. Brazil is pending and not offered. Other countries and territories, including European countries, the United Kingdom, Quebec, other Caribbean countries, Africa, Asia and unreviewed overseas territories, are outside the offer. Being listed does not establish readiness: each local package, transfer mechanism, provider condition and publication hold must first be resolved. Retired or historical texts for other markets do not reopen those markets.