VstreamX Studio Inc. provides DentalX. This page lists the companies that process data for DentalX as the Service is built today, what each one receives, and where, in three groups: the sub-processors we engage to deliver DentalX, our payment provider for subscription billing, and the services a clinic connects itself. Each receives only what its purpose needs. The Privacy Policy explains how we handle personal information, and the Terms of Service set out how we process the data clinics enter.
Our sub-processors
We engage these providers to deliver DentalX. Each processes data under its written terms with us, and we remain responsible to the clinic for the part of the Service each one performs, as section 8.6 of the Terms of Service provides.
| Provider | Purpose | Data | Where |
|---|---|---|---|
| Google Cloud / Firebase | Hosting, database, file storage, sign-in (including the text messages that carry a second-factor code), server functions, backups and server logs | All Customer Data, including patient health information, and the accounts of clinic staffEvidence that Google’s Cloud Data Processing Addendum and HIPAA Business Associate Agreement have been accepted for DentalX’s Google Cloud account is pending, so we do not state that either covers these services. Text messages carry only second-factor sign-in codes. Google may take up to 180 days to complete deletion from its systems, and gives 30 days’ notice of a new sub-processor of its own, the same period we give clinics. | The United States, with the database, its backups and point-in-time recovery in Google’s United States multi-region (nam5) and files and server functions in Iowa (us-central1); sign-in and server logs where Google operates, in the United States and other countries |
| Google Vertex AI (Gemini) | Administrative office drafts, ID and insurance card entry, supply invoice extraction, and support reply drafts | The office text or administrative document submitted with the request; support ticket context for support draftsCalled from DentalX’s own Google Cloud project. AI is limited to administration and operations; clinical AI generation is unavailable. | The United States: Vertex AI’s US multi-region (us) |
| Google (Gmail) | 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 oneOne shared DentalX sender address sends the clinics’ automatic emails and the monthly summary a clinic owner can choose to receive. Documents sent by hand can instead use a mailbox the clinic connects, listed under services you connect. DentalX uses no other email service. | The United States and other countries where Google operates |
| Meta (WhatsApp Business Platform) | Reminders, recall notices and the two-way inbox over WhatsApp, for a clinic that sends through DentalX’s own WhatsApp Business account rather than one it connects itself | The patient’s phone number, the messages sent and received, and the files a patient sendsNot available to clinics in the United States or any country DentalX has not yet reviewed. A clinic that connects its own WhatsApp Business account is listed under services you connect instead. | The United States and other countries where Meta operates |
| Google reCAPTCHA | Automated-abuse and app-integrity checks through Firebase App Check, and browser verification for a text-message second factor | Browser, device, application and page-use metadata sent to Google; DentalX does not intentionally include patient record contents in verification payloadsFirebase initialization can load these checks on public and app pages, including legal pages, as well as SMS-factor screens. Google's privacy policy and terms apply. Provider configuration and any required health-data contractual coverage must be verified; a successful page load is not proof of a working App Check control. | The United States and other countries where Google operates |
Our payment provider for subscription billing
VstreamX Studio Inc. supplies DentalX and sells and bills its subscriptions directly. Stripe processes the card payments under its services agreement with us and its own privacy policy. It receives clinic subscription billing data, never Patient Data, and does not collect dental-treatment payments.
| Provider | Purpose | Data | Where |
|---|---|---|---|
| Stripe | Card payments for the clinic software subscriptions VstreamX sells and bills directly, including checkout, renewals, invoices and the billing portal | Clinic billing contacts, subscription, invoice and payment identifiers, and the card and payment information entered with Stripe; no Patient Data or special-category health dataVstreamX Studio Inc. supplies and sells DentalX. Stripe Payments Canada, Ltd., with Stripe, LLC for the processing of personal data, acts under Stripe’s services agreement with us and its privacy policy. Card details never reach DentalX’s servers; patient treatment payments are excluded. | Canada, the United States and other countries where Stripe operates |
Services you connect
A clinic can connect these accounts of its own to DentalX. DentalX sends them what the table shows, but they are not our sub-processors: the clinic’s own agreement with the provider governs each one, as section 10 of the Terms of Service provides.
| Provider | Purpose | Data | Where |
|---|---|---|---|
| Your connected Gmail or Google Workspace mailbox | Clinic or clinician email conversations, reply retrieval and manually emailed documents, only after an authorized user connects and selects that account | The connected account's email address and assignment, encrypted authorization grants, recipients, subjects, message bodies, thread identifiers and attachments used by the selected featureA clinic mailbox is available to staff with the required Messages access. A clinician mailbox is limited to that clinician and clinic owners/managers. DentalX imports replies to threads started through DentalX, not the whole mailbox. Disconnecting removes DentalX's stored grant; imported clinic records remain under the clinic's retention rules. Your agreement with Google governs your account, while DentalX remains responsible for its own processing. US patient-email restrictions continue to apply. | The connected Google account and the United States/other locations where its Google service operates; imported DentalX conversation records are stored in DentalX's US database |
| Your Google Calendar | Appointment sync, only for a clinic that connects its own Google account | Appointment time, the treatment, the dentist and the patient’s nameNo phone numbers or clinical notes. Your own agreement with Google governs that account. | Your Google account, which Google keeps in the United States and other countries where it operates |
| Your WhatsApp Business account (Meta) | Reminders, recall notices and the two-way inbox over WhatsApp, for a clinic that connects its own WhatsApp Business account, where DentalX offers it | The patient’s phone number, the messages sent and received, and the files a patient sendsNot available to clinics in the United States or any country DentalX has not yet reviewed. Your own agreement with Meta governs that account, its number and its bill. Connecting it loads Meta’s sign-up script, which can set Meta’s cookies in that browser. | The United States and other countries where Meta operates |
What is not on this list, and why
- Other AI providers. Every AI feature runs on Google Gemini through Vertex AI. The code can reach OpenAI only if we switch it on, and it is switched off, so no data is sent to OpenAI or to any other AI provider.
- Analytics and advertising. DentalX loads no analytics, advertising or session-recording tool on any page, including the public website.
- Your browser’s speech recognition. Dictation uses the speech recognition built into the browser, which sends the audio to the company that makes the browser (for example, Google for Chrome) under that company’s terms. We do not engage it and never receive the audio. Dictation is off for clinics in the United States or any country DentalX has not yet reviewed.
- DB-IP. To show the prices for where a visitor is, DentalX’s server looks up the country of the visitor’s IP address in DB-IP’s IP to Country Lite database, which it holds itself. DB-IP receives nothing.
- Other email and text-message services. DentalX sends email only through Google and WhatsApp messages only through Meta, as listed above, and uses no other email or text-message service. It sends no text messages to patients: text messages carry only the second-factor sign-in codes that Firebase Authentication sends.
When this list changes
We publish a change here before it takes effect. When a new sub-processor will receive patient data, we publish it at least 30 days before it starts and tell clinic owners by email, as section 8.6 of the Terms of Service provides. Google gives us 30 days’ notice of a new sub-processor of its own, the same period we give clinics, so we pass such a notice on to clinic owners by email promptly, and it may reach them with fewer than 30 days remaining. Removing a provider, or narrowing what one receives, can take effect at once. Questions: admin@vstreamx.com or +1 204 441 0078.