Skip to content
Log in
VetBis
Try free

Data security

Data security practices: which layers protect your clinic data

Every VetBis action passes identity verification, role and branch permission and clinic-level data separation, and the action is recorded. We only describe safeguards that can be verified. For the full picture see the trust centre, the security feature and our data protection approach.

54321
  1. 1Secure session
  2. 2Role and permission
  3. 3Clinic and branch separation
  4. 4Audit log
  5. 5Backup

Five gates for one request

As you scroll the layers pull apart. Each layer answers a separate question: who may do what, whose clinic's records, who did it, can it be recovered.

54321
Infrastructure · no figures published

Backup

Backup is operated as part of the service. We have no written confirmation to publish for frequency, retention or data location, so this page states no figure or promise; write to support for details.

Steps

  1. 1Secure sessionEvery action is authenticated first. A user whose session cannot be verified or has expired cannot act.
  2. 2Role and permissionThe user's role, personal overrides and the branches they may reach are checked on every action; an action without permission is rejected.
  3. 3Clinic and branch separationEach clinic's and branch's data is kept separate; one clinic cannot see another clinic's records. The separation is applied in more than one layer.
  4. 4Audit logWho did what and when is written to the activity record. Personal data is not spelled out in technical records.
  5. 5BackupBackup is operated as part of the service. We have no written confirmation to publish for frequency, retention or data location, so this page states no figure or promise; write to support for details.
Rows of black server racks receding down a long data centre aisle
A veterinarian reviewing records on a monitor in a clinic
Illustrative image.

What shows up on the clinic screen

The layers produce these three outcomes on screen. They describe product behaviour and carry no figure or success-rate claim.

  • Only their own data

    Vets and staff see the patient and owner records of their own clinic and the branches they are authorised for.

  • No button without permission

    An action the role does not allow disappears from the screen; if it is attempted anyway, the system rejects it.

  • A trail is left

    The action, the user and the time are written to the activity record.

Keep reading