VstreamX Studio Inc. (“VstreamX”, “we”, “us”) makes DentalX, software that dental clinics use to run their practice. This policy explains what personal information DentalX handles (on the website at dentalx.studio, in the clinic app at app.dentalx.studio, and on the pages patients open from a clinic’s messages), what we do with it, who helps us, where it is kept, and the choices people have.
We operate from Brandon, Manitoba. Manitoba has no private-sector privacy statute in force, so Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) governs how we handle the personal information we are responsible for. A clinic in Canada may also be subject to its province’s health-information law for its patients’ information, such as Manitoba’s Personal Health Information Act or Ontario’s Personal Health Information Protection Act, 2004; we process that information for the clinic as its information manager or agent, under section 8 of our Terms of Service. Section 2 explains the two different roles we play, and section 15 names the person accountable for this policy.
1. Who we are
DentalX is provided by VstreamX Studio Inc., a Manitoba corporation:
VstreamX Studio Inc.
Office B - 1043 Rosser Ave, Brandon MB R7A 0L5, Canada
admin@vstreamx.com
2. Our two roles
Information we decide about
We decide how we handle the information of the people who visit our website, the clinic staff who hold DentalX accounts (owners, managers, dentists and receptionists), the people who manage a clinic’s billing, and anyone who writes to us. For that information VstreamX is the organization accountable under PIPEDA, and this whole policy applies to it.
Patient information we process for clinics
A clinic that uses DentalX enters information about its patients, and patients send it information through DentalX. That information belongs to the clinic, which decides what is collected and why. We process it only on the clinic’s behalf, under our Terms of Service, to provide DentalX to that clinic. The clinic’s own privacy notice governs how it handles its patients’ information, and sections 4 to 11 of this policy describe how we handle it for the clinic.
If you are a patient, please contact your clinic about your information: it can see, correct, export and delete your records, and it can ask us for help. In Mexico, your rights of access, rectification, cancellation and opposition (ARCO rights) are exercised with the clinic, which is responsible for your data. In the United States, your rights under HIPAA are exercised with your dental practice, as its Notice of Privacy Practices explains; VstreamX acts for a United States practice only as its business associate, under the business associate agreement it has signed with that practice. If you write to us about a clinic’s records, we pass your request to that clinic and tell you that we have.
3. What we collect
- Connected email accounts. If an authorized user connects Gmail or Google Workspace, we record the account address, its clinic or clinician assignment, who connected it and when, the permissions granted, and encrypted authorization credentials needed to use the connection. These credentials are separate from the user’s Google password, which DentalX does not receive. The selected feature uses recipients, subjects, message bodies, thread identifiers and attachments to send messages and retrieve replies. The imported records are described in section 4, access in section 8, and retention in section 11.
- Clinic accounts. When a clinic signs up: the clinic’s name and country, and the owner’s name and email address. The owner’s email address also becomes the clinic’s contact address: the pages patients open from the clinic’s messages can show it, and patients’ replies to the emails DentalX sends for the clinic go to it. The clinic’s owner or a manager can change it in Settings. Later, the clinic’s address, telephone, logo, opening hours, currency, tax and printing settings, and its other settings. If the clinic names a privacy contact in Settings, that person’s name, title, email address and telephone; our notices to the clinic go to its owner and to that contact.
- Staff accounts. Each User’s name, email address and role; a telephone number, if the clinic enters one when it invites them or they choose text messages as a second factor; and, for those who prescribe, their professional licence numbers and specialty. Passwords are stored by our sign-in provider in a form we cannot read. A User who signs in with a Google account shares their name, email address and profile photo from it. Firebase App Check and Google reCAPTCHA perform browser/app-integrity and abuse checks, and reCAPTCHA also supports text-message second factors. Firebase initialization can load these checks on public and app pages, including legal pages. Google receives browser, device, application and page-use metadata; DentalX does not intentionally include patient record contents in verification payloads (section 8).
- Billing. The clinic’s Plan, billing period and subscription status, Paddle’s customer, subscription and transaction identifiers, and the clinic billing contact we give Paddle. Card details are entered with Paddle and never reach us (section 7).
- The audit trail. A record of who did what and when in a clinic’s account, such as opening a patient’s chart, exporting or deleting data, changing a patient or treatment record, and changing important settings, and a separate record of what our own staff do in DentalX’s administrative console. When our staff act on a clinic’s account, the clinic’s own audit trail shows it too, naming DentalX support and their role rather than the person. Entries identify the person’s account and the role they had in the clinic, and many carry their email address; some name the patient concerned. They do not record IP addresses.
- Performance measurements. How long pages of the clinic app take to load: the page, the time, the app’s version, and the clinic and role of the person using it, but not who they are and nothing about patients.
- Error reports. When the clinic app meets an error: the page, the error message, the browser type, and the account, email address, role and clinic of the person using it. Web-address parameters, email addresses and phone-length numbers are removed from the message before it is stored.
- Server logs. Our server functions record what they do, for example that a reminder was sent or failed. They are designed to keep patients’ names, addresses and numbers out of these logs.
- Usage counts. Each month, how many AI requests and messages a clinic used and how much storage it holds, to apply its Plan’s limits.
- Support and messages to us. Support requests a clinic opens in the app, the messages in them, and emails people send us. Please leave patient information out of a support request unless we need it to help.
- Website visitors. The website sets no analytics or advertising cookies and uses no session-replay scripts. Google security checks can load on public pages as described in section 13. Our hosting provider receives the technical information any website receives, such as the IP address and browser type, to deliver the page. To show the prices for where a visitor is, the website asks DentalX’s server which price list applies: the server looks up the country of the visitor’s IP address in a database it holds itself (IP to Country Lite, by DB-IP, which receives nothing), uses only the country, and does not store the address or write it into the log entries DentalX’s own code makes. Google Cloud’s standard request log for that server records the address, as it does for every request, and server logs are deleted after 30 days (section 11). For a signed-in member of a clinic, it uses the clinic’s country instead.
- Data agreements. When a clinic accepts a data agreement in DentalX, such as the Business Associate Agreement or a data processing agreement, we record who accepted it (their name, title, email address and account, how they signed in and whether that sign-in used a second factor), the clinic, each document with its version and fingerprint, the version of the sub-processor list it was accepted against, the boxes ticked, when each document was scrolled to its end, and the time, together with the network address recorded with the request, the forwarded-address header received with it, the browser’s user agent, the time zone the browser reports, and a reference to the sign-in that does not reveal it. We keep this as evidence of the contract.
4. Patient information we process for clinics
Depending on what a clinic records and which features it uses, this can include:
- identity and contact details: name, date of birth, gender, telephone, email, address, emergency contact and insurance details;
- medical and dental history, allergies and medicines, appointments, treatments and treatment plans, dental and periodontal charts, clinical notes, prescriptions and lab orders;
- radiographs, clinical photographs, a profile photograph and documents;
- consent forms and their signatures. When a patient signs from a link, the record also keeps the name they typed, how they signed, a fingerprint of the exact text they signed, the browser they used, the network address recorded with the request (which may not identify the patient’s device) and the time, as evidence of the signature;
- invoices, payments, balances and cash-register lines;
- the requests patients make about their information (to see, correct, delete or move it, or to object to or restrict its use), which the clinic records with how and when each arrived, when it is due, its notes and when it was answered;
- messages exchanged with the clinic over WhatsApp, including photographs, voice notes and documents a patient sends (not available in the United States or any country DentalX has not yet reviewed), a patient’s reply of STOP or START with their phone number, and the emails the clinic sends through DentalX. When it connects its own mailbox, this also includes replies imported for those DentalX-initiated threads, their senders, subjects, message bodies, timestamps and thread identifiers. The connection does not import the entire mailbox; and
- what a patient does on the pages opened from the clinic’s messages: confirming, cancelling, booking or rescheduling an appointment, and signing a consent form.
5. How we use information
We use the information we decide about to:
- provide DentalX, create and secure accounts, and confirm email addresses and second factors;
- bill subscriptions and keep the business records the law requires;
- answer support requests and messages;
- send service messages, such as sign-in and security emails, notices about changes to DentalX or to a clinic’s billing, and the monthly summary a clinic owner can choose to receive;
- keep DentalX secure, investigate misuse, measure its performance and fix errors; and
- comply with the law.
We use patient information only to provide DentalX to the clinic that holds it: to store and show it to that clinic’s Users, to send the messages the clinic asks DentalX to send, to run the AI features its staff ask for, to back it up and keep it secure, to support the clinic when it asks us to, and where the law requires. DentalX’s administrative console does not show patient records to our support staff. The people who administer our Google Cloud project can technically reach stored data; they do so only to keep DentalX running or secure, at a clinic’s request, or where the law requires.
We do not sell personal information, use it for advertising or share it for anyone else’s marketing, and we do not use patient information to train AI models or for any purpose of our own.
6. AI features
DentalX’s AI features serve administrative and operational purposes only. They run when a clinic’s User asks, on a Plan that includes them. The submitted office text or administrative document goes to Google’s Gemini models through Vertex AI from DentalX’s own Google Cloud project. OpenAI remains disabled. Stored patient records are not fetched for administrative scans.
The AI assistant drafts office workflows, scheduling messages, billing correspondence and staff communications. Scans read identity cards, insurance cards and supply invoices into forms. These features are available to every User of a clinic on a Plan that includes them.Staff must review drafts and extracted fields before use. Use placeholders instead of patient information in the office assistant. Identity and insurance cards can contain personal information; submit them only when the Clinic has authority to do so. AI does not interpret radiographs, draft clinical notes, summarize patient records or clinical documents, or provide medical advice. Existing saved findings are retained with the Clinic’s records under the same retention rules. Our support staff may use the same models to draft administrative replies to support requests, which a person reviews before sending.
Dictation. The microphone button in the clinic app uses the speech recognition built into your browser, which sends the audio to the company that makes the browser (for example, Google for Chrome) under that company’s terms. We never receive the audio, only the text the browser returns. Dictation is off for clinics in the United States or any country DentalX has not yet reviewed, and anyone can type instead.
7. Payments
For subscription purchases through Paddle, Paddle is the merchant of record and VstreamX Studio Inc. supplies DentalX. Paddle handles buyer and payment information as an independent controller, under Paddle’s privacy policy. Card details are entered with Paddle and never reach DentalX’s servers. We retain business billing records and use subscription and transaction identifiers to manage access and reconcile purchases. The data shared with Paddle is limited to clinic subscription billing and contact information. No Patient Data or special-category health data may be sent to Paddle; it does not collect patients’ treatment payments.
8. Service providers
These are the companies that process data for DentalX, in the same three groups as our Sub-processors page, which also shows them in tables.
Our sub-processors
The providers we engage to deliver DentalX:
- 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. Receives: All Customer Data, including patient health information, and the accounts of clinic staff. Where: The United States, with the database in Google’s United States multi-region (nam5) and files and server functions in Iowa (us-central1). Firestore, Cloud Storage and Cloud Functions are covered by the Google Cloud Business Associate Agreement.
- Google Vertex AI (Gemini). Administrative office drafts, ID and insurance card entry, supply invoice extraction, and support reply drafts. Receives: The office text or administrative document submitted with the request; support ticket context for support drafts. Where: The United States: Vertex AI’s US multi-region. Called from DentalX’s own Google Cloud project. AI is limited to administration and operations; clinical AI generation is unavailable.
- Google (Gmail). Reminders, recall notices, consent links, prescriptions and treatment plans sent by email. Receives: The recipient’s email address and the message, with its PDF attachment where there is one. Where: The United States and other countries where Google operates. One DentalX sender address sends for every clinic. It also sends the monthly summary a clinic owner can choose to receive.
- 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. Receives: The patient’s phone number, the messages sent and received, and the files a patient sends. Where: The United States and other countries where Meta operates. Not 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.
- Google reCAPTCHA. Automated-abuse and app-integrity checks through Firebase App Check, and browser verification for a text-message second factor. Receives: Browser, device, application and page-use metadata sent to Google; DentalX does not intentionally include patient record contents in verification payloads. Where: The United States and other countries where Google operates. Firebase 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 merchant of record for subscription billing
- Paddle. Merchant of record for clinic software subscriptions, including checkout, renewals and billing support. Receives: Clinic billing contacts and identifiers, purchases and payment information; no Patient Data or special-category health data. Where: The United States, United Kingdom and other countries described in Paddle’s privacy policy. VstreamX Studio Inc. supplies DentalX. Paddle acts as an independent controller for billing. Card details never reach DentalX; patient treatment payments are excluded.
Services a clinic connects
Accounts a clinic connects itself. The clinic’s own agreement with the provider governs each one, and they are not our sub-processors:
- 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. Receives: The connected account's email address and assignment, encrypted authorization grants, recipients, subjects, message bodies, thread identifiers and attachments used by the selected feature. Where: 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. A 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.
- Your Google Calendar. Appointment sync, only for a clinic that connects its own Google account. Receives: Appointment time, the treatment, the dentist and the patient’s name. Where: Your Google account, which Google keeps in the United States and other countries where it operates. No phone numbers or clinical notes. Your own agreement with Google governs that account.
- 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. Receives: The patient’s phone number, the messages sent and received, and the files a patient sends. Where: The United States and other countries where Meta operates. Not 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.
Connected Google accounts and Limited Use
Connecting a Google account is optional and requires Google’s authorization screen. Email uses permission to read messages and to send mail; Calendar uses the permissions explained when that feature is connected. We use Google API data to provide the connected features you select, including replying to DentalX-initiated threads and sending a document from the selected mailbox. Connecting an account does not authorize advertising, sale of its contents or training general-purpose AI models with those contents.
Our use and transfer of Google API data comply with the Google API Services User Data Policy, including Limited Use. Access by our personnel is limited to authorized support, security, legal or other purposes that policy permits. We do not represent that Google has certified DentalX or approved every connected use merely because an account can be authorized.
Clinic mailbox records are available to staff with the required Messages access. A clinician-specific mailbox is limited to the assigned clinician and clinic owners or managers. The clinic must authorize that access and use it only where lawful. Its agreement with Google governs its Google account; VstreamX remains responsible for the processing it performs through DentalX. A personal Gmail connection is not evidence of a HIPAA business associate agreement or a required data-region commitment.
Each receives only what its purpose needs. We use no analytics or advertising provider. Your browser’s speech recognition (section 6) is not engaged by us, and is described where it applies. When a new sub-processor will receive patient information, we publish it on the sub-processors page before it starts.
9. Where information is kept, and transfers across borders
DentalX stores its data on Google Cloud in the United States: the database in Google’s United States multi-region and files and server functions in Iowa. Its backups are kept in the same Google Cloud project. AI requests are processed by Google in the United States too (Vertex AI’s US multi-region). Email is delivered by Google, WhatsApp messages by Meta and subscription purchases by Paddle, in the United States and the other countries where those companies operate.
If you are in Canada, Mexico or elsewhere in Latin America, or anywhere outside the United States, this means your information is transferred to and processed in the United States and possibly other countries. While it is there, it is subject to the laws of those countries, and may be accessible to their courts, law enforcement and national security authorities under those laws. We use established providers whose terms with us include security and privacy commitments. Clinics tell their own patients about this in their own privacy notices.
10. Security
- Information travels encrypted (TLS), and Google encrypts everything DentalX stores on Google Cloud.
- In addition, DentalX encrypts the patient record’s name, date of birth, telephone, address, emergency contact, medical history and insurance details with AES-256-GCM before they are stored, under a key kept in Google Secret Manager. Consent forms and prescriptions are encrypted the same way: a consent form’s text, the patient’s name and signature and the details of how it was signed, and a prescription’s patient name, medicines, notes and prescriber. Those saved before this encryption began may not be yet. The patient’s email address is not encrypted this way. A patient’s name is also copied, without this additional encryption, onto the other records that need it, such as appointments, invoices, treatments and recalls; appointments also carry the patient’s telephone number and email address, and WhatsApp conversations the patient’s telephone number. Those copies, and other records such as treatment notes, images, documents and messages, are protected by Google’s encryption at rest and by the controls below.
- Each clinic’s data is isolated by security rules that refuse access by default, and each User sees and does only what their role allows.
- DentalX asks every User for a second factor at sign-in: the app does not open a clinic’s data to a User until they have set one up and signed in with it, and no one at the clinic can switch this off. Our own staff must use a second factor to open DentalX’s administrative console. DentalX signs a User out after 30 minutes without activity, including when the browser was closed in the meantime.
- The audit trail records the opening of a patient’s chart, exports and deletions, and changes to patient and treatment records (section 3). It does not record every read, such as opening a stored file.
- The database is backed up daily, with seven days of backups and seven days of point-in-time recovery. Links in patients’ messages expire, and a consent-signing link works once.
No system is perfectly secure. If a breach of the information we are responsible for creates a real risk of significant harm, PIPEDA requires us to report it to the Privacy Commissioner of Canada, to notify the people affected as soon as feasible, and to keep a record of every breach. If a breach affects patient information, we tell the clinic without undue delay so that it can meet its own duties. The individual named in section 15 is responsible for this. If you believe information has been exposed, write to admin@vstreamx.com.
11. How long we keep information
- Connected mailbox grants and email records. Disconnecting a mailbox removes DentalX’s stored authorization grant and prevents further use through that connection. It does not erase imported conversations, sent-message records or documents already kept in the clinic’s records; those follow the clinic-record retention and deletion rules below. Copies already in a sender’s or recipient’s Google account remain subject to that account’s rules. VstreamX cannot delete a recipient’s copy by disconnecting the sender.
- Patient information is kept for as long as the clinic keeps it in DentalX, until the clinic’s data is deleted after it leaves. The clinic chooses a retention policy subject to applicable country restrictions. These choices are recorded, but automatic retention review and deletion are not active for records created in DentalX. Saving a retention policy does not delete patient information or files. The clinic can request deletion or anonymization where its law permits. Consent forms and signing evidence stay with the record. WhatsApp messages and files stay with the clinic until it deletes the patient or its data is deleted.
- When a clinic leaves, we keep its data for 60 days after its subscription ends, then prepare a complete export of it and make it available to the clinic owner. When 90 days have passed since the subscription ended, or sooner if the clinic instructs us in writing, we delete the clinic’s patient information within 30 days, after telling the clinic owner by email at least 30 days before, as sections 8.11 and 13 of our Terms of Service describe. Deleting it also deletes that export.
- Clinic and staff accounts are kept while the clinic’s account exists. When a clinic’s data is deleted, we keep its account details and staff accounts until we close them; a person can ask us to delete their account at any time (section 12).
- The audit trail is kept for seven years while the account exists, subject to earlier deletion when the Clinic’s data is purged. An individual patient’s deletion does not itself erase audit entries; some may identify the patient. The complete clinic export includes the audit trail, and our copy is deleted when the Clinic’s data is purged. Older entries without an expiry date remain until assigned one, removed or included in that purge.
- Billing records are kept for at least six years, as Canadian tax law requires. Subscription, transaction and checkout references are separate from clinical records and can remain after a clinic purge. Records used to recognize already-processed Paddle events expire after 90 days; these are not the underlying invoices or accounting records.
- The record of a data agreement’s acceptance (section 3) is kept for as long as the clinic’s account exists and afterwards for as long as it may be needed to evidence the agreement. It is not deleted when the clinic’s data is deleted. Nor are our notices to a clinic (such as the date its data will be deleted), who they were emailed to, and the clinic’s acknowledgements of them and approvals of a change of sub-processor, which we keep as evidence that the notice was given.
- Error reports and performance measurements are deleted after 90 days, and server logs after 30 days. Error reports made before the 90-day deletion was introduced carry no expiry date, and stay until we remove them.
- WhatsApp opt-outs. When a patient replies STOP or START to a clinic’s WhatsApp messages, we record their phone number with that choice, so that it keeps being honoured. That record survives an individual patient’s deletion. It is included in the clinic export and removed when the Clinic’s data is purged.
- Export files a clinic creates are deleted seven days after they are made. The complete export we prepare when a clinic leaves is deleted with the clinic’s data.
- Backups. Deleted information remains in database backups until they expire, within seven days. The clinic purge removes stored files and their retained versions. Until removed or expired, recovery copies remain protected and are used only to recover from a failure.
12. Your rights
Disconnect a Google account. An authorized user can disconnect a mailbox or Calendar in Settings. You can also review and remove DentalX’s access in your Google account connections. DentalX’s mailbox disconnect removes its stored mailbox grant rather than revoking every shared Google permission; removing access at Google can also affect Calendar connected through the same grant. To request deletion of retained DentalX records, follow the clinic/personal-information process in this section.
Clinic staff, website visitors and anyone who writes to us may ask for access to, correction of, export of or deletion of their personal information by writing to admin@vstreamx.com. Users can correct much of their own profile in the app; some details are managed by their clinic. You may also withdraw your consent to our use of your personal information, subject to legal or contractual restrictions and reasonable notice; tell us and we will explain what that would mean for your account before it takes effect. We respond within 30 days of receiving your request, as PIPEDA requires; if we need longer, we tell you within those 30 days why, and for how long. Requests reach the individual named in section 15. If you are not satisfied with our answer, you may complain to the Office of the Privacy Commissioner of Canada.
Patients exercise their rights with their clinic, as section 2 explains. A clinic can export a patient’s record, which lists the patient’s files (they can be downloaded from the patient’s chart), and can correct, delete or anonymize it. Deleting a patient also deletes their WhatsApp conversations and the files they sent over them, and takes their name off the clinic’s cash-register lines, whose amounts stay in the cash book; the audit trail is retained as section 11 explains. We help clinics answer their patients’ requests.
13. Cookies and browser storage
DentalX itself sets no cookies and uses no browser storage for advertising, analytics or tracking. What it keeps in the browser is what it needs to work:
- the sign-in session, kept by our sign-in provider;
- preferences: the language, the tooth-numbering system, the dictation language, the console theme, whether the side menu is open, the dentist and time last chosen when booking, and which notices have been dismissed;
- a copy of the signed-in User’s own profile (name, email address, role and clinic) and of whether they have and need a second factor, so the app opens quickly;
- the time of the signed-in User’s last activity, a bare timestamp coalesced while the User interacts, so that the sign-out after 30 minutes without activity applies even after the browser was closed; and
- a working copy of the clinic’s records, so the app loads quickly. The patient record’s encrypted fields stay encrypted in it; the copies of names, telephone numbers and email addresses on other records (section 10), and those other records, are in it as they are stored.
Signing out from the menu and the automatic sign-out after 30 minutes without activity clear the displayed account and in-memory working data, remove the profile and second-factor copies, and end the browser session. Both also attempt to remove the on-disk working copy. That removal can be prevented by another open tab or browser restrictions. The recorded activity time is removed when Firebase confirms sign-out; if sign-out fails, an expired time is retained so reopening the app does not restore that expired session.
Some screens load another company’s script, which can store information in the browser under that company’s own policies: Firebase initialization and text-message second-factor screens can load Google reCAPTCHA/App Check on public or app pages, subject to Google’s Privacy Policy and Terms of Use; connecting a clinic’s own WhatsApp Business account loads Meta’s sign-up script, which can set Meta’s cookies. The installed app also stores DentalX’s own program files, which hold no clinic data. The pages patients open from a clinic’s messages remember only the language chosen for that visit.
Subscription checkout runs on a separate billing-only web origin and loads Paddle’s checkout script and payment frame. DentalX supplies a short-lived checkout link; the billing page receives the subscription transaction identifier and public checkout configuration, without the clinical application’s sign-in credentials or patient records. Paddle can receive browser, device, network and payment information and use browser storage under its own privacy policy (section 7). Do not enter patient information in checkout.
14. Children
DentalX is for clinics. Accounts are for adults who work at or for a clinic, and the website is not directed to children. Clinics record information about patients of every age, including children, and are responsible for the consent of a parent or guardian where their law requires it.
15. Who is accountable
PIPEDA requires an organization to designate an individual who is accountable for its compliance and to make that person’s identity available. For VstreamX Studio Inc. that individual is:
Ricardo Javier Sandoval Sandoval
Chief Financial Officer, VstreamX Studio Inc.
admin@vstreamx.com
Office B - 1043 Rosser Ave, Brandon MB R7A 0L5, Canada
That accountability covers all personal information in our custody, including information we transfer to the providers listed in section 8. Other people at VstreamX handle personal information day to day; delegating the work does not move the accountability.
16. Changes to this policy
We may update this policy. The effective date and revision at the top of this page always identify the current text, and changes are published here. If a change affects how we handle patient information, we tell clinic owners by email before it takes effect.
17. Contact
Questions about privacy, requests about your information, and reports of a suspected breach: admin@vstreamx.com, or by mail to VstreamX Studio Inc., Office B - 1043 Rosser Ave, Brandon MB R7A 0L5, Canada.