1. Who is responsible for your data
The controller of personal data of Beezz users and of this website is AKN Software Kasper Janowski, ul. Maczka 8, 94-328 Łódź, tax ID 7272900394 (“we”, “us”), a sole trader registered in Poland.
For anything concerning personal data write to privacy@beezz.app. For everything else — kontakt@beezz.app. We have not appointed a data protection officer; the owner of the business reads the mail directly.
2. The ground rules
- We do not connect to your bank. You enter expenses by hand, so we have no access to your account or your bank transaction history.
- We show no ads and ship no advertising SDK in the app.
- We do not track you across apps or websites. We use no advertising identifiers (IDFA, GAID) and never ask for tracking permission.
- We do not sell data and never hand it to data brokers.
- Budget data is visible only to the people invited to your household. That is enforced by database-level access rules, not just by app code.
3. What we collect and why
| Data | Where it comes from | Why | Legal basis |
|---|---|---|---|
| Email address and password | You provide it when signing up | Creating the account, signing in, password reset | Art. 6(1)(b) GDPR — performance of a contract |
| Display name, app language | You set it in your profile | Identifying you inside the household, interface language | Art. 6(1)(b) GDPR |
| Household members' first names and colours | You enter them | Splitting expenses between people in the household | Art. 6(1)(b) and 6(1)(f) GDPR |
| Expenses and income: amount, currency, category, date, merchant, note | You enter them | The core function of the app — running a budget | Art. 6(1)(b) GDPR |
| Budgets, limits, categories, recurring entries | You set them | Working out what is left this month | Art. 6(1)(b) GDPR |
| Household invite codes | Generated by the app | Letting a household member join a shared budget | Art. 6(1)(b) GDPR |
| Plan (BEE / BEEZZ), store purchase identifier, subscription validity dates | From Apple or Google after a purchase | Unlocking paid features, handling renewals and refunds | Art. 6(1)(b) and 6(1)(c) GDPR |
| In-app events: event name, app version, platform, date, and the days the app was opened | Recorded automatically | Usage statistics and product development — which features work and which do not | Art. 6(1)(f) GDPR — our legitimate interest |
| Bug reports: description, area of the app, reporter's name, app version, platform | You send them from the app | Handling the report and fixing the bug | Art. 6(1)(b) and 6(1)(f) GDPR |
| Crash and performance data: stack trace, device model, OS and app version, start-up time | Recorded automatically | Detecting and fixing crashes, app stability | Art. 6(1)(f) GDPR |
| The sentence you turn into an entry, together with the parsed result | You type it | Turning a sentence into an amount, a category and a date | Art. 6(1)(b) GDPR |
We do not know your password and cannot read it — the server stores only an irreversible hash of it.
An email address and a password are required to use the app. Everything else is optional, but without it the app has nothing to add up.
4. What we do not collect
- Location. The app never asks for location access and stores no coordinates. A merchant name you type is plain text, not a place on a map.
- Your address book. Household invites work on a code precisely so that we never touch your contacts.
- Photos, videos or files from your device.
- Audio recordings. If you dictate an entry, speech recognition happens on the device — only the finished text reaches the server, never the recording.
- Payment card details. Payment is handled entirely by Apple or Google; your card number never passes through our app or our servers.
- Advertising identifiers or advertising data.
- Special categories of data — health, ethnicity, beliefs, sexual orientation or biometrics. We never ask for them and there is nowhere in the app to put them.
5. Other household members' data
When you add a household member's name and assign expenses to them, you are processing another person's data. Enter only what is genuinely needed — a first name is plenty — and let that person know their spending is being recorded in the app.
6. Children
Beezz is not directed at children. An account is created by an adult, and that adult is responsible for the data in their household.
A child in Beezz is only a name on the household list that an expense can be assigned to — there is no account, no login and no app access behind it. We do not knowingly collect data from anyone under 16. If you believe a child created an account on their own, write to privacy@beezz.app and we will delete it.
7. Who processes data for us
We share data with nobody beyond the providers the service cannot run without. Each of them processes data only on our instructions and under a data processing agreement.
| Recipient | What they receive | Where they process it | Why |
|---|---|---|---|
| Supabase Inc. (on Amazon Web Services infrastructure) | The account and all budget data | European Union (Paris) | Database, authentication, hosting of server functions |
| Functional Software, Inc. (Sentry) | Crash and performance data. We do not send your email address or the content of your expenses | European Union and United States | Detecting and fixing app errors |
| Anthropic PBC | The sentence you turn into an entry | United States | Recognising the amount, category and date in that sentence |
| Apple Inc. / Google Ireland Ltd. | The fact and status of a subscription purchase | Per Apple's and Google's own policies | Handling payments, renewals and refunds |
Data sent to Anthropic is not used to train models — that follows directly from the terms of their developer API.
Transfers outside the European Economic Area (Sentry, Anthropic) rely on the Standard Contractual Clauses approved by the European Commission.
We may also disclose data to competent authorities where the law obliges us to.
8. How long we keep data
- Account, budget and the whole spending history — until you delete the account.
- Database backups — up to 30 days after deletion, after which the data is gone from those too.
- Crash and performance data — 90 days.
- In-app events and active days — up to 24 months.
- Sentences turned into entries — until the account is deleted; you can remove them earlier by deleting the entry they created.
- Bug reports — up to 24 months after the report is closed.
- Subscription purchase records — 5 years from the end of the year in which the tax payment fell due, as Polish tax law requires.
9. Security
- All traffic between the app and the server runs over encrypted HTTPS/TLS.
- Access is restricted at the database level: every query can only see rows belonging to a household you are a member of.
- Passwords are stored as an irreversible hash.
- Access to the administration panel is protected by two-factor authentication.
- You can additionally lock the app with a PIN or biometrics — that stays on your device and never reaches us.
10. Your rights
Under the GDPR you have the right to:
- access your data and receive a copy of it,
- have inaccurate or incomplete data corrected,
- have your data erased (“the right to be forgotten”),
- restrict processing,
- port your data to another service in a commonly used format,
- object to processing based on our legitimate interest — chiefly the usage statistics,
- withdraw consent at any time where processing was based on consent.
You delete the account yourself in the app — see Deleting your account.
Send any other request to privacy@beezz.app. We reply within 30 days at the latest. To protect your data, we may ask you to write from the address the account is registered to.
If you believe we process data unlawfully, you can lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stawki 2, 00-193 Warsaw, Poland.
11. Changes to this policy
We may change this policy — when a feature is added, for instance, or a provider changes. We will announce material changes in the app or by email at least 14 days before they take effect. The date of the last update is always at the top of this page.