Privacy Policy

SpendWe ("SpendWe", "we", "us") makes a personal and couple expense-tracking app for iPhone, iPad and Android, with a companion web app. This policy explains what data the app handles, why, and the choices you have. We built SpendWe to be useful without profiling you: there are no ads, no advertising trackers, and we never sell your data.

1. What we collect

Data you create in the app

• Financial entries - expenses and income you add (amount, currency, merchant, date, note, category, and who paid), your categories, and your budgets.
• Receipt images - photos you scan are read on your device first. If Use AI is on, each scanned photo (reduced in size, with its location and other metadata removed) and the text read from it are sent to SpendWe's server, which passes them to Anthropic to read every item; the server does not store or log the photo (see AI features). If Use AI is off, nothing about the scan leaves your device. Separately, you choose whether a photo is kept at all, kept on this device only, or kept and backed up (see below). Receipt photos are never included in your phone's own device backup.
• Display name - a username you choose (it does not need to be your real name), used to label who paid for an expense.
• Apple Pay purchases you choose to log (iPhone) - the app never reads your Apple Wallet. If you set up a Shortcuts automation yourself, your Shortcut sends SpendWe only the amount, merchant and date of a purchase, which are saved as an expense like any entry you type.
• Incomes used for an income-based split - if you split household costs in proportion to income, the incomes you enter stay on your device. Only the resulting share percentages are synced with your household.
• Price memory - item prices remembered from your receipts are kept on your device only. They are not synced, not included in the cloud backup, and never included in your phone's own device backup.

As long as you don't use a cloud feature or AI, these financial entries stay on your device. On iPhone and iPad they are also part of your own device backup (iCloud Backup, or a backup to your computer), if you use one: that backup belongs to you, under your Apple account or on your computer, and we have no access to it. Receipt photos and price memory are never included in a device backup. On Android, nothing from your entries, receipt photos or price memory goes into Google's device backup, so without a SpendWe account an exported backup is the way to move them to a new phone. The app may still contact Firebase for configuration delivery and crash diagnostics, as described below.

What changes when you use a cloud feature

Two things store data on our servers: automatic backup, and sharing a household with a partner. Either one needs an identity to attach your data to:

• Without signing up - for example if you only share a household, or turn on AI without an account - the app creates an anonymous identifier for your device. We hold no email or name for you, but your synced entries are stored on our servers under that identifier. Because it lives only on that device, resetting or replacing the phone can permanently lose access to it.
• If you add your email, that identity becomes a real account, which is what lets you restore your data on a new phone and keep several devices in sync.

Data collected only if you use a cloud feature (backup or household sharing)

