Privacy notice

This covers the hosted service at homeaccounting.com. If you self-host, none of it applies to you — we never receive your data, and there is nothing here for us to describe.

Last updated 24 September 2026.

The short version

We hold what you type in and what your bank returns. It lives on one server in Germany. We do not sell it, we do not advertise, and we set no analytics cookies. Two things are worth reading in full below: what the free-text prompt sends to a model provider, and the fact that getting your data out or deleting it is still a manual request by email rather than a button.

Who is responsible

The hosted service is currently run by the maintainer of HomeAccounting as an individual — there is no company behind it yet. That is a real answer, not a placeholder: until an entity exists, the person operating the server is the data controller. Write to legal@homeaccounting.com for anything on this page. When an entity is formed, this notice will name it and we will say so on the page.

What we hold

Your account: Your email address and a hash of your password (Argon2id — we never store the password itself). If you sign in with Google, the account identifier Google returns. If you link Telegram, your Telegram user id and username.
What you record: Accounts, balances, transactions, amounts, dates, categories, labels, counterparties and any comments you write. This is the financial picture of your household, and it is the most sensitive thing here.
Bank connections: Only if you set one up. The access token you give us is encrypted at rest (AES-256-GCM) and is never stored in plaintext. We also store the transactions the bank returns, which is the point of connecting it.
Operational logs: Request logs and metrics, so we can tell whether the service is working. They carry your account identifier — that is deliberate, it is how a report of “my import failed” gets diagnosed — and they are kept on the same server, not shipped to a logging vendor.
Website analytics: Page views on this marketing site, via GoatCounter. No cookies, no cross-site identifier, and paths are scrubbed in your browser before they are sent, so identifiers in a URL never leave your machine.

Where it lives

On a single server rented from Hetzner Online GmbH in Nuremberg, Germany. Backups stay in the same place. Nothing is replicated outside the EU except where a processor below is named.

Who else sees it

This is the whole list. Everything on it is either the hosting itself or something you switch on by using a feature.

Hetzner Online GmbH

Nuremberg, Germany

Rents us the server everything runs on, and holds the backups. They do not access the data; they host the disk it sits on.

When: Always — this is the hosting.

Groq, Inc.

United States

Runs the language model behind free-text entry. It receives the sentence you typed and the names of your own accounts, categories and labels, so it can map "coffee, 80 hryvnia, mono" onto the ones you actually use. It does not receive your transaction history, your balances, your email or anything about your bank connection.

When: Only when you use the free-text prompt or send a message to the Telegram bot. Never for typed-in or bank-imported transactions.

monobank / PrivatBank

Ukraine

Your bank, returning your own transactions to us over its API with the token you issued.

When: Only if you connect that bank yourself.

operated by Telegram FZ-LLC

Carries the messages between you and our bot — so anything you send it passes through Telegram, as any Telegram message does.

When: Only if you link Telegram.

Google

United States

Confirms who you are when you choose "sign in with Google", and tells us the account identifier and email for that.

When: Only if you sign in with Google.

GoatCounter

European Union

Counts page views on this marketing site. No cookies, no cross-site identifier, and paths are scrubbed of identifiers in your browser before anything is sent.

When: On this marketing site only — not inside the app.

What we do not do

We do not sell or rent your data, in any form, to anyone.
We do not advertise, profile you for advertising, or embed ad SDKs.
We set no cookies for analytics or tracking. The app keeps your session token in your browser’s local storage because it has to; that is not a tracker and it never leaves your device except as an authorisation header to our own API.
We do not read your transactions to build anything. The only automated system that sees their text is the model provider named above, and only for the prompt you typed.

Getting your data, and leaving

You can ask for a copy of everything we hold about you, ask us to correct it, or ask us to delete your account and its contents.

Be aware of how this works today: there is no export button and no delete-account button in the app yet. Both are a manual job for the operator, done from an email to legal@homeaccounting.com. We answer within 30 days. We would rather tell you that than imply a self-service flow you will go looking for and not find — the buttons are being built, and this paragraph changes when they land.

If you are in the EU or the UK you also have the right to complain to your data-protection authority. The other route out is the one that needs no permission from us at all: the whole system is open source, and you can run it yourself.

How long we keep it

For as long as you have an account, because it is the account. When you ask us to delete it, we delete it — including the underlying event log, which is where the data actually lives. Server backups roll over within 30 days, so a deleted account can survive in a backup until then.

Security

Passwords are hashed with Argon2id and bank tokens are encrypted at rest. Traffic is HTTPS-only. The code is public, so you do not have to take any of this on trust — and if you find a hole, report it.

Changes

This page is versioned in the public site repository, so every edit to it has a diff and a date. If a change affects what we collect or who receives it, we will say so rather than quietly updating the date.

See also the terms of service. Neither document has been reviewed by a lawyer; they describe what the system does, in plain language, and will be replaced with reviewed versions when the project has a legal entity.