Privacy, in plain words.

We collect what Kibo needs to work, we don't sell any of it, and your receipt photos never leave your phone. Here's the long version, with no asterisks.

Last updated: 2026-11-06
Contents
TL;DR

Your data stays yours. We use it to run and improve Kibo, and we never sell it.

1. Who we are

Kibo is run by Saúl Molinero Malvido, who is responsible for your data under the GDPR (the "controller").

  • Address: Calle Simón Bolívar 14, 36203 Vigo (Pontevedra), Spain
  • Email: privacy@ki-bo.com

Kibo is not required to appoint a data protection officer. For anything about your data, write to privacy@ki-bo.com. A person answers, usually within a few days.

2. What we collect

Your account

  • Your email address and password. We only store a hash of the password.
  • If you sign in with Apple or Google: your email, your name if you share it, and the account ID that Apple gives us.
  • If you sign in with Apple, a token from Apple. We keep it so we can end Kibo's access to your Apple ID when you delete your account.
  • If you use Kibo without an account: a random ID created on your phone, which keeps your guest account.
  • Your language and region (for example es_ES). We use them to pick your currency.
  • Which version of these terms and this policy you accepted, and when, and your answers about analytics and ads.

What you log

  • Expenses and income: amount, currency, title, category, date and note.
  • Categories, budgets, Spaces, subscriptions and fixed costs.
  • Bank statements you import as a CSV file. We keep the rows you import, not the file.
  • If you invite a friend, their email address, so we can send the invite and tell you when they join.

Receipts

Kibo reads receipts on your phone. The photo does not leave your device. We receive only the text read from it, use that text to create the expense, and don't keep it.

Google Wallet payments (Android)

Only if you turn it on, Kibo reads Google Wallet payment notifications on your phone to log the expense for you. It does not open any other notification. We don't store the content of notifications. We use them only to detect Google Wallet payments. Only the merchant and the amount, with its currency, leave your phone and reach our server, as an ordinary expense. We don't store or send anything else from the notification, such as the card name or its last digits. You can turn it off in Profile at any time and remove notification access in Android Settings.

Saved places (iPhone)

If you save a place, we store its name, its exact coordinates, the radius you pick and the expense to log there. The map starts at your current position, so a saved place is often where you stood when you saved it. Your phone checks when you arrive. When it logs an expense at a place, we store that expense with the place and the time. We don't receive your live location. To search places and draw the map, the app uses Apple Maps, which receives your search and the map area. You can delete a saved place at any time. Saved places are not in the Android app yet.

Notifications and purchases

  • A push token, your device model and your app version, so we can send the notifications you allow.
  • For Premium: the store's order or transaction ID, the plan and its dates. Apple or Google take the payment. We never see your card.

How the app is used

  • Firebase Analytics, by Google, records screens you open, buttons you tap and events such as "expense created". It is linked to your Kibo user ID. It uses an app instance ID and, on Android, your device's advertising ID. Google works out an approximate location (country or city) from your IP address.
  • On Android, we tell Google Ads when someone who installed Kibo from one of our ads creates an expense. That is how we measure our ads. On iPhone, Apple tells us which Apple Search Ads campaign and keyword led to your install, if any.
  • Once per account, the app sends our server where the install came from. On Android: the campaign tags in the Google Play install referrer (source, medium, campaign), an invite code if there is one, and whether the install came from a Google ad click. We store yes or no, never the click ID. On iPhone: the Apple Search Ads result above. We keep it with your account to count which channels bring people who keep using Kibo, and it is deleted with your account.
  • Firebase Crashlytics, by Google, receives crash reports with your device model, system version, language and Kibo user ID. A report can include the last things the app did, such as an expense title or a search. Our server sends its own errors to Sentry, without your email address or IP address.

In the EU, the EEA and the UK, Kibo asks before it turns on analytics and ads measurement, and you can change your answer in Profile at any time. App versions released before that question turn analytics on without asking, so update the app to choose. Crash reports stay on for everyone, because they are how we find and fix crashes.

Backups on your phone (Android)

If Google backup is on, your phone's backup includes Kibo's local settings and any expenses waiting to sync. Your sign-in details are left out.

We don't collect your contacts, your photos, recordings of your voice, your browsing history or data from other apps, except the Google Wallet payments you turn on, described above.

3. Why we use it

