Trust center
Your reports, inspections and training records are sensitive. This page says what we do to protect them, who handles them, and what we have not finished yet.
These are controls Reldro runs itself. They are not audit results or third-party certifications.
12+characters
Minimum password length, checked against breached lists
2-steprequired
For every company admin, with no way to switch it off
12hours
Until an idle admin sign-in ends
2years
Activity log kept, each entry linked to the last
7days
A full data export stays available to download
14days
Wait before a deletion happens, and anyone can cancel
Every sign-in is checked, limited and visible to the person who owns it.
Company admins sign in with a password and a code from an authenticator app. It is required, not optional, and it cannot be switched off. Reldro staff need the same, and their sign-ins last eight hours.
Passwords need at least 12 characters and are checked against a public list of breached passwords. Only the first five characters of a one-way fingerprint are sent for that check, so the password never leaves Reldro. Passwords are stored as salted bcrypt hashes.
Everyone can see where they are signed in and end any session. Admin sign-ins end after 12 hours without use, Reldro staff after 30 minutes. Changing a password signs out every other device.
Each person sees only what their role allows, and every company's data is kept apart. Reldro staff can see account-level counts, not report contents.
Records you can take with you, check, and have removed.
Every sensitive action is recorded, and each entry is linked to the one before it, so a change or a deletion shows up when the log is checked. Admins can check it at any time and download it as a spreadsheet. Entries are kept for 2 years.
Admins can download everything in their workspace as a zip file, available for 7 days. Secrets such as passwords are left out.
Admins can have the workspace deleted. It is removed after a 14-day wait that any admin can cancel, every admin is emailed, and backups roll off within 30 days.
Every week an automated drill takes a backup of a test copy, restores it into a fresh database, and checks that the data and the activity log came back whole.
Defaults that make common attacks harder, and checks on every change.
All traffic uses HTTPS, and browsers are told to insist on it for a year.
Nothing can be framed by another site, and forms can only post back to Reldro. A stricter policy that blocks any script Reldro did not issue is running in monitoring mode and will be enforced once it has run clean.
Every change runs type checks, unit tests, browser tests across every role and a scan for committed secrets. Dependencies are updated automatically each week.
Two separate halves, both in US East (N. Virginia): the application that people use, and the database that holds their records.
Netlify
What people reach, and where the rules are applied.
Managed Postgres on AWS
Where everything you enter is stored, apart from the application.
Netlify, AWS and our database provider each publish their own independent audit reports. Those cover their platforms, not Reldro.
Amazon Web Services
US East (N. Virginia)
The cloud that Netlify and the database run on
Data: Everything that passes through the application, in transit, and all stored records
Netlify
Runs on AWS, US East
Hosting and delivery of the application
Data: Everything that passes through the application, in transit
Neon
Runs on AWS, US East
Managed Postgres database and its backups
Data: All customer records, including uploaded documents, stored encrypted at rest
Resend
Sending email (invitations, reminders, digests)
Data: Recipient addresses and the text of each email
Upstash
Rate limiting and short-lived shared cache
Data: Counters keyed by address or account, no report content
GitHub
Source code, automated tests and checks
Data: Code only. No customer data
We are working toward SOC 2. We do not hold a SOC 2 report yet, and we will say so plainly until we do.
Reldro does not certify that your workplace is safe or compliant. It helps your team keep the records.
Email us what you found and how to see it. We reply within three business days. If you test in good faith, stay within your own account and do not read or change anyone else's data, we will not take action against you. A machine-readable copy of this is at /.well-known/security.txt.
Last reviewed October 2026. Questions about any of this: [email protected]