Privacy Policy for MOPX — Retail POS & Inventory

Last updated: 22 October 2026 Applies to: MOPX (Android package com.arpanpatra.mopx), version 2.9.0 and later Developer: Arpan Patra Contact: thispc119@gmail.com

Summary

MOPX is an offline application. It has no MOPX account and no MOPX server. Everything you enter — products, prices, stock, bills, returns, customer names and phone numbers — is stored in a private database on your own phone.

Your shop’s data stays on your phone. It leaves the phone only if you turn on Google Drive backup, and then it goes to your own Google Drive, which only your Google account can open. We, the developer, cannot see your data.

When the app crashes or hits an error, it can send a technical crash report so the problem can be fixed. Crash reports never contain your products, bills, prices, customers or business details, and you can turn them off in Settings.

Your choices at a glance: Google Drive backup is off until you tap “Connect Google Drive”. Crash reports can be turned off in Settings → Data → Send crash reports. PIN lock is off until you turn it on. Notifications are only used for backup reminders and backup problems you can see in the app. The camera, Bluetooth and photos are optional.

1. Information the app stores on your device

MOPX stores the following on your phone, inside the app’s private storage area:

What	Why
Product names, barcodes, prices, buying costs, stock counts, categories	To run your stock
Product photos you choose to attach	To help you identify products
Bills, line items, totals, discounts, taxes, payment methods, parked bills, cancelled bills, returns and money given back	To create, correct and reprint receipts and to keep your accounts right
Customer name and phone number, when you choose to enter them on a bill	To print them on that customer’s receipt and track money still to collect
Suppliers and purchases you record	To restock and keep a stock history
Your business profile (shop name, owner name, address, phone, tax ID, currency) and your UPI ID and UPI QR picture	To print on receipts and to show your payment QR to customers
PIN lock settings, if you turn PIN lock on: the owner and worker PINs as one-way codes (salted hashes, never the PINs themselves), what workers may do, the recovery code, and a list of who (owner or worker) made each change	To keep the app locked and to show who did what
App preferences (language, theme, text size, printer, backup reminders, Google Drive backup settings and the email address of the connected Google account)	To remember your settings

This information is not sent to the developer or to anyone else, except to your own Google Drive if you turn on Google Drive backup (section 2.4).

2. Information that leaves your device

MOPX makes four kinds of network requests. Only the Google Drive backup (2.4), which you turn on yourself, contains your shop’s data.

2.1 App code updates

When the app starts, it contacts Expo’s update service (u.expo.dev, operated by Expo / 650 Industries, Inc.) to ask whether a newer version of the app’s code is available. This request includes technical information only:

A randomly generated installation identifier
The app version and update runtime version
Device platform and OS version

It does not include any of your products, bills, customers, prices, or business profile. This check is used solely to deliver app updates.

Expo’s privacy policy: https://expo.dev/privacy

2.2 New versions on Google Play