The GDPR asks us to name a legal basis for each use. Here they are.

  • To run your account and the app. Sync your data across devices, show your dashboards, send the reminders you turn on, and send account emails. Basis: our contract with you.
  • To suggest categories and read receipts. Google's Gemini models on Vertex AI process expense titles, receipt text, quick-add text, the first rows of an imported statement, and Space names. They suggest a category, an amount or an image, and you can change any of it. Google does this on our behalf, under the Google Cloud terms, and doesn't use it to train its models. Basis: our contract with you.
  • To find and fix crashes and keep Kibo secure. Crash reports and server error logs. Basis: our legitimate interest in a working, safe app. You can object, see section 7.
  • To learn how the app is used. Firebase Analytics. Basis: your consent in the EU, the EEA and the UK; our legitimate interest in improving Kibo elsewhere.
  • To see how Kibo is doing as a service. Totals we count from the account data we already hold, such as sign-ups, expenses logged and purchases. We look only at totals, never at one person. Basis: our legitimate interest in running and improving Kibo.
  • To measure our ads. Google Ads and Apple Search Ads. Basis: your consent in the EU, the EEA and the UK; our legitimate interest in knowing which ads work elsewhere.
  • To send the invites you ask for. Your friend gets the invite and one note is sent to you when they join. Basis: our legitimate interest in sending the invite you requested.
  • To meet the law. When the law requires us to keep data or hand it over, for example to answer a court order. Basis: legal obligation.

Account emails are only these: verifying your email, resetting your password, confirming when you save a guest account or merge two accounts, invites you send, and a note when a friend you invited joins. We don't send marketing emails.

Kibo makes no decision about you based only on automated processing that has legal or similarly serious effects. AI suggestions are suggestions.

4. Who we share with

We don't sell, rent or trade your data. These companies process it for us:

  • Google Cloud hosts the server and the database in Madrid, runs Gemini, and keeps our server logs and backups.
  • Google Firebase runs analytics, crash reports, Android push notifications and remote settings.
  • Google Ads measures installs, and expenses created, after one of our Android ads.
  • Apple handles Sign in with Apple, App Store purchases, iPhone push notifications, Apple Search Ads attribution and, for saved places, Apple Maps.
  • Google Play handles purchases and Google sign-in on Android.
  • Resend sends our emails: verification, password reset and invites.
  • Sentry receives our server's error reports and stores them in the EU (Germany).

Some of them process data outside the EU, mainly in the United States. Gemini runs on Google's global endpoint, so the texts listed in section 3 can be processed outside the EU. Firebase, Google Ads and Apple process app data in the United States too. Google, Apple and Sentry rely on the EU-US Data Privacy Framework, and on the EU Standard Contractual Clauses where the framework does not apply. Resend is certified under the framework and also uses the clauses.

5. Security

Your data travels over HTTPS. The database runs on Google Cloud, which encrypts disks at rest. Only the developer can reach the server and the database.

No system is perfect. If a breach puts your data at risk, we report it to the AEPD within 72 hours, as the law requires. If it is likely to put your rights at high risk, we also tell you directly, without delay and in plain language.

6. How long we keep it

We keep your data while you have an account. When you delete it, we delete your data from the database straight away. Copies stay in encrypted backups for up to 90 days, in server logs for up to 30 days, in billing logs (store purchase IDs) for up to 60 days and in error reports for up to 90 days. After that, they expire. A count of how many AI suggestions and notifications an account used stays linked to the old account ID, without your email or name. Apple and Google keep their own purchase records under their own policies.

7. Your rights

Wherever you live, you can:

  • Get a copy of your data. Export your expenses as a CSV file from the app. For everything else, write to us and we'll send it in a file you can reuse.
  • Correct it. Fix anything that's wrong, in the app or by writing to us.
  • Delete it. Delete your account and its data from the app (Profile, then Delete account) or from the delete account page.
  • Limit it. Ask us to pause using your data while we check something you raised.
  • Object. Object to any use based on our legitimate interest, such as crash reports. We stop unless we have strong legitimate grounds that override yours.
  • Withdraw consent. Change your analytics and ads answers in Profile at any time. This doesn't affect what happened before.

To use a right, write to privacy@ki-bo.com from your account's email. If you write from another address, we may ask you to confirm from that one, so nobody else gets your data. We answer within one month. If a request is complex, the law lets us take two more months, and we tell you why within the first month.

You can also complain to a data protection authority. In Spain, that is the AEPD (aepd.es).

8. Cookies and this website

ki-bo.com sets no cookies and runs no analytics or trackers. Its fonts and images come from our own server, so a visit sends your IP address only to us, and it stays in server logs for up to 30 days. The app doesn't use cookies either; it keeps its settings on your phone.

9. Children

Kibo is not for anyone under 14. If you believe a child has signed up, write to us and we'll remove the account.

10. Changes

If we change this policy, we'll update the date at the top. If a change affects how we use your data, we'll tell you in the app or by email before it applies. We won't quietly change the parts that matter.

Want to delete your account? You can do it from Profile inside the app, or from our deletion page.

Back to top