Where your work lives, and who can see it.
For directors and the people who look after their IT. Nothing lives on anyone's computer: every job is kept in one record and one file store, walled off from every other studio, and copied somewhere else every night.
From an email to the job record, and a copy every night.
- 1 Comes in
Emails
Only what's sent or CC'd to the studio's own address.
PostmarkFiles
The Send us files link and uploads, any size.
Straight to storagePeople
An email sign-in link, then two-step for the money seats.
Supabase Auth - 2 Checked
Filed on the right job
Every request checks who you are and which studio and seat you're in.
Vercel, LondonVirus checked
Every file, before anyone opens it. Previews made here too.
Our own checker, Fly.io, LondonThe AI helper
Gets only what one task needs. Never used to train models.
Anthropic - 3 Kept
The job record
Emails, briefs, approvals, hours and prices. Every studio walled off in the database itself.
Supabase, LondonThe files
Every file, in its own studio's space, named by job number. Proofs frozen once sent.
Cloudflare, Western Europe - 4 Copied every night
A copy elsewhere
The whole record, encrypted, and every new or changed file. Nobody can delete a copy in its first 30 days, not even with the password.
BackblazeEnd of day report
Every evening, in each director's inbox, readable with nothing else running.
Email
The app, the job record and the virus checker run in London. Files are kept in Western Europe. A few services that help run InRegister are based in the United States; where information leaves the UK, it's protected by the safeguards UK law requires.
Everyone sees what their seat allows. Nothing more.
Between studios
Every studio's clients, jobs and files are walled off from every other studio's. The database refuses to cross the wall, not just the screen.
Between seats
Freelancers never see quotes, rates, budgets or margin, not on screen, in downloads, in emails or in the database. Project managers can look at quotes but only directors and finance change money.
Clients
A client only ever sees their own work: their own jobs, files and links, never another client's.
Links
Links in emails are long and random, and only a fingerprint of each is kept, so they can't be guessed or read back. Buttons in emails ask for one tap, so an email scanner can't act by itself.
The safeguards you don't have to think about.
Signing in
No passwords to steal: people sign in with a link sent to their email. Directors and finance are asked to add two-step sign-in with an authenticator app, and once it's on, the database won't show money without the code.
InRegister only reads what's sent to the studio's address. Connecting Gmail is optional, asks for one permission, and the key Google gives us is encrypted before it's stored.
Files
Every file is virus checked and held until it's clean. If the checker is ever down, the file is let through with a clear note that it hasn't been checked, and the studio is told.
Payments
Card payments go through Stripe's own checkout. Card numbers never touch our system.
Undo and a record of changes
Almost anything can be undone by the person who did it, and important changes are recorded: who, when and what.
Your records are yours
Directors can download every record at any time. When a studio leaves, it takes a copy of everything, and we then delete it.
The services behind InRegister.
| Service | What it does | Where |
|---|---|---|
| Vercel | Runs the website and the app | London |
| Supabase | The database (the job record) and sign-in | London |
| Cloudflare | Stores the files | Western Europe |
| Fly.io | Runs our own virus checker and makes file previews | London |
| Postmark | Receives the studio's email and sends sign-in links and reminders | United States |
| Anthropic | The AI helper, for the one task in hand | United States |
| Backblaze | The nightly copy, kept apart from everything else | A different company |
| Stripe | Card payments for plans | United States |
| The Gmail connection, only if a studio switches it on | United States | |
| Xero | The studio's own accounts, only if a studio connects it: clients, invoices and credit notes go in, paid comes back | The studio's own Xero |
| Intuit (QuickBooks) | The studio's own accounts, only if a studio connects it: clients, invoices and credit notes go in, paid comes back | The studio's own QuickBooks |
None of them sell or advertise with a studio's information, and the AI helper's provider doesn't use it to train its models. More in the privacy notice.
Tested the way an attacker would try.
A separate security review
The code and every database rule were reviewed by a separate AI security reviewer that had no part in the building work, looking for ways in as an attacker would. The most serious findings were fixed the same day, and the rest are being worked through.
Testers that try the walls
Automated testers sign in as every kind of seat and try to reach what they shouldn't: another studio's jobs, a freelancer seeing prices, a client seeing another client.
Never on real work
All testing happens in pretend studios with made-up people. No real studio's work is ever used to test InRegister.
Your IT person has a question we haven't answered? We're happy to go through it with them.
Email us →