Clear answers about how Molar protects practice and patient data.
Molar is designed to support HIPAA-compliant dental operations. Rather than a badge in a footer, here is what that actually means — and a direct line for the questions this page doesn't answer.
Secure cloud infrastructure
Molar runs on secure, professionally managed cloud infrastructure — no on-premise server for your practice to secure, patch, and back up.
Encryption
Data is encrypted in transit and at rest.
Role-based access controls
Team members see the workflows and records their role requires. Access follows responsibility, and administrators control it.
Audit trails
Activity in the system is logged, supporting accountability for who accessed and changed what.
Backups and recovery
Practice data is backed up with recovery procedures in place.
Monitoring
Infrastructure and application monitoring support availability and help surface issues early.
Business Associate Agreement
Molar enters into a Business Associate Agreement (BAA) with practices, as expected of a vendor handling protected health information.
Data ownership and export
Practice and patient data belongs to the practice. If you leave Molar, we provide your data in a usable export format.
Incident response
We maintain procedures for responding to and communicating about security incidents.
A note on scope: this page describes safeguards at a level appropriate for a public website. Detailed architecture and security-sensitive implementation specifics are shared with practices under appropriate agreements — ask us for documentation.
Patient data deserves more than a badge.
Bring your security and compliance questions to the walkthrough — or send them ahead of time.