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, the merchant of record 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.
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 staffFirestore, Cloud Storage and Cloud Functions are covered by the Google Cloud Business Associate Agreement. | The United States, with the database in Google’s United States multi-region (nam5) and files and server functions in Iowa (us-central1) |
| 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 |
| 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 DentalX sender address sends for every clinic. It also sends the monthly summary a clinic owner can choose to receive. | 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 | Checking that a person, not a program, is at the browser when a User sets up or uses a text-message second factor | Information about the User’s browser and device and how the page is used, which the browser sends to Google; no patient dataLoaded only on the screens where a text-message second factor is set up or used. | The United States and other countries where Google operates |
VstreamX Studio Inc. supplies DentalX. For subscriptions purchased through Paddle, Paddle is the merchant of record and an independent controller of buyer and billing information under its own privacy policy. It receives clinic subscription billing data, never Patient Data, and does not collect dental-treatment payments.
| Provider | Purpose | Data | Where |
|---|---|---|---|
| Paddle | Merchant of record for clinic software subscriptions, including checkout, renewals and billing support | Clinic billing contacts and identifiers, purchases and payment information; no Patient Data or special-category health dataVstreamX Studio Inc. supplies DentalX. Paddle acts as an independent controller for billing. Card details never reach DentalX; patient treatment payments are excluded. | The United States, United Kingdom and other countries described in Paddle’s privacy policy |
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 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 |
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. Removing a provider, or narrowing what one receives, can take effect at once. Questions: admin@vstreamx.com.