Privacy Policy

Pocket Compass · Last updated: 10 April 2026

This policy describes how Pocket Compass (“the App”), developed by Cuong Nguyen (“we”, “us”), handles information when you use the mobile application on iOS and Android. If you do not agree with this policy, please do not use the App.

This document is written to align with common store disclosure expectations, including the Google Play Data safety section (how user data is collected, shared, and secured). Your answers in Play Console must match what the App and its dependencies actually do; use this policy together with Google’s definitions in the Data safety form.

How we use key terms (including Google Play)

On Google Play, “collect” generally means user data is transmitted off the device to the app developer or a third party (subject to Google’s listed exceptions). “Share” means user data is transferred to a third party (on or off the device), again subject to Google’s exceptions. Processing that stays entirely on the device and is not sent to us or a third party as part of your use of the App is on-device processing from the App’s perspective.

Summary

• The App is a digital compass and does not require an account or login.
• We do not sell your personal information.
• We do not operate our own backend that receives your compass readings, raw location, or similar data from the App for storage or profiling. The App is not designed to upload that data to servers we control.
• The App does not embed third-party analytics or advertising SDKs in its published dependency set.
• Location and sensor data are used to run the App on your device (heading, declination / true north). The operating system and platform location stack (for example Google Play services on Android, Apple location services on iOS) may process data under their own policies when you use system location APIs.

Data the App accesses (by category)

Depending on permissions and device capabilities, the App may involve the following:

• Location (approximate or precise, while the App is in use) — Used to compute magnetic declination and show headings relative to true north where supported. The App uses this for that purpose; we do not use it to build an advertising or marketing profile. Location is obtained through platform APIs (not a custom server we operate for that purpose).
• Compass / device motion and orientation — Used to derive heading for the compass UI. Handled on the device as part of normal App operation.
• App information — For example, app version from the system (package_info_plus) to show version text in the UI. Read locally on the device.

Collection and sharing by the developer

We do not intentionally collect personal or sensitive user data from the App by sending it to servers we control for storage, analytics, or advertising. We do not intentionally share such data with third parties for those purposes through the App.

You should still complete Play’s Data safety questionnaire based on all data handling, including by libraries and the OS. For example, on Android, obtaining a location fix may involve Google as part of the platform location stack; that is outside our direct control. See Google’s help for how to declare location and optional “ephemeral” / on-device handling where applicable.

Libraries (SDKs) in the App

The App bundles open-source Flutter plugins used for sensors, permissions, and platform metadata, including (as shipped in source): flutter_compass, geolocator, permission_handler, package_info_plus, and a local geomagnetic model (geomag) for declination math. We do not add separate analytics or ad networks in that list. Review each library’s documentation and Play’s Data safety guidance when you fill out the form.

Security

We do not operate a user-facing cloud service for this App, so there are no developer-hosted account databases or app-specific APIs to describe here. You should keep your device OS updated and only install the App from trusted stores. Use device settings to revoke location access if you choose.

Retention and deletion

We do not retain user data from the App on infrastructure we operate. Data processed on your device is subject to normal app and OS behavior. Uninstalling the App removes the App’s local data from your device; we have no corresponding cloud copy to delete on your behalf.

Permissions (Android)

On Android, the App may declare permissions including:

• ACCESS_COARSE_LOCATION and ACCESS_FINE_LOCATION — for the location-based declination feature described above.
• INTERNET — May be present in the manifest (for example, for the platform or transitive dependencies). The App is not designed to send your compass or location data to developer-controlled servers.

Permissions (iOS)

On iOS, the App requests location when in use where needed for declination / true-north related functionality, consistent with the system permission prompt (NSLocationWhenInUseUsageDescription).

Third parties (platform providers)

Apple and Google provide the operating system, Play Store / App Store distribution, and system services. They may process data according to their own policies when you use your device. The App relies on standard platform APIs and bundled libraries as described above. Review your device privacy settings to manage location and sensor access.

Children’s privacy

The App is not directed at children under 13 (or the minimum age required in your region). We do not knowingly collect personal information from children.

Changes to this policy

We may update this policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the App after changes means you accept the updated policy.

Contact

For questions about this privacy policy, contact:
c.ng.devie@gmail.com

Google Play Data safety (form checklist)

Play Console’s Data safety questions use Google’s definitions of collect and share (data leaving the user’s device to you or a third party, subject to Google’s exceptions). You must declare data handled by the App and by bundled SDKs, even if data is not sent to servers you operate.

For this App, review especially:

• Location — Declared in the manifest and used for declination / true north. Declare purposes (for example, App functionality) and whether data is collected, shared, or only processed in ways Google allows you to describe as on-device / ephemeral, following current Play Console options and help articles.
• Device or other IDs — Only declare if an SDK or the OS stack actually transmits identifiers off-device in a way that counts as collection under Google’s rules for your build.
• Security practices — Answer the security questions truthfully for your app; we do not host a separate backend for this App’s user data.

If anything in this policy and your Play declarations disagree, update the policy or the form so they match.