Privacy policy
Your GPS data deserves a clear map.
This policy explains what GPS Area collects, what stays on your device, what third-party SDKs may process, and how to control or delete data.
Last updated: July 8, 2026
Support: ravi.patel20102002@gmail.com
Effective July 8, 2026No account requiredAdMob disclosures included
GPS Area is designed around local measuring, with clear disclosures for analytics and ads.
- No account is required. We do not ask you to sign in to use the app.
- Location is core to the app. GPS Area uses device location to measure land areas and distances, show maps, find nearby places, calculate speed, and show local weather.
- Saved measurements stay on your device by default. Area names, coordinates, notes, map snapshots, and preferences are stored locally unless you choose to export or share them.
- Analytics and remote configuration help operate the app. Firebase Analytics may record app opens, screen views, app-instance identifiers, purchase/subscription events, and basic device/app information. Remote configuration may adjust app behavior such as feature availability, ads, or attribution setup without an app update.
- Ads may be shown in the free experience. Google AdMob may serve app open, interstitial, and rewarded ads. If the app asks for App Tracking Transparency permission, allowing tracking lets advertising/attribution partners use the device advertising identifier and related activity for ads or measurement.
Information we collect, use, or process
This table describes GPS Area’s current app behavior and near-term ad/attribution behavior supported by the app code and Remote Config. If a feature is not enabled for a user, the related collection may not occur for that user.
| Category | Examples | Why it is used | Storage / sharing | Tracking? |
|---|---|---|---|---|
| Location and map data | Precise device location, selected pins, boundary coordinates, distances, area/perimeter values, searched places, reverse-geocoded place names. | Measure land, calculate routes, center maps, show nearby points of interest, speed, weather, and compass-related tools. | Saved measurements are stored locally on device. Apple MapKit, Core Location, CLGeocoder, and WeatherKit may process requests needed to provide maps, place search, geocoding, and weather. | Not used by us to track you across other companies’ apps/websites. We do not intentionally send measured boundary coordinates to ad networks. |
| Saved content | Measurement name, notes, coordinates, unit preference, map snapshot image, display color, date created. | Show your saved areas/distances in the Library and exports. | Stored in the app’s local database on your device. Shared only when you choose to export/share through iOS. | No. |
| Preferences and device sensors | Area units, map style, export format, haptics, high-accuracy GPS preference, Celsius/Fahrenheit, compass/heading, motion/level/clinometer readings, speed readings. | Personalize tools and operate field instruments. | Preferences are stored locally. Sensor readings are processed on device unless included by you in an export/support message. | No. |
| Analytics and app activity | App opens, screen views, sessions, app-instance ID, device/app version, product interaction events, subscription/purchase events such as product ID, price, and currency. | Understand feature usage, app health, subscription conversion, and improve the product. | Processed through Firebase/Google Analytics. Purchase payments are handled by Apple; we do not receive card numbers. | Analytics by itself is not intended for cross-company tracking. If advertising or attribution partners receive events and identifiers, those may be used for tracking when permitted. |
| Advertising and ad measurement | IP address/general location, device identifiers such as IDFA or app/developer-bounded identifiers, ad views, ad clicks/taps, rewarded video views, app launch interactions, performance data, diagnostic/crash logs. | Show ads, limit abuse/fraud, measure ad performance, improve SDK reliability, and support personalized or non-personalized advertising where allowed. | Google AdMob / Google Mobile Ads SDK may process this data. Meta App Events and TikTok Business SDK may process app-open, registration, purchase, or subscription events if configured remotely. | Yes, when data is linked with third-party data for advertising or measurement and when permitted by ATT/consent choices. |
| Support contact information | Your email address, message content, screenshots, device/app details you choose to send. | Respond to support, privacy, subscription, refund, or data deletion requests. | Stored in our support email inbox and related support records. Do not send sensitive coordinates unless needed for your request. | No. |
| Camera access | Camera frames/photos if a future AR measurement feature is enabled and you grant permission. | Potential AR measurement features. | Not uploaded by default. The current policy will be updated if camera-based cloud processing is added. | No. |
What ads may be shown and what ad data may be used
Ad formats: GPS Area may show Google AdMob app open ads, interstitial ads between non-critical flows, and rewarded ads when the user chooses an optional rewarded action. Ads are not intended to interrupt an active measurement in progress.
- Personalized ads: Where available and permitted, ads may be personalized using device advertising identifiers and ad activity.
- Non-personalized/contextual ads: Even non-personalized ads may use limited data for delivery, frequency capping, reporting, fraud prevention, and security.
- ATT permission: On iOS, if GPS Area asks to track, you can choose Allow or Ask App Not to Track. You can change this later in iOS Settings → Privacy & Security → Tracking.
- Consent messages: In regions where Google requires additional privacy choices, the app may show a Google User Messaging Platform privacy message before requesting ads.
Privacy disclosure categories
This summary explains the main data categories users may see disclosed for GPS Area. Data practices should stay current when app features, ads, analytics, or SDKs change.
| Likely data type | Why it may apply | Suggested handling |
|---|---|---|
| Location | Precise location is used for GPS measurement, speed, weather, maps, and POI features. | Disclose location use for app functionality. Do not mark location as tracking unless you intentionally share it for tracking. |
| Identifiers | Firebase app-instance IDs and advertising/device identifiers may be used by Firebase, AdMob, Meta, or TikTok. | Disclose identifiers. Mark tracking if IDFA or related identifiers are used for third-party advertising/measurement. |
| Purchases | StoreKit purchases/subscriptions and Firebase purchase/subscription events can include product ID, price, and currency. | Disclose purchase history if these events are collected. |
| Usage Data | App opens, screen views, ad interactions, product interactions, sessions. | Disclose analytics and advertising uses where applicable. |
| Diagnostics | AdMob SDK may collect non-user crash logs and performance data. | Disclose diagnostics if AdMob or any diagnostics SDK is included. |
| Contact Info | Email address only if the user contacts support. | Usually disclose as support/contact data if retained outside optional one-time support criteria. |
Your privacy choices
- Location: Open iOS Settings → Privacy & Security → Location Services → GPS Area to change or revoke location access.
- Tracking: Open iOS Settings → Privacy & Security → Tracking → GPS Area to change App Tracking Transparency permission.
- Saved measurements: Delete individual saved areas from Library/Detail screens or delete all areas from Settings → Danger Zone → Delete All Areas.
- Subscriptions: Apple handles subscription billing. Manage or cancel subscriptions in iOS Settings → your Apple Account → Subscriptions.
- Data deletion requests: Visit Data Deletion or email ravi.patel20102002@gmail.com.
Third-party services used or supported
These providers may process data under their own terms and privacy policies when their services are used in the app:
- Apple Privacy Policy for Core Location, MapKit, WeatherKit, StoreKit, subscriptions, and App Store purchases.
- Firebase Privacy and Security for Firebase Core, Analytics, and Remote Config.
- Google AdMob iOS data disclosure for Google Mobile Ads SDK data practices.
- Google Privacy Policy and Google Advertising information.
- Meta Privacy Policy if Meta/Facebook attribution is configured.
- TikTok Privacy Policy if TikTok Business attribution is configured.
The app’s Remote Config defaults leave Meta and TikTok attribution keys empty. Those SDKs are only initialized when valid configuration is provided.
Retention, security, and children
- Local data: Saved measurements and preferences remain on your device until you delete them or delete the app.
- Support data: Support emails are retained as long as needed to respond, maintain records, resolve disputes, or meet legal obligations.
- Analytics/ad data: Firebase, Google, Apple, Meta, and TikTok retain data according to their own controls, retention settings, and policies.
- Security: We use platform providers that support encrypted transport. No method of electronic storage or transmission is perfectly secure.
- Children: GPS Area is not directed to children under 13. If you believe a child provided personal information, contact us for deletion help.
Privacy questions
Email ravi.patel20102002@gmail.com with the subject “GPS Area Privacy Request”. We aim to respond within 30 days, or sooner where required by applicable law.
This policy may be updated when ads, analytics, subscriptions, or app features change. The date at the top shows the latest update.