Now live · See DIAL3D on a live treatment center site — chat, call, and verify insurance. No demo call required.

Privacy Policy.

Last reviewed · October 14, 2026

This policy describes how Disl LLC d/b/a DIAL3D collects, uses, and protects personal information collected via dial3d.ai and related properties. For protected health information (PHI) processed on behalf of treatment-center customers, separate HIPAA and 42 CFR Part 2 obligations apply — see those pages and your executed BAA for governance.

Information we collect

When you visit dial3d.ai, we collect: pages visited, browser type and version, IP address (anonymized after 90 days), and any information you voluntarily provide via demo, contact, or trial-signup forms (typically: name, work email, organization, role, and what you'd like help with).

How we use it

To respond to your inquiry, schedule demos, route to the appropriate team, and (for customers) to deliver and improve the DIAL3D platform. We do not sell or rent personal information.

Cookies + analytics

We use Google Tag Manager and Google Analytics 4 to measure aggregate site usage. No PHI is processed by analytics. You can opt out by enabling Do Not Track or using a browser extension that blocks GTM/GA4.

DIAL3D Comply and connected ad accounts

DIAL3D Comply lets healthcare providers connect their own advertising accounts (Google Ads, Microsoft Advertising, Meta, TikTok) so DIAL3D can send conversion events on their behalf. Learn about DIAL3D Comply.

Google user data we access. When you connect a Google Ads account, you grant DIAL3D access through Google OAuth with the Google Ads scope. We use this access only to: list the ad accounts you can access (their names, IDs, and whether each is a manager or test account), so you can choose which one to connect; read the account's existing conversion actions and, only when you choose to, set up the ones DIAL3D's events are recorded against; and upload conversion events (calls, form leads, qualified inquiries, admissions) to the account you connect. We do not read, create, or change campaigns, ads, audiences, budgets, or reporting data.

How we store it. OAuth refresh tokens are encrypted at rest and stored in AWS in the United States. Before a conversion event is sent, IP addresses, browser details, and page query strings (other than ad click identifiers) are removed, and the addresses of treatment and intake pages are replaced with a generic label. Contact details are removed, or one-way hashed only for the advertising platforms the provider chooses to enable. No health or treatment information is sent to Google.

Sharing. We do not sell Google user data or share it with third parties, and we do not use it for advertising, profiling, or to train AI models.

Retention and deletion. Tokens are kept while the account is connected. You can disconnect at any time in the Comply console or at myaccount.google.com/permissions. When you disconnect, or when we detect that access was removed, we delete the stored token, and in every case within 30 days.

DIAL3D's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Your rights

If you are a California, Virginia, or other US state with consumer privacy rights, you may request access, correction, or deletion of your information by emailing dpo@dial3d.ai. We respond within the statutory window for your jurisdiction.

Contact

Data protection inquiries: dpo@dial3d.ai. For HIPAA compliance specifically, see our HIPAA page and contact your account team.

This policy is a summary. Material updates are announced via in-product notice and direct email to account owners. Effective date: October 14, 2026.

Chat with Avery