Security
How Revarden keeps each agency’s records private, in plain facts, gaps included.
Your agency’s records
Checked in the database itself, on every read and every change.
Agency isolation
Each record is locked to its agency in the database, so one agency’s records can’t be read or linked from another. Automated tests check this on every change to Revarden’s code.
Roles
Owner, Admin, Editor or Viewer. The database checks membership on every read and the role on every change.
| Action | Viewer | Editor | Admin | Owner |
|---|---|---|---|---|
| Read records and download documents | Allowed | Allowed | Allowed | Allowed |
| Add and change records | Not allowed | Allowed | Allowed | Allowed |
| Change talent payout terms | Not allowed | Not allowed | Allowed | Allowed |
| Record advances | Not allowed | Not allowed | Allowed | Allowed |
| Invite editors and viewers | Not allowed | Not allowed | Allowed | Allowed |
| Invite admins, and change or remove access | Not allowed | Not allowed | Not allowed | Allowed |
| Delete an agreement | Not allowed | Not allowed | Allowed | Allowed |
| See the agency’s security events | Not allowed | Not allowed | Allowed | Allowed |
- Viewer
- Read records and download documents
- Editor
- Read records and download documents
- Add and change records
- Admin
- Read records and download documents
- Add and change records
- Change talent payout terms
- Record advances
- Invite editors and viewers
- Delete an agreement
- See the agency’s security events
- Owner
- Read records and download documents
- Add and change records
- Change talent payout terms
- Record advances
- Invite editors and viewers
- Invite admins, and change or remove access
- Delete an agreement
- See the agency’s security events
Documents
Original files sit in private storage. Each download is checked on Revarden’s server, and Revarden creates no public links to documents.
History of changes
Each change is logged with who made it and when, without copying document text. Recorded payments and payouts are corrected with a new entry, never edited away.
Support access
Revarden support sees your records only while an Owner allows it, for 24 or 72 hours, with a reason. While it’s on, every workspace page says so, and each download or import by support is a security event.
Your team’s accounts
What protects each person, and what Owners and Admins can review.
Sign-in
A confirmed email address and a password, with optional two-step sign-in through an authenticator app. Sign-in cookies travel only over encrypted connections, out of reach of scripts on the page.
Two-step sign-in, account changes and sessions
- Two-step sign-in
- Optional for each person, with an authenticator app, and checked by the database as well as the app.
- Account changes
- Changing the sign-in email or removing an authenticator app asks again for a current code or the password.
- Other sessions
- Each person can sign out of every other session from their account settings.
Security events
Owners and Admins see sign-ins, team and role changes, exports, downloads and changes to payment details, kept at least 24 months. Repeated attempts are limited.
Everything recorded and limited
- Security events
- Owners and Admins see sign-ins and failed sign-ins, password, email and two-step changes, team and role changes, invitations, billing changes, changes to invoice payment details, exports and document downloads, and refused access, and can export them as a CSV file.
- How long events are kept
- At least 24 months, with no automatic deletion after that. Each IP address is kept only as its network, never in full.
- Repeated attempts
- Sign-in, sign-up and password reset are limited for each IP address and each email address, access requests for each IP address, two-step codes for each IP address and each account, invitations for each IP address, invited email address and account, and exports, downloads and search for each account. If a limit can’t be checked, sign-in, sign-up, two-step codes and password resets wait a minute, and everything else goes ahead.
Payment details
Revarden never stores card numbers. The bank details you print on your invoices stay with your agency’s records, and each change to them is a security event.
Where your data lives
Stored in London, with each provider handling only its part of the service.
Location
London, United Kingdom. The app’s servers run in London too.
Encryption
Every connection is encrypted (HTTPS, with HSTS on every response). The database and files are encrypted at rest by our database provider. Keys with full access to the database are never sent to the browser.
Backups
Daily database backups, kept for 7 days. Uploaded documents are stored separately and aren’t in these backups.
Logs
Revarden’s own error logs keep an error type and status code, never document text. Our hosting and database providers keep their standard service logs.
Export and deletion
Any member can download records as CSV files and the original documents. For a full export or deletion, the Owner emails hello@revarden.com. Records are kept while the agency uses Revarden, and deleted within 30 days of the Owner asking, as the privacy policy sets out.
What each role can export
Any member can download agreements, invoices, payments, deliverables, talent payouts, tasks, the pipeline and the reports as CSV files, unless the Owner asks Revarden to limit CSV exports to some roles. Any member can download invoice and payout statement PDFs and the original documents.
Companies that process data for Revarden today
| Provider | What it does | Where |
|---|---|---|
| Supabase | Database, sign-in and file storage | London, United Kingdom |
| Vercel | Hosting and edge network for the website and the workspace, and cookieless page analytics for the website | Global |
| Google Workspace | Email to hello@revarden.com | Global |
| Cloudflare Turnstile | Bot check on sign-in, sign-up, password reset and confirmation email requests, password confirmations, the Request access form and the waitlist and partner forms | Global |
| Better Stack | Error reports and uptime checks | United States |
| GitHub | Hosting our code, running our automated checks, and running the workflows that move the database and back it up | United States and other countries |
Not in place
What Revarden doesn’t have, so your reviewer doesn’t have to ask.
- SOC 2 report or other security certification
- An independent penetration test
- Single sign-on
- Malware scanning of uploads
- A published uptime commitment
- Deleting a whole agency in the app
Found a security issue? Email hello@revarden.com, or see our security.txt.
Questions from your IT reviewer?
Email hello@revarden.com and we’ll answer in writing.