Security

Built to protect clinic and patient data

Security and data separation are foundational to VetaSphere, not an afterthought.

🔐

Role-based access control

Every user sees only the workspaces their role permits. Access is enforced centrally on the server, not just hidden in the interface.

🧱

Per-clinic data isolation

Each clinic's data is isolated so one clinic can never see another's clients, patients or records.

🍪

Secure sessions

Browser sessions use HttpOnly, Secure, SameSite cookies, with additional protection against cross-site request forgery.

🛡️

Brute-force protection

Login attempts are rate-limited to protect accounts against automated guessing.

📝

Auditing

Sensitive actions are recorded, supporting accountability and review within each clinic.

🔑

Optional 2FA

Two-factor authentication (TOTP) is supported for stronger account protection.

Data separation you can rely on

VetaSphere keeps clinical knowledge, each clinic's own protocols, and individual patient records as strictly separate layers. Updating global knowledge never rewrites a patient's history, and a clinic's protocols never leak to another clinic.

Website enquiries are isolated too

Demo requests submitted on this website are stored separately from any clinic's operational data, and are only accessible to authorised platform administrators.

Responsible disclosure

If you believe you have found a security issue, please contact us via the Contact page so we can investigate.

Have a security question?