• Email address - only if you choose to add one. Used to sign in with a one-time code and to identify your account. The code sent by email is the standard way to sign in. Sign-in with Apple or with Google appears in the apps only where we have switched it on; the web app does not offer it. If you use one of them, that service gives us your email address (with Apple's Hide My Email, a relay address) and a stable identifier for your account; Google may add the name and the picture address of your Google profile, which we do not use or display. We never receive your Apple or Google password. Without an email address, your cloud data is tied to an anonymous identifier instead.
• Your synced financial entries - the entries above, stored in your private cloud space so they can be backed up and shared within your household.
• Receipt photos you back up - only if you keep a photo and choose to back it up (you can decide per receipt). It is stored in your household's access-controlled cloud storage; the photo of an expense you mark Private is stored where only you can read it.
• Household membership - if you link with a partner, the fact that your accounts share a household, and a display name for each member.
• Reactions & comments - reactions and comments you add to an expense in a shared household are stored with that household and are visible to its members.
• Notification preferences - which notifications you've enabled, your quiet-hours window, and your time zone, so alerts and summaries arrive at sensible local times.
• New sign-in notices - when a new sign-in to your account starts, our server notes that session, your account identifier and the time (no device, place or IP address) to send a "new sign-in" notice to your devices that receive notifications; the note is deleted after seven days.
• Device push token - on Android, a token from Firebase Cloud Messaging (Google) so we can deliver the notifications you turned on. It is stored only while notifications are enabled, and the text of each notification passes through Google's delivery service. On iPhone and iPad, notifications sent from our servers are not active yet: the app registers no push token, and the reminders and budget alerts you see there are created by the app on the device itself. When they are switched on in a later version, the app will ask your permission first, and a token from Apple Push Notification service, obtained through Firebase, will be stored in the same way. The web app sends no notifications.

AI features (optional)

SpendWe's AI features are: reading the items of a receipt you scan, Ask SpendWe (questions about your spending), a written summary of your month, category suggestions, and a check of the columns of a bank file you import. Receipt reading runs on every scan while Use AI is on (a free account gets 4 receipt corrections a month); the others run only when you ask for them and are part of SpendWe Pro.

• AI is your choice - AI runs through our server, not on your phone. The app asks you when you first open it, and nothing is sent until you turn AI on; Use AI is off until you do. You can switch it off or on at any time in the app's settings; switching it off stops every AI request, receipt scans included, and a scan then keeps what your phone read. The web app has its own Use AI switch, kept in your browser and asked once after you sign in; it covers the web's AI features only. AI needs a connection to SpendWe's server: an account, or the anonymous identifier described above.
• What AI sends - only what the task needs, to SpendWe's server, which passes it to our AI provider, Anthropic (its Claude model): for a scanned receipt, the photo of each page (made smaller, at most 1,600 pixels on its long side, re-encoded so that its location and other metadata are removed), the text read from it with the position of each line, and the names of your categories so each item can be filed; for a question or a summary, your monthly spending and income totals, the totals by category, your top merchants and their amounts, your budgets and their period, your currency and language, today's date and the question you type; for category suggestions, the merchant names and amounts to sort and the names of your categories; for a bank file, a profile of its columns (titles, kinds of value and proportions), never its rows or amounts. Transfers and expenses you mark Private are left out of the totals.
• What is never sent - your notes, the names of your household members, comments, your location, or photos other than the receipt you are scanning; and nothing that identifies you, such as your email address or account identifier, is passed to Anthropic. A receipt can show whatever is printed on it (for example the store's address or the last digits of a card): that is part of the photo and its text.
• What is kept - SpendWe's server does not store or log the content of AI requests or answers, receipt photos included: a photo is passed to Anthropic for that one request and then discarded. It keeps a count of requests per account, to apply the limits (100 a day; for a free account, 4 receipt corrections a month); counts older than about five weeks are removed the next time you use AI, and all of them with your account. To keep the cost of AI within a budget, it also records for each request the task, the model, its size in tokens, its cost and whether it succeeded, with no account identifier and no content; these records are deleted after 400 days. Anthropic processes these requests as our service provider under its commercial terms. As of 21 October 2026, Anthropic states that by default it does not use inputs or outputs from its API to train its models, and that it deletes API inputs and outputs within 30 days, except where it must keep them longer by law or to enforce its Usage Policy (for example, content flagged as violating it). See Anthropic's pages on model training and data retention.
• AI answers are generated automatically and can be wrong; they carry an "AI" label. Check them before you rely on them. A receipt read by AI shows its items for you to check before you save it.

The web app

The web app at spendwe.com/app works with the same SpendWe account and the same cloud data as the apps (what you back up or share in a household). You sign in with a one-time code sent to your email. Your session is kept in your browser: for the current tab only, unless you tick Remember this browser, in which case it stays until you sign out. Signing out removes it. The web app also keeps in your browser's local storage: your display choices (language, theme, colour palette, hidden amounts, dismissed hints), cached exchange rates, your pinned tags, payment handles you save for settling up, the incomes you type for an income-based split, the amounts you type in "Will I cover my bills?", your account alert levels, the layout of bank files you imported, your answer to Use AI, your progress in the Home "Get started" cards, the bank-statement lines you marked as not matching an expense, and short technical records it needs to finish its work (which rows your last import added, which receipt photos are still to be moved or removed). Signing out removes the session, your pinned tags, the payment handles, the typed incomes, the bills figures, the account alert levels, the bank-file layouts, your Use AI answer, the "Get started" progress, those statement answers and the record of your last import; your display choices, the cached exchange rates and the records of receipt photos still to be moved or removed stay in that browser until you clear its site data. It uses no cookies, analytics or advertising. The only outside script it loads is Paddle's checkout, and only when you press a button to buy Pro.

Buying SpendWe Pro on our website

Purchases on spendwe.com are handled by Paddle, our reseller and Merchant of Record: Paddle is the seller, takes the payment, and handles tax, invoices, refunds and cancellations. Paddle's checkout opens on top of the web app; the card, PayPal or wallet details you enter there go to Paddle, and SpendWe never sees them. To attach the purchase to your account, the web app gives Paddle your SpendWe account identifier and email address when you open the checkout, and Paddle tells us the plan, its status and Paddle's purchase references, so that Pro is unlocked on your SpendWe account on every device. Paddle handles the information it collects as a separate controller under its own privacy notice. Web purchases are not open yet; this describes how they work once they are.

Buying SpendWe Pro in the apps

Purchases in the apps are made with Apple's App Store or Google Play, which take the payment; we never see your card. To unlock Pro, the app sends us the store's signed proof of purchase, and we keep the plan, its status and the store's purchase references with your SpendWe account. Purchases in the apps are not open yet; this describes how they work once they are.

Visit statistics on our website

Our website is hosted by Cloudflare, and we use Cloudflare Web Analytics to count visits to its public pages (the home page, legal and support pages). A small Cloudflare script measures each page view and reports: the page address, the site that linked to it, your country, your device type, browser and operating system, and how quickly the page loaded. It sets no cookies, stores nothing in your browser, and, according to Cloudflare, does not fingerprint you or follow you across other websites. We see only totals (for example, how many visits came from a given country or link), never a list of individual visitors. It is not used inside the web app, where our security settings block it, and it is not part of the iPhone, iPad or Android apps.

Cookies and browser storage

Our website and the web app set no cookies, and neither does the visit-statistics script described above. A few small items are kept in your browser's storage instead. They stay in your browser, are never sent to us, and are not used for advertising, tracking or statistics. On the public pages there are four:

• spendwe.lang (local storage): the language you picked with the EN | FR switch, so the site keeps showing it.
• spendwe.langAuto (local storage): a note that the site already chose a language from your browser's language on your first visit, so it never switches language on its own again.
• spendwe.langBannerOff (local storage): you closed the banner that offers the other language, so it stays closed.
• spendwe.country (session storage, removed when you close the tab): the two-letter country used to show prices in your currency, taken from the country Cloudflare reports for your connection or from your time zone, so it is not looked up again on every page.

The web app keeps your session and the settings and short working records listed under The web app above. It needs them to sign you in and to do what you ask, and it sets no cookies either.

Each item is strictly necessary for something you asked for, or remembers a choice you made. Under the ePrivacy rules (Article 5(3) of Directive 2002/58/EC, as applied in France by the CNIL), such storage does not need your consent, which is why there is no cookie banner. If we ever add anything that does need consent, we will ask before setting it. You can remove all of it at any time by clearing this site's data in your browser settings.

Crash reports

If the app crashes, Firebase Crashlytics (Google) sends us a diagnostic report so we can fix it: the technical stack trace, your device model, OS version and app version, plus a random installation identifier. We do not intentionally attach expenses, amounts, merchants, categories or email to these reports, and they carry no advertising identifier. They are used only to find and fix crashes.

What we do not collect

• No advertising identifiers, no ad SDKs, no behavioural or usage analytics in the apps or the web app, and no location tracking. We do not track what you tap, which screens you visit, or how often you use the app. Our website and web app set no cookies. The only statistics we collect are the anonymous visit totals for our public web pages described in Visit statistics on our website.
• We do not access your bank accounts. PDF statement import happens from files you choose.
• We never log your session tokens or the contents of your entries on our servers.

2. How we use it

• To run the core app features on your device (tracking, budgets, categories, charts, scanning, import/export).
• To back up your entries and sync them across your devices and with your household partner, when you use an account.
• To send only the notifications you have switched on, honoring your quiet hours; a notice of a new sign-in to your account is a security notice and may arrive at any hour.
• To read the receipts you scan and answer the AI requests you make, while Use AI is on, as described above, and to keep the cost of AI within a budget.
• To unlock Pro on your account when you buy it.
• To secure the service (for example, limiting repeated attempts to guess a household invite code) and to fix problems.
• To understand, in aggregate, how people find our website and how fast its pages load.

We do not use your financial data for advertising, and we do not sell or rent it.

3. Legal bases (GDPR / EEA & UK)

• Performance of a contract - to provide the account, backup, sync and notification features you request, and the Pro plan you buy.
• Consent - for AI (the Use AI switch), for push notifications and for optional sign-in providers; you can withdraw it at any time in the app, in your browser or in your device settings, without affecting what was done before.
• Legitimate interests - to keep the service secure and working (for example the notice of a new sign-in, and the cost records of AI requests, which carry no identity and no content), and to measure visits to our public web pages in aggregate, balanced against your privacy.

4. Who processes your data

We use a small number of reputable providers strictly to operate the app. They process data on our behalf under their own security and privacy commitments, and each publishes data processing terms (see Safeguards below) that commit it to confidentiality and security measures for the data it processes for us:

• Supabase - hosts the database, authentication and backup storage for accounts, in the European Union (Frankfurt, Germany, on Amazon Web Services), and runs our small server programs (for example the ones that send notifications, pass a cloud AI request on, or delete an account).
• Google - Firebase Cloud Messaging delivers push notifications on Android; a small configuration document is delivered to the apps and the web app at launch (Firestore, with Firebase App Check on Android); and Firebase Crashlytics receives crash diagnostics from the apps.
• Resend - sends the email that carries your sign-in code (from noreply@spendwe.com); it receives your email address and the code. According to Resend, its sending logs are kept for 30 days.
• Apple - Apple Push Notification service will carry notifications to iPhone and iPad once they are active there (see "Device push token" above). It is not used today.
• Anthropic - processes AI requests (Claude model), including the receipt photos you scan, only while Use AI is on, as described in AI features.
• Cloudflare - hosts the website and the web app and delivers them to your browser, and provides the visit statistics for our public web pages (Cloudflare Web Analytics).
• Currency exchange rates - a public, keyless rates file (served by jsDelivr, with a copy on Cloudflare Pages as a fallback) is fetched to convert foreign-currency receipts; these requests do not include your identity or your entries. Like any web server, the host sees the IP address the request comes from.

Paddle, which sells Pro on our website, is not our processor: as Merchant of Record it is the seller, and it handles the buyer information it collects as its own controller (see Buying SpendWe Pro on our website).

The App Store and Google Play, where you download the apps and can buy Pro once purchases open, are not our processors either: Apple and Google handle your store account and your payments under their own privacy policies.

Where your data is stored, and transfers to other countries

• Your account data (synced entries, household, sign-in records and the receipt photos you back up) is stored in the European Union, in Frankfurt, Germany.
• Processing in other countries. Our small server programs can run in the Supabase data centre closest to you, so a request (for example an AI question) may be handled outside the European Union before it is answered; nothing is kept there. Google (notifications, crash reports), Resend (sign-in code emails), Anthropic (AI) and Cloudflare (delivery of the website and the web app, visit statistics) are companies based in the United States; they may process the data described above there, or in the other countries where they or their own providers operate.
• Safeguards. Each of these providers publishes data processing terms that include standard contractual clauses for transfers out of the European Economic Area, the United Kingdom and Switzerland: Supabase, Google Firebase, Anthropic, Cloudflare, Resend. Google and Cloudflare also state that they are certified under the EU-US Data Privacy Framework, and Resend states that it complies with it. You can ask us for a copy of these safeguards at privacy@spendwe.com.
• If you live outside the European Union, using a cloud feature means your data is sent to, and stored in, the European Union, and is handled by the providers above.

We share data with a household member only when you deliberately link accounts. By default every entry in that household is visible to its members, and an expense's shared-balance setting controls settlement, not who can view it. An expense you mark Private is the exception: it stays visible to you alone, it is never included in the shared balance, and our servers enforce that: other members cannot retrieve it even in principle. We may disclose information if required by law, or to protect our rights and users' safety.

5. Retention

• On your device. Your data stays until you delete it, choose "Erase all data" or remove the app. On iPhone, your sign-in can survive removing the app and is restored if you reinstall on the same phone; sign out first if you do not want that.
• When you sign out or delete your account. The app first backs up what must be backed up, then clears its local copy on that phone. Other devices keep theirs until you do the same there.
• Expenses kept on this phone. If you sign in to an account whose household is not the phone's, or a change of household cannot be completed, the app deletes nothing: rows it cannot move stay on the phone, read-only, under "Kept on this phone". They are sent to no server and count in no total. You can export or delete them; signing out and deleting the account do not remove them, only "Erase all data" does.
• Receipt photos. A photo you keep "on this device" exists only on that phone. A backed-up photo stays in your household's storage while its expense exists; when you delete the expense, remove the photo, stop backing it up or make the expense private or shared, the old copy is removed from the cloud, at the latest during a later sync. When the last member leaves a household, or when you erase all data of a household you are alone in, all its photos are removed.
• Device backups. On iPhone and iPad your entries are part of your own iCloud or computer backup, which you manage and we cannot access; receipt photos and price memory are never in it. On Android none of this goes into Google's backup. Those backups follow Apple's or Google's retention, not ours.
• In the cloud. Account data is kept while the account is active. A deleted expense leaves an empty marker on our servers (no amount, merchant or note) so that your other devices and your household delete it too.
• When you delete your account. Your account data is removed from our systems. If another member remains in a shared household, what that household already shared stays available to them; your private expenses are deleted.
• Your private photos when you leave a household. When you leave a household that other members keep, or delete your account while you are in one, your private expenses in that household are deleted from our servers at once, and the app then removes their backed-up photos from the cloud right after. If that is interrupted (no network, app or page closed), it resumes the next time you open SpendWe on the same device or in the same browser, signed in to the same account; until then only you can read those photos. Account deletion waits until it is finished. If it cannot finish (for example the device is lost, the app is removed or the browser's data is cleared before then), write to privacy@spendwe.com and we will delete them.
• Technical records. "Sent once" notification markers are purged after seven days, and those of budget alerts after 62 days (so the same alert is not sent twice in one budget period). The note of a new sign-in is deleted after seven days. AI request counts older than about five weeks are removed the next time you use AI, and all of them with your account; the cost records of AI requests, which carry no account identifier and no content, are deleted after 400 days; the content of AI requests, receipt photos included, is not kept by SpendWe.
• Purchases. The record of your Pro plan (plan, status and the store's or Paddle's references) is kept while your account exists and deleted with it, except the records listed in the next item; Paddle and the app stores keep their own transaction records under their own terms.
• Purchase records that outlive an account. Some purchase records stay after the account is deleted, because they are needed to make sure a purchase is never applied twice and to handle refunds, disputes and accounting: the purchase notifications we receive, stored encrypted; a one-way code of each purchase (not your name, email or payment details); and, for a purchase that could not be applied to an account, its transaction reference, detached from the account. They are used for nothing else. The purchase notifications are deleted 13 months after we receive them, once they have been processed; a transaction reference 13 months after its case is closed (applied or refunded). The one-way code, which no longer points to any account, is kept without an end date, because it is what stops the same purchase from being applied twice.
• Support log. When we act on an account (for example a deletion asked for by email, or Pro granted by our support), a log entry keeps the account identifier, the action and its reason, to show what was done and why. It is deleted after 24 months.
• Unused anonymous identifiers. An anonymous identifier (see section 1) that shows no activity for 12 months is deleted with its data, its cloud receipt photos included, exactly as when an account is deleted. One that holds an active purchase, trial or grant is never deleted this way. An account with an email address is never deleted for inactivity.
• Reports and blocks. When you report a comment or a household member, we keep the reason, a short excerpt (at most 280 characters), the household and the identifiers of the person reporting and the person reported; the report is deleted 12 months after we have handled it, and a deleted account's identifier is removed from it at once. When you report an AI answer, we keep the reason, an excerpt of the answer (at most 500 characters), the app and its version, and a one-way code instead of your account identifier; it is deleted after 90 days. The members you block and your acceptance of the comment rules are kept while your account exists and deleted with it.
• In your browser (web app). The session and the personal items listed under The web app are removed when you sign out; the display choices, the cached exchange rates and the technical records described there stay until you clear the site's data.

Deleting the app from a device does not by itself delete a cloud account - use in-app deletion for that.

6. Your rights & controls

• Access & portability - export a full JSON backup or a CSV spreadsheet any time from Settings. You can also ask us for a copy of the data we hold about you.
• Erasure - delete your account and its data in the app (Settings → Automatic backup), or via our account deletion page.
• Rectification - edit or remove any entry directly in the app.
• Restriction - you can ask us to pause the use of your data in the cases the law provides, for example while a request of yours is being examined.
• Withdraw consent - switch Use AI off, turn off notifications, or leave your household ("Leave household") at any time.
• Objection - you can object to processing we base on our legitimate interests (keeping the service secure, website visit totals); contact us.
• Complaint - you can complain to the data protection authority of your country (see "By country or region" below).

To exercise any right, email privacy@spendwe.com. We answer within one month. We may ask for what we need to check that a request comes from the holder of the account, usually a message sent from the account's email address. If your cloud data is held under an anonymous identifier, we cannot find it from a name or an email address: use the export and deletion controls in the app. Using a right is free and never changes how you are treated.

Giving your email address is optional: without it you can still use the app, share a household and use AI, but you cannot restore your data on a new phone or use the web app. No decision that has legal or similarly significant effects on you is taken by automated means alone; AI results are suggestions that you check.

By country or region

SpendWe is offered worldwide, and the controls above are the same for everyone. Some laws add the following.

• European Economic Area, United Kingdom and Switzerland. The GDPR, the UK GDPR or the Swiss data protection act applies. You have all the rights above, the legal bases are those of section 3, and you can complain to your national authority: the list for the EU and the EEA is on edpb.europa.eu; in the United Kingdom it is the Information Commissioner's Office (ico.org.uk); in Switzerland, the Federal Data Protection and Information Commissioner (edoeb.admin.ch).
• France. The authority is the CNIL (cnil.fr). You can also give instructions about what should happen to your data after your death. A child under 15 needs a parent's agreement for processing based on consent.
• California (United States). In the words of California's privacy law (CCPA), we collect: identifiers (email address, account identifier, device push token, and a random installation identifier in crash reports); the financial entries and other content you create and choose to sync; the receipt photos you back up; purchase records once purchases open; and, for visitors of our website, internet activity in the form of visit totals. We collect them from you and your device, for the purposes of section 2, and disclose them only to the service providers of section 4 and to the household members you choose. We do not sell personal information, we do not share it for cross-context behavioural advertising, and we use no sensitive information for anything other than providing the service. You have the right to know, to delete and to correct your information, and not to be treated differently for using these rights. Use the controls above or email privacy@spendwe.com; an authorised agent may write for you.
• Other US states. If you live in another US state with a consumer privacy law (for example Virginia, Colorado or Connecticut), you have the same rights as above, whether or not that law applies to us; we do not sell your data, do not use it for targeted advertising or profiling, and process no sensitive data beyond what you choose to enter.
• Canada. Under PIPEDA, or the private-sector privacy law of your province where it applies, you can access and correct your information and withdraw your consent. Your information is processed for us by the providers of section 4, in the European Union and the United States, where their local laws apply. You can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca) or your provincial commissioner.
• Australia. Under the Australian Privacy Principles you can access and correct your information. It is disclosed to the providers of section 4, in the European Union and the United States. Write to privacy@spendwe.com first; if you are not satisfied with our answer within 30 days, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au).
• Other countries. You have the rights the data protection law of your country gives you. Nothing in this policy limits rights that the law of the country where you live makes mandatory.

7. Security

Traffic is encrypted with HTTPS. Session tokens are stored in the device's secure storage (iOS Keychain / Android encrypted preferences), never in plain files; in the web app the session stays in your browser as described above, so leave Remember this browser unticked on a shared computer. Cloud data is protected by per-user, row-level access rules so one account cannot read another's data. The apps ship without embedded secret keys - sensitive credentials live only on secured servers. No system is perfectly secure, but we work to protect your information and to limit what we hold in the first place.

8. Children

SpendWe is not directed to children under 13, and we do not knowingly collect their data. Where the law of your country sets a higher age for agreeing to data processing on your own (15 in France; 16 in several European countries, for example Germany, Ireland and the Netherlands), a younger person may use the cloud features only with the agreement of a parent or guardian. If you believe a child has provided us data, contact us and we will delete it.

9. Changes to this policy

We may update this policy as the app evolves. We'll revise the "Last updated" date above and, for material changes, provide a more prominent notice.

10. Who is responsible, and contact

SpendWe is published by an independent app publisher, who decides how and why the personal data described in this policy is used (the "controller", in the words of the GDPR). Questions or requests about privacy: privacy@spendwe.com. General support: spendwe.com/support. The publisher's legal identity and postal address are given on request to an authority, or to anyone who needs them to exercise a legal right: write to privacy@spendwe.com.

Hosting. The website and the web app are hosted by Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA. Account data is hosted by Supabase, in Frankfurt, Germany.