At most once a day, MOPX asks the Google Play Store app on your phone whether a newer version of MOPX is available. This goes through Google Play’s in-app update service under Google’s own privacy policy (https://policies.google.com/privacy); MOPX itself sends nothing. When you tap an available update in Settings, Google Play downloads it in the background and installs it when you tap Restart. If that download or install fails, the crash report described below includes Google Play’s error code for it; nothing else is added.

2.3 Crash reports

To find and fix bugs, MOPX uses Sentry (operated by Functional Software, Inc.) to receive crash and error reports. A report is sent when the app crashes, stops responding, or hits an unexpected error, and once per session a small record that the app was used without crashing (used only to count the share of sessions that end in a crash). A report contains:

The error message and the place in the app’s code where it happened
The screens visited just before the error (screen names only)
App version and build, Android version, device manufacturer and model, available memory and storage, and whether the app was open on screen
A random identifier for the installation, and the time
For an in-app update that fails to download or install, Google Play’s error code and the update steps that ran

A report never contains your products, prices, bills, customers, business profile, photos or anything you type. Before a report leaves the phone, the app removes anything that looks like a phone number, email address, UPI ID or GSTIN. No screenshots or screen recordings are taken, and no account, name, contacts, location or advertising ID is attached. Like any internet request, sending a report reveals your network’s IP address to Sentry’s servers; MOPX’s Sentry project is set not to store IP addresses or any location derived from them.

Reports are sent over encrypted connections (HTTPS) and are processed and stored by Sentry in the United States. Crash reports are on by default. You can turn them off at any time in Settings → Data → Send crash reports; while they are off, the reporting component is not started at all. Sentry deletes reports automatically after its retention period (at most 90 days), and they are used only to fix problems in MOPX.

Sentry’s privacy policy: https://sentry.io/privacy/

2.4 Google Drive backup (optional, off until you turn it on)

MOPX can back up your shop to your own Google Drive. It is off until you tap Connect Google Drive (Settings → Backup & restore) and choose a Google account on Google’s own screen. MOPX works fully without it; connecting Google Drive does not create a MOPX account.

Permission MOPX asks Google for: only “See, edit, create, and delete only the specific Google Drive files you use with this app” (drive.file). MOPX can see and change only the files it created. It cannot see any other file in your Google Drive.
What is uploaded: a backup file of the whole shop — everything listed in section 1, including customers’ names and phone numbers, bills, returns, product photos and the PIN lock settings (PINs only as one-way codes, and the recovery code) — into a folder named “MOPX Backups” in your Google Drive. Product photos are stored once each in a “photos” folder inside it. A small file in the same folder records which phone backs the shop up.
Details stored with each backup file in your Drive, so MOPX can list your shops and backups: the shop name, the phone model, a random identifier for the phone and for the shop, the number of bills and products, the currency, the app’s database version, and whether you made the backup with “Back up now”.
When: every day by default (weekly or monthly if you choose), when you tap Back up now, and in the background through Android’s job scheduler. It uses any internet connection the phone has, including mobile data.
Google account information used: the email address of the connected account, shown on the Backup screen so you know which account is connected. It is kept on the phone and not sent anywhere else.
Who can read the backups: only your Google account. The developer of MOPX has no access and receives nothing. Files travel over encrypted connections (HTTPS) and are stored by Google under Google’s terms (https://policies.google.com/privacy). MOPX does not add its own password to Google Drive backups; they are protected by your Google account. (Backup files you make with a password in Settings → Backup & restore, described in section 6, are still encrypted with that password.)
Restore: you can restore a shop from these files on any phone where you connect the same Google account. A restore replaces the data on that phone after you confirm.
Old backups: MOPX keeps the last 7 daily, 4 weekly and 6 monthly backups and the last 3 made with “Back up now”, and deletes older ones from the “MOPX Backups” folder.
Stopping and deleting: tap Disconnect Google Drive in MOPX to stop backups (the files stay in your Drive). Delete the “MOPX Backups” folder in Google Drive to delete the backups. Remove MOPX’s access to your Google account at https://myaccount.google.com/permissions. Uninstalling MOPX does not delete backups in your Drive.

MOPX’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3. Permissions the app requests

Permission	Why it is needed	Optional?
Camera	To scan product barcodes, to take product photos and to photograph your UPI QR	Yes — you can type barcodes and skip photos
Nearby devices (Bluetooth)	To list paired Bluetooth receipt printers, to find nearby Bluetooth LE printers when you search for one, and to print to them; asked only when you choose a Bluetooth printer. MOPX does not use Bluetooth to find your location.	Yes — sharing receipts as PDF needs no permission
Notifications	Backup reminders, a notice when Google Drive backups have failed for 3 days, and a notice when an update is ready	Yes
Internet / Network state	For the update checks, crash reports and Google Drive backup described in section 2	The app works fully offline without it
Run at startup, keep awake	So backup reminders and scheduled Google Drive backups you turned on still run after the phone restarts	Used only for these
Vibrate, audio settings	Scan feedback and the scan beep	—

Product photos and the UPI QR picture from your gallery are chosen with Android’s photo picker, so MOPX only receives the photo you pick and needs no storage permission.

MOPX does not request location, contacts, microphone, SMS, call logs, or any other sensitive permission. Camera frames are processed on the device to read barcodes and QR codes and are never recorded or uploaded.

4. Children

MOPX is a business tool intended for shop owners and staff. It is not directed at children and does not knowingly collect information from children.

We do not sell your data. We do not share it. We do not have access to your business data.

Crash reports (section 2.3) are processed by Sentry on our behalf, only to fix problems in the app. Google Drive backups (section 2.4) go to your own Google account, which you control; we cannot open them. No advertising SDKs, analytics beyond crash and session-health reports, or tracking libraries are included in this app.

6. Data retention and deletion

Your data is stored on your device, and in your Google Drive if you turn on Google Drive backup. You control both:

Back it up to a file: Settings → Backup & restore → Create private backup. The file is encrypted with a password you choose and can be restored on a new phone.
Back it up to Google Drive: see section 2.4.
Export it: Settings → Export products CSV; any receipt can be shared as a PDF.
Delete it from the phone: uninstall the app, or go to Android Settings → Apps → MOPX → Storage → Clear storage.
Delete it from Google Drive: delete the “MOPX Backups” folder in your Google Drive.

Uninstalling the app permanently deletes all business data on that device. Since we hold no copy, there is nothing for us to delete on our side and no deletion request is necessary. Crash reports expire automatically after at most 90 days; to have them deleted sooner, email us and tell us roughly when the crash happened and your phone model (reports carry no name, so these help find them).

Important: without Google Drive backup or a backup file kept somewhere else, uninstalling or losing your phone means losing your data. Please make backups regularly.

7. Security

Your data is held in the app’s private storage, which Android prevents other apps from reading. The app keeps up to three automatic daily copies of its database in the same private storage, so a file damaged by a crash or power cut can be restored, and it keeps a copy of the database before it updates the database to a new version; these copies never leave the device. Backup files you create in Settings are encrypted with your password (AES-256-GCM, with the key derived from the password); keep the password safe, because without it a backup cannot be restored and we cannot recover it. Google Drive backups are protected by your Google account and sent over encrypted connections. PINs are stored only as salted one-way codes. CSV exports and PDF receipts are ordinary, readable files placed where you choose to share or save them. Crash reports are sent over encrypted connections (HTTPS).

8. Your rights

You can ask us what crash reports exist about your installation, or ask us to delete them, by emailing thispc119@gmail.com. We reply within 30 days. Your business data never reaches us, so requests about it are handled on your phone and in your Google Drive (section 6). If you are in India, these are your rights under the Digital Personal Data Protection Act, 2023, as far as they apply to the little data we process.

9. Changes to this policy

If this policy changes, the updated version will be published at this same address with a new “Last updated” date.

10. Contact

Questions about this policy or about your data:

Arpan Patra Email: thispc119@gmail.com Website: https://arpan111.vercel.app/

This policy is published at https://arpan111.vercel.app/mopx/privacy-policy (the address in the Google Play listing) and mirrored at https://mopx.me/privacy. Both copies are kept identical.