Curofyxis built for clinics handling sensitive patient data, so security isn't bolted on afterwards — it's in the design of every part of the platform.
Every clinic's data is isolated at the database and API layer. Every request is checked against the authenticated user's clinic — there is no path for one clinic to access another clinic's patients, reviews, or team data, even by guessing a URL or record ID.
Access to a clinic's data is governed by granular, per-user permissions, not an all-or-nothing login.
Passwords are hashed with bcrypt and never stored or logged in plain text. Sessions use short-lived signed access tokens with automatic refresh, rate-limited login attempts, and account lockout after repeated failed logins.
Data is regularly backed up to prevent loss and ensure business continuity.
We continuously monitor, test, and improve our security practices to stay aligned with evolving industry standards and emerging threats.
Email: info@curofyx.com