The whole household, in a file.
A full snapshot as JSON or Excel, or your transactions as CSV.
Your data
Money is personal.
So is your trust.
A clear account of what Kahu stores, who can access it, and what happens when you import.
Where a record goes today
Three places. Nothing hidden.
Where a record goes in today’s web app. A record you type, such as Coop, groceries, −€60.02, is saved to your household’s ledger, hosted by Kahu. When you import a screenshot from your bank app, Kahu sends it to an AI reader, which sends back the transactions it read for you to check. Kahu never asks for your bank login.
Alex & Sam’s sample household
- What you type is saved. A record you add goes to your household’s ledger, hosted by Kahu, ready when you sign in.
- A screenshot is read for you. When you import, the screenshot goes to an AI reader. It sends back the transactions it read, and you decide what goes in.
- Your bank login stays with you. Kahu never asks for it. Your records come from what you type and the screenshots you pick.
Your copy, whenever you want it
Your data leaves with you.
Export everything at any time, and bring a copy back without losing work. Every row keeps a stable id, so nothing is duplicated.
See every change first.
Nothing is written until you apply it. A row missing from the file is never deleted, and newer work is never overwritten.
Bring in another person’s copy.
What is new on their side is added to yours. Where you both changed something, the newer change wins.
Excellent disguise. Terrible intentions.
Nice try, little guy.
Not on
the guest list.
The mask is cute. Access to your household records still needs more than a convincing face.
- First, a verified sign-in.
- The backend checks your authentication before serving household records.
- Your household has a boundary.
- Record access is scoped to the signed-in household, with database policies enforcing that boundary.
- No bank password in his bag.
- Kahu works with records you enter or import. It never asks for your bank login.
Our EU residency commitmentEU-only handling.
Across the whole service.
The commitment is EU-only handling across Kahu’s hosted services, including authentication and AI processing. This is a future commitment. The current setup is shown alongside.
Where things stand today
Financial database & backendFrankfurt, European Union
The hosted ledger runs in the EU.
AuthenticationLondon, United Kingdom
Sign-in currently uses a separate service in the UK.
AI image extractionAn external provider
Importing an image sends it to an extraction provider. This is a separate data path, so EU database hosting does not mean every service processes data only in the EU.
Current app, future plans
Different things. Kept apart.
Today Kahu is a web app that isn’t open to the public yet. A local-first phone app, optional sync and automatic bank imports are planned. None of them is how the current web app works.
What am I looking at on this website?
A fictional household, Alex and Sam. The stories play on their own. The loan’s extra payment is the one thing you can change, and reloading resets it.
How will automatic bank imports work?
They are planned for the paid plan and not built yet. Transactions would come through a third-party bank data provider, where you sign in with your bank. Kahu would receive the transactions, not your bank login. That provider is another data path, and it will be listed here before the feature goes live.
Does every record stay on my device?
No. The current application has a hosted backend. Statement image extraction also involves an external provider. Local-first mobile is future work.
Next: Our story
A place for the whole household picture.