Privacy policy
Last updated: 17 October 2026
Draft
Draft — must be reviewed and completed by the operator before launch.
1. Who is responsible
The controller responsible for processing your personal data is:
[Operator name]
[Street and number]
[Postcode and city]
[Country]
Email: [privacy contact email]
[If required under Art. 27 GDPR: name and address of the representative in the EU.]
This policy covers the website and the INMB app at budget.netcope.ch.
2. Legal framework
We process personal data in accordance with the Swiss Federal Act on Data Protection (FADP, revDSG) and, where it applies to you, the EU General Data Protection Regulation (GDPR).
3. Data we process
Account data: email address, name (optional), password (stored only as a scrypt hash), settings and preferences.
Security data: passkey public keys, two-step verification secrets (encrypted) and recovery codes, signed-in sessions with IP address, browser/user agent and timestamps, failed sign-in attempts and an audit log of administrative actions.
Budget data: everything you enter or import — plans, accounts, balances, categories, targets, transactions, payees, memos and notes, imported statement files and their results. Budget data can reveal a lot about your finances and habits; we treat all of it as confidential.
Billing data: subscription status and period, trial end date and any complimentary access an administrator grants (end date, reason, granting administrator), invoices, your Stripe customer ID and the type and last four digits of your card. Full card details are processed only by Stripe.
Integration data: API tokens and OAuth applications you create (secrets stored hashed or encrypted), and — if you enable the Telegram import — your bot token (encrypted), the IDs of the chats you link and your account mappings.
YNAB migration: when you migrate from YNAB, we use the token you provide to read your data from YNAB’s API on your instruction. The token is used for this import only and is not stored; the imported data becomes budget data.
Server logs: IP address, time, requested address, status and browser/user agent, for security and troubleshooting.
4. Why we process it
To provide INMB under our contract with you: your account, your budget, imports, exports and the API (GDPR Art. 6(1)(b)).
To keep INMB secure and prevent abuse: sign-in protection, rate limits, logs and audit trails (our legitimate interest, Art. 6(1)(f)).
To handle subscriptions, payments and accounting obligations (contract and legal obligation, Art. 6(1)(b) and (c)).
To answer your questions and inform you about important changes to the service (contract and legitimate interest).
We don’t use your data for advertising or profiling, and we don’t sell or rent it to anyone.
5. Processors and other recipients
Amazon Web Services (AWS) — hosting. Your data is stored on servers in the AWS Frankfurt region (Germany). [Contracting entity, e.g. Amazon Web Services EMEA SARL, Luxembourg — operator to confirm.]
Stripe — payment processing and invoicing for subscriptions. [Contracting entity, e.g. Stripe Payments Europe, Ltd., Ireland — operator to confirm.]
Telegram — only if you enable the Telegram import. The statements and messages you send to your bot pass through Telegram, which processes them under its own privacy policy.
YNAB — only if you migrate. We retrieve your data from YNAB on your instruction; YNAB processes it under its own privacy policy.
[Further providers, e.g. domain, DNS, email or backup providers — operator to complete.]
We disclose data to authorities only where we are legally required to do so.
6. International transfers
Your data is stored in the European Union (Germany), which Switzerland recognises as providing adequate data protection. Some providers, such as AWS and Stripe, are part of groups based in the United States and may access or transfer data there. Where this happens, we rely on the Swiss-US and EU-US Data Privacy Framework where the provider is certified, or on the standard contractual clauses approved by the EU Commission and recognised by the Swiss FDPIC. [Operator to verify for each provider.]
Data you send through Telegram is transferred under Telegram’s terms, outside our control.
7. How long we keep data
Account and budget data: as long as your account exists. When you delete your account in Settings, we delete it together with all plans you own. [Backups are overwritten within X days — operator to define.]
Accounts without an active trial or subscription: [retention period and deletion process — operator to define].
Billing records: as long as Swiss law requires (generally 10 years for accounting records).
Signed-in sessions: deleted after 30 days without use. Server and security logs: [X days — operator to define].
9. Security
We protect your data with appropriate technical and organisational measures: HTTPS for every connection, password hashing with scrypt, encrypted storage of secrets, optional passkeys and two-step verification, rate limits and restricted administrative access. The admin console shows your email address, sign-in details (signed-in devices with IP address, passkeys, API tokens and connected apps), plan names and how many accounts and transactions they hold, and your subscription and billing status — never balances, transactions, payees or categories. No system is perfectly secure; if a breach affects your data, we will inform you and the authorities as required by law.
10. Your rights
You have the right to access your personal data, to have it corrected or deleted, to restrict or object to its processing, and to receive it in a portable format. You can export your plans as JSON or CSV and delete your account at any time in the app. Where processing is based on consent, you can withdraw it at any time.
To exercise your rights, write to [privacy contact email]. You also have the right to complain to a supervisory authority — in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU the authority in your country of residence.
11. Automated decisions
We don’t make decisions based solely on automated processing that have legal or similarly significant effects on you.
12. Changes to this policy
We may update this policy when the service or the law changes. We will announce material changes in the app before they take effect. The current version is always available on this page.