Αυτό το έγγραφο δημοσιεύεται προς το παρόν μόνο στα αγγλικά. Δεσμευτικό είναι το αγγλικό κείμενο: Διαβάστε την αγγλική έκδοση
Surplus — Privacy Policy (v2.0)
Effective Date: 29 October 2026
Last updated: 15 November 2026
Controller: GGkas Sàrl-S, 12 Rue de la Gare, L-3377 Leudelange, Luxembourg
RCS: B279432 · EU VAT: LU35348364
Contact (privacy & rights): support@surplus-app.com
This Privacy Policy explains how we collect, use, share, and protect your personal data when you use:
- the Surplus apps for iOS, Android and web (my.surplus-app.com),
- our website surplus-app.com and its subdomains.
“Surplus”, “we”, “us”, or “our” refers to GGkas Sàrl-S.
We comply with the EU GDPR and Luxembourg law, and with UK-GDPR where applicable. If this Policy conflicts with mandatory local law, the latter prevails.
1) Summary
- Surplus forecasts your household’s money from the balances and plan you enter. We never ask for your bank login and do not connect to your bank.
- CSV and Excel statements you import are read on your device. PDF import is switched off; if we enable it, an uploaded PDF is parsed on our EU server and deleted after parsing (see §4). Only the normalised transactions are stored, for 24 months from import.
- AI classification (Surplus Plus) is off unless the household owner switches it on. Then the names of the shops and companies the app could not categorise on your device are sent, without amounts, dates or account details, to Google Cloud Vertex AI in the EU, where Anthropic's Claude model suggests a category. We do not keep the names after the answer, and Vertex AI keeps a request only if Google's automated abuse checks flag it, then for up to 90 days in the EU (see §4).
- Your household data and your profile are stored in Google Cloud/Firebase in europe-west1 (Belgium).
- Some of our providers process some of your data in the United States: Google (your sign-in details, and technical data such as crash reports and server logs), Resend (the emails we send you) and RevenueCat (your subscription status). See §8 and §10.
- If you share a household, the other members can see that household’s data according to their role (see §9).
- We email you about your account, your subscription and your household (see §4). Household emails can be turned off, and the Month ahead email of Surplus Plus is sent only if you turn it on. We do not keep your email address in our database for this.
- No ads, no ad tracking, no sale of data.
- Subscriptions (Surplus Plus) are bought through the Apple App Store or Google Play; entitlements are managed by RevenueCat. We do not process card details.
- You can download a copy of your data and delete your account in the app. You can also email us for a copy, or for any other request.
- Minimum age is 16.
2) Who we are & how to contact us
Controller: GGkas Sàrl-S (Luxembourg), 12 Rue de la Gare, L-3377 Leudelange
Email: support@surplus-app.com
No Data Protection Officer (DPO) is appointed; this is not legally required given our size and processing. We reassess periodically.
Supervisory authority: Commission nationale pour la protection des données (CNPD), Luxembourg. You may also complain to your local authority in the EEA/UK.
3) Scope
This Policy covers the Surplus apps, the surplus-app.com website, and the backend services, support channels and mailings that go with them. It does not cover third-party sites or the app stores, which have their own policies.
4) What we collect
- Account & profile — name (optional), email, sign-in provider and authentication UID (Google, Apple, or email link), language, notification and email preferences, and your choices on crash reports and usage analytics, with the version of this notice they were given for and when you made them.
- Household data you enter — household name and settings; accounts (current, savings, card) with balances and card terms; income and scheduled payments; day-to-day budgets; one-off items; savings and purchase plans; checkpoints; notes; member list and roles. We also keep the household's activity log, which only our backend can read: a note when an invitation is created or used and when the owner hands the household to another member (who, for which role or to whom, and when; never an email address).
- Imported transactions — CSV and Excel statements are parsed on your device and the original file is not uploaded. We store only the normalised transactions (date, amount, description, category) and your categorisation rules. PDF import is switched off. If we enable it, household owners and editors on Plus can upload a PDF: it is uploaded to our server in the EU, parsed there and deleted after parsing; only the normalised transactions are kept. While it is off, an uploaded PDF is deleted on arrival.
- AI classification (optional, Surplus Plus) — off by default. If the household owner switches on Classify with AI in the app's settings, then each time a statement is imported into that household, the merchant names the app could not categorise on your device are sent to our server in the EU, which passes them to Google Cloud Vertex AI in the EU, where Anthropic's Claude model suggests a category for each. Each name is sent as the app cleaned it (card numbers, dates, places and company legal forms removed), with only whether money came in or went out and the household's country. We never send amounts, dates, account numbers (IBANs), account, household or user identifiers, or lines that look like a transfer between the household's own accounts or a payment to or from a person. The app cannot always tell a person's name from a business name, so the model is also told to give no category for a name that could belong to a private person. A merchant name can still say something about the household (for example a pharmacy or a doctor's practice); that is why this is off unless the owner switches it on. The names are used only to return the categories, and they are not used to train AI models. We do not keep them after answering. Vertex AI does not keep them either, unless Google's automated abuse checks flag a request: Vertex AI then keeps that request for up to 90 days, stored in the EU; authorised Google staff may review it to check that the service is not misused. The suggested category is stored on the transaction, marked as suggested by AI, and owners and editors can change it; a merchant once answered is not sent again. To apply a daily limit, we keep a count of the names sent for each household and day (a number, no names). The owner can switch AI classification off at any time; categories already suggested stay until someone changes them.
- Invitations — an invitation record: the household, the role offered, who created it, when it was created and expires, and who used it and when. In the app, you can share an invitation yourself as a link (or QR code), which gives us no email address for the invitee, or enter the invitee's email address so that we email the invitation for you. We use that address only to send that one email and do not keep it in our database. To stop invitations being misused, we limit them to 3 emails per address and 20 per member a day: for this we keep only a count under a keyed one-way hash of the address, never the address itself (see §11).
- Reminders — your reminder settings and the scheduled reminder records needed to send them (push notifications; device push token). You get at most one reminder notification a day for each household you belong to. By default its text says only what there is to do and how many things, and how many days until a payment is due, without amounts, calendar dates or account names. Amounts, dates, and account and item names appear in it only if you turn on Show amounts in notifications in the reminder settings. The text of each push is delivered to your device by Apple's push service (iOS), Google's (Android, Firebase Cloud Messaging) or your browser's push service (web app), and it can appear on your lock screen (see §9 for who these services are). Our reminder records never contain amounts.
- Service emails — we email you about your account (a welcome email, sign-in links, and a confirmation when you delete your account), your Surplus Plus subscription (when it starts, when a trial or Plus is about to end, before an annual renewal, a billing problem, when it ends or is refunded, a household losing Plus because the person paying left, and any price increase) and changes to our terms or this Policy. These are part of the service and cannot be turned off. Household emails tell you about a household you belong to: someone joined, your role changed or you were removed, you became the owner, or the household was deleted. They are on by default and you can turn them off in the app's settings or with the link in each one. The Month ahead email (Surplus Plus) is a summary of the month to come on payday, sent only if you turn it on. We read your email address from your sign-in account when we send (for a sign-in link, from the address you enter), and do not store it in our database. The email is in your app language. Like reminders, an email shows amounts only if you turned on Show amounts in notifications, and a subject line never shows a balance. For each email sent to your account we keep a send log: which email, when, and the message id from our email provider, never the address or the content (see §11). Sign-in links and the email confirming your account deletion are not logged.
- Subscription — your subscription status (Plus or Free, expiry, source store) and purchase identifiers from RevenueCat, the App Store or Google Play. We do not receive your card or payment details.
- Crash reports — only if you consent: app and OS version, device model, crash reports and stack traces (Firebase Crashlytics, iOS and Android only; the web app sends none). Crash reports do not contain amounts or descriptions.
- Usage analytics — only if you consent: a limited set of events (e.g., which screen or feature was used) via Firebase Analytics, and the approximate location (such as the country or city) that Google Analytics derives from your device's masked IP address. Firebase Analytics may also record, by itself, your purchases and renewals of Surplus Plus in the App Store or Google Play, with the product, its price and currency. Apart from those purchases, events never include amounts, names, descriptions, or a user or household identifier.
- Security & logs — IP address and standard server logs; App Check attestation tokens (Play Integrity, Apple App Attest, reCAPTCHA Enterprise in the web app) used to ensure requests come from genuine apps. Our backend logs record identifiers only, not financial content. Sign-in audit: when someone tries to sign in with an email address that has no Surplus account, we keep one record per address with a keyed hash (HMAC) of the address, the email domain in plain text, the platform (iOS, Android or web), one-way hashes (SHA-256) of the IP address and of the browser or app user-agent, a count, and the first and last time seen. Hashed IP counters limit how often sign-in attempts are recorded.
- Newsletter — email address, the language of the page you subscribed from, and a record of your consent and confirmation (double opt-in), when you subscribe on our website (see §15).
- Support — emails you send to support@surplus-app.com.
- Beta feedback — if you test a beta version and fill in our feedback form (Google Forms): your answers (device type, who shares money in your household, ratings, free-text comments, the parts of the app you used) and, only if you choose to give it, an email address so we can contact you about your answers. The form does not collect your email address automatically and does not require you to sign in.
We do not intentionally collect special-category data nor data about children under 16. Free-text fields (notes, descriptions) are yours; please do not enter sensitive data there.
5) Sources
- You (data you enter, import or share).
- Other household members (data they add to a household you belong to).
- Your device (diagnostics).
- App stores and RevenueCat (subscription status).
6) Purposes & lawful bases
| Purpose | Examples | Lawful basis |
|---|---|---|
| Provide the service | Sign-in, storing and forecasting your household data, sharing with members, reminders | Contract (Art. 6(1)(b)) |
| Service emails | Account, sign-in, subscription and policy emails (see §4) | Contract (Art. 6(1)(b)), including the notice of a price increase (Terms §4); Legal obligation (Art. 6(1)(c)) for a notice of a material change to this Policy |
| Household emails | Telling you that someone joined a household you share, that your role changed or you were removed, that you became the owner, or that the household was deleted | Legitimate interests (Art. 6(1)(f): keeping members informed of changes to a household they share); on by default, and you can turn them off at any time |
| Month ahead email (Surplus Plus) | A summary of the month ahead on payday | Consent (Art. 6(1)(a)), given by turning it on; withdrawable in the app or with the link in each email |
| Invitations | Emailing the person you invite | Legitimate interests (the invitee is not a party to the contract; one email, no profiling) |
| Automatic backups (optional) | Sending a copy of the household to your own Google Drive | Contract for your own data; Legitimate interests for other members' entries (a member keeping a copy of a household they can already see and export) |
| Subscriptions | Verifying entitlement, applying Plus to a household | Contract + Legal obligation |
| AI classification (optional, Surplus Plus) | Suggesting a category for the merchant names the app could not categorise (see §4) | Consent (Art. 6(1)(a)) of the household owner, given by switching it on and withdrawable at any time in the app's settings; for the lines other members imported into the household, Legitimate interests (Art. 6(1)(f): categorising the household's own transactions, with only cleaned merchant names sent and nothing kept by us; Google's abuse checks may keep a flagged request, see §4), and you may object |
| Security & abuse prevention | App Check, rate limits, logs, sign-in audit | Legitimate interests (protecting accounts and the service) |
| Crash reporting | Crashlytics (iOS, Android) | Consent (Art. 6(1)(a)), withdrawable in Settings → Privacy |
| Product analytics | Firebase Analytics events | Consent (Art. 6(1)(a)), withdrawable in Settings → Privacy |
| Newsletter | Product updates | Consent (Art. 6(1)(a), double opt-in) |
| Newsletter consent record | Keeping the record of your consent and opt-out after you unsubscribe | Legitimate interests (Art. 6(1)(f): being able to prove consent and honour the opt-out) |
| Newsletter abuse protection | Sign-up rate limits, hidden bot field | Legitimate interests (stopping abuse of the form and of other people's email addresses) |
| Support | Answering your emails | Legitimate interests |
| Beta feedback | Improving the app from testers' answers | Legitimate interests (Art. 6(1)(f)) |
| Beta feedback contact | Contacting you about your answers, if you left an email address | Consent (Art. 6(1)(a)), withdrawable by email at any time |
| Legal & accounting | Records we must keep | Legal obligation |
Forecasts and figures about your household. Providing the service means analysing the data entered in your household (balances, plan, imported transactions) to forecast its balances and to show figures about it, such as how the plan splits into needs, wants and savings. Data protection law calls an analysis of a person's economic situation profiling. We do it only to show these figures to you and the other members of the household, on the basis of the contract: the app does it on your device, and our servers in Belgium do it to prepare your reminders (see §4). We do not use it to assess you for anyone else, for advertising or for marketing, and no decision with legal or similarly significant effects on you is made by automated means. The figures are estimates, not advice (Terms §2).
Where we rely on legitimate interests, we balance them against your rights and you may object.
7) Cookies and similar technologies
- The apps use local storage on your device for sign-in and offline data. Analytics and crash-reporting identifiers are used only with your consent.
- The web app (my.surplus-app.com) uses Google reCAPTCHA Enterprise for App Check, to verify that requests come from the genuine app (security, see §6). It reads browser and interaction signals and may set Google cookies for that purpose only.
- The website uses no advertising or analytics cookies and loads no third-party tracking or anti-bot scripts.
- We do not use advertising SDKs, ad identifiers or cross-site tracking.
8) Where we process & store data
- Primary storage: Google Cloud/Firebase europe-west1 (Belgium) for your household data and your profile (your name, language, settings and privacy choices).
- Optional PDF uploads and data export files are kept in Cloud Storage for Firebase in europe-west1 (Belgium) (see §11).
- AI classification (optional): our server in europe-west1 (Belgium) sends the merchant names to Google Cloud Vertex AI in the EU (its EU multi-region endpoint), which runs Anthropic's Claude model for us under Google's data processing terms for Google Cloud. Vertex AI processes the names in the EU and stores a request Google's abuse checks flag there (see §4).
- Google: Google's sign-in service, Firebase Authentication, keeps your sign-in details (your email address, the sign-in provider, your user ID, and your name if your sign-in provider gives it) in the United States. The other Google services we use run on Google's global infrastructure, so Google may process their data in any country where Google or its sub-processors have facilities, including the United States: crash reports (Crashlytics), usage analytics (Google Analytics), push notifications (Firebase Cloud Messaging), app attestation (App Check, and reCAPTCHA Enterprise in the web app), app configuration (Remote Config), web hosting (Firebase Hosting), our server logs (Cloud Logging), and support email and the beta feedback form (Google Workspace). Google lists where its Google Cloud regions and its data centres are (Google Cloud locations and Google data centre locations), and Google's sub-processors may have facilities in other countries too. Google's transfers to the United States are covered by Google's certification under the EU-U.S. Data Privacy Framework, which the European Commission has found adequate (Art. 45 GDPR), and its UK Extension. Where the framework does not apply, Google's transfers are covered by the EU Standard Contractual Clauses in Google's data processing terms for Firebase, for Google Cloud and Google Workspace and for Google Analytics (Art. 46(2)(c) GDPR).
- Email: our email provider Resend sends our emails (sign-in links, the service and household emails in §4, the Month ahead email, household invitations and the newsletter) from the EU (Ireland). It stores everything it keeps about them (see §11), including the recipient's address, the message and its logs of sending them, in the United States. This transfer is covered by the EU Standard Contractual Clauses in Resend's data processing agreement (Art. 46(2)(c) GDPR), with the UK Addendum for transfers from the UK, and by Resend's certification under the EU-U.S. Data Privacy Framework, which the European Commission has found adequate (Art. 45 GDPR), and its UK Extension.
- Subscriptions: RevenueCat, which manages Surplus Plus in the iOS and Android apps, keeps your Surplus user ID, your purchase identifiers and receipts and your subscription status in the United States. This transfer is covered by the EU Standard Contractual Clauses in RevenueCat's data processing addendum (Art. 46(2)(c) GDPR), with the UK Addendum for transfers from the UK.
9) Sharing & recipients
Household sharing. A household can have several members (owner, editors, viewers). Every member can see the household’s data (accounts, balances, plan, imported transactions); editors and owners can change it. Members see each other’s name/email as shown in the member list. The owner controls invitations and roles. If you leave a household, you lose access to it; the household’s data stays with the household. Before you add someone, make sure they should see this information.
Other recipients. We do not sell your data and do not share it for cross-context behavioural advertising. We disclose data to:
- Processors acting on our instructions: Google Cloud/Firebase (including Google Cloud Vertex AI for AI classification, only if the household owner switches it on), RevenueCat, Resend (email: sign-in links, the service and household emails, the Month ahead email, household invitations and the newsletter), Google Workspace (support mail; the beta feedback form and its responses in Google Forms and Google Sheets). Sign-in links are sent by Resend; Google (Firebase Authentication) sends them instead only if our own sending is switched off or fails. Reminders are push notifications sent through Firebase Cloud Messaging, which also delivers them on Android. See /subprocessors.
- Independent controllers: Apple and Google (App Store / Google Play purchases, and sign-in if you choose Apple or Google). Push delivery: on iOS, Apple's push service, and in the web app, your browser's push service (for example Apple for Safari, Mozilla for Firefox, Microsoft for Edge; Chrome uses Google's Firebase Cloud Messaging) deliver reminder notifications to your device under their own terms. They receive the push token and the notification text (with amounts only if you turned them on, see §4). Update checks: when you open the app, and when you come back to it at most every 6 hours, the app asks whether a newer version is available. On iOS it asks Apple's App Store lookup service, which receives your device's IP address, the app's identifier and the country of your device's region setting (to pick the App Store country). On Android it asks Google Play's in-app update service on your device, which checks with Google Play under your own agreement with Google; if you accept, Google Play downloads the update. We send them no account, user or household identifier of ours, and we receive only whether a newer version exists. In the web app, the check asks our own hosting (Firebase Hosting) which version is live, and nothing goes to a third party.
- Your own Google Drive (optional, Surplus Plus): if you turn on Automatic backups, a copy of the household's data, with what other members added, your own profile, your own reminder records and your Surplus Plus subscription record if you have one, goes to your Google account about once a week, into a folder named "Surplus backups". Each backup is the same export as Back up my data: we prepare the file in Cloud Storage (kept as set out in §11), and your device downloads it and uploads it to Google Drive. Google is then an independent controller of that copy under your own agreement with Google. We use the limited Google Drive "drive.file" permission, which covers only the files Surplus creates: we cannot see anything else in your Drive. The access token stays on your device and never reaches our servers. Our use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Any member can turn this on, and their copies stay in their Drive after another member leaves or deletes their account, so tell the other members first.
- Authorities, where required by law or to protect rights, safety and security.
- Corporate transactions: in a merger, acquisition or asset sale, subject to continued protection.
10) International transfers
Google, Resend and RevenueCat process some personal data in the United States, and Google may also process some in other countries where it has facilities; §8 says which data and under which transfer tools. Where processing involves a country without an EU/UK adequacy decision, we use Standard Contractual Clauses (SCCs) and, where applicable, the UK IDTA/Addendum, plus supplementary measures. Google and Resend are also certified under the EU-U.S. Data Privacy Framework, which the European Commission has found adequate. Contact us for details.
11) Retention
- Account & profile: for the life of your account; erased within 30 days of deletion (cleanup starts as soon as you delete the account).
- Household data (accounts, plan, items, activity log): until the household is deleted: by its owner in the app, or when its last member deletes their account (see §13).
- Imported transactions: 24 months from import, then deleted automatically.
- Uploaded PDFs (optional import): deleted after parsing; an hourly check deletes any upload left unprocessed.
- AI classification (optional): we do not keep the merchant names sent after the answer. Vertex AI does not keep them either, unless Google's automated abuse checks flag a request: Vertex AI then keeps that request for up to 90 days in the EU. A suggested category is kept with its transaction. The daily count of names sent for a household (a number) is deleted automatically about 2 days later.
- Data export files (the household's data, your profile, your own reminder records and your Surplus Plus subscription record if you have one, see §13): each file is deleted automatically about 24 hours after it is created (checked every hour), or earlier when you make a new export. If you delete your account, the file is deleted with it (within 2 hours at the latest). The download link is valid for 15 minutes.
- Reminder records: 30 days.
- Sign-in audit: 30 days after the last recorded attempt, deleted automatically. Hashed IP counters: 1 hour.
- Newsletter: confirmed subscriptions until you unsubscribe. After you unsubscribe we keep your address marked as unsubscribed, with the consent history, to prove your consent and honour the opt-out, and delete it 3 years after you unsubscribe. Sign-ups never confirmed are deleted 30 days after the request (the confirmation link itself expires after 7 days). Both deletions are automatic and can lag the date by up to a few days. Sign-up rate-limit counters (hashed): 1 hour (per network address) or 24 hours (per email address), deleted automatically. Our email provider Resend keeps each email it sends you (the confirmation email, the one-time re-confirmation email and each newsletter issue, with your address) and its logs of sending them for 30 days. If an email to you is permanently rejected or marked as spam, Resend keeps your address on its suppression list, so that no further email is sent to it. It stays there with no time limit until we remove it, which you can ask us to do (see §13). Resend's backups keep a copy of these emails, their logs and any suppression entry for up to 7 days after Resend deletes them.
- Invitations: an invitation expires after 7 days; the invitation record is deleted about 37 days after it was created, or earlier with its household. The record holds no email address. An address given to send an invitation by email goes only to our email provider Resend, to send that email (see §9), and is not stored in our database. The count of invitation emails per address (under a keyed one-way hash, HMAC-SHA-256, of the address) and per member counts only over 24 hours and is then deleted automatically, at the latest about 48 hours after the first invitation it counts. Resend keeps that email (the address and the message) and its logs of sending it for 30 days. If the email is permanently rejected or marked as spam, Resend also keeps the address on its suppression list, so that no further email is sent to it. It stays there with no time limit until we remove it, which you can ask us to do (see §13). Resend's backups keep a copy of that email, its logs and any suppression entry for up to 7 days after Resend deletes them. The household's activity log keeps its note of the invitation until the household is deleted.
- Service emails: the send log of each email (which email, when, and the message id) is deleted automatically 90 days after the email is sent, or earlier with your account. Your email preferences are kept with your profile. Our email provider Resend keeps each service email it sends you (your address and the message) and its logs of sending it for 30 days. If an email to you is permanently rejected or marked as spam, Resend keeps your address on its suppression list, so that no further email is sent to it. It stays there with no time limit until we remove it, which you can ask us to do (see §13). Resend's backups keep a copy of these emails, their logs and any suppression entry for up to 7 days after Resend deletes them.
- Crash reports: 90 days.
- Server logs (incl. IP): 30 days.
- Analytics data: 2 months (event-level data).
- Backups: we keep no database backups.
- Automatic backups in your Google Drive: Surplus keeps the last 4 copies of each household and moves older ones to your Drive trash. The copies are in your account, so we cannot reach them for you: turning the feature off, signing out, leaving or deleting a household, or deleting your Surplus account does not delete them, and neither does another member deleting their account. Delete them yourself in Google Drive. You can remove Surplus's access at any time in your Google Account settings.
- Support emails: 24 months after last contact.
- Beta feedback: 12 months after you submit the form, then deleted from Google Forms and Google Sheets. If you withdraw your consent to be contacted, we delete your email address from your answers.
- Data-subject request records: 3 years.
- Subscription records: as long as required for tax/audit (up to 10 years), held by the stores and RevenueCat.
- Subscription notices after you delete your account: if RevenueCat sends us a notice about your subscription after you have deleted your account (for example a renewal), we do not store anything about you again. We keep only the notice's id, its type and when it happened and arrived, so that it is not handled twice, and delete that automatically about 90 days after it arrives.
We may retain minimal data to comply with legal obligations, resolve disputes and enforce agreements.
12) Security
We apply technical and organisational measures including: encryption in transit and at rest; Firestore security rules enforcing household membership and roles; App Check on our backend; least-privilege access with MFA for admin accounts; no secrets in code; logging of identifiers only; incident response with GDPR notification (authorities within 72 hours where required; affected users without undue delay).
No system is perfectly secure.
13) Your rights
Under GDPR/UK-GDPR you can access, rectify, erase, restrict or object to processing, port your data, withdraw consent at any time, and lodge a complaint with a supervisory authority.
- Export: in the app under Settings → Privacy → Back up my data, any member can download a copy (JSON) of the current household's data (without its activity log), their own profile, their own reminder records in that household (see §11) and their Surplus Plus subscription record, if they have one (a record stays after a subscription or trial ends); if you belong to several households, do it in each one. The file is kept as set out in §11. You can also email us and we send you a copy of your data (JSON).
- Deletion: in the app under Settings → Account → Delete account, or by email. Deleting your account removes your profile, your memberships and your reminder settings. A household where you are the last member is deleted with all its data. In a shared household the data stays with the household for its other members, including what you added; if you were the owner, ownership passes automatically to the longest-standing editor, or otherwise to the longest-standing member. The owner of a household can delete it as a whole, for every member, in the app under Household → Delete household, or ask us by email. It is deleted at once with all its data and invitations, and its members are told by email unless they turned household emails off. A Surplus Plus subscription attached to it is not cancelled: it stays with the person paying, who can attach it to another household. In the activity log of every household you belonged to, including ones you left earlier, the entries that name you (who sent or accepted an invitation, who passed ownership and to whom) then name "a deleted user" instead; the rest of each entry stays. Our backend starts the cleanup as soon as you delete your account, and it completes within 30 days. Copies that Automatic backups put in your own Google Drive are not deleted with your account (see §11). Deleting your account, or the app, does not cancel a Surplus Plus subscription: cancel it in your App Store or Google Play account settings (see Terms §4).
- Other requests: email support@surplus-app.com. We respond within one month (extendable by two months for complex requests). We verify identity via your signed-in account or email match; we do not generally require photo ID.
14) Children
Surplus is intended for users 16+. We do not knowingly collect data from children under 16. If you believe a child has used Surplus, contact us and we will delete the account.
15) Marketing & newsletter
We send newsletters only with your explicit double opt-in, and you can unsubscribe at any time (link in every email). Service messages are not marketing: sign-in links, invitations, push reminders you enabled, the account, subscription and household emails, and the Month ahead email if you turned it on (see §4).
Newsletter. You can subscribe to occasional news about Surplus with the form on surplus-app.com.
- What we collect: your email address; the language of the page you subscribed from (English, French, German, Luxembourgish or Greek; other languages are recorded as English); and a consent record: when you submitted the form with the consent box ticked, where you subscribed (our website, or our one-time re-confirmation email described below), when you confirmed and, if you unsubscribe, when.
- Purpose and lawful basis: to send you the newsletter, based on your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by unsubscribing; this does not affect sending that took place before. After you unsubscribe we keep the consent record on the basis of our legitimate interests (Art. 6(1)(f)), so that we can show you agreed and honour your opt-out.
- Double opt-in: after you submit the form we email you a confirmation link. You are subscribed only after you open the link and press Confirm subscription. The link is valid for 7 days. If you do not confirm, you receive no newsletter.
- Subscribers from the previous version of our website: if you subscribed there, we have no record that you confirmed your subscription. We email you once in the language you subscribed in and ask whether you want to keep receiving the newsletter, and we send you no newsletter until you confirm. If you confirm, the time of your confirmation is recorded as your consent. If you do not confirm, your address is deleted 30 days after that email. Lawful basis for this one email: legitimate interests (Art. 6(1)(f): asking people who subscribed before whether they still want the newsletter, instead of either mailing them without proof of consent or deleting them without asking).
- Abuse protection: the form has a hidden field that filters out bots, and we limit sign-ups to 10 per hour per network address and 3 per day per email address. For this we store only one-way hashes (SHA-256) of your IP address and email address, deleted automatically after 1 hour or 24 hours. Lawful basis: legitimate interests (stopping abuse of the form and of other people's email addresses).
- Where it is stored and who processes it: subscriptions are stored in our database (Google Cloud Firestore, europe-west1, Belgium), which only our backend can read. We send the confirmation email and each newsletter issue through Resend, from news@surplus-app.com, as a separate email to each subscriber. Resend sends them from the EU (Ireland) and stores them, with your address, in the United States (see §8). Resend receives your address with each email it sends you, and we do not keep a subscriber list at Resend. We will update /subprocessors before any other provider sends the newsletter.
- Unsubscribe: every newsletter email, including the confirmation email, has an unsubscribe link, and mail apps that support it show a one-click unsubscribe button. You can also write to support@surplus-app.com. Unsubscribing takes effect immediately. To subscribe again you must give your consent again.
- Retention: see §11.
16) UK users & representative
If and when Article 27 UK-GDPR requires a UK representative, we will update this Policy before commencing the relevant activities. Until then, UK users can contact us directly.
17) Changes to this Policy
We may update this Policy to reflect changes in law, technology or our services. For material changes we will give reasonable notice (email, in-app or banner).
18) Contact & complaints
- Contact us: support@surplus-app.com
- Supervisory authority (Luxembourg CNPD): you may lodge a complaint with the CNPD or your local authority.