Privacy Policy

The short version

• Your transactions are stored on your phone. You can use all of Kesef without creating an account.
• If you create an account, a copy is also stored on our server so you can use several devices. Only your account can read it.
• We do not sell your data, and we do not hand it to anyone to advertise to you.

What data Kesef handles

Data you enter:

• Transactions: amount, currency, date, category, payment method, and any note or merchant you type.
• Your setup: categories, accounts, tags, budgets and recurring templates.
• Your in-app profile: the name you chose and your preferences (currency, language, theme).

Data that appears only if you use certain features:

• Account: if you sign in with Apple or Google we receive a user identifier and, depending on what you allow, your name and email. We never receive your password.
• Groups: a group's shared expenses, splits and settlements are visible to that group's members. That is the point of the feature.
• Voice: the audio you dictate and the NAMES of your categories, so we can work out which expense you mean.
• Notifications: an installation identifier (push token) so we can reach this phone.

Technical data:

• App usage: which screens are opened, which features are used, and errors. Never amounts, descriptions, notes or merchant names.
• Advertising: on the free plan, device advertising identifiers.

Where your data lives

On your phone, in a local database, always. That copy is the primary one: Kesef works offline and without an account.

If you sign in, a copy is synced to our server (Supabase, hosted in the United States). Access is enforced at the database level: every row is tied to your account and the server rejects any request that tries to read someone else's. The one exception is group data, which by definition its members can see.

If you never sign in, nothing is uploaded: there is no copy on any server of ours.

Who it is shared with

No one, other than the providers needed to run the app. None of them receive your data to use for their own purposes:

• Supabase — stores the synced copy of your account, if you created one.
• Groq — transcribes and interprets voice entry audio. It receives the audio and your category names. It does not receive your amounts, your history or your identity.
• PostHog — usage analytics, with no amounts or descriptions.
• Google AdMob — advertising on the free plan.
• RevenueCat, the App Store and Google Play — handle the Kesef Pro subscription. Payment is processed by the store; we never see your card details.
• Expo — delivers push notifications to your phone.

We may also disclose data where a competent authority legally requires it.

Advertising and tracking

The free plan shows ads. On iOS we ask before using the advertising identifier: if you decline, you still see ads but less personalised ones, and the app works exactly the same. Kesef Pro shows none.

This website

Everything above is about the app. getkesef.app — the page you are reading this on — is a separate thing, and it measures too: how many people arrive, from which country, how they got here (a search engine, a social network, a shared link, a campaign) and which pages they look at.

Two services do this, each with its own storage in your browser so that coming back is not counted as a new person:

• PostHog — in a project separate from the app's, so anonymous site visits never mix with how you use your finances.
• Google Analytics, through Firebase — the same project the app uses, so we can see how many people who read the page end up downloading it.

The site has no forms, no accounts and no checkout: we never ask for your name or your email, so there is nothing to attach to you. Your IP address is used to derive the country and city, and is not stored alongside the events.

What gets recorded is page views and clicks on the download buttons. No app data — not a transaction, not an amount, not a category — passes through here: the site has no access to any of it. If you use a blocker or private browsing, the page works exactly the same.

How long it is kept

Data on your phone, for as long as the app is installed. Uninstalling removes it — which is why it is worth exporting a backup first.

The server copy, for as long as your account exists. Deleting the account removes it along with everything attached to it.

Your rights

• Take your data with you: Settings → Export. JSON or CSV, free.
• Erase everything local: Settings → Reset data.
• Delete your account and the server copy: Settings → Profile → Delete account. Immediate and irreversible.
• Access, correct or object to processing: write to us and we will sort it out.
• Manage or cancel Kesef Pro: on iOS, Settings → your name → Subscriptions; on Android, Google Play → Payments and subscriptions.
• Control personalised advertising: on iOS, Settings → Privacy & Security → Tracking; on Android, Google settings → Ads.

If you are in the European Union or the United Kingdom, our legal bases are performance of the contract (making the app work), your consent (personalised advertising, notifications) and our legitimate interest (running the service and understanding how it is used).

Security

Traffic is encrypted. Your session is stored in the operating system keychain (Keychain on iOS, Keystore on Android), not in plain text. On the server, isolation between accounts is enforced in the database and not only in the app.

You can also require Face ID, Touch ID or a fingerprint to open Kesef, from Settings.

What no system can promise is absolute security. The local database on your phone is protected by the device's own encryption: keep a passcode on your phone.

Children

Kesef is not directed at children under 13 and we do not knowingly collect their data. If you believe a child has sent us data, write to us and we will delete it.

Changes

If something material changes, we update this page and the date above. Substantive changes are also announced inside the app.

Contact

Write to kesefappinfo@gmail.com. We answer.