← Back to Keppet

Keppet Privacy Policy

Effective 18 November 2026 · applies to the Keppet app (web, Android and iOS) and keppet.app

Who we are

Keppet is run by Cyguee Limited, company number 17139686, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ. Cyguee Limited decides how and why your personal data is used, which makes it the controller under UK data protection law. You can contact us at [email protected].

The short version: your financial ledger lives in your own git repository, Google Drive, or OneDrive, on your own account. Keppet's servers never store it. Keppet keeps a hashed sign-in record, your Keppet AI usage and subscription status, any receipt images you upload, and any bug report you send. The full list is under "What Keppet's servers keep". When you use Keppet AI (free reads, then a subscription), your receipt image or typed text is processed by a major cloud AI provider to extract the transaction. Under our paid-tier terms it is not used to train models. Keppet's servers do not store the typed text. Every receipt you snap, attach or share is uploaded to Keppet's servers. It stays there while a transaction uses it, and is deleted after the transaction is deleted, as described under "How long we keep it".

Your financial data

Keppet stores your accounts, transactions, budgets and recurring rules as plain-text files in a private git repository (keppet-data) on your own GitHub, GitLab, Codeberg, or self-hosted account. Your device syncs with your git provider using your own sign-in. For GitHub the device talks to GitHub directly. For GitLab, Codeberg and self-hosted servers the requests pass through a relay on Keppet's servers that forwards them and stores nothing. Keppet does not keep a copy of your ledger. You can leave at any time. The files are plain JSON that you can read without Keppet.

If you instead choose to store your data in Google Drive or Microsoft OneDrive, the same plain-JSON files are written to a private folder named keppet-data in your own Google Drive or OneDrive account. Your device syncs directly with Google Drive or OneDrive using your own sign-in. Keppet holds no copy of your ledger on these backends either. Sign-in is Google or Microsoft OAuth (see "Sign-in" below). Your device also keeps a working copy of your ledger in your browser or app storage.

What Keppet's servers keep

There are no third-party analytics, no advertising SDKs, and no tracking of your financial activity.

Keppet AI

When you use Keppet AI (snapping a receipt or typing a purchase), your receipt image or text is sent over an encrypted connection to Keppet's server, which forwards it to a major cloud AI provider that processes it on Keppet's behalf. Under our paid-tier terms, this content is not used to train models. Keppet's servers process it in memory to return the transaction and do not store the text. The receipt image is stored separately, as described under "What Keppet's servers keep". The provider keeps it only in abuse-detection logs for up to 30 days, then deletes it. The provider's temporary cache is switched off. The resulting transaction is written to your ledger by your device with your credentials, never by our servers. Every account is limited to 50 AI requests a day.

Voice input is turned into text by your device's or browser's own speech service, such as Apple's or Google's, which may process the audio on its servers. Keppet's servers do not receive the audio.

Android permissions for reminders

The Android app can remind you the day before a bill is due. It uses two standard Android permissions that the system grants when you install the app. Receive boot completed lets Keppet schedule your reminders again after the phone restarts. Wake lock is requested by the reminder component. Keppet uses neither for anything else. Neither permission gives Keppet access to your ledger, and neither sends anything off your device.

Sign-in

You sign in with your git host, Google or Microsoft account using OAuth. Your sign-in token is stored on your device. When you sign in, your provider sends a one-time code to Keppet's server, which exchanges it for your token using Keppet's app credentials, reads your account name or ID from the provider, and passes the token to your browser or app. Keppet does not store the token. When you use a feature that needs to know who you are (receipt storage, Keppet AI, subscriptions), your device sends the token to Keppet, which checks it with your provider and remembers the result in memory for up to five minutes. Keppet does not store the token. Keppet holds no passwords and no server-side sessions.

What each sign-in token can reach, and what Keppet does with it, depends on the provider.

Google Drive. Keppet asks Google for the openid and drive.file scopes. The drive.file scope lets the token open and change only the files and folders that Keppet created in your Google Drive, which is the keppet-data folder and what is inside it. It cannot open your other files. Keppet does not ask for your email address and reads only your Google account ID. Keppet also asks for offline access, so Google issues a refresh token as well as an access token. Your device stores both and calls Google directly to read and write your ledger. Keppet's server handles the tokens when you sign in, when your device asks it to refresh the access token, and when you use receipt storage, Keppet AI or a subscription, where it checks the token with Google. Keppet does not store them.

Microsoft OneDrive. Keppet asks Microsoft for the openid, offline_access, User.Read and Files.ReadWrite scopes. The Files.ReadWrite scope covers all files in your OneDrive, and Microsoft's consent screen describes it that way. Keppet's code reads and writes only the keppet-data folder in the top level of your OneDrive, and creates that folder if it is missing. Keppet does not ask for your email address and reads your Microsoft account ID and display name, or your sign-in name if you have no display name. Microsoft also issues a refresh token. Your device stores both tokens and calls Microsoft directly to read and write your ledger. Keppet's server handles the tokens when you sign in, when your device asks it to refresh the access token, and when you use receipt storage, Keppet AI or a subscription, where it checks the token with Microsoft. Keppet does not store them.

