This Privacy Policy explains how the PairPay mobile application (the “App”) handles information. It applies to the App published on Google Play by Mesix (the “Developer”, “we”, “us”). Please read it carefully.
PairPay lets you track shared and personal expenses between two people. It can be used in two modes, and what happens to your information depends on which you choose:
The information you enter — the names you choose for the two people, expense amounts, your transaction history, and in-app preferences (theme, currency symbol, layout) — is saved only in local storage on your own device. In Offline mode this data is never sent off your device, and we have no ability to access or retrieve it.
The App does still send crash reports and basic usage diagnostics to Google Firebase in Offline mode — see Diagnostics and analytics below. These tell us that the App was opened or that it crashed; they never include the names, amounts or history you enter.
When you opt in to cloud sync by signing in with Google, we collect and process the following:
| Data | Why |
|---|---|
| Your Google account email address, name, profile picture URL, and Google account identifier | To identify you, create your account on our backend, and mint our own session tokens. We receive this from Google Sign-In; we never receive your Google password, and we do not access your Gmail, Drive, contacts, or any other Google service. |
| Shared expense data — member names/nicknames, expense amounts, shared/personal categories, transaction history, currency, and group membership | To synchronise your group across both members' devices. This data is, by design, shared with the other member of your group. |
| Device push notification token (Firebase Cloud Messaging) | To notify you when the other member of your group makes a change. Removed from our servers when you sign out. |
| Subscription status | To unlock cloud features. Purchases are processed by the Google Play Store; we store only your subscription's validity period. We never receive or store your payment card details. |
To keep the App stable and to understand how it is used, the App uses Google Firebase to collect crash reports (Firebase Crashlytics) and basic usage events such as app opens (Firebase Analytics). This applies in both modes, including Offline mode, and does not require signing in. These reports never contain the expense data you enter — your names, amounts and history are not part of them.
Alongside these events, Firebase Analytics collects your device's advertising ID — a resettable identifier provided by Google Play services — together with general device and app information such as device model, operating system version, app version and country. We use this only for analytics: to understand overall usage of the App and to improve it.
We do not show ads in the App. We do not use the advertising ID to target, serve or measure advertising, and we do not share it with advertisers or data brokers. You can reset your advertising ID, or delete it entirely, at any time from your device's Settings (typically under Settings → Privacy → Ads). Deleting it does not affect any feature of the App.
Firebase Analytics also derives an approximate location from your device's IP address. This is only accurate to a broad area such as your city or country, and we use it only for analytics. The App does not use GPS, does not request any location permission, and never collects your precise location. As with the diagnostics above, this applies in both modes and does not require signing in.
We share data only with the service providers necessary to operate the features above:
We do not sell your data, and we do not share it with advertisers or third-party data brokers.
Offline data is protected by the Android operating system's standard app-sandboxing. Cloud-sync data is transmitted over encrypted HTTPS connections and stored on access- controlled servers. Signing in is handled entirely by Google — your Google password is never seen by, sent to, or received by us. Google simply confirms your identity to the App, which then uses session tokens issued by our own backend.
The App is not directed to children and we do not knowingly collect personal information from children.
We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date.
If you have any questions about this Privacy Policy, or to request deletion of your
cloud data, contact the Developer:
Mesix — Mesrop Davoyan
Email: mesix.app@gmail.com