This page explains how Odontheon thinks about security in plain language. It is not a “HIPAA certified,” ISO, or SOC seal. Clinics remain responsible for lawful handling of patient information in the products they choose.
Identity
One person maps to one Odontheon account (email). Connected apps should extend that identity rather than invent a second signup product. Protect your password and email inbox; we will never ask you to paste passwords into a marketing form.
Secrets and keys
API keys, payment secrets, and AI provider credentials stay on the server side. Browser-facing VITE_* values are for public configuration only (for example an AdSense publisher id), never for passwords or private API keys.
Clinical data boundaries
- Chart-of-record and clinic systems keep patient data in their configured environments.
- We do not put clinic PHI into marketing newsletters or AdSense audiences.
- Education tools that store notes or practice cases on-device should not be treated as an EMR.
Advertising
When AdSense is enabled, it may load on public marketing pages and some education pages. It is kept out of clinical chart workflows and signed-in clinic chart modules. Publisher ids are designed by Google to appear in the browser; they are not account passwords.
Payments
Card data for subscriptions is handled by Paddle as Merchant of Record. See Pricing and Refunds.
Report a concern
Email hello@odontheon.com with “Security” in the subject. Do not attach patient charts. Related: Privacy, Clinical trust, Terms.