Security
Security built into how RepairOps works
Your customers trust you with their devices and their details. Here's how RepairOps protects the information your shop keeps.
Protections
How shop data is protected
These protections apply on every plan unless noted.
Each shop's data kept separate
Shop data is separated at the database level with Postgres row-level security. Automated checks fail the build if a table is missing its access policies.
Encrypted secrets
API keys, integration credentials, device passcodes, and recovery codes are encrypted with AES-256-GCM. Connections to RepairOps use HTTPS.
Two-factor sign-in
Staff can sign in with an authenticator app, recovery codes, or passkeys, and shops can require two-factor authentication for owners and managers.
Access by role and shop
Owners, managers, front desk, technicians, and QC reviewers get the access their role needs, and staff can be limited to the shops they work in.
A record of changes
Status changes and edits are recorded with who made them and when. Enterprise plans can review and export the full audit trail.
Backups and exports
Automatic daily backups with the retention you choose, plus CSV exports of customers, tickets, and inventory. Restores are run by our team on request.
Questions
Doing a security review?
If you have questions about how RepairOps handles data, or you need details for your own compliance review, get in touch and we'll walk you through it.
Now onboarding beta shops
Ready to see it in your shop?
RepairOps is onboarding repair shops in small batches. Join the beta and we'll be in touch when a spot opens.