Legal
Privacy Policy
WhereDidItGo holds your money data, so this policy is specific: what we hold, why, who else sees it, how long it stays, and how you get it back or make it go away. Every period in it is one our systems enforce.
Version of 29 September 2026, last edited 28 October 2026.
1.Who is responsible for your data
DraVan Technologies S.A.R.L. -S., 13 Massewee, 9633 Baschleiden (B307230) is the controller of the personal data described here: we decide why and how it is handled. Privacy questions and requests go to [email protected].
2.What we collect, and where it comes from
- Your account. Your email address and name; how you sign in (a passkey’s public key, a linked Google or Apple account, whether you have a second step turned on); your language, time zone and the country your request appeared to come from, used once to suggest which country’s banks to show first. We never store a password, because there is none.
- What you and your household enter. Accounts, transactions (amounts, dates, the shop or person named, notes), categories, budgets, goals and scheduled bills and income, plus the household’s settings and members. Everyone in a household can see all of it.
- Investments, if you follow any. What an investment account holds: a symbol for each share or fund and how many you have. To value them, when prices are switched on, our servers ask a market-data source for the price of each symbol, and the European Central Bank’s published rates to convert a price into your currency. Those requests contain the symbol and nothing else: nothing about you, your household or how many you hold, and a symbol many households hold is asked for once.
- Bank data, if you connect a bank. Through Salt Edge: the bank and accounts you choose to share, a masked account number (never the full IBAN), balances and transactions. We never receive your bank login. The permission is read-only.
- Subscription and payment. Your plan and its status, and a customer reference at Stripe or in the app stores. Card details are held by Stripe and never reach us.
- Security and device data. Each sign-in and security event with the time, the method, your IP address and your browser or app’s description; the devices signed in to your account; and a random identifier per browser.
- Crash reports from the phone app. When the app crashes it sends, the next time it opens, what went wrong (the error and where in the app’s code), the screen it was on and the last few steps before it (screens opened, and requests made without their contents), the app version, and the phone’s model and system version. Never an amount, a name, an email address or anything that says who you are or which household you belong to. You can read every report on the phone, and switch sending off, in Settings, Crash reports.
- What you agreed to. That you accepted the terms and the privacy policy, which version and when, and each time a household turned a bank connection or AI categorization on, renewed or ended it.
- When you write to us. Your message and our reply.
- From other people. A household member who invites you gives us your email address. If you sign in with Google or Apple, they tell us your name, your email address and whether they verified it.
Transactions can reveal sensitive things about a person, such as health, religion or membership of a union, simply through where money went. We do not look for that, we do not use it to work out anything about you, and it is treated like the rest of your data. By entering, importing or connecting your transactions you choose to give it to us for the purposes below.
3.Why we use it, and on what legal basis
| What we do | Data used | Legal basis (GDPR art. 6) |
|---|---|---|
| Provide the service: your account, the forecast, budgets, goals, households and exports | Account, household and transaction data | The contract with you (b): you asked for the service. |
| Read your bank, when you connect one, and keep it up to date | Bank data | The contract with you (b). You start it and can end it at any time, which revokes the permission at once. The permission to read your bank is a separate one you give to your bank. |
| Take payment and manage your subscription | Subscription and payment data | The contract with you (b), and our legal duty to keep accounting records (c). |
| Keep your account and the service secure: sign-in and security logs, notice of a new device, rate limits, fraud and abuse prevention | Security and device data | Our legitimate interest in protecting your money data and the service (f). We have weighed it against your interests, and keep to what is needed and delete it on a schedule. |
| Find and fix crashes in the phone app, unless you switch crash reports off | Crash reports, which say nothing about who you are | Our legitimate interest in an app that works (f). Switching it off in the app is your objection, taken at once. |
| Send you emails about the service: sign-in codes, security notices, invitations, confirmations, notices about your subscription or a household that is about to be deleted | Email address, name | The contract with you (b) and our legitimate interest in keeping you informed (f). We send no marketing. |
| Show that you agreed to the terms and to a bank or AI connection | Acceptance and consent records | Our legal claims, and our legitimate interest in being able to show what was agreed (f). |
| Answer your questions and requests, including privacy requests | What you send us | The contract with you (b), our legal duty to answer your rights requests (c), and our legitimate interest (f). |
| Categorize transactions with AI, if a household has that on and its plan includes it | A shop name, whether money came in or went out, and a few words of the bank's text with account numbers taken out; never an amount, a balance or your bank | The contract with you (b): it is a feature you choose to switch on. See the AI section below. |
| Comply with the law and defend claims | As needed | Legal duty (c) and legitimate interest (f). |
Where we rely on a legitimate interest you have the right to object (see “Your rights”). Where you enter or connect information that reveals a sensitive category, our basis for that part is your explicit consent (art. 9(2)(a)), which you give by choosing to enter, import or connect it and can withdraw by deleting it or your account.
4.AI categorization
On plans that include it, a household can let WhereDidItGo suggest categories for transactions with AI. Your own rules always run first, and it is a household setting: one switch, in Settings, turns it off for everyone in the household, and turning it on or off is recorded.
It is only asked about a merchant your rules and the built-in patterns do not recognise, and once per merchant: the answer is remembered for the household, so the same shop is never sent twice. What is sent is the merchant’s name, whether money came in or went out, and a few words of the bank’s own text with account numbers, email addresses and long numbers taken out. That text can still contain the name of a person or a business you paid. It is never sent an amount, your balance, your email or your own name.
When it is confident, it files the transaction; when it is not, it only suggests, and the suggestion waits in Review for you to accept or change. You can change any category, and nothing it does has a legal or similarly significant effect on you.
6.Where your data goes
Your data is stored in Belgium, in the European Union. Some providers we use, such as those that send email, take payments or run app stores, may process limited data outside the European Economic Area. When they do, the transfer relies on an EU adequacy decision (for example the EU–US Data Privacy Framework, for participating recipients) or on the European Commission’s Standard Contractual Clauses in our agreement with the provider. You can ask for a copy of the safeguard at [email protected].
7.How long we keep it
We keep each kind of data for the time in this table and no longer. These are the periods our systems apply, not aspirations: a scheduled job enforces them, and deleting your account is immediate.
| What | How long | Why |
|---|---|---|
| Your account: email address, name, sign-in methods, devices, sessions and preferences. | Until you delete your account. Deleting it is immediate. | It is needed to run the service you asked for. Nothing is kept afterwards except what this table lists. |
| A household's accounts, transactions, categories, budgets, goals, scheduled flows and what AI categorization said about its merchants. | While the household exists and its subscription is active. A household that lapses is kept for 12 months, then deleted. | Coming back after a lapse should restore everything. We email its owners 60 days and again 14 days before, and nothing is deleted without that last reminder. You can export or delete it yourself at any time. |
| The sign-in and security events of an account that still exists (when, from which device, which method). | 24 months. | It is shown on your Security page and is what lets us investigate a stolen session. |
| Sign-in and security events about someone who has deleted their account. | Made unidentifiable within minutes of the deletion: the email address and IP address are replaced by a keyed hash and the browser identifier is removed. The row is deleted 12 months after the event. | A fraud or abuse investigation must still be able to tell that the same person or address came back, without keeping who they were. |
| Failed sign-in attempts for an address that has no account. | Identifiable for 30 days, then the same treatment as above. Deleted after 12 months. | Enough to read an attack while it happens. |
| Who changed what in a household, and when (its activity log). | 24 months. When the person who made a change deletes their account, their IP address and browser identifier are removed and the change is shown as by a former member. | Accountability inside a household two people can both change. |
| Expired sessions, expired sign-in codes and the rate limiter's counters. | Sessions 7 days after they expire; codes and counters within a day. | Nothing needs them once they have expired. |
| Household invitations, with the invited address. | Deleted 30 days after the invitation's expiry date, whether or not it was used. | Long enough to see that an invite was sent and by whom; not longer. |
| A data export you asked for. | The file is deleted after 24 hours, downloaded or not. The record that you asked for one is kept 30 days. | It holds your whole financial history in one file, so it should not sit around. |
| Your consent to read a bank connection, and the data read through it. | The bank grants at most 180 days at a time; after that you renew it or it lapses. It is revoked at the bank the moment you disconnect, your subscription lapses, or the household or account is deleted. | Access to a bank account is limited to what you currently allow. |
| The record that you accepted the terms and the privacy policy, and that a household turned on a bank connection or AI categorization: what, when, and which version of the wording. | While the account (or, for a household's consents, the household) exists. | We must be able to show what you agreed to. |
| What you write to us and our replies, including privacy requests. | 24 months after the matter is closed. | Long enough to follow up, and to show how and when we answered a request; not longer. |
| Invoices and payment records held by Stripe, or by the App Store or Google Play. | As long as tax law requires (seven years in the Netherlands). Deleting your account deletes the customer record we hold, not those invoices. | A legal obligation, not ours to waive. |
| Encrypted database backups. | 14 days. Data you delete leaves the backups within that time. | Recovery from a failure; backups are never read for any other purpose. |
| Operational logs: what the app writes (the method, path, status and duration of a request, never a body or a header), crash reports the phone app sends (what went wrong, on which screen, and the app version and phone model, never who you are), and the request log Google Cloud writes for every request, which also carries the client IP address and the address requested. | 30 days. | Keeping the service running and investigating an attack. They are used for nothing else. |
8.Your rights, and how to use them
Under the GDPR you have the right to:
- Access and portability. Get a copy of your personal data, and the data of the households you belong to, in a machine-readable format. In the app or on the website: Settings, Security & privacy, “Download my data”. We prepare it within minutes and email you a link that expires in 24 hours.
- Rectification. Correct what is wrong: edit it in the app, or write to us.
- Erasure. Delete your account, immediately, in the app, in Settings, Security & privacy on the website, or from our deletion page without installing anything. A household only you belong to is deleted with it; a household you share keeps its money and loses your name from what you added. To delete only some of the data, an owner can erase parts of a household’s data (bank connections, transactions, budgets, goals and bills, rules and what the app learned, investment holdings) and keep the rest.
- Restriction and objection. Ask us to pause the use of your data, or object to processing based on our legitimate interests, by writing to us.
- Withdraw a consent. Disconnect a bank (which revokes access at once), turn AI categorization off, or delete the data or your account. Withdrawing does not affect what we did before.
- Not be subject to automated decisions with legal or similar effects. We make none.
To use a right that is not a button, write to [email protected] from the address of your account, so we know it is you. We answer within one month; if a request is complex we may take up to two more months and will tell you why. It is free unless it is manifestly unfounded or excessive.
You may also complain to a data protection authority: that of the EU or EEA country where you live or work, or of Luxembourg. We would appreciate the chance to put things right first.
9.How we protect it
- Everything travels over HTTPS, and the database encrypts what it stores.
- Each household’s data is separated inside the database itself: a query that forgets to filter by household returns nothing rather than another family’s money.
- Sign-in is by passkey, Google or Apple, or an emailed single-use link or code, with an optional second step; sensitive actions ask you to confirm it is you again.
- Our systems run with the least access each needs, and every change made in a household, and every sign-in, is logged.
- Bank access is read-only, and we never hold your bank credentials. Security researchers can report a problem under our security policy.
11.Children
The service is for people aged 18 or over. We do not knowingly collect data about anyone younger; if you think we have, write to [email protected] and we will delete it.
12.Changes to this policy
When we change this policy in a way that matters to you, such as a new provider that receives personal data, a new purpose or a longer retention period, it gets a new version date and you are asked to acknowledge it before you carry on. A correction that changes nothing of substance only updates the “last edited” date. The version you acknowledged, and when, is kept in your account, under Security & privacy.