Privacy Policy

Last updated: September 10, 2026

This policy describes how MyShare ("we", "us") handles information in the MyShare mobile app and on shared receipt pages served from myshareapp.net. MyShare is an independent project run by its developers in Lebanon. You can reach us at parallelsystemslb@gmail.com.

What we collect

• Receipt photos. When you scan a receipt, the photo is sent to our server and passed to an AI provider that reads the items and prices from it. See How receipt scanning works below, which explains exactly what happens to the image and how long it exists.
• Receipt data. When you generate a share link, the item names, prices, and quantities from your receipt are stored on our servers (Google Firebase, in the European Union) so the link can be viewed by the people you share it with. The share link also records which device created it, so we can answer support requests about a receipt and investigate abuse.
• What you ticked. If you pick your items on a shared receipt, that selection is stored with the receipt so it is still there when you reopen the link. It is not tied to your name or to anything else about you — only to a random identifier your browser keeps.
• A device identifier. The app creates or reads an identifier for your device and sends it with each scan, so we can count how many scans that device has used. See Your device identifier below.
• Your country and your phone's model. We record which country your phone is in — worked out from its time zone, so a country and nothing finer — and which model of phone it is. We use them to know which countries use the app and which handsets it runs badly on. See Recognising your device below.
• Advertising data. Ads appear inside the app and on the shared receipt pages you generate — the myshareapp.net/r/… links you send to your group. Two different companies serve them: ads inside the app come from Google AdMob, and ads on the shared receipt pages come from Adsterra. Each may collect your IP address, device information, and usage signals to serve and measure those ads, as described in Google's advertising policies and Adsterra's privacy policy. The receipt itself — the items and prices on the page — is never sent to either of them.
• Service measurements. We record daily totals about scanning — how many scans ran, how long they took, which AI model answered, whether it failed, and what it cost us. These are counters only. They contain no receipt content and no device identifier, so they describe the service rather than any individual using it. Separately, and described under Recognising your device, we do keep a running cost total against your device.
• App analytics. We record which screens you open and which actions succeed or fail — for example, that a scan was started and that it failed — so we can see which parts of the app break or go unused. These are counts of what happened, never of what it happened to. See Analytics, crash reporting and performance below.
• Performance measurements. We record how long the app takes to start, how long screens take to draw, and how long requests to our own servers take — measured on your phone, so we can see the wait you actually experience rather than only how fast our servers answered. It records the address of the request and how long it took, never what was in it. See Analytics, crash reporting and performance below.
• Crash reports. When the app crashes we record the programming error itself, your device model, and the operating system version, so the crash can be reproduced and fixed.
• Technical logs. Our servers record standard request information such as IP address and timestamps, which is used to operate the service and prevent abuse.

Analytics, crash reporting and performance

We use three Google tools for this: Google Analytics for Firebase, which records the screens and actions described above, Firebase Crashlytics, which records crashes, and Firebase Performance Monitoring, which records how long things take. Each crash also carries the name of the screen you were on when it happened, so we can tell which part of the app is failing.

What performance monitoring records. How long the app takes to start, how long each screen takes to draw, and for requests to our own servers, the address requested and how long the round trip took. It measures the wait on your phone, which is the only place the effect of a slow connection is visible — our servers can only time themselves. It records how long a request took and never what it contained, and the app makes no request that carries a receipt in its address.

What these never contain. No receipt photograph, no item names, no prices, no total, no merchant, and no identifier for your device. An analytics event from this app counts that something happened; it never carries what it happened to. This is a rule about what the code is permitted to send, not only a promise about what we intend to look at: event names come from a fixed list, anything not on that list is refused, and the refusal is covered by tests that run before every release.

Not used for advertising. This data is not linked to you across other companies' apps or websites, and is not used to target ads. It is used to fix and improve this app.

