Privacy

Last updated 8 September 2026

This says what Bitaboh holds, where it sits, who else can see it and how long it stays. It is written to be checked rather than skimmed, so it names the actual companies and the actual retention periods.

The short version. Your books and your venture records belong to you. They are stored in Frankfurt, separated by company at the database level, and are never sold, never used for advertising, and never used to train anybody's model. Five other companies are involved and each is named below.

Who is responsible

Bitaboh is operated from Uganda by Martin Kisembo. Write to support@bitaboh.com with any question about this page or about data held about you.

What is held

About you

Your name and email address.
A password, stored only as a bcrypt or scrypt hash. Nobody at Bitaboh can read it.
If you sign in with Google: the address Google confirms, and Google's own identifier for your account. Bitaboh never receives your Google password and asks Google for nothing beyond your address and your name.
If you turn on two step sign in: the shared secret for your authenticator app and your unused recovery codes, the codes stored as hashes.
Devices you have signed in from, as an approximate address and the browser you used, so a sign in from somewhere new can be reported to you.
Failed sign in attempts against your address, so an account can be locked after too many. This is kept against the address typed rather than the account found.

About your business

Whatever you record. In the accounting half that is your ledger, purchases, sales, stock movements, staff and salaries, customers and suppliers. In the venture half it is what you are building, what it costs to make, what you have spent and any files you upload as evidence.

Bitaboh does not read any of it for its own purposes. It is not analysed across companies, it is not aggregated into benchmarks, and it is not shown to anybody outside your company unless you share it deliberately.

What the system writes about itself

An audit record of who did what and when, which cannot be edited or deleted.
A record of every message sent to you, being the address, the subject and whether it was accepted. Not the contents.
Where the assistant is used, the number of tokens and the cost. Never the prompt. A prompt would carry what you said about your own business, so the code is written to keep the provider's error message and nothing else.

Where it is kept

What	Who holds it	Where
The database, all of it	Neon	Frankfurt, Germany
The running application	Vercel	Frankfurt, Germany
Files you upload as evidence	Cloudflare R2	Distributed, Cloudflare's network
Email in transit	Brevo	European Union

Uganda has no data centre in this arrangement. Your records leave the country to be stored, which is what makes them available to you from any connection and what makes them survive the loss of a machine.

Who else is involved

Company	What it does	What it can see
Neon	Runs the database	Everything stored, as any database host can
Vercel	Runs the application	Requests as they are served
Cloudflare	Stores uploaded files, and checks that sign ups are not automated	The files, and the sign up check
Brevo	Delivers email	The address, subject and contents of mail sent to you
Google	Optional sign in, and the assistant	Only what is described below

None of these is paid to advertise to you, and none is given data for its own use.

The assistant, and its limits

The venture half can ask Google's Gemini a question on your behalf, and only when you press a button. Nothing is sent while you browse.

It runs on two screens: a question about what your spending might be missing, and reading a receipt you have uploaded.
What is sent is a summary of the figures on that screen. Your prompt is never written to any log, by design.
What comes back can only ever be a question. The database refuses to store a suggestion that is not one, and refuses any answer containing an amount, a price, a cost or a margin. The assistant cannot put a figure into your books.
Google's terms for this service say your content is not used to train their models.

How long it is kept

Files you upload as evidence: 30 days, then deleted automatically. What was read from them is kept; the original is not.
Records of devices you signed in from: 90 days after last use.
Your business records: until you delete them or close the account. Accounting entries are never silently removed; voiding one keeps the original and writes a record of the voiding, because that is what an audit trail means.
Your account: until you ask for it to be removed.

How it is kept apart

Every table that belongs to a company carries that company's identity, and the database enforces the separation itself rather than trusting the application to remember. A query that does not say which company it is acting for returns nothing at all.

What you can ask for

A copy of what is held about you.
Correction of anything wrong.
Deletion of your account and its data.
An explanation of anything on this page.

Write to support@bitaboh.com. Deletion of a company's accounting records may be constrained by the record keeping the law requires of you as a business; where that applies it will be explained rather than used as a reason to refuse.

Cookies

Bitaboh sets a cookie to keep you signed in, and short lived ones during a sign in. There is no advertising cookie, no analytics cookie and no third party tracking on any page.

Children

This is business software and is not intended for anybody under 18.

Changes

If this page changes in a way that affects what is held or who can see it, that will be said on the page and the date at the top will move.