Reparo (operated by Timothy Short trading as Ordo Operis, Australia) holds your team's rosters, timesheets and pay rates, your buildings' maintenance history and your guests' reports. This page sets out how we protect them, and how to tell us if you find a problem. It describes what's in place today; we don't list plans as if they were done.
Where your data lives
- Our servers (Fly.io) and database (Supabase) are in Sydney, Australia. Photos and files are stored privately in Cloudflare R2.
- A few named providers process limited data overseas, for example email delivery and push notifications. The full list, with what each receives, is in our Privacy Policy (section 3).
Keeping your organisation separate
- Every record belongs to one organisation, and every request is limited to the signed-in person's organisation. Automated tests check this on every change.
- Inside your organisation, roles and per-person permissions decide what each person can see and do, and our server checks them on every request. Pay rates are only visible to the people you allow.
Signing in
- Passwords are stored only as bcrypt hashes. New passwords are checked against passwords exposed in known data breaches.
- Two-factor sign-in (an authenticator app) is available for every account, and an owner can require it for admins, managers or everyone.
- Sessions are short-lived and renewed with rotating tokens; removing someone, resetting their password or deleting their account signs them out everywhere.
- Repeated wrong passwords and verification codes are locked out.
Our own access
- Reparo support staff must use two-factor sign-in, and each only has access to the tools their job needs.
- Viewing your account as support needs a reason and shows in your organisation's activity log.
Protecting data in transit and at rest
- All traffic is encrypted (HTTPS). Our database only accepts encrypted connections.
- Photos and files are private and only reachable through links that expire. Uploaded photos are re-encoded, which removes location and camera details.
- Our web pages only run Reparo's own code (a Content Security Policy) and can't be embedded by other sites.
Backups and availability
- The database is backed up every night, encrypted, and kept for 30 days. We've tested restoring it.
- We check that Reparo is up every few minutes. Live status: status.reparoapp.net.
How we build Reparo
- Every change runs our automated tests, code scanning, secret scanning and a check of the libraries we depend on.
- We review Reparo's security regularly; the last full reviews were in October 2026.
If something goes wrong
- We have a written incident plan. If a breach affects your organisation's data, we'll tell you within 48 hours of confirming it (see our Data Processing Addendum).
Reporting a security problem
If you think you've found a security problem in Reparo, please email support@reparoapp.net with "Security report" in the subject. Tell us what you found and how to reproduce it.
- We'll reply within 3 working days and keep you updated until it's fixed.
- Please don't access, change or delete other people's data, disrupt the service, or share the problem publicly before it's fixed.
- If you act in good faith and follow these rules, we won't take legal action against you for your research.
Machine-readable contact details: /.well-known/security.txt.
Questions
Security questionnaire or due-diligence questions: support@reparoapp.net.