In the UK and EEA, all three are off unless you choose to turn them on, and the app is fully usable without them. Elsewhere they are on by default and you can turn them off at any time in Settings — one switch governs all three, because they are one decision.

What we don't collect

We do not collect your name, phone number, contacts, or precise location. We never sell your information, and we don't share it with anyone beyond the service providers described below.

Analytics, crash reporting and performance monitoring, described in Analytics, crash reporting and performance above, carry no receipt content and no device identifier. They tell us that a screen was opened, that a scan failed, or that something took four seconds; they never tell us what was on the receipt.

We hold an email address only for people who choose to create an account, which is optional — see Accounts. If you don't, we never have one.

How receipt scanning works

This is the part of the app that changed most, so it is worth being precise about.

When you scan a receipt, the app crops and shrinks the photo on your device and sends it to our server. Our server strips the photo's metadata — including any GPS location your camera recorded — re-encodes it, and sends the image to an AI provider, which reads the items, prices, and quantities and returns them as text. Those items are then shown to you for editing.

We do not store the image. It exists in memory for the few seconds the request takes and is discarded when the request ends. It is never written to disk, never saved to a database, and never attached to your receipt or your share link. What is kept is only the text you go on to share.

The AI providers we send images to are:

• Google (Gemini models), which handles scanning normally.
• OpenAI, used only as a fallback when Google is unavailable, so that a scan doesn't simply fail.

Both process the image under their own API terms as our processors. Those terms provide that data sent through their paid APIs is not used to train their models, and each may retain it briefly for abuse monitoring under their own policies. You can read Google's Gemini API terms and OpenAI's API data usage policies.

A receipt photo can contain more than items and prices — the last four digits of a card, a restaurant name, a date and time. Only the items you keep are stored, but the whole image is what the provider reads, so it is fair that you know that before you scan.

Recognising your device

The app gives each device its own allowance of scans, so it needs to tell devices apart. It does that with an identifier that belongs to MyShare on your phone — either one your phone provides to apps for this purpose, or one the app generates at random the first time it runs. We store a scrambled version of it rather than the identifier itself.

Against it we keep what the allowance needs — your scan count, whether the free trial has been used, any credits earned from ads, and whether a subscription is active — and one thing the allowance does not need: a running total of what your scans have cost us to run. It is two numbers, how many scans and how much they cost, and we keep it so we can tell whether the free tier pays for itself. Nothing from your receipts is attached to it, and there is no record of what any individual scan cost.

We also keep two things that describe the phone rather than the allowance: which country it is in and what model it is — for example Lebanon, and iPhone 16 Pro or Samsung SM-S928B. We keep them to know which countries use the app and which handsets it runs badly on, so a crash that only happens on one kind of phone is one we can find and fix.

The country is worked out from your phone's time zone, which is a setting on the device and not a position. It is a country and nothing finer — no town, no coordinates, and we do not record or store your IP address to derive it. We keep only where the phone is now; we do not keep a history of where it has been. The model is the one your phone reports to every app, and never the name you may have given your phone. Both are deleted with everything else when you delete your data, and neither is kept in the small record that survives deletion.

That total is deleted with everything else when you delete your data. It is not kept in the small record that survives deletion, which is described below.

It is not an advertising identifier. It is never shared with advertisers, never used to target ads, and never combined with information from other apps. It is also not built from your phone's hardware or settings.

It survives reinstalling the app, so your scan count doesn't start over. It does not survive a factory reset or moving to a new phone.

Deleting the app does not delete this record. To remove it, use Delete my data — tap the information icon at the top of the Add Bill screen. It deletes the record for that device immediately. Full instructions are here. If you can no longer open the app, email us and we will explain what we need to find it.

When you do that, we keep one thing: a scrambled, one-way version of the device identifier, together with a short record of what that device had already spent: whether it used its one-time set of free scans, whether it claimed the one-time bonus for signing in, and where it had reached in its monthly allowance. Nothing else — no email address, no platform, no bills, nothing about what you scanned. Without it, deleting your data would hand back a fresh set of free scans every time, which would make the button a way to scan for free forever rather than a way to be forgotten. What we keep cannot be turned back into your device or into you, it is only ever used to work out what a returning device may claim, and it is used for nothing else.

