Built carefully, with patient data in mind.
How we think about security at Plandentic - the principles, the practices, and what's coming next.
- TLS Encryption in transit
- EU Hosting region
Plandentic is a dental treatment planning platform - and dental practices entrust us with sensitive information. We take that seriously. This page describes the principles guiding how we build, and the practical measures that protect data in our care today.
Our principles
Before specific tools or controls, four principles shape every decision we make:
-
Privacy by design
Security and privacy are product decisions, not afterthoughts. Every feature is reviewed against the question: "what is the minimum data we need to deliver this?"
-
Minimal data collection
We collect only the data that is strictly necessary to provide our dental treatment planning services. No cross-site tracking, no third-party data brokers, no fingerprinting.
-
Encryption in transit
All traffic to and from Plandentic is encrypted using industry-standard TLS. Sensitive data never travels over an unprotected connection.
-
Least privilege access
Internal access to systems and data is restricted on a need-to-know basis. Production credentials are scoped narrowly and rotated when team membership changes.
Protecting your data
Inside the product, we apply layered safeguards:
- Encrypted transport: all client-server traffic uses TLS. We do not accept unencrypted connections.
- Hardened infrastructure: production runs on managed infrastructure with restricted network access and platform-level patching.
- Authentication: account access requires strong credentials. Sessions are time-bound and tied to the originating device context.
- Access controls: roles and permissions inside the product limit what each user can see and do, so a clinician's account isn't a back door to admin functions.
- Audit trail: sensitive actions are logged so we can investigate if anything looks unusual.
Infrastructure
Plandentic runs on managed cloud infrastructure with EU-region hosting. The provider handles physical security, network isolation, and platform patching at the layers we don't operate ourselves. On top of that we apply our own configuration hardening, monitoring, and access controls.
Backups are taken on a regular schedule and stored separately from primary storage so we can recover quickly from operational issues.
Security assessments
We carry out continuous security code reviews, and do annual penetration testing to ensure the integrity of our platform.
If something goes wrong
No system is immune to incidents. If an event affects data we hold for you, we will:
- Investigate, contain, and resolve the issue with priority over feature work.
- Notify affected customers directly, with the facts as we understand them.
- Provide an honest post-incident write-up describing what happened, what we changed, and how we'll prevent a repeat.
Where we're going
Plandentic is a young company. The mechanisms above are real - but third-party-audited certifications take time, paperwork, and scale. As we grow, we plan to formalize our security posture with the certifications customers and procurement teams expect from a dental SaaS. We will publish each milestone here when it lands, rather than make claims we can't back up today.
If your organization needs specific assurances or documentation before adopting Plandentic, please reach out and we'll work with you directly.
Questions or disclosure
Found something that looks like a vulnerability? Have a procurement question? We want to hear from you:
Email: info@plandentic.com
Postal Address:
Plandentic d.o.o.
Trg Hrvatskih Branitelja 25/1
43000 Bjelovar
Croatia
Our Security and Privacy Protocols
The documents and references that frame how we operate.
Frequently asked security questions
-
How is my data protected in transit?
All traffic between your device and Plandentic is encrypted using industry-standard TLS. We do not accept unencrypted connections.
-
Where is my data hosted?
Plandentic runs on managed cloud infrastructure with EU-region hosting. The provider handles physical security and platform-level patching; we apply our own configuration hardening, monitoring, and access controls on top.
-
Who at Plandentic can access my data?
Internal access is granted on a need-to-know basis. Production credentials are scoped narrowly and rotated when team membership changes. Sensitive actions are logged.
-
Do you use my data to train AI models?
No. Treatment plans, patient information, and any content you upload are not used to train third-party models. We act only as the processor that runs the platform on your behalf.
-
Can I export or delete my data?
Yes. You retain ownership of your data and can request export or deletion at any time. See our Privacy Policy for the rights you can exercise and how to do so.
-
Do you have formal security certifications?
Not yet. Plandentic is a young company and third-party-audited certifications take time and scale. They are on our roadmap and we will publish each milestone here when earned, rather than make claims we can't back up today.
-
What happens if there is a security incident?
We investigate, contain, and resolve the issue with priority over feature work, notify affected customers directly with the facts as we know them, and publish an honest post-incident write-up afterwards.
-
How do I report a vulnerability?
Email info@plandentic.com with as much detail as you can share. We take responsible disclosure seriously and will respond promptly.
See what your patients could be saying yes to.
Start creating treatment plans that reflect your expertise.