Security
You are being asked to upload your bank statements. That deserves specifics rather than a page of reassuring adjectives, so each claim below says what actually enforces it.
Your data is isolated in the database itself, not by application code
Every customer table has PostgreSQL Row Level Security. A query for another company's data returns nothing even if the application asks for it. This is tested automatically on every change.
Statements are stored privately and served only to your own company
Uploads go to a private bucket whose access policies check company membership on the file path. There are no public URLs.
Your data stays in the EU
Database, authentication and files are hosted in Frankfurt, Germany (eu-central-1). The exception is the AI CFO — see the subprocessor list.
The AI never does the arithmetic
Every figure is computed in code from your transactions and handed to the model as a fact. The model explains and compares; it does not calculate. This is why the numbers can be checked.
Your data is not used to train AI models
Content sent to our AI provider through its commercial API is not used to train its models. We do not sell data or share it for advertising.
You can take your data out, or have it erased, at any time
Settings offers a full JSON export and permanent deletion. Deletion removes the files, the transactions and the account — there is no hidden copy kept.
Where your data lives
Database, login and uploaded statements are hosted in Frankfurt, Germany (eu-central-1). The services that touch your data at all are these — the full detail, including exactly what each receives, is in the Privacy Policy.
- SupabaseDatabase, authentication and file storageFrankfurt, Germany (eu-central-1)
- AnthropicThe AI CFO — generating answers to your questionsUnited States
- CloudflareThe spam check on the contact form and the signup form (Turnstile)Global (EU entry points)
- Cal.comBooking a call with usEU
- StripeSubscription paymentsUnited States / EU
- VercelApplication hostingFrankfurt, Germany (fra1)
What we do not claim
Kiki is not SOC 2 or ISO 27001 certified, and has not been penetration tested by a third party. Saying so is more useful than implying otherwise: if your procurement process requires either, we are not yet the right supplier, and you should ask again later rather than take a vague answer now.
Reporting a vulnerability
Tell us through our contact form rather than disclosing publicly. We will acknowledge within three working days, keep you updated, and credit you if you would like that. We will not pursue anyone who reports in good faith and does not access other people's data.