DENTALHUB CONNECTOR

Privacy policy

Effective September 22, 2026. This policy describes Dia DentalHub Connector version 0.7.1 during the protected pilot.

Protected pilot: Office-scoped cloud import, private storage, encryption, row-level access controls, and audit logging are active. Real-patient use still requires the practice's healthcare agreements and production approval. Patient information is not sent to an AI provider unless that protected processing is separately approved and enabled.

What the connector accesses

The connector runs only on app.dentalhub.com and the signed-in Dia workspace. When an authorized employee starts a check, it reads supported claim, pre-authorization, payer, and remittance information needed for the office workflow.

This information may include:

Patient, claim, and authorization reference information shown in DentalHub
Payer, procedure, tooth, service date, and status information
Billed, allowed, paid, and patient-responsibility amounts
Decision, denial, remark, and follow-up details
Original remittance and determination PDFs selected by the supported workflow

How information is used

The connector uses this information only to organize authorized DentalHub results, show original evidence, provide validated Dia feedback, and identify the next office action.

Current storage and sharing

The connector keeps collected PDFs and transfer receipts in the employee's Chrome profile for retry and original-file viewing. In connected mode, an authenticated worker also sends them through Dia on Vercel to the assigned office's private Supabase storage and database. Row-level security restricts access to workers assigned to that office. Local copies remain until the extension's local data is cleared or the extension is removed. Cloud retention follows the practice's Dia agreement.

Dia does not sell information or share it with advertisers, data brokers, or unrelated third parties. Operational audit events exclude patient names, dates of birth, identifiers, and document text.

Information the connector does not collect

The connector does not store or send DentalHub passwords or session tokens to Dia. To retrieve PDFs the signed-in worker is authorized to view, it reads DentalHub's current access token in browser memory and uses it only for requests to DentalHub. It stores a short-lived Dia upload token in the Chrome profile to connect the worker to the correct office. It does not read browsing history from unrelated websites, keystrokes, precise location, advertising identifiers, or payment-card information.

Security

The connector requests access only to the DentalHub application, Dia workspace, and Dia's Supabase storage host. It uses packaged code and does not load remote JavaScript. Cloud transfers require worker authentication, HTTPS, private storage, office-level access controls, and audit logging.

Limited use

Dia limits information use to providing and improving the disclosed insurance-workflow purpose. Dia does not use connector data for advertising, lending, credit decisions, or unrelated profiling.

Changes

By default, real-patient feedback uses Dia's deterministic rules and is not sent to an external AI provider. If protected OpenAI processing is enabled later, API response storage is disabled and the applicable contractual and retention controls must be active first.

Contact

For privacy questions, use the Dia Connector support page or contact the Dia pilot owner through the support channel provided during onboarding. Do not include patient information in a support message.

Connector support Dia workspace