GitHub. Keppet is a GitHub OAuth App and asks for the repo scope. That scope gives the token read and write access to every repository your account can reach, public and private. Keppet's code uses it for one private repository named keppet-data, which it creates if it is missing, and to read your username. GitHub does not issue a refresh token for this sign-in and the token has no expiry, so it works until you revoke Keppet in your GitHub settings. Signing out removes it from your device. Your device calls GitHub directly. Keppet's server handles the token when you sign in and when you use receipt storage, Keppet AI or a subscription, where it checks the token with GitHub. Keppet does not store it.

GitLab (gitlab.com). Keppet asks GitLab for the api scope. That scope gives the token full read and write access to the GitLab API as you, including every project and group you can reach. Keppet's code uses it for one private project named keppet-data, which it creates if it is missing, and to read your username. GitLab also issues a refresh token. Your device stores both tokens. Sync requests go through the relay on Keppet's servers, which forwards each request and the ledger files in it to GitLab and stores nothing. Refreshing the token also passes through Keppet's server. Keppet does not store the tokens.

Codeberg. Keppet asks Codeberg for the write:repository and read:user scopes. Those scopes let the token read and write your repositories and read your profile. Keppet's code uses them for one private repository named keppet-data, which it creates if it is missing, and to read your username. Your device stores the token and any refresh token Codeberg issues. Sync requests and token refreshes go through the relay on Keppet's servers, which forwards them to Codeberg and stores nothing.

Self-hosted Gitea, Forgejo and GitLab. You give Keppet the address of your server, which must use https. For Gitea and Forgejo Keppet asks for the same scopes as for Codeberg, and for GitLab it asks for the api scope, with the same reach on your server as described above. You register the OAuth application on your server and enter its client ID. Keppet uses one private repository or project named keppet-data. Your device stores the token. Sign-in and every sync request go through the relay on Keppet's servers, which forwards them to your server and stores nothing. Keppet cannot refresh these tokens, so when one expires you sign in again. The operator of your server can see everything that reaches it.

Access token sign-in. You can instead paste a personal access token for GitHub, GitLab, Codeberg, Gitea, Forgejo or a self-hosted GitLab. Keppet does not choose the scopes of that token, so it can reach whatever you allowed when you created it. Keppet needs permission to create a private repository and to read and write its contents. Keppet checks the token once by asking the provider for your username, then stores it on your device in the same place as a sign-in token. There is no refresh token, and the token works until it expires or you revoke it at the provider. The token goes to the provider directly for GitHub and through the relay for the others, and Keppet's server handles it in the same ways as described above. Google Drive and OneDrive do not support this option.

All tokens are kept in your browser or app storage and are removed from your device when you sign out. Your browser or app also stores your session and a working copy of your ledger. During sign-in a temporary cookie holds the sign-in state for up to ten minutes. Keppet's code does not write any token to a database or a log.

Payments

On keppet.app the Keppet AI subscription is sold through Onelink, a Stripe company, which acts as merchant of record. Buying creates a Onelink account, and Onelink holds the order data. Keppet does not see or store your card details. Keppet sends Stripe your hashed ID as a reference so the payment can be matched to your account. In the Android app the subscription is sold as an in-app purchase through Google Play, and in the iOS app through the App Store. The store processes the payment. Keppet does not see or store your card details, and receives the purchase token (Google) or original transaction ID (Apple), the product, status and dates from the store.

Who receives your data

Keppet uses these providers to run the service: Cloudflare (hosting, database, file storage and Email Routing, which forwards the email you send to our addresses and stores none of it), the AI provider described above, Onelink, a Stripe company, and Stripe (web payments), Google (Play billing, including the billing library's own diagnostics), Apple (App Store billing), Resend (email) and GitHub (the private tracker for bug reports). The sync provider you choose (GitHub, GitLab, Codeberg, Google or Microsoft) holds your ledger under its own privacy policy.

How long we keep it

Sign-in, usage, subscription and gift code records stay until you ask us to delete them. Nothing deletes them automatically. Daily request counts are deleted after about a week. Bug reports and screenshots stay until you ask us to delete them. Receipt images stay while a transaction uses them. After you delete a transaction, its image is deleted about 90 days later, once a signed-in device next syncs, unless another record still uses it. It then sits in a server trash for 30 more days before it is erased, so it is fully erased within about 120 days of the delete. A receipt you dismiss while it is waiting also moves to the 30 day trash. Start-now request records are kept as described under "What Keppet's servers keep". Email you send us is forwarded by Cloudflare, which stores none of it, and we delete it 12 months after it arrives.

Deleting your data

Your rights

Under UK data protection law you can ask us for a copy of your personal data, ask us to correct it, ask us to delete it, ask us to restrict or stop using it, and ask for it in a portable format. Where we rely on your consent you can withdraw it at any time. To use any of these rights, email [email protected]. We will reply within one month. Keppet's records are keyed to a hashed ID, so we will ask you to confirm that you control the account before we act on a request. You can complain to the Information Commissioner's Office at ico.org.uk.

Changes and contact

If this policy changes materially we will note it here with a new effective date. Questions: [email protected]. Cyguee Limited, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ.