Security
How RIO protects your data
RIO is multi-tenant: many organizations share one installation. This page describes the controls in the product today, including what is not available yet.
Organizations are kept apart
- Every record stores the organization it belongs to.
- A database guard refuses queries that do not name the organization.
- Public pages (forms, careers, booking pages) look up only the one published item they show.
Permissions are checked on the server
- Each request is authorised by the API against the person’s role, not by what the browser hides.
- Built-in roles cover most teams; custom roles grant exactly the permissions you choose.
- Customers, vendors and partners get portal access only to what is theirs.
Sign-in
- Passwords are hashed with scrypt and a random salt.
- Sessions use HTTP-only cookies, and refresh tokens are rotated on every use.
- Repeated failed sign-ins are rate limited, and responses do not reveal whether an account exists.
- You can sign out of devices you do not recognise from your security settings.
- Two-factor sign-in and single sign-on are not available yet.
Audit trail
- Changes that matter record an audit event in the same database transaction as the change itself.
- Organization admins can see who changed what; entries are kept for 400 days.
Files and secrets
- Uploads are checked against an allowed list of types, by their actual content as well as their name, and capped at 10 MB.
- Files are served as downloads so they cannot run as pages in your browser.
- Vault encrypts passwords on your device with your master password; RIO stores only encrypted data and never sees the master password.
Bring the whole business into one place
Create your organization, invite your team and start with the apps you need. No card required.