Your books are the most sensitive thing your business owns. Here is what protects them, described specifically enough to be checked — and an honest note about what tBiz does not have.
Every row carries the workspace it belongs to, and the rules that enforce that live in the database rather than in application code — so a bug in a screen cannot expose another workspace’s data.
Roles carry permissions per module and per action, so a storekeeper can receive goods without seeing the profit and loss and a CA can read the books without changing them.
Changes are recorded by a database trigger with the values before and after, the actor and the time — which means it captures changes made by any path, not just by the screen that remembered to log.
Taken nightly and retained, and — the part that matters — actually restore-tested, because an untested backup is a hope rather than a protection.
Email verification on signup, password reset, and a single active session per account so a forgotten login on a shared machine does not stay open indefinitely.
The marketing site, the signup form and the quote form load no third-party analytics or tracking script. The human check is first-party.
No. Every row is scoped to its workspace and the enforcement is in the database rather than in application code, so it does not depend on a screen remembering to filter. The isolation has been audited internally and no cross-workspace access was found.
No. tBiz holds no formal security certification, and we will not imply otherwise. If your procurement requires one, that is a real blocker today.
Nightly, with retention, and they are restore-tested rather than merely taken — an untested backup is not a backup.
Yes, per role and per module. A branch manager can be limited to their branch, a storekeeper to stock, and your CA given read-only access to the books — and users are unlimited, so nobody needs to share a login.
Send your security questionnaire with a quote request and you will get a direct answer to each item.