● Legal
Privacy Policy
Last updated 10 October 2026 · Effective 10 October 2026
This policy explains what SplitChamp collects, why it is collected, who else processes it, how long it is kept, and how to get it deleted. SplitChamp is a shared-expense app: it records who paid what within a group and works out who owes whom.
Contents
1. Who we are
SplitChamp is built and operated by Adel Ashraf Hamouda and Ahmed Tarek, trading together as beanvoid ("we", "us"), a product studio based in Egypt (see beanvoid.com). For data protection purposes we are jointly the controllers of the personal data described below.
Contact: support@beanvoid.com. Write to us there for anything in this policy, including requests about your data; we will give a postal address on request.
2. What we collect
| Category | What exactly | Where it comes from |
|---|---|---|
| Account | Your email address, your display name, and the account identifier your sign-in provider gives us. On iOS you can sign in with Apple instead of Google, and if you choose Hide My Email, the address we hold is the forwarding one Apple gives us, never your own. | Google or Apple when you sign in; your display name if you change it in the app |
| What you create in the app | Groups and their members, expenses (amount, currency, description, category, notes, date, who paid, how it is split), settlements you record (amount, date, an optional note, and the name of the payment method used), currency conversions between balances (the two amounts only; the exchange rate you type is used once and not stored), recurring expense rules and the time zone your phone reports when you create one (so a rule runs on the right local date), invite codes and the email addresses you use to invite people. | You and the people in your groups |
| How you can be paid | One payment method, if you choose to add one: its type, the identifier you type (an IBAN or bank account number, a phone number, a crypto wallet address, or one you name yourself), and the name you give it. Cash takes no identifier. See section 5. | You, only if you add one |
| Sign-in state | Session records so the app can keep you signed in. Refresh tokens are stored only as a one-way hash, never in a readable form. | Created by us |
| Technical logs | IP address, request time, endpoint, response status and error details, produced when the app talks to our servers and by the security layer in front of them. | Automatic |
Receipt photos stay on your phone. When you scan a receipt, the app reads its text on your device to find the total, then deletes the photo. Neither the photo nor its text is sent to us; only the expense you choose to save is.
We do not collect your Google password, contacts, calendar, photos or location, and we do not ask Google for anything beyond your basic profile and email address. We do not use advertising trackers, and the only diagnostics are the ones Google ML Kit sends when you scan a receipt (see section 6). We never ask for a card number, a CVV, a bank login or any other credential, and no money moves through SplitChamp. The one payment detail we hold is the identifier you choose to publish to your groups, described next.
3. Why, and our legal basis
- To run the service: create your account, show your groups, calculate balances and settlements. Legal basis: performance of a contract with you.
- To keep the service secure and working: abuse and rate-limit protection, error diagnosis (including the diagnostics Google ML Kit sends, see section 6), backups, and enforcing our Terms, including reviewing content reported to us. Legal basis: legitimate interests in keeping a service available, correct and safe.
- To answer you when you email support, looking at the relevant account or group data only as far as needed to help. Legal basis: legitimate interests in responding to enquiries.
- To meet legal obligations where they apply. Legal basis: legal obligation.
We do not sell personal data, and we do not use it to profile you or to target advertising.
4. Data about other people
When you invite someone by email, we store that email address so the invitation can be matched to them when they sign in, and so their share of expenses can be tracked in the meantime. Only invite people who expect to be in the group. If someone would like their address removed before they ever sign in, email us and we will remove it.
Anyone in a group can see your display name, the group's expenses, who paid, how each expense is split, and the balances and settlements that follow from it. That is the point of a shared ledger, so treat what you put in a group as visible to that group.
5. How you get paid
You can add one payment method to your profile so that someone settling up with you knows where to send the money. It is optional: SplitChamp works without it, and you can remove it at any time from You → Payment method.
If you add one, understand who sees it:
- Everyone you share a group or a friendship with can see and copy the identifier you typed. That is what it is for: the app shows it to the payer at the moment they settle up, and tells you so before you save.
- It is not public, not searchable, and not shown to anyone outside your groups.
- We store it as you typed it, so that the payer can copy it exactly. We do not verify it, check that the account exists, or use it ourselves.
- When someone records a settlement, we keep the name of the method they chose (“Bank transfer”) alongside that payment, so the group's history says how it was paid. The identifier itself is never copied into that record.
Because you are handing it to real people, put in only an identifier you are content for them to have, and keep it current. The Terms explain what happens if a payment goes to the wrong place.
6. Who else processes it
We keep the list of processors deliberately short:
| Processor | What for |
|---|---|
| Google (Google Sign-In) | Verifying who you are when you sign in. Google's own handling of your account is covered by Google's privacy policy. |
| Apple (Sign in with Apple) | Verifying who you are when you sign in on iOS, and forwarding your mail if you chose Hide My Email. Apple's own handling of your account is covered by Apple's privacy policy. |
| Railway | Hosting the SplitChamp service and its database. |
| Cloudflare | DNS, TLS, and the security layer in front of the service; also object storage for encrypted database backups. |
| Google ML Kit | Reading the text on a receipt photo, on your phone. The photo and its text never leave the device. ML Kit sends Google basic diagnostics: device model, system and app version, performance and error data, and an identifier for the installation. Google does not pass these to anyone else. |
| Firebase App Distribution (Google) | Only for pre-release test builds given to our own testers, not for public releases. |
Each processes data on our instructions, for the purpose above, and nothing else.
We may also disclose personal data where the law requires it, for example in response to a valid court order or request from a public authority, and only what is required.
If SplitChamp or beanvoid is ever sold or merged, your data may pass to the new owner as part of that transfer. The new owner would have to keep to this policy, and we would tell you before it happened.
7. Where it is stored
We are based in Egypt, and our service, database and backups are hosted by the providers above, so data is processed in countries outside your own, including the United States. Where a transfer is subject to EU or UK data protection law, it relies on the safeguards those providers offer, such as the European Commission's standard contractual clauses.
8. How long we keep it
- Account and app content: for as long as your account exists.
- Sign-in sessions: refresh tokens expire within 30 days, and a session ends immediately when you sign out.
- Your payment method: until you remove it or delete your account, whichever comes first. Removing it takes it out of the app for everyone at once.
- Technical logs: kept for a short period for diagnosis and security, then discarded.
- Backups: encrypted database backups are kept for 30 days and then deleted automatically. Deleted data can persist in a backup until that window passes.
9. Your rights
You can ask us to: give you a copy of your data, correct it, delete it, restrict or object to how we use it, or provide it in a portable format. Email support@beanvoid.com and we will respond within 30 days. There is no charge.
These rights are given by Egypt's Personal Data Protection Law (Law No. 151 of 2020), and, if you are in the EU or the UK, by the GDPR. You can also complain to your local data protection authority.
10. Deleting your account
You can delete your account yourself, at any time, in the app: You → Delete account. It takes effect immediately: your display name, email, sign-in link, session records, activity feed and payment method are removed, and you are taken out of every group and friendship. If you signed in with Apple, we also tell Apple to revoke the sign-in, so SplitChamp no longer appears in your Apple ID settings. Backups age out within 30 days after that. Full detail, including what to do if you have lost access to the app, is on Delete your account.
One limit worth stating plainly: expenses you were part of belong to a shared group ledger. If we removed your side of a shared expense, the other members' balances would stop adding up. Where that is the case we anonymise your entries instead of erasing them, so the group's history stays correct but is no longer linked to you.
11. Security
- All traffic between the app and our servers uses TLS 1.2 or newer.
- The service sits behind Cloudflare, with rate limiting on sign-in endpoints, and it accepts traffic only through that layer.
- The database is not exposed to the public internet.
- Refresh tokens are stored hashed; access tokens are short-lived.
- A payment identifier is served only to someone who shares a group with you, and every request for one is checked against that group's membership.
- Backups are encrypted at rest, access-controlled, and protected against deletion for a rolling period.
No system is perfectly secure, but if a breach ever affects your data we will tell you and the relevant authority as the law requires.
12. Children
SplitChamp is not intended for children under 16. We do not knowingly collect their data; if we learn that we have, we delete it.
13. Changes and contact
If this policy changes materially we will update the date at the top and, where the change matters to you, tell you in the app. Questions, requests, or anything that looks wrong: support@beanvoid.com.
This policy is governed by the laws of the Arab Republic of Egypt, without affecting any rights you have under the data protection law of the country you live in.