Privacy
Wabi checks a payment against the bank's own record. This page says what we hold while doing that, who else sees it, and how to get rid of it.
Last updated October 13, 2026
The short version
- We never ask for your banking login or password. We cannot move money.
- We do not sell anything about you. There is no advertising and no analytics here.
- A check keeps the bank's own answer: reference, amount, sender, receiver, date.
- You can erase a personal history yourself, and write to us to close your account.
What we hold
Only what a check needs, what a team needs, and what a bill needs.
- Your account
- The email address you sign up with, the name you give us, and a password stored hashed by Supabase Auth. If you continue with Google, Google tells us your email address, name and profile picture, and nothing more.
- Your team
- Its name, its branches, the roles you set, and the staff logins you create.
- Your checks
- What the bank returns about a payment you verify: reference number, amount, sender and receiver names, the account numbers as the bank prints them, the date, the bank, and the bank's full answer. The customer's phone number if you type one. A receipt you refuse is kept the same way, with the reason.
- Your receipts
- The photo you scan and the bank's own slip, in private storage only your team can read.
- Your saved accounts
- The bank account numbers and holder names you save, so a payment into the wrong account is caught.
- Your bill
- Your plan, your invoices, the reference of the transfer you pay us with, and how many checks were run.
Checking without an account
Anyone can run a few checks without signing up. To keep a free allowance from being taken endlessly, those checks are counted against three signals: a random id in a cookie, a hash of your browser's settings, and a hash of your IP address with the day's date mixed into it.
We store the hashes. The IP address itself and the raw browser string are never written down, and a hash keyed to one day cannot follow you into the next.
What we do with it
- Answer the check you asked for, and tell you when a receipt has been seen before.
- Show your history and your team's, and export it when you ask.
- Count what you use, and bill it.
- Keep the service running and work out why it broke.
- Write to you about your account, your bill, or an outage.
We do not profile you, sell your data, or hand it to anyone for advertising.
What goes to the bank
To check a payment we ask the bank or wallet that issued the receipt. It gets the reference number, and where that bank needs it, the last digits of the receiving account. Nothing about you goes with the question.
Several Ethiopian bank hosts refuse traffic from outside the country. Those requests travel through a relay we run in Ethiopia, which passes the question on and returns the bank's answer. The relay writes nothing down.
- Commercial Bank of Ethiopia
- Telebirr
- Awash Bank
- Zemen Bank
- Dashen Bank
- CBE Birr
- Wegagen Bank
- Bank of Abyssinia
- M-Pesa
Photos of receipts
When you scan a receipt, the picture is read for text on a server we run in Germany. It is written to a temporary folder for as long as the reading takes, then deleted. Nothing about the picture is logged on either side: not the image, not the text it held, not its length.
The photo is then stored against the check it verified, in a private bucket. A public link to it never exists.
What your team can see
On a named business the owner sees everything filed under it, and pays the bill. A member sees the payments they are holding; once they hand them over, those rows are the receiver's to answer for and leave the giver's screen. A branch manager sees their branch.
That is enforced in the database, not in the screens, so no page and no API key can be talked into showing more.
Who else sees it
- The bank or wallet
- The one you are checking. It gets the reference and nothing about you.
- Supabase
- Runs the database, the sign-in and the file storage.
- Vercel
- Serves this site.
- Our own two servers
- The text reader in Germany and the relay in Ethiopia.
- Only if you choose to sign in with Google.
Nobody else. We have no advertising partners and no analytics vendor. We would hand something to an authority only against a valid legal demand.
Where it is kept
The database, the sign-in and the receipt files sit in Supabase's Ireland region, and the site itself runs in Dublin. The text reader runs on our own server in Frankfurt. The relay in Ethiopia keeps no copy of anything that passes through it.
How long we keep it
- Checks and receipts stay until you delete them. A deleted row is marked and kept, because that reference is how the same receipt is recognised if it comes back a second time.
- On a personal account, Erase my history in Settings destroys the rows and the photos outright. It is the one path in the product that does, and the duplicate memory goes with them. A team with a key that reads its payments keeps, for up to 181 days, only the fact that a removed payment existed, so its connected systems can remove it too.
- If your account is deleted, the checks on your personal history are deleted with it by the nightly sweep. Checks you filed for a named business stay with the business, with your name off them.
- The rows that count free checks are deleted after 180 days.
- Invoices are kept for as long as accounting requires, whatever else is erased.
Your choices
- Read your history on the History screen, and export it to CSV on a plan that includes export.
- Erase a personal history outright in Settings.
- Correct your name and change your password in Settings.
- Write to us to close your account and remove what is left of it.
- Ask us for a copy of what we hold about you.
Cookies
- The sign-in cookie
- Set by Supabase Auth, and what keeps you signed in.
- wabi_lang
- Remembers English or Amharic.
- wabi_team
- Remembers the team you were last on.
- vfy_id
- A random id that counts free checks on this browser.
Four, and not one of them is for advertising.
How it is protected
- Every request, to us and to the banks, goes over TLS. A receipt is refused rather than sent in the clear.
- Who may read a row is decided in the database by row level security, not by the screen drawing it.
- Passwords are handled by Supabase Auth. We never see them.
- API keys are stored hashed and shown once, when you create them.
- IP addresses and browser strings are stored as hashes, never in the raw.
Children
Wabi is for businesses and the people who run them. It is not meant for anyone under 18, and we do not knowingly hold anything about a child.
Changes to this policy
If this changes, the date at the top changes with it. A change to what we hold or who sees it will be said plainly on the site, not slipped in quietly.
Contact
Write to us with any question about this policy, to ask for a copy of what we hold about you, or to have it deleted. We answer within 30 days, usually sooner.