Information We Process
Precise and Coarse Location
After you grant Location permission and start monitoring, SpeedGuard may process latitude, longitude, GPS accuracy, heading, speed or speed-derived readings, timestamps, and a short recent location trace. This information is used to display speed, identify the current road, look up speed-limit information, evaluate alert thresholds, provide alerts or announcements, and safely recover or stop an active session.
If iOS provides approximate rather than precise location, SpeedGuard may process that coarse location for the same app-functionality purposes, although accuracy and speed-limit results may be reduced or unavailable. Google services used for eligible free-tier advertising may also derive an approximate location from an IP address for advertising delivery and analytics.
Free iOS monitoring stops when SpeedGuard leaves the foreground or the iPhone locks. Premium monitoring may continue while the app is minimized or the screen is off only after you start monitoring and grant background-capable Location access. Monitoring can be stopped in the app.
SpeedGuard does not use precise or coarse location for advertising targeting or cross-app tracking.
Speed-Limit Requests
SpeedGuard sends location-derived road-lookup data through protected SpeedGuard gateway services. Requests may include recent chronological latitude and longitude points, GPS speed, heading, GPS accuracy, timestamps or request timing, a random installation token used for diagnostics and rate limiting, Firebase App Check proof, and basic request metadata. Premium HERE requests may also include the anonymous RevenueCat app-user identifier needed to verify the SpeedGuard Pro entitlement.
Valhalla-backed map matching detects the current road. Trusted Valhalla data may provide free-user speed limits. For Premium users, HERE is the authority for displayed speed limits, alerts, and announcements; Valhalla remains a road detector. A Premium HERE request may contain two to six recent chronological points after sufficient movement. A newly detected Premium road remains unavailable until HERE confirms it.
SpeedGuard does not intentionally retain a complete route history on its servers. Providers may process request data and retain limited operational, security, diagnostic, rate-limiting, or legally required records under their applicable policies and agreements.
Identifiers
SpeedGuard and its integrated services may create or receive random, pseudonymous, app-bounded, installation, or device identifiers. These may include:
- A random SpeedGuard installation token used for gateway security, diagnostics, abuse prevention, and rate limiting.
- Firebase installation and analytics identifiers used for app security, configured analytics, crashes, and diagnostics.
- An anonymous RevenueCat app-user identifier used for purchases, subscriptions, restores, and entitlement verification.
- Advertising-related or app-bounded device identifiers used by Google for eligible free-tier, non-personalized advertising and analytics where permitted.
SpeedGuard does not require an in-app account and does not intentionally connect these identifiers to a user's name, email address, or phone number. Apple's App Store disclosure may nevertheless classify certain information as “linked to the user” when it is associated with a device or persistent pseudonymous identifier.
Product Interaction and Usage Analytics
After the User Agreement is accepted, configured Firebase Analytics may process allowlisted information such as app launches, screen views, monitoring start and stop events, feature use, purchase initiation and restore events, subscription tier, app version, and bounded event parameters. This information is used for app functionality, analytics, and, where applicable, evaluating eligible free-tier advertising.
Product analytics does not intentionally include precise location, road names, route traces, free-form text, App Check tokens, device tokens, or RevenueCat customer identifiers. Failed allowlisted events may remain temporarily in a bounded local queue until a later delivery attempt.
Advertising Data
Eligible free users may receive a banner ad only when advertising is enabled, a production iOS ad unit is configured, and Google's User Messaging Platform (UMP) authorizes an ad request. Google AdMob may process IP address, basic device and network information, app-bounded or advertising identifiers where permitted, ad request and delivery information, and ad views, clicks, or other interactions. This information may be used for third-party advertising and analytics.
The iOS app requests non-personalized ads only and denies advertising storage, advertising user-data, measurement, and personalization consent signals. SpeedGuard does not request ATT permission, does not declare an ATT tracking usage string, does not use location for ad targeting, and does not integrate TikTok on iOS. Premium users are not shown ads.
Purchases and Subscriptions
Apple's App Store, StoreKit, and RevenueCat process purchases and subscriptions. SpeedGuard may receive product identifiers, localized product information, purchase and entitlement status, trial or introductory-period type, expiration and renewal state, store, restore results, management links, paywall events, and Customer Center events. This information is used for app functionality and purchase analytics.
SpeedGuard does not receive your full payment-card number. The app uses RevenueCat's randomly generated anonymous app-user identifier and does not tie purchase history to a SpeedGuard account, name, or email address. Apple, RevenueCat, or payment providers may independently associate purchase information with accounts they control under their own privacy practices.
Crash, Performance, and Other Diagnostic Data
Firebase Crashlytics, Google services, and related infrastructure may process crashes, non-fatal errors, diagnostic logs, app version, device model, operating-system version, request timing, IP address, app launch time, hang rate, energy use, and similar reliability or technical information.
Crash data and other diagnostic data are used for app functionality and analytics and are not intentionally linked by SpeedGuard to a user's identity. Performance data may be associated with an app installation or device and may also support third-party advertising performance. SpeedGuard does not set a personally identifying Crashlytics user ID.
Current iOS App Store Disclosure
The current iOS release is intended to use the following App Store privacy disclosure. “Linked” does not mean that SpeedGuard knows the user's name; Apple also treats association with a device or persistent identifier as linkage.
| Data type | Purposes | Linked to user | Used for tracking |
|---|---|---|---|
| Precise Location | App Functionality | Yes | No |
| Coarse Location | App Functionality; Analytics; Third-Party Advertising | Yes | No |
| Device ID | App Functionality; Analytics; Third-Party Advertising | Yes | No |
| Purchases | App Functionality; Analytics | No | No |
| Product Interaction | App Functionality; Analytics; Third-Party Advertising | Yes | No |
| Advertising Data | Analytics; Third-Party Advertising | Yes | No |
| Crash Data | App Functionality; Analytics | No | No |
| Performance Data | App Functionality; Analytics; Third-Party Advertising | Yes | No |
| Other Diagnostic Data | App Functionality; Analytics | No | No |
No iOS data category is used for tracking as Apple defines that term.
Completed-Drive Statistics Stored on the Device
When a meaningful monitoring session ends, the app may create a local summary containing start and end time, duration, estimated distance, estimated average and maximum sustained speed, moving and stopped time, stop and driving-event counts, GPS coverage and accuracy aggregates, trusted posted-limit coverage and compliance aggregates, and a derived score when enough usable data exists.
Completed-drive summaries do not contain latitude, longitude, coordinate traces, routes, road names, or raw GPS sample history. They remain on the device, are not sent to SpeedGuard services or analytics, are available to every subscription tier, and support only the History, Drive Details, and Insights features. Because this information remains solely on the device, it is not treated as collected for the App Store privacy disclosure.
Other Information Stored on the Device
The app may store:
- Speed unit, alert preferences, Premium thresholds, language, and announcement preferences.
- Onboarding, current User Agreement acceptance, and permission-introduction state.
- Active monitoring-session state used for recovery and cleanup.
- Aggregate completed-drive summaries and a local history index.
- Temporary same-road speed-limit continuity state.
- A random installation token, subscription tier, and anonymous RevenueCat app-user identifier.
- Trial-promotion qualification, a product-analytics retry queue of no more than 100 events, and durable once-only analytics markers.
Persistent weak repeat-route HERE caching is disabled. Debug Log retention and navigation are disabled in release builds. Local information is generally removed when the app is uninstalled, subject to normal iOS backup and restore behavior.
How Information Is Used
- Provide monitoring, speed display, speed-limit information, alerts, and announcements.
- Match the device to a road and request available speed-limit data.
- Recover or stop monitoring sessions safely.
- Verify app integrity, protect gateway services, prevent abuse, and enforce rate limits.
- Provide, restore, and manage subscription features and entitlements.
- Deliver and evaluate eligible non-personalized banner advertising.
- Diagnose crashes and failures, monitor performance, and understand allowlisted product use.
- Provide support, comply with law, and meet App Store requirements.
Service Providers and Disclosure
Information may be processed by:
- SpeedGuard backend infrastructure for protected speed-limit lookup, security, diagnostics, entitlement verification, rate limiting, and abuse prevention.
- Valhalla-backed services for road detection, map matching, and supported speed-limit results.
- HERE for Premium speed-limit results.
- Firebase and Google for App Check, configured analytics, crash reporting, diagnostics, UMP, and eligible non-personalized AdMob banners.
- Apple App Store and StoreKit for products, purchases, subscriptions, restores, and billing administration.
- RevenueCat for products, purchase validation, subscription status, entitlements, paywalls, restores, and Customer Center features.
- Transistorsoft Background Geolocation for on-device location monitoring and session support.
Providers process information under their applicable terms, privacy policies, contracts, and legal obligations. Information may also be disclosed when required by law, to protect rights or safety, investigate abuse, or complete a business transfer subject to applicable law.
SpeedGuard does not sell personal information or sensitive personal information.
Permissions and Privacy Choices
SpeedGuard requests Location permission contextually when monitoring is first started, not during onboarding. Premium background monitoring may require Always Location access.
You can:
- Stop monitoring at any time in the app.
- Change or revoke Location access in iOS Settings.
- Manage or cancel subscriptions through the App Store or available RevenueCat Customer Center features.
- Use UMP privacy options when offered.
- Delete one completed-drive summary or use Clear All History.
- Uninstall the app to remove locally stored app information, subject to backup and restore behavior.
- Request access, correction, or deletion of information controlled by SpeedGuard by emailing speedguardapp@gmail.com with the subject Privacy Request.
Because SpeedGuard does not require an account, some information exists only on your device and cannot be accessed or deleted by us. To locate an applicable record, we may ask for your platform, app version, approximate dates of use, anonymous installation or RevenueCat identifier, or a store transaction reference. Do not send passwords, full payment-card details, private keys, API keys, or unrelated sensitive information.
We may take reasonable steps to verify a request. We will respond as required by applicable law and delete or de-identify eligible information unless retention is required for security, fraud prevention, transactions, legal compliance, or another lawful purpose. We may direct you to Apple, Google, RevenueCat, or another provider when that provider independently controls the requested record.
Retention
Completed-drive summaries remain on the device until you delete them, clear all history, or uninstall the app, subject to iOS backup and restore behavior. Other local information remains until removed by app behavior or uninstall.
SpeedGuard backend logs and diagnostics are retained only as reasonably needed for operation, security, debugging, rate limiting, abuse prevention, and legal compliance. Providers retain information under their own policies, contracts, and legal obligations. A deletion request to SpeedGuard does not automatically delete records independently controlled or legally retained by Apple, Google, RevenueCat, HERE, or another provider.
Security and International Processing
SpeedGuard uses safeguards such as HTTPS where supported, iOS permissions, Firebase App Check, rate limiting, and restricted analytics event schemas. No method of transmission or storage is completely secure.
SpeedGuard and its providers may process information in Canada, the United States, and other countries where they operate. Those countries may have data-protection laws that differ from the laws where you live.
Children
SpeedGuard is intended for licensed drivers and is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided personal information through SpeedGuard, contact us so we can review and delete it where appropriate.
Third-Party Privacy Policies
Changes to This Policy
We may update this policy to reflect changes to the app, providers, or legal requirements. We will post the revised policy at the same public URL and update the effective date. Material changes may also receive notice in the app or the App Store.