Privacy Policy
In short
- Our servers hold your budget in the clear. That is what lets them do the arithmetic for you. Nobody on our team accesses it: no admin screen returns its contents.
- We also hold your email address — in the clear, so we can write to you, and as a hash so we can find your account at sign-in — plus an account identifier.
- The disks holding the database and the backups are encrypted at rest. That is not end-to-end encryption, and we do not call it that.
- No advertising, no resale, no tracking, no analytics cookies. That is why this site shows no cookie banner.
- Everything is hosted in the European Union.
- You can export everything from the app, at any time, for free.
- What you delete is erased after 30 days: its contents disappear from our servers, then from each of your devices as soon as you open Arca on it again (for a deletion made offline, once it has reached our servers). Until then, a deleted transaction waits in the trash, where you can recover it or erase it right away.
- The beta is free: no payment details are collected at all.
- A forgotten password does not destroy your budget: resetting it gives you back the account and the data.
1. Who is responsible for your data
The data controller is the Arca team (T.B.), trading as Arca Budget — Entrepreneur individuel (EI), SIREN 931302947, France. Contact for any privacy matter: privacy@arcabudget.app.
No Data Protection Officer has been appointed. None is required under Article 37 GDPR: we are a sole trader, we carry out no large-scale monitoring, and we do not try to infer any special category of data from your budget (section 3). Requests are handled directly by the controller at the address above.
2. What our servers hold, and what we see of it
Your budget — accounts, transactions, categories, amounts, notes — is stored in the clear on our servers. That is what lets them work out your balances, what is available and your month ahead once and for all, instead of redoing that work in every browser.
Until 25 August 2026 this was not the case: your budget was encrypted on your device and we only ever received unreadable blocks. We gave that up, and we write it here rather than let the word “encrypted” keep a false idea alive. The technical detail, and what it no longer protects against, are on the security page.
What we process is therefore, plainly, personal data:
- the contents of your budget;
- your email address — in the clear so we can write to you, and as a hash so we can find your account — and an opaque identifier if you sign in with Google;
- technical metadata for routing and ordering: identifier, vault identifier, record type, last-modified timestamp, deletion marker — when you delete an item, its contents are erased after 30 days (section 3) and only a technical trace of it remains;
- connection and security records (see the table in section 3).
What we undertake not to do. Nobody on our team accesses the contents of a budget: the admin console only ever returns metadata — a record count, dates, a subscription state — and no endpoint exposes a transaction. Admin actions are logged. If support ever needed access to help you, it would be with your explicit consent, and it would leave a trace. We do not sell or hand over your data, and we draw no advertising from it.
3. What we process, why, on what legal basis, and for how long
| Data | Purpose | Legal basis (Art. 6 GDPR) | Retention |
|---|---|---|---|
| Email address (and its hash), password hash, Google identifier | Creating your account, signing you in | Performance of a contract — 6(1)(b) | Until you delete your account, or 24 months of inactivity, after a warning email |
| Performance measurements: screen name, durations, app version, order of magnitude of vault size, device type, app health (crash, storage, memory) | Finding and fixing slow screens in the app | Consent — 6(1)(a). Off by default, revocable at any time | 90 days |
| The contents of your budget and its routing metadata | Storing, syncing, computing and analysing for you your budget (section 3a) — this is the service | Performance of a contract — 6(1)(b) | Until you delete your account. What you delete in the app follows the next line. Purged within 30 days of account deletion |
| The contents (amounts, names, notes…) of what you delete in the app | Letting you go back on a deletion for 30 days: with ⌘Z, and for a transaction from the trash, on all your devices | Performance of a contract — 6(1)(b) | 30 days from the deletion; a transaction erased from the trash is erased right away. The contents are then erased from our servers, then from your devices as soon as you open Arca on them again (for a deletion made offline, once it has reached our servers), and from the backups within 30 days. Only a technical trace remains, with no amount, no name and no note — identifiers, the “deleted” mark and a few markers such as the date — kept with your budget so that your devices stay in agreement |
| Suggestions learned from your entries (category, payee, payee order), and a monthly count of what you do with them (kept, replaced, declined) | Suggesting the category and the payee based on your history, and measuring what you do with them (section 3a) | Legitimate interest — 6(1)(f). Objection: section 7 | The suggestions themselves are not kept separately: they are recomputed from your budget, and only the learned rules, visible on the Rules page, live with it. The count is kept in your budget: per month, a number of suggestions kept, replaced or declined, without the content of your entries. 13 months |
| Email address, message content | Transactional email only: address verification, password reset, security alerts | Performance of a contract — 6(1)(b) | Deleted once sent; failed messages purged after retries |
| Session and refresh tokens | Keeping you signed in; revoking access on sign-out | Performance of a contract — 6(1)(b) | 30 days, rotated on each use and revoked on sign-out |
| Audit log: deletion of your account (with the IP address of the request), the administration's actions on your account, notices sent to you before an automatic deletion (unconfirmed account, ended subscription) and those deletions themselves, subscription and refund events where applicable. Sign-ins are not logged | Security of the service and traceability of actions affecting your account | Legitimate interest — 6(1)(f) | 12 months |
| IP address, for rate limiting and anti-abuse: in memory only | Preventing brute-force and fraudulent access attempts, and limiting the load a single visitor puts on the demo | Legitimate interest — 6(1)(f) | Dropped from memory once idle for more than 10 minutes (swept at most every 10 minutes), and lost on every restart of the service. Nothing is written to the database, and no access log records it |
| Opening the demo, without an account: a demonstration token, valid for one hour, that our servers hand to your browser. Your browser keeps it in memory, with no cookie; our servers keep no copy of it, no log records it, and they create no account and no record in your name. Your IP address is counted by the limit in the previous row | Showing you Arca with a fictional demonstration vault, shared by all visitors, before you create an account | Steps taken at your request before entering into a contract — 6(1)(b) | One hour at most: the token lives only in the tab's memory, which closing or reloading the page empties; it is not renewed, the demo asks for a new one when it expires. IP address: see the previous row |
| Diagnostics from the iOS app: report type, app and system version, device model, app state, an opaque installation identifier (not your identity), the text of your report and a crash summary — redacted on your device —, a screenshot masked on your device only if you choose to attach it, and your truncated IP address (the end is dropped: /24 for IPv4, /48 for IPv6). The web app sends none | Diagnosing crashes and defects | Legitimate interest — 6(1)(f) | 90 days |
The legitimate interests we rely on are named above, one by one, and for site audience measurement in section 10, as Article 13(1)(d) requires: securing the service, tracing actions that affect your account, preventing abuse, diagnosing defects, knowing which pages of the site are read, and suggesting what you usually enter while counting what you do with it. We have carried out and documented a balancing test for each. You can obtain the details by writing to privacy@arcabudget.app.
Is providing this data required? An email address is contractually necessary to create an account: without it we cannot provide the service and no account can be created. Everything else listed above is generated by using the service.
Financial data is not, in itself, a “special category” under Article 9 GDPR. A transaction may however reveal one: a pharmacy purchase, a donation, a membership fee. We do not try to infer any: no calculation sorts your transactions by these categories, and what you enter stays in your budget.
3a. What Arca computes and learns for you
Your budget's calculations. Balances, available amounts, budget health (savings rate, coverage, age of money, months ahead), upcoming cash flow, regular payments and advice cards are computed by our servers and your browser from your budget alone, when you display them. That is the service you asked for (performance of a contract, Art. 6(1)(b)). Nothing from these calculations is kept separately or passed on.
Suggestions learned from your entries. When you enter a transaction, Arca may suggest the category you usually choose for that payee; it follows your recent choices: a choice counts half as much every 30 days, and a one-off purchase does not override a frequent habit. When you merge two payees (“Merge and learn”, or the “Also rename future imports” option, on by default), it remembers the original bank label as a rule. It also lists first the payees you have used most in the last 12 weeks. These suggestions are computed from your budget, in your browser: no data from any other budget goes into them. In a shared budget, every member's entries serve everyone. When you enter a transaction, the suggested category is marked “suggested”; when you import, it is written directly and you change it in the register. The Rules page shows what Arca has learned, payee by payee. Legal basis: our legitimate interest in sparing you from typing what you always do (Art. 6(1)(f)).
What you do with the suggestions. To know whether these suggestions help you, your budget keeps, per month, how many suggestions were kept, replaced or declined: the category suggested when you enter a transaction, the match suggested when you import, the regular payment detected. These are only counters: no amount, no payee, no category name, nothing of the content of your entries. They are stored with your budget — which our servers read, like the rest —, kept for 13 months, and leave with it when you delete your account. If you switch off “Suggest from my entries”, nothing is counted any more. Legal basis: our legitimate interest in improving these suggestions (Art. 6(1)(f)). We also plan to derive anonymous improvement statistics from them, added up across all budgets: they are not active yet, and we will tell you before putting them in place. The “Contribute to improvement statistics” setting (Settings, “Data & privacy”) lets you object right now.
Objecting to learned suggestions. For the category suggested for a payee, one gesture is enough: “Stop learning” (Rules page). For everything else, switch off “Suggest from my entries” in Settings, “Data & privacy” section: Arca stops suggesting anything it has learned, on this device right away, on your other devices at their next sync. In a shared budget, it takes only one member switching the setting off for everything to stop, for every member. Learned rules are suspended, not deleted: you can delete them from the Rules page, with “Delete learned rules”. Rules you wrote yourself keep applying.
What we never do with them. No sale, no advertising, no rating passed to a third party, no decision made in your place. No machine-learning model is trained on your budget.
4. Who receives your data
| Recipient | Role | Location | What they receive |
|---|---|---|---|
| Hetzner Online GmbH | Hosting (processor) | Germany — European Union | Your budget (accounts, transactions, categories, amounts, notes), account records, logs. Stored on encrypted disks. |
| Zoho Corporation B.V. (ZeptoMail) | Transactional email (processor) | Utrecht, Netherlands — European Union | Your email address and the content of transactional messages |
| Google Ireland Ltd | Sign-in with Google (independent controller) | Ireland — European Union, with onward transfers to Google LLC (USA) | Nothing before you click “Continue with Google”. After the click: your IP address, details about your browser and the site the request comes from (loading Google’s script), then the sign-in itself |
We name our recipients here rather than describing vague “categories”. Each processor is bound by a data processing agreement meeting Article 28 GDPR. We never sell your data, and we share it with no advertiser and no data broker.
During the free beta, no payment details are collected and nothing is transmitted to any payment provider. If and when paid subscriptions open, Paddle.com Market Ltd (30 Old Bailey, London EC4M 7AU, United Kingdom) will act as Merchant of Record and as an independent controller for the purchase; this policy will be updated beforehand.
5. Transfers outside the European Union
Hosting and storage take place within the European Union, with no transfer to a third country. The only possible transfer concerns Sign-in with Google, if you choose it: Google Ireland Ltd may transfer data to Google LLC in the United States, on the basis of the EU–US Data Privacy Framework, under which Google LLC is certified.
You may obtain a copy of the safeguards applying to these transfers by writing to privacy@arcabudget.app. Certifications can also be checked on the Data Privacy Framework register.
6. Security
The measures we apply (Article 32 GDPR):
- encryption at rest: the database, the backups and the swap file live on an encrypted volume (LUKS); the backups are additionally encrypted with a public key whose private half is not on the server;
- your password never reaches us: your browser derives a fingerprint from it (PBKDF2-HMAC-SHA256, 600,000 iterations) and sends only that, which we re-hash with Argon2id;
- two-factor authentication (TOTP) and passkeys available on your account;
- encryption in transit (HTTPS/TLS) for every exchange;
- passwords stored as salted hashes, never in clear;
- short-lived sessions with rotating refresh tokens, revocable at any time;
- rate limiting and brute-force protection;
- an audit log stored in the same database as your data, and purged automatically when its retention period ends;
- hosting within the European Union.
In the event of a data breach, we notify the CNIL (Commission Nationale de l'Informatique et des Libertés) within 72 hours where Article 33 GDPR requires it. We do not claim the exemption in Article 34(3)(a): it assumes data made unintelligible to a third party, which encryption at rest does not deliver against access obtained on a running machine. A breach affecting the contents of budgets would therefore be notified to you. Where there is any doubt, we undertake to inform you anyway.
7. Your rights
You have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and not to be subject to automated decision-making (Art. 22). Here is concretely what each one means at Arca:
- Access and portability. Your budget is exportable at any time, for free, from the app, in an open format (
arca.vault.v1). On request we additionally provide everything we hold on our side (email address and its hash, identifiers, metadata, logs). - Rectification. You correct the contents of your budget from the app; we correct your account details on request.
- Erasure. Fully available. What you delete in the app is erased after 30 days (section 3); a transaction can be erased right away from the trash. Deleting your account removes the contents of your budget, the metadata, your email address and its hash, and the tokens. Backups are purged within 30 days. Audit-log entries may be kept until the end of their retention period, on the security ground set out in section 3.
- Restriction. You may ask us to suspend the processing based on legitimate interest (learned suggestions, audit log, rate limiting and anti-abuse, diagnostics, site audience measurement) while a request is being examined.
- Automated decisions and profiling. Arca takes no decision based solely on automated processing that would produce legal effects concerning you or similarly significantly affect you (Art. 22): no credit, no refusal of service, no rating passed to anyone. Arca does, however, analyse your budget for you: for example, it works out your savings rate, how many months ahead you are and your regular payments, and it suggests a category or a payee based on what you entered before. Under Article 4(4) GDPR, that is profiling. It serves only you, nothing of it leaves your account, and every suggestion can be changed in one gesture. The details, the legal basis and how to object are in section 3a.
We reply within one month (Art. 12(3)), extendable by two months for complex requests, in which case we tell you within the first month. If we cannot act on a request, we explain why, and you may lodge a complaint or seek a judicial remedy (Art. 12(4)).
Your right to object (Art. 21 GDPR)
You may object at any time, on grounds relating to your particular situation, to the processing we carry out on the basis of our legitimate interest — namely suggestions learned from your entries, the audit log, rate limiting and anti-abuse, diagnostics, and site audience measurement. Write to privacy@arcabudget.app. We will stop that processing unless we demonstrate compelling legitimate grounds which override your interests, rights and freedoms. For the audit log and rate limiting, which serve the security of the service, such grounds will most often prevail: we examine each request and reply with our reasons. For learned suggestions, you do not have to write to us: switch off “Suggest from my entries” in Settings, “Data & privacy” section (on this device right away, on your other devices at their next sync), or use “Stop learning” (Rules page) for a single payee. For site audience measurement, a visit's fingerprint does not let us find it again afterwards: an objection cannot erase your past visits. To stop being counted from now on, use the “Don't count my visits” link in section 10.
8. Directives on your data after death
Under Article 85 of the French Data Protection Act, you may give directives on the retention, erasure and communication of your data after your death — either general directives registered with a certified trusted third party, or specific directives sent to us at privacy@arcabudget.app. We are able to act on those directives: the contents of your budget are accessible to us, and are therefore not lost with you.
9. Lodging a complaint
If you consider that your rights are not respected, you may lodge a complaint with the CNIL (Commission Nationale de l'Informatique et des Libertés): 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France — https://www.cnil.fr. We would rather you write to us first, but that is your right and it is not conditional on contacting us.
10. Cookies and local storage
This site and the app show no cookie banner: what we store on your device is strictly necessary for the service you asked for, or only serves to show the interface the way you set it. No advertising, no third-party analytics. Only one item comes from a third party, and only if you choose it: Sign-in with Google (below). Here is what we store on your device when you use the app, the marketing site or the documentation:
| Item | Purpose | Lifetime |
|---|---|---|
| Session token | Keeping you signed in | Session, renewed while you are active |
Refresh token (arca_rt cookie) | Avoiding signing you out every hour | 30 days, rotated on each use and revoked on sign-out |
| Display preferences (language, theme, currency, formats, sidebar, opting out of audience measurement) — in the app, on the marketing site and in the documentation | Showing the interface the way you set it | Until you clear your browser data |
| Local copy of your budget | Making the app work, stay fast and remain usable offline | Until you sign out or clear your browser data. For the demo: until you choose “Leave the demo” in Settings, or clear your browser data; closing the tab or choosing “Sign in” keeps it. It is also erased, then filled again, the first time you open the demo after its nightly renewal. What you enter there stays on your device and does not go to our servers |
| Undo history: your last 50 actions and the contents they touched, in the clear on your device, like the local copy of your budget | Letting you undo an action with ⌘Z, even after the page is reloaded | Until you sign out or clear your browser data. An action older than 30 days is removed from it, with the contents it kept. For the demo: like its local copy, above |
| Offline app (service worker and app cache) | Loading the app without a network, and updating it | Until the next version |
| Local vault identifier, installation identifier, time of the last session renewal | Reopening the right vault on this device, tying the count of suggestions (section 3a) to the device, preventing two tabs from renewing the session at the same time | Until you sign out or clear your browser data. For the demo: until “Leave the demo”, in Settings, or until you clear your browser data; it has no session to renew, so no timestamp |
| Token of an invitation to a shared vault | Keeping the invitation while you sign in | For the life of the tab, removed after use |
| Sidebar state in the documentation | Keeping sections collapsed while you read | For the life of the tab |
These items are exempt from consent under Article 82 of the French Data Protection Act, being strictly necessary to provide a service you expressly requested, or limited to the display you set.
Sign-in with Google — only if you choose it
Google’s service does not load when the page opens on the sign-in, vault creation and account deletion screens. It loads only if you click “Continue with Google” (or “Sign in with Google”, “Sign up with Google”), and a line of information next to the button says what is sent. Before that click, Google receives nothing from your visit and sets nothing on your device.
On click, Google’s script is requested from accounts.google.com: Google receives your IP address, details about your browser and the site the request comes from, and its script sets a cookie, g_state, on app.arcabudget.app (about six months at the last check; the lifetime is set by Google). You then click a second time on Google’s button, which replaces ours. Google acts for its own account (section 4). To avoid this cookie, sign in with your email address.
Audience measurement on this marketing site
We measure traffic on this marketing site only. In the app we do not follow your path from screen to screen. Only two things are measured there: how long screens take, and only if you let us — see the next section; and, in your budget, the monthly count of what you do with Arca's suggestions, with nothing of the content of your entries (section 3a). This site measurement sets no cookie and creates no identifier that would follow you.
For each page viewed, we record exactly three things:
| Data | Precision kept | Retention |
|---|---|---|
| Page viewed | The path only (never URL parameters, which could contain a personal link) | 13 months |
| Where you came from | The site's name (“google.com”), never the full address nor your search terms | 13 months |
| Visit duration | In seconds | 13 months |
| Device type | Three families only — phone, tablet or computer — never the exact model or browser | 13 months |
| Browser language | The main language only ("fr", "en"), never your full preference list | 13 months |
| Country | The country alone ("France"), derived from the truncated address before it is discarded — never the city or region | 13 months |
To count visitors without identifying them, your IP address — truncated first, that is, stripped of its ending, as the French regulator recommends — and your browser are turned into a one-way fingerprint, mixed with a random secret that is renewed every day and held in memory only. That secret is never written to disk: it vanishes each night. The direct consequence — nobody, not even us, can link your visit today to your visit tomorrow, or work back from a fingerprint to an IP address. Your IP address and browser are themselves never stored.
This measurement runs on our own servers, in Europe, for our use alone. No data is shared with a third party, cross-referenced with any other processing, or used to track you across sites. It therefore falls under the consent exemption for audience measurement in Article 82 of the French Data Protection Act — which is why this site does not confront you with a banner. Under the GDPR, its legal basis is our legitimate interest in knowing which pages are read (Art. 6(1)(f)). Should we ever add a tracker that falls outside that exemption, we would ask for your consent beforehand.
You can choose not to be counted. The link below remembers your choice in this browser, and measurement stops on every page of this site, including after a reload. It applies to arcabudget.app. The documentation (doc.arcabudget.app) does not measure its traffic.
App performance measurements — only if you agree
Some screens may be slow, and we cannot know it without measuring. You can help by turning on “Performance measurements” in the app settings. It is off by default, and nothing is measured until you say yes: the instruments themselves are not put in place.
If you agree, each measurement contains exactly this:
| Data | Precision kept | Retention |
|---|---|---|
| Screen concerned | A name from a fixed list (“budget”, “transactions”…), never the address — which would carry an account identifier | 90 days |
| Duration | In milliseconds: time to display, or time to respond to a gesture, broken into waiting, computing and painting | 90 days |
| App version | The version number alone | 90 days |
| Vault size | An order of magnitude (“between 2,000 and 5,000 transactions”), never the exact count — an exact count would almost certainly single you out | 90 days |
| Device type | Three families — mobile, tablet, computer | 90 days |
| App crash | The fact that the previous session stopped suddenly while on screen (memory full, crash) — a plain “yes”, with no time and no screen | 90 days |
| Storage used | How much space the app takes on the device, in rounded megabytes, and its ratio to the real size of your vault — to spot storage that swells abnormally | 90 days |
| Memory used | The page’s memory, in rounded megabytes — only when the browser provides it (Chrome and derivatives), on opening and then every five minutes | 90 days |
What is never in it: no transaction, no amount, no payee, no envelope, no account name, no date from your budget. There is no field where any of these could go, not even by a programming mistake.
On the device, for everyone: the app counts its own crashes and shows how much space it takes, under Settings › This device. Both stay on your device; only taking part in the measurements above sends them.
These measurements are not linked to your account. They are sent without your sign-in token, to an address that does not ask for one: our servers therefore have no way to match a measurement to a person, even if they wanted to. They carry the same daily fingerprint as the site measurement — truncated IP address, secret renewed every night and never stored — which serves only to avoid counting the same session ten times in one day, and allows nothing else.
Legal basis: your consent — GDPR art. 6(1)(a). We keep the record of that agreement separately (your account, the date, and the version of the text you read), because the law requires us to be able to show it. You can withdraw at any time from the same setting; withdrawal takes effect immediately, and it is as easy to take back as it was to give.
11. Free beta and future billing
Arca is currently in free public beta. We collect no payment details, and no billing provider receives any data about you. Arca will become paid one day: you will be informed at least 60 days in advance, by email, and nothing will ever be charged to you without an explicit order on your part. This policy will be updated before any payment processing begins.
12. Changes to this policy
If we change this policy, we update the date at the top of this page. For any change that materially affects your rights or introduces a new purpose, we inform you by email before it takes effect (Art. 13(3)).
13. Contact
Privacy: privacy@arcabudget.app · Support: support@arcabudget.app
Arca Budget — the Arca team (T.B.), France
Hosting: Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany
