Security & Trust
PracticeReady Hub
PracticeReady Hub is built for dental, medical, and other healthcare practices, so protecting the records you store with us is a core requirement, not an afterthought. This page summarizes the safeguards that are in place today and how we check them. It is a summary of our work, not a promise that nothing can ever go wrong.
How your practice data is protected
Requests for your private practice records are checked on our servers before any of that data is returned or changed: the request must come from a signed-in account associated with your practice, stay within the locations that account can access, and match the role and permissions your practice has assigned. When your practice sets a staff member's role, the app applies those settings — the role determines the locations and actions available to that staff member in the app.
Documents you upload — compliance records, service invoices, equipment manuals, and similar files — are stored privately. They can be opened only through access-checked requests, and new uploads are not stored as public links.
You control who has access
Access is managed by you, not by us. Practice account holders invite staff, assign roles and permissions, and can adjust or remove access at any time from within the app. We encourage practices to review their staff list periodically.
Protecting public forms
Our public Contact and Demo forms are protected by a human-verification challenge, and every submission is verified on our servers before an email is sent. If verification fails or cannot be completed, the submission is rejected.
No single safeguard stops all abuse, and we don't present verification as anything more than one layer of protection. We continue to improve these defenses over time.
How we verify our work
Whenever security-relevant functionality changes — who can access which records, how documents are downloaded, how public submissions are handled — we run focused automated regression suites that lock in the expected behavior before the change ships.
We treat verification as ongoing work rather than a finished milestone, and we would rather fix issues than hide them.
Our approach to risk
No software can promise perfect security, and we do not claim ours is an exception. Safeguards can fail, and issues can be found that we have not yet detected. What we commit to is checking our work, fixing problems as we find them, and being straightforward with you about how the platform is built.
If you believe you've found a security or privacy issue, or something looks wrong with your data, you can report a concern through our Contact page.
Report a concern