The questions everyone asks first.

Klikli is a personal budget tracker, a small app that lets you log expenses in seconds, set monthly limits per category, and see how much you have left this month. It runs in your browser as a Progressive Web App (PWA), so it installs on iOS, Android, and desktop with no app-store download.

No. Open klikli.app/app in your browser and you're in. To "install" it (so it gets an icon on your home screen and opens like a normal app), use your browser's Add to Home Screen or Install option.

About three minutes. You pick a currency, choose categories, set a monthly budget per category, optionally add recurring income. Done.

CZK, EUR, USD, GBP, PLN, HUF, and CHF at launch. Daily exchange rates come from the European Central Bank (via Frankfurter, an open-source proxy).

No. Klikli ships zero analytics, telemetry, or third-party SDKs in the client. We don't know how often you open the app, what you spend on, or even that you exist, unless you opt into cloud sync.

The full list of network calls the app makes is on the Privacy page.

In local mode (the default), in your browser's IndexedDB on your device. Nothing leaves it.

In cloud mode, in Google Firestore, region europe-west3 (Frankfurt, Germany), under a per-user path. Firestore enforces a per-user isolation rule via security rules: nobody but you can read or write your records.

No. We don't sell, rent, share, or otherwise pass your data to third parties for advertising, profiling, or analytics. Ever. The Terms commit us to that contractually.

In transit: yes, TLS 1.2+ between your device and Firestore.

At rest in Firestore: yes, with Google's standard storage-level encryption. Today we don't add a client-side encryption layer in cloud mode, which means Google can technically read the records. We're transparent about this trade-off on the Privacy page. End-to-end-encrypted sync is something we may add later, opt-in.

The local passcode you set is hashed with Argon2id (memory-hard) and gates the UI. It is not used as an encryption key.

Yes. Settings → Account → Export downloads your full record history as JSON. No vendor lock-in.

No. By design. Bank-connection APIs (Plaid, GoCardless, etc.) require sending your transactions through a third party, exactly the kind of data flow Klikli exists to avoid. You log expenses manually, and the app makes that take five seconds.

Yes. Each transaction can be entered in any supported currency; the app converts it to your home currency for budget totals using the daily ECB rate.

One budget per month, with budgets set per category. We don't have separate "envelopes" or sub-budgets, one of the fewer-choices design decisions. If you've outgrown that, tell us at feedback@klikli.app.

You add a recurring income source (salary, rent, side gig) with a day-of-month. It auto-logs on that day. Same for recurring expenses.

Yes, minimal ones. Spend per category, month-over-month comparison, and a budget-burn meter. We deliberately don't ship dozens of charts. The blog goes into why.

When cloud sync is on, your records are written to Firestore. Open Klikli on any device, sign in with the same account, and your history is there.

The local IndexedDB cache stays in place as a performance and offline layer.

Yes. Klikli is a Progressive Web App, install it on iOS, Android, or desktop and it works fully offline. Changes you make offline sync the next time you have a connection (cloud mode), or just stay local (local mode).

Yes, a native iOS app is on the roadmap as a separate workspace in this repository. Today the PWA installs on iOS via Safari → Share → Add to Home Screen and behaves like a native app.

Same answer, install the PWA from Chrome (or any Chromium-based browser) and it gets a launcher icon, splash screen, and offline support out of the box.

Not in local mode. You only create an account if you turn on cloud sync. The account is a Firebase user, sign in with email or Google.

Settings → Account → Sign out. This terminates the Firebase session and wipes the local cache. Your records remain in Firestore until you delete the account.

Settings → Account → Delete account. Type your name to confirm. This deletes the Firebase user and every Firestore document under your tree, irreversibly. If you've enabled cloud mode, it also clears the local cache.

In local mode you delete the data by clearing the site's storage in your browser.

In cloud mode, you can re-authenticate with your email/Google to reset the passcode. In local mode there is no recovery: the passcode gates the local UI and doesn't leave your device. Choose one you'll remember.

Yes. Local mode is free forever, there is no business case for charging for it (no servers to pay for). Cloud sync is free during the current alpha. If we ever introduce a paid tier we'll be transparent about what's free vs paid, with at least 30 days' notice and an export path.

The honest answer: most likely a small paid tier for cloud sync (cents per month) once it's out of alpha. Local mode will stay free. We will never monetise via ads or selling data, it would defeat the entire premise.

Klikli is built by Andrej Prazenica, an independent developer based in Czechia. Today it is a one-person operation.

The client code that runs on your device is published in a public repository. See the LICENSE file in the repo for the exact terms. The reasoning: privacy claims are easier to trust when you can read the code.

Local mode is unaffected, the app lives on your device and the source is public. For cloud mode, we commit (in Terms §8) to giving at least 30 days' notice and an export path before shutting down sync.

Email security@klikli.app. Please give us 90 days before public disclosure. We don't run a paid bounty, but we credit responsible reporters.