Security and access
How RenOps protects your clinics' operational data, and who can see what.
Hosting
RenOps is hosted in Johannesburg, South Africa, for Southern African groups. Groups in other markets, such as the United States, can be hosted in their own region.
Encryption
Data is encrypted in transit over HTTPS and encrypted at rest.
Organisation isolation
Each organisation's data is kept separate. Every request is scoped to the signed-in organisation.
Audit logs
RenOps keeps audit logs of activity in each organisation, alongside the time and person recorded on every check and ticket.
Backups
RenOps data is backed up, so it can be restored if something goes wrong.
Accounts and roles
Every account is authenticated, and access follows four roles: group admin, general manager, clinic manager and staff.
Clinic staff PINs
Clinic staff sign in with system-issued 4-digit PINs. PINs are scoped to their clinic and stored hashed.
Photo evidence
Photos are held in private storage and shown only through short-lived signed links.
Vendor access
Outside vendors see only the checks and jobs a clinic chooses to share with them.
AI assistant access
Connecting an AI assistant is off by default, and is switched on and scoped per organisation by its admin.
RenOps is designed to support POPIA obligations. Data protection terms, retention and hosting region are confirmed with each group in writing. The public website uses fictional demo data only.
Report a security issue
If you believe you have found a security issue in RenOps or this website, email info@siriuz.ai with the details, and please do not access or change data that is not yours. The same contact is published in our security.txt.