Accounts

You can scan, split, and share without an account, and opening a shared receipt link never needs one.

You can create one if you want to. Signing in earns you a one-off bonus of free scans, and it means your scans — and your subscription, if you have one — follow you to a new phone instead of starting over. We store your email address and which devices you have used it on. We do not email you unless you separately ask us to, and you can change your mind about that at any time.

If you subscribe, the payment is handled by the App Store or Google Play under their terms. We never see or store your card details — we only record that your account holds an active subscription. One account can cover several devices.

To delete your account and everything attached to it, use Delete my data in the app's settings, or email us.

Camera

The app asks for camera access so you can photograph a receipt. Photos you take or choose are used for scanning as described above, and are not stored by us.

What's stored on your device

The app stores the device identifier described above, a cached list of currency exchange rates, and your light or dark theme preference. Apart from the identifier, which is sent with scan requests, none of this leaves your device.

Advertising and cookies

Ads keep MyShare free to use. In the app, some ads appear on their own at natural break points, such as after you share a bill. Others are videos you choose to watch in exchange for an extra scan. Ads also appear on the shared receipt pages you generate, and may appear on this site's home, about and guide pages.

This page, the Terms, and the Delete Your Data page carry no advertising and load no advertising code at all. You should be able to read what we do with your information without being advertised to while you do it.

Shared receipt pages may use cookies set by Google to serve and measure ads. You can review how Google uses information from sites that use its services and adjust your preferences at Google Ad Settings.

In regions where consent is required, including the European Economic Area and the United Kingdom, you will be asked for consent before personalized ads are shown. You can decline and still use MyShare; you will see non-personalized ads instead.

Subscribers see no ads in the app, and the receipt links they create show no ads to anyone who opens them.

How long we keep receipts

Shared receipts are kept indefinitely. The reason is that a share link is something you have already sent to other people: deleting it would break it in their messages, weeks after the fact, with no warning to anyone. In time a receipt link stops accepting changes and becomes a read-only record of how the bill was split, but it keeps working.

If you want a receipt removed, email us the link and we will delete it.

Your rights

For shared receipts, the link is how we identify your data — email us at parallelsystemslb@gmail.com with a link and we can delete it or tell you what it contains.

For your device record and your account, Delete my data in the app's settings removes both, without needing to contact us. If you can no longer open the app, email us — if you have an account we can find it from your email address, and if you don't, we will tell you what we need to identify your device.

If you are in the European Economic Area or the United Kingdom, you also have the right to access, correct, or delete your information, to object to how we use it, and to complain to your local data protection authority.

Service providers

We use Google Firebase to host the service and store shared receipts, and Google Firebase App Check — which uses Apple's DeviceCheck and Google's Play Integrity — to confirm requests come from a genuine copy of the app rather than a script. We use Google Analytics for Firebase, Firebase Crashlytics and Firebase Performance Monitoring to measure use of the app, to receive crash reports, and to measure how long the app takes to respond. We use Google AdMob to serve ads inside the app, and Adsterra to serve ads on the shared receipt pages. We use Google and OpenAI to read receipt images, as described above. Exchange rates are fetched from a public currency data provider. Subscriptions are processed by Apple and Google. These providers process data on our behalf under their own terms.

Children

MyShare is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has shared information with us, email us and we will remove it.

Changes

We may update this policy as MyShare changes. The date at the top always reflects the current version. Where a change means collecting something new, we will update this policy before that starts, and ask for your consent where the law requires it.

Contact

Questions or requests? Email us.

← Back to MyShare · How to split a bill · About · Terms & Conditions · Delete your data

© 2026 MyShare · v0.3.0 (273)