Data Processing Agreement
Where you use Kiki to process personal data about your own customers, employees or suppliers, you are the controller and we are your processor. These are the Article 28 terms that govern that. They form part of the Terms of Service and need no separate signature.
Last updated 1 November 2026
1. Roles
You are the controller. Maritini Konstantinou, trading as Kiki, is the processor. We process personal data only on your documented instructions — which, in practice, means using the product as it is designed to be used.
Where we determine our own purposes — account administration, billing, security — we act as a controller, and the Privacy Policy governs that instead.
2. Subject matter and duration
Subject matter: providing financial reporting, transaction classification, alerting, forecasting and AI-assisted analysis from bank statements you upload.
Duration: for as long as your account exists. Processing ends when you delete your company or the agreement terminates.
Nature and purpose: storage, extraction, categorisation, computation, display and generation of written analysis.
3. Categories of data and data subjects
Data subjects: your employees and other authorised users; and any individual identifiable from the transactions on your statements — typically counterparties such as customers, suppliers, contractors and employees receiving payments.
Personal data: names and account identifiers appearing as counterparties, transaction amounts, dates and descriptions, payment references, and the email addresses and names of your users.
Bank statements routinely contain salary payments and other information that may reveal personal circumstances. Upload only what you need, and only what you are entitled to process.
4. Our obligations
- Process personal data only on your instructions, unless the law requires otherwise.
- Ensure everyone authorised to process it is bound by an appropriate duty of confidentiality.
- Apply the technical and organisational measures in clause 6, and keep them under review.
- Assist you with data subject requests, as described in clause 7.
- Assist you with data protection impact assessments and with security incidents, taking into account the information available to us.
- Delete or return the data at the end of the agreement, at your choice — see clause 9.
- Make available the information needed to demonstrate compliance with Article 28, and allow audits as described in clause 10.
5. Subprocessors
You give general authorisation for the subprocessors below. Each is bound by data protection obligations no less protective than these.
| Subprocessor | Purpose | Location |
|---|---|---|
| Supabase | Database, authentication and file storage | Frankfurt, Germany (eu-central-1) |
| Anthropic | The AI CFO — generating answers to your questions | United States |
| Cloudflare | The spam check on the contact form and the signup form (Turnstile) | Global (EU entry points) |
| Cal.com | Booking a call with us | EU |
| Stripe | Subscription payments | United States / EU |
| Vercel | Application hosting | Frankfurt, Germany (fra1) |
| Resendnot yet in use | Transactional email (confirmations, alerts) | EU |
| Sentrynot yet in use | Error reporting, so faults are noticed and fixed | EU |
We will give at least 30 days' notice before adding or replacing a subprocessor. If you reasonably object on data protection grounds, you may terminate and receive a refund of any prepaid, unused period.
6. Security measures
- Tenant isolation in the database. PostgreSQL Row Level Security on every customer table, so one company's data is unreachable from another's session even if the application requests it. This is covered by automated tests that run on every change.
- Private file storage. Statements are held in a private bucket with access policies keyed to company membership. No public URLs are issued.
- Encryption. In transit over TLS; at rest by the hosting provider.
- Least privilege. The credential that bypasses database access rules is server-side only and never reaches a browser; this is enforced at build time.
- Audit trail. Significant actions are recorded with actor and timestamp.
- Data residency. Database, authentication and files in Frankfurt, Germany (eu-central-1).
7. Data subject requests
The product answers most requests directly: Settings provides a complete export in a machine-readable format, and permanent erasure. Where a data subject contacts us instead of you, we will not respond substantively but will refer them to you and tell you promptly.
8. Personal data breaches
We will notify you without undue delay, and in any event within 48 hours of becoming aware of a breach affecting your data, with the information available at the time and updates as we learn more. Notification is not an admission of fault.
9. Deletion and return
You can export and delete your data yourself at any time. On termination, data is deleted when you delete your company; if you do not, we delete it within 90 days of the account closing. Backups age out on their own cycle and are not restored selectively.
Billing records are retained where tax law requires, and are not deleted on request.
10. Audits
We will provide the information reasonably needed to demonstrate compliance with Article 28. Where that is insufficient, you may audit no more than once a year, on 30 days' notice, at your cost, subject to confidentiality — or more often if a supervisory authority requires it or following a breach affecting your data.
11. International transfers
Data is stored in the EU. The AI CFO transfers computed figures and transaction details to the United States for processing, under the provider's Standard Contractual Clauses. Not using the AI CFO avoids the transfer entirely; the rest of the product is unaffected.
12. Contact
Questions, subprocessor objections and audit requests: get in touch through our contact form.