If you want mPOS data deleted, you can do it yourself in most cases — see the self-service instructions below. If you need assistance from the developer, you can request deletion directly by emailing:
leonchoo@users.noreply.github.com
Please include the subject line "mPOS Data Deletion Request" so the request can be identified and processed. The developer does not operate any mPOS backend server; please see the explanation below for what the developer can and cannot delete.
When you request deletion, the following data is deleted (where applicable):
All of your point-of-sale data (products, orders, stock movements, shop profile, app settings, backup metadata) is stored only on your device, in the app’s private database. The app does not run any backend server, and the developer does not have a copy of this data on his own systems.
Because the developer never received this data, there is no copy of it to delete on the developer’s side. To remove it, delete it from your device using the self-service steps below.
Backup files are stored in your own Google Drive under the app’s app-created folder. The developer does not host these files. Only you (and Google) have access to them.
If you delete mPOS backup files in your Drive, the next time you sign in with mPOS on the same or another device, that backup will no longer be available for restore.
Pick one of the following options on your Android device:
mPOS folder (or the folder where mPOS backups were saved).After this, mPOS can no longer read or write files in your Google Drive on your behalf, even if you sign in once more. To use backup again in the future, you would need to sign in and grant access again.
The developer does not retain any of your POS data on his own systems, because the app does not transmit it to him. After you complete the self-service deletion steps above, no copy of your POS data remains in the developer’s control.
Data that exists outside the developer’s control:
mPOS is an offline-first, no-account app. The developer does not receive or store your POS data, so no legally-mandated retention period applies to the developer. If Google retains AdMob or Drive data under its own legal obligations (e.g., tax, anti-fraud), that retention is governed by Google’s own policies and is outside the developer’s control. See Google’s Privacy Policy for details.
This Privacy Policy describes how the mPOS app ("mPOS — Mobile Point of Sale", also referred to as "the app", "we", "us", "the developer") handles your data.
The app is designed for offline use: all your point-of-sale data (products, orders, sales history, app settings) is stored locally on your device in a private database. The app does not require account creation or login. It does not operate any backend server and does not collect your sales data through any infrastructure controlled by the developer.
What leaves your device, if anything, is limited to:
The following data is stored exclusively on your device, in an encrypted SQLite database (managed by Android Room):
This data:
/data/data/com.llcailabs.mobilepos/)The app requests the following Android permissions:
| Permission | Why | Optional? |
|---|---|---|
INTERNET | AdMob ads, Google Drive backup | Required |
BLUETOOTH, BLUETOOTH_ADMIN (API ≤ 30) | Bluetooth receipt printer | Required if using printer |
BLUETOOTH_SCAN, BLUETOOTH_CONNECT (API ≥ 31) | Bluetooth receipt printer | Required if using printer |
ACCESS_FINE_LOCATION (API ≤ 30) | Bluetooth printer discovery (Android 9 and below require this) | Required if using printer |
CAMERA (optional, user must grant) | Optional product photo | Optional |
WRITE_EXTERNAL_STORAGE (if granted) | Save backup file to Downloads | Optional |
No permission is used for surveillance, location tracking, or analytics.
The app uses Google AdMob to display banner ads and (after a successful local backup) an interstitial ad. AdMob is operated by Google LLC.
When ads are displayed, AdMob may collect:
This data is collected by Google per its own privacy policy:
You can opt out of personalized ads by enabling "Opt out of Ads Personalization" in your Android device settings (Settings → Google → Ads).
v0.5.23 ad personalization status: This app version does not implement the Google User Messaging Platform (UMP) consent flow. In EEA / UK regions, AdMob serves non-personalized ads by default for apps that do not request UMP consent. In other regions, ads may still be personalized by Google. The developer does not collect or control any of this data — deletion of AdMob-side data is governed by Google’s policies (see Google’s Privacy Policy and Google’s AdMob data controls).
The app can optionally back up your local database to your personal Google Drive. This is opt-in: the backup only happens when you tap the "Backup" button in Settings.
The backup uses Google Sign-In (OAuth 2.0). When you sign in:
drive.file scope — limited to files the app creates)Backup files contain the same data as Section 2 (products, orders, shop profile, app settings).
The backup file is uploaded to your Google Drive. The developer does not host the backup on his own servers.
OAuth scopes requested:
https://www.googleapis.com/auth/drive.file — read and write only files the app createsTo revoke the app's access: visit https://myaccount.google.com/permissions and remove "mPOS". See the Data Deletion Request section above for full instructions.
| Category | Collected? | By Whom | Purpose |
|---|---|---|---|
| Products, orders, settings (POS data) | Yes — local only | App, on your device | App functionality |
| Google account email (only if you enable Drive backup) | Yes (opt-in) | Google Sign-In | Account connection |
| Advertising ID | Yes | Google AdMob | Ad serving |
| Device ID / model | Yes | Google AdMob | Ad optimization |
| IP address | Yes | Google AdMob, Google APIs | Networking |
| Crash logs | No | — | — |
| Analytics | No | — | — |
| Contacts / location / microphone | No | — | — |
The app itself does not collect, transmit, or sell any of your product / order / sales data.
| Recipient | What Is Shared | Why |
|---|---|---|
| Google LLC (AdMob) | Advertising ID, ad interactions | Ad serving |
| Google LLC (Drive API) | Backup file content (only if you enable Drive backup), your Google account email | Cloud backup (opt-in) |
The developer does not share your data with any other third party.
drive.file scope (cannot read your other Drive files).This app is not directed at children under 13. The developer does not knowingly collect data from children. If you believe a child has used this app, contact the developer via the email below.
You have the right to:
The developer may update this Privacy Policy. The "Last updated" date at the top will change when this happens. Material changes will be reflected in this page and (where practical) noted in the app.
For privacy questions or data deletion requests, contact the developer:
Developer: leon choo (independent developer)
Email: leonchoo@users.noreply.github.com
Mailing address: Not provided
For data deletion requests, please include the subject line "mPOS Data Deletion Request". See the Data Deletion Request section above.
This app is provided as a software product. By installing and using the app, you consent to the data practices described above. The app does not require account creation or login and operates offline-first by default.
mPOS v0.5.23 is built with the following components, each governed by its own license:
Full license texts are available in the app's third-party licenses screen.