PhonePOS Privacy Policy

Last updated: 16 June 2026

PhonePOS (“the app”, “we”, “us”) is a point-of-sale and shop-management app for phone and gadget shops, developed by Khem My (kmsoftstore.com). This policy explains what data the app handles and how. We designed PhonePOS to keep your business data on your own device.

1. Data stored only on your device

The following information you enter is saved locally on your device in the app’s private storage. It is not collected by us, not uploaded to our servers, and not shared with anyone:

If you uninstall the app, this local data is deleted with it. You can also delete records inside the app at any time.

2. Information sent to us (license activation only)

PhonePOS is a licensed app. To start or verify a license, the app contacts our licensing backend (Google Cloud Firestore) and sends only:

This is used solely to validate your license and bind it to one device, so a key cannot be used on unlimited devices. We do not use it for advertising, profiling, or tracking.

3. Permissions we use and why

4. Data we do NOT collect

We do not collect or process your location, contacts, advertising ID, hardware identifiers, usage analytics, or browsing activity. PhonePOS contains no advertising and no third-party analytics or tracking SDKs.

5. Service providers

Our license verification uses Google Firebase / Cloud Firestore as backend infrastructure to store license keys and the randomly-generated Device ID described in Section 2. Google processes this data on our behalf. See Google’s Privacy Policy at policies.google.com/privacy.

6. Payments

Bank QR codes (e.g. ABA, ACLEDA) shown in the app are static images you provide or that are bundled for accepting payment. PhonePOS does not process payments, card numbers, or banking credentials.

7. Data retention and deletion

8. Children’s privacy

PhonePOS is a business tool intended for shop owners and staff. It is not directed to children under 13, and we do not knowingly collect data from children.

9. Security

Local data is kept in the app’s private storage. An optional PIN and biometric lock add a further layer of protection. License traffic to our backend uses encrypted HTTPS connections.

10. Changes to this policy

We may update this policy from time to time. The “Last updated” date at the top will reflect any changes, and the current version will always be available at this URL.

11. Contact us