Security
The details you'd get sued over, encrypted in the database itself.
Tax file numbers, bank accounts, dates of birth, next of kin. Seventeen fields that never reach the database as readable text, and that nothing in the app is allowed to read straight back out.
The problem
Right now those details are on somebody's desktop.
Every business holding a crew's paperwork holds the same handful of things, and almost nobody set out to store them the way they ended up stored.
Emailed once, kept forever
A tax file number sent as an attachment is now in two inboxes, on two phones, and in every backup either company has ever taken.
A spreadsheet with everyone in it
One file with the whole crew's bank details, copied to whoever needed it that week. There is no way to take a copy back.
Nobody knows who has looked
If a bloke asked who in the office can see his medical notes, most businesses could not answer it, because the answer is everyone.
How it works
Locked on the way in, not guarded on the way out.
It is encrypted before it is stored
The seventeen fields are scrambled on their way in, with a key of your business's own. Readable text never reaches the database, so there is nothing in there to find.
The app cannot read them back
Not "is not meant to". It has no permission to. One narrow path opens one record at a time for someone whose role allows it, and that path is the only one there is.
The key is not kept with the lock
The key that unwraps your business's key is held outside the database entirely. A copy of the database on its own opens nothing.
For the crew
It knows where you clocked on. It doesn't follow you home.
While a bloke is on the clock, the app takes a location fix. Sitting on a break it stops. Clocked off it stops. That is not a checkbox somebody in the office can quietly turn on, either: the database itself refuses to record a location for anyone who isn't on the clock at that moment.
Who can open what
Being logged in is not the same as being allowed.
Your business, and only your business
The fence is in the database, not in the screens, so a fault in a page cannot hand a row over to the wrong company. Ask for someone else's worker and you get nothing back.
The role is read fresh, every time
Not taken from the login and not remembered from this morning. What you are allowed to see is read off your membership as you ask, so taking somebody's access away takes effect immediately.
Bank and tax sit behind their own permission
An admin without it gets the rest of the record and not those fields. A worker cannot be given it at all, which is enforced in the database, not left to whoever sets people up.
Certificates and docket photos sit in private storage as well. There is no public link to any of them.
The blunt ones
Three a cautious owner always asks.
These three are the questions that get dodged in fine print. They held this spot unanswered until each one could be answered straight, and here they are.
Where the data is hosted
In Australia. The database is run by Supabase in Sydney and your records stay there. The app's own pages and images are delivered worldwide so it loads fast on any site, but that is delivery, not storage.
How it is backed up
Every day, automatically, with the last 7 days kept and restorable. The backups are managed by Supabase, stored separately from the live system, and encrypted in transit and at rest.
Straight about the edge of it: those backups cover the records, not the image files. Certificates and docket photos are not inside them yet.
What happens to your records if you leave
When your subscription ends, your records stay readable to you, read-only. Records the law requires your business to keep, like time and wage records which must be held for 7 years, are retained for that period. Where no legal obligation applies, we delete data on request, and we'll help you get your data out.
Every outside service CrewBase uses is named, all of them, on the privacy page.
Straight answers
What people actually ask.
Seventeen fields, and they are the ones you would not want read out: tax file number, bank name, account name, BSB and account number, super fund, member number and USI, date of birth, email, residential and postal address, emergency contact name, relationship and phone, work restrictions and emergency response notes. Names, phone numbers and licence classes are not encrypted, because the office has to be able to read them to run the day.
No, and it isn't the screens that stop it. The rule sits in the database, so every read is filtered to the businesses you actually belong to before a screen ever sees a row. Ask it for a worker who belongs to someone else and you get nothing back, not even a hint that the record exists.
Only someone with a live role in your business, and only if they hold the financial permission on top of it. An admin without it gets the rest of the record and not those fields. A worker can never hold it at all, so a worker can never open anyone's.
No. Location is only taken while a bloke is clocked on. Go on a break and it stops, clock off and it stops. It isn't a setting somebody can quietly turn on either: the database will not accept a location for anyone who isn't on the clock at that moment.
Questions your IT bloke wants answered?
Send them over. If the answer is "not yet", you will get that instead of a brochure, the same as the three above.
7 days free. No card, no contract.