# Schedule 3 — Providers and connected services **Wording approved under delegated owner instruction; unsigned and subject to activation conditions.** **Review edition: 17 November 2026. proposed version 3.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. | Service | Purpose and data | Processing location and conditions | |---|---|---| | Google Cloud / Firebase | Hosting, database, files, sign-in, server functions, backups and operational logs; Clinic Data needed by those services | US database multi-region nam5; files/functions in Iowa us-central1. Review actual backup locations, supplier DPA/BAA coverage and access. | | Google Vertex AI | Administrative drafting, permitted identity/insurance-card entry, supply-invoice extraction and reviewed support drafts; the content submitted to that feature | US 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 sender | Recipient address, messages and document attachments sent for a clinic; optional owner summaries | Google 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 files | US and other Meta processing locations. Verify actual contracting entity and processing terms. Unavailable for US clinics and unreviewed countries. | | Google reCAPTCHA / Firebase App Check | Application integrity, abuse protection and SMS second factor; browser/device/application and page-use metadata; DentalX does not intentionally submit patient-record contents | Can 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 **Paddle** is merchant of record for clinic software subscriptions and an independent billing controller; it receives billing contacts, purchases and payment identifiers, never Patient Data or patient treatment payments. **OpenAI** is not called by DentalX. 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 applicable country/province annexes and transfer instruments identified for the Clinic. The US bundle uses the BAA and applicable state schedules instead. Current documents and languages are at [the agreement index](/legal/agreements/); [previous texts](/legal/archive/) are historical copies. The target region is the US, Mexico, Central America, South America excluding Brazil, Canada excluding Quebec, and the Dominican Republic. Other Caribbean countries, Europe, Africa, Asia and unreviewed overseas territories are outside the new offer. Being in the target region does not establish readiness: each local package, transfer mechanism, provider condition and publication hold must first be resolved. Historical European, Brazilian and Quebec texts do not reopen those markets.