Security
Your books, and who can actually reach them
You are about to put your revenue, your suppliers and your staff's hours into somebody else's software. Here is what we do with it, and — as much to the point — what we deliberately never ask for.
What we never ask for
The safest data is the data we do not have
Your banking login
Payments leave BizBoard as a file you upload to your own bank. Nothing here can move money.
Your email password
A mailbox is connected through your provider's own consent screen, and you can withdraw it there without asking us.
Your card details
Subscription payments go through our payment provider. Card numbers never reach our servers.
An AI key, unless you want one
If you add one it is yours, used for your business only, with a spending cap you set.
Separation
Between businesses, and inside yours
Every record belongs to one business, and the queries that fetch them are filtered by which business you are signed in to rather than by the page remembering to ask. A bug in one screen cannot become a leak across customers.
Inside your own business the same idea applies to people. A login opening everything is the most common way small businesses lose control of their own data, so each page decides for itself which roles may open it.
| Role | Can open | Cannot open |
|---|---|---|
| Owner | Everything, including settings, billing and the AI key | — |
| Manager | Stock, rota, bills, customers and tasks for their venues | Billing, the AI key, other venues |
| Staff | Their own hours, tips and tasks | Revenue, payroll, invoices, bank details |
| Accountant | The books, the VAT figures, the ledger export | Payroll, the till, stock, bank details |
| Supplier | Their own product list and quote requests | Any customer's prices, volumes or suppliers |
Passwords and sign-in
Passwords are stored as PBKDF2 hashes, never as anything reversible. Sign-in and password reset are rate limited per address — making each guess expensive only helps if something is also counting the guesses.
Where your data is
On infrastructure inside the European Union, and it stays there. We do not sell it, do not share it with other customers, and do not use one customer's figures to build a feature for another.
Taking it away
Exportable while your account is open: the ledger in your accountant's format, invoices as PDFs, records as files. Software that makes leaving difficult is making an argument about itself.
The AI, specifically
Only figures we computed ourselves leave the building
When you connect your own key, what gets sent is the numbers the app worked out — never the free text somebody typed into a note, and never an invoice's raw wording for the advisor to obey.
That is a security decision as much as a quality one: a note field reaching a prompt would be a way for somebody to tell the reader what to think about the next invoice.
- Your own provider key, on your own account, never ours
- A spending cap you set, per feature
- Every feature off until you switch it on
- Every figure in the app still works with AI switched off entirely
- No customer data is used to train anything, by us or for us
What we are not claiming
No badges we have not earned
We are a young company and we are not going to dress this page in certifications we do not hold. We have not completed a SOC 2 or ISO 27001 audit. If your procurement process needs one, tell us — it is useful for us to know how many people it blocks.
Telling us about a problem
If you believe you have found a security issue, write to us and we will reply. We will not threaten anyone who reports something in good faith, and we would much rather hear it from you than from somebody else.
Questions before you trust us with the books?
Ask them. You will get a straight answer from a person who built the thing.