Where your data is held and who can get to it
Your quotes, your hourly rates, your margins and your clients’ addresses. This is what happens to them. Not in reassuring words, but in what has actually been built.
The separation between companies
Several companies run on the same installation. The question is not whether that is possible, but where the wall stands.
Enforced in the database
Every row carries the mark of the environment it belongs to, and the database itself refuses to return rows from another environment. That is not a filter in the application code that somebody could one day forget. It is a bolt underneath, and it applies to the owner of the connection too.
Four gates for a user
Is this module in the plan, does this user have this permission, may they see this record, and does the amount stay inside their authority. All four closed when in doubt: no permission means nothing allowed, and an empty setting means closed rather than open.
An address of your own
You sign in at your own address, with a certificate in your own name. That way a user from one company never ends up in another company’s environment by accident.
What we can see
We build and run this system, so technically we can reach the data. The question is what has been put in place to limit that and make it visible.
Counts only, by default
Our management environment reads across all environments, but by default it sees numbers only: how many users, how many job sheets, how many breakdowns. No names, no amounts, no content.
Content only through a support session
Anyone who wants to see something opens a session with a reason attached. By default that is read-only, with nothing that can be changed. That read-only state is enforced by the server and not by a button that is switched off.
It appears in your audit log
A support session shows up in the audit log of your own environment, with who, when and why. Where you are looking anyway, and not in a report you have to request. Visibility works better than a promise.
A session expires on its own
After 24 hours it is closed, even if nobody thinks of it. A door left open waiting on somebody’s memory is not a door.
Operations and recovery
What happens on the day something goes wrong.
A backup every night
With tested restore. A backup that has never been restored stays an assumption. So restoring it is genuinely done, on a schedule.
Nothing irreversible happens on its own
Suspending an environment for non-payment is only possible sixty days past due and never automatically. It is a button with a name underneath it.
Your data stays yours
Contacts, projects, job sheets and invoices can be exported for as long as your environment exists. A system you can only leave by retyping everything is not a system but a trap.
No tracking in the application
No external scripts, no ad networks, no fonts fetched from another company. The system pulls nothing in from outside. That is a server setting and not an intention.
Want to go through this with your own IT person?
Bring them along to the demo. Questions about the separation between environments, about backups or about export are ones we would rather answer beforehand than afterwards.