Melbee Privacy Policy
Version 1.0 — Effective 22 June 2026
Last updated: 13 October 2026
Melbee is a family expense-tracking app. This policy covers the Melbee app and website and explains what personal data we process, why, who receives it, and your rights. App-related processing applies when you use the relevant features; visiting the website does not connect your bank accounts. If something is unclear, write to support@melbee.app.
1. Who we are
The data controller is FILANTO INVESTMENTS LTD, a company registered in Cyprus, registration number HE384993 (“Melbee”, “we”). Contact: support@melbee.app. Registered address: Limassol Center, Block B, Floor 4, Flat 406, 2 Riga Feraiou, 3095 Limassol, Cyprus.
2. What we collect and why
| Data | Where it comes from | Why we process it | Legal basis (GDPR Art. 6) |
|---|---|---|---|
| Account data — your name, email address, profile image where provided, and sign-in identifier | You and the sign-in provider you choose, such as Google or Apple | To create and secure your account and contact you about the service | Contract (Art. 6(1)(b)) |
| Bank account and transaction data — account names, balances, transaction amounts, dates, descriptions and provider-assigned categories | Your bank, through a bank-connection provider (see section 4), after you authorise the connection | To show your transactions, balances and spending in the app — this is the core of the service | Contract (Art. 6(1)(b)) |
| Data you enter manually — transactions, tags, notes, wallet names, currency preferences and details of people associated with spending | You | To provide the features you use | Contract (Art. 6(1)(b)) |
| Optional photos — profile or person images you choose to upload | You | To display the image you select | Contract (Art. 6(1)(b)) |
| Shared wallet data — transactions, tags, notes and associated names in wallets you share | You and the members of your shared wallets | To let members see shared spending and make changes allowed by their permissions | Contract (Art. 6(1)(b)) |
| Subscription status — whether you or your household has an active Melbee subscription, the plan, trial and renewal dates, and an anonymous subscriber ID that is not your email address | Apple, through our subscription-management provider RevenueCat | To provide and administer the purchased service, including access for your household and a reminder before a free trial ends | Contract (Art. 6(1)(b)) |
| Household invitations — the email address of a person you invite to your household, and your name | You, when you invite someone | To send that person one invitation email and recognise them when they sign in with that address | Legitimate interest (Art. 6(1)(f)) in letting you invite a household member |
| Technical data — device identifiers and name, OS and app version, IP address, timezone, timestamps and error logs | Your device and our hosting service | To operate the app and website, diagnose faults and prevent abuse | Legitimate interest (Art. 6(1)(f)) in operating a reliable, secure service |
| Notification data — your device’s push-notification token and notification preferences | Your device, if notifications are enabled | To deliver service notifications you have enabled | Contract (Art. 6(1)(b)) |
| Support correspondence — your email address and the information you send us | You, when you email us | To answer you and resolve service issues | Legitimate interest (Art. 6(1)(f)) in assisting users |
| Access requests and waitlist data — your email address, available name, sign-in provider, request details and request status | You, when you join the in-app waitlist or submit the access-request form | To respond to your request and notify you when access is ready | Consent (Art. 6(1)(a)), given by submitting the request; you can leave the in-app waitlist or withdraw a website request by contacting us |
We do not request access to your device’s precise location or contacts, or collect advertising identifiers. Uploading a selected photo does not give us access to your whole photo library. Bank descriptions or information you enter may include names, places or other personal details. Please avoid including sensitive information that is not needed to track your spending. We do not use your data for advertising, and we do not sell it.
Account and financial information are needed to provide the corresponding app features. Photos, sharing and bank connections are optional; you can use manual wallets without connecting a bank. Where we must retain or disclose information to comply with the law, the legal basis is legal obligation (Art. 6(1)(c)). We do not make automated decisions that produce legal or similarly significant effects about you.
3. Optional AI assistance
With your permission, Melbee uses external AI services to help you understand and organise transactions. You can decline and continue using Melbee, including viewing transactions, editing descriptions and categories, and using your saved rules. You can change your choice in Profile → AI assistance. We record your choice, the date and the version of the information you were shown. The legal basis for this optional sharing is consent (Art. 6(1)(a)).
AI assistance helps explain and organise financial information, for example by improving descriptions, suggesting classifications or researching unfamiliar payments. Depending on the feature, we send selected transaction details to external AI and, where relevant, search-service providers. These details may include descriptions, merchant information, amounts, currencies, dates, relevant category labels and context you choose to provide. Descriptions and context may contain personal information. We limit the information sent to what the feature needs; removing some identifiers does not make the remaining information anonymous. Bank-provider information, your own edits and saved rules can also organise transactions without external AI.
Turning AI assistance off stops future AI requests for your data. It does not recall requests already sent, erase existing transaction annotations, or automatically remove information retained by a provider. We do not send bank login credentials to these AI services. External providers process the information under the terms and agreements applicable to the service. Their processing may take place outside the EEA as described in section 6. You can contact us for information about the providers used for your data.
For description cleanup, Melbee stores original descriptions and cleaned results in an internal lookup that can be reused across accounts. The lookup has no direct account link, but a description can still identify a person. Private ledger descriptions use a separate internal lookup. Payment-identification prompts and results are not stored by Melbee as a research history; edits you choose to save become part of the transaction.
AI results can be wrong. Check suggestions before relying on them. We do not make automated decisions with legal or similarly significant effects about you. If we introduce a materially different use of your data, we will provide updated information and obtain any new permission required before that use begins.
4. Bank connections
We do not ask you to give Melbee your online-banking password. Bank connections use third-party account-information providers. Current examples include:
- Salt Edge (for supported banks in the EEA and the UK) — Privacy policy.
- Plaid (for supported banks in the United States) — End-user privacy policy.
The connection flow identifies the provider and any bank authorisation needed. The provider supplies authorised account and transaction data to Melbee. Depending on the service and connection arrangement, a provider may process data on our behalf or act as an independent controller for its own account-information, security or legal purposes. In particular, Salt Edge’s general aggregation policy describes processing on behalf of app developers; separate account-information services may have their own notices. Read the terms and privacy information shown during connection.
You can disconnect a bank in the app to stop further imports. Disconnecting does not itself erase transactions already imported or information the provider must retain under its own obligations. See section 7 for retention and section 9 for deletion requests.
5. Who else receives your data
| Recipient | What they do for us | What they get | Location |
|---|---|---|---|
| Hosting and storage providers | Operate the app, website and data storage | Data stored in the service and technical request information | Main application storage: EU. Other processing may take place outside the EEA |
| Sign-in providers, such as Google or Apple | Authenticate the account you choose to use | Sign-in and verification information; we receive the account details you authorise, which may include a private relay email | Depends on your provider; may include the United States |
| AI and search-service providers | Supply optional assistance described in section 3 | Selected transaction information and relevant context needed for the feature | May include the United States and other countries outside the EEA |
| Apple | Delivers iOS push notifications and, when offered and purchased, processes App Store billing | Notification tokens and delivery content; purchase information for App Store transactions. We do not receive payment-card details from Apple | May include the United States |
| RevenueCat | Manages App Store subscriptions for us and tells us whether a subscription is active | The anonymous subscriber ID, App Store purchase and renewal information, and app and device information its software collects to process purchases. Not your email address or bank data | United States |
| Bank-connection providers | Connect the accounts you authorise (section 4) | Your bank authorisation; they supply account and transaction data | Depends on the provider; may include the EU, UK, Canada and United States |
| Error-monitoring providers | Help diagnose crashes and service faults | Error types, stack traces, app and OS versions, and limited technical context; our reporting is configured to omit account identities and financial payloads | May involve processing outside the EEA |
| Members of your shared wallets | Other Melbee users | Transactions, tags and notes inside that shared wallet, and your display name | Wherever they are |
| Email and support service providers | Deliver communications and help us answer support requests | Technical request data and the correspondence needed for those services | Depends on the provider and service; see section 6 |
| Web3Forms (Web3Creative) | Processes and emails website access requests to us and checks submissions for spam | Your email address, form details and technical request information such as IP address and timestamp | India and its infrastructure providers’ locations, including outside the EEA |
| Authorities, if legally compelled | — | Only what the law requires | — |
These categories describe the services we use; the particular provider can change. Service providers receive data needed for their work. Contact us for details about the recipients of your personal data. Shared-wallet members receive the information you make available through sharing, subject to their role. We do not provide personal data to advertising networks.
6. Transfers outside the EEA
The main application database and file storage are configured in the EU. This does not mean that all provider processing or access stays in the EEA: sign-in, AI assistance, support and bank-connection services may involve other countries.
For transfers subject to the GDPR, the applicable protection depends on the recipient and service: an adequacy decision covering that recipient, or appropriate safeguards such as the European Commission’s Standard Contractual Clauses. The EU-US Data Privacy Framework covers transfers only to participating certified US organisations. Canada’s adequacy decision covers qualifying commercial organisations, not every Canadian recipient. You can contact us for details of the safeguards applicable to your data and a copy where available.
Web3Forms’ Data Processing Agreement incorporates Standard Contractual Clauses for relevant international transfers of form-submission data and identifies its subprocessors.
7. How long we keep data
We retain personal data for the purpose for which it was collected, taking account of your account’s status, unresolved support requests, security needs and any legal retention requirement. The relevant criteria are:
- Account, manual and bank data: kept while needed to provide your account. An in-app deletion request starts a 30-day recovery period before permanent deletion is processed. Sharing access and registered notification devices are removed when the request is made. If you want to exercise an erasure right without that recovery period, contact us. Some records may need to be retained to meet legal obligations, resolve disputes or protect against abuse; this does not permit indefinite retention of all account data.
- Disconnected banks: further imports stop, while historic transactions remain until you delete them or your account. Connection details may be retained temporarily where needed to complete disconnection or resolve a failed provider request.
- Shared wallets: leaving a wallet removes your access but does not automatically erase the shared record, including transactions, notes or associated names. Remaining members may continue to see it. Contact us about personal data you want removed; other members’ rights may also be relevant.
- Description lookup: original descriptions and cleaned results are retained separately from accounts to reuse matching descriptions. Account deletion does not automatically remove these shared entries. You can ask us to erase personal data contained in them.
- Support correspondence and technical records: retained as needed to answer the request, investigate faults or abuse, and meet applicable legal requirements. The type of issue, whether it is resolved and any continuing legal need determine retention.
- AI permission records: current choices and their history are kept with your account and removed when the account is permanently purged, subject to any necessary legal records.
- In-app waitlist: entries remain while we arrange access. Leaving removes the active entry; redeeming an invitation marks it as admitted. Admitted entries are removed when the account is permanently purged. Necessary operational records follow the technical-record retention described above.
- Website access requests: retained while we handle your request and arrange access, or until you withdraw the request, subject to any necessary legal records. Web3Forms’ privacy policy states that submission data may be retained for up to three years unless deleted earlier. Email copies are also held in our inbox. Contact us to withdraw your request or ask for deletion from these records.
- Subscriptions and invitations: subscription status is kept while your account exists and removed when it is permanently purged; RevenueCat keeps purchase records under its own retention terms. A household invitation is kept until it is accepted, declined or withdrawn, and removed when the inviting account is purged.
- Backups: copies may remain until replaced or expired under the backup process. Backup retention is separate from live-system deletion; backups are used for recovery rather than ordinary access to deleted accounts.
8. Security
We use encrypted connections, encrypted application storage and access controls to protect personal data. No system is perfectly secure. If a personal-data breach requires notification under applicable law, we will notify the relevant authority and affected people as required.
9. Your rights
Under the GDPR, subject to its conditions and exceptions, you can request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting processing already lawfully carried out.
You can disconnect banks or request account deletion in the app. For access, a portable copy or other requests, email support@melbee.app. We may need proportionate information to verify your identity. We respond without undue delay and normally within one month; if the GDPR permits an extension for a complex request, we will explain it within that first month.
You can complain to the Office of the Commissioner for Personal Data Protection, Cyprus or your local data protection authority.
US residents: we do not sell personal data or share it for cross-context behavioural advertising. You can contact us to request access, correction or deletion, regardless of whether a particular state privacy law applies. Where applicable state law provides additional rights, such as portability or an appeal of our response, you may exercise them through the same address. We will handle requests within the applicable legal deadlines and will not discriminate against you for exercising your rights. Authorised agents may contact us; we may need to verify their authority and your identity.
10. Children
Melbee accounts are for people aged 18 and over. We do not knowingly allow children to create accounts. Adults may enter information about household spending that relates to children; that information is covered by this policy. Please enter only what is necessary and consider what other shared-wallet members will see. If you believe a child has created an account or that we hold children’s information we should not have, contact us so we can investigate and remove it where appropriate.
11. Cookies and the website
Our website does not set analytics or advertising cookies and does not use advertising trackers. The hosting service may process technical request information, such as IP addresses and access logs, to deliver and secure the site. Any storage strictly necessary for a service you request is used only for that purpose.
When you submit the access-request form, your email and request are sent through Web3Forms to our inbox. Its service also processes technical information to deliver the request and prevent spam. We use the request to respond to you and send access-related emails, not to enrol you in an unrelated marketing newsletter. You can withdraw your request at any time by emailing support@melbee.app. Joining the in-app waitlist stores your verified sign-in email, any available display name, sign-in provider and join date in Melbee’s backend. Joining does not grant access to the app. You can leave the waitlist from the invitation screen, which removes the entry; when you redeem an invitation we mark it as admitted. Waitlist requests are for access-related communications, not unrelated marketing.
Clicking a contact email link opens your email application; we receive the information you choose to send in that email.
We do not track visitors across third-party websites for advertising, and do not change that practice in response to a browser’s Do Not Track signal.
12. Changes
We publish updates on this page and change the “Last updated” date. For material changes affecting account holders, we will provide an appropriate notice, such as email or an in-app notice, before the change takes effect where required. Previous versions are available on request.