What we hold, where it is held, and who else can see it. In plain terms, because you are deciding this on behalf of your clients as well as yourself.
Two different things live in Mikkl and they are not treated the same.
Your business’s books — your transactions, your clients, your employees’ payroll — are yours. You decide what goes in and why. We hold and process it on your instruction and for no other purpose: we do not sell it, we do not use it to train anything, and we do not look at it except when you ask us to help with something specific.
Your account — your name, email, which plan you are on, what you have paid — is ours to manage, and we decide to collect it so that the service can work and be billed.
If you keep books for other businesses, the data about their employees belongs to them. An employee asking what is held about them should ask their employer, who decides it; we cannot answer on their behalf.
The database is in Canada (Supabase, on AWS in ca-central-1). The application runs on a server we rent. Backups are encrypted before they leave that server and stored separately — the key that could decrypt them is not kept on the machine that writes them, so somebody who takes the server cannot read its backup history.
Everything is encrypted in transit, to your browser and to the database.
The full list, and what each one gets, is on the sub-processors page. Two are worth stating here because they surprise people.
Error reports go to Sentry, in the United States, when something breaks. They are stripped first: no request bodies, no cookies, no authentication headers, and payroll identifiers — TRN, NIS, NHT, dates of birth, pay rates — are removed by name and by shape. What is left is which account hit which bug.
Document scanning is off until you turn it on. If you do, the receipt or bank statement you upload is sent to Anthropic, in the United States, to be read. Nothing else is — not your ledger, not your payroll. You can turn it off again at any time, and CSV statement import never uses it, because a CSV is read on our own server.
Payroll identity — TRN, NIS and NHT numbers, dates of birth and pay rates — is not merely hidden from people without payroll access. It is removed from the data their browser receives, so it is not there to be found.
Every change to your books records who made it and when. Owners and admins, platform operators and accountants you have engaged are required to use two-factor authentication, because those accounts can see everything.
Your books stay as long as your workspace does. If you close it, we delete it.
Encrypted backups are the exception, and we will not pretend otherwise: they age out on a fixed schedule rather than being edited, because a backup you can reach into and rewrite is not a backup. So a deletion takes effect immediately in the live system and works its way out of the backup window after that.
Jamaican tax rules may require you to keep records for a period that outlasts your wish to delete them. That is your obligation as the business, not ours, but it is worth knowing before you ask us to erase something.
A copy of everything. Settings → Export gives you your whole workspace as a file, without asking us.
Corrections — edit them yourself; the change is recorded with your name on it.
Deletion — ask us and we will purge the workspace, subject to the backup window above.
If data is exposed, we will tell you what happened, what was affected and what we have done, within the time the law requires. We would rather tell you early and be incomplete than tell you late and be tidy.
Mikkl is operated from Jamaica and the Data Protection Act 2020 applies. Write to us about anything on this page, including to object to something we do with your data.