SpeedGuard

Draft for review

Privacy Policy

Effective date: May 10, 2026

This draft is based on the current Android repository behavior and should be reviewed by 17920318 CANADA INC. before relying on it as legal advice or final publication copy.

1. Operator and contact

SpeedGuard is operated by 17920318 CANADA INC. You can contact us at info@vehiclespeedingguard.com.

2. Data we process

SpeedGuard is an Android driving and speed-limit awareness app. Based on the current Android code, the app may process the following categories of data:

  • Device location readings while live monitoring is active, including latitude, longitude, accuracy, heading, speed, and timestamps.
  • Location-derived road lookup requests sent to SpeedGuard services for speed-limit lookup.
  • App settings and local state, such as speed unit, alert thresholds, alert style, onboarding status, subscription tier, and active monitoring session state.
  • App Check tokens and a locally generated install token used for gateway request protection, diagnostics, or rate limiting.
  • Firebase Analytics and Crashlytics data after onboarding when collection is enabled for the build.
  • Ad request data for free-tier users when Google Mobile Ads is enabled and a banner ad unit is configured.
  • Purchase, subscription, entitlement, and customer-center data handled through Google Play Billing and RevenueCat.

3. Location and monitoring

SpeedGuard requests fine, coarse, and background location permissions on Android. The app uses a foreground service and notification for monitoring. Location is used to estimate speed, evaluate alert settings, and request speed-limit information while the user chooses to monitor driving.

The current Android app may continue processing location while the app is minimized or the screen is off after monitoring has started. Monitoring can be stopped from the app or related foreground-service controls.

4. Speed-limit lookup requests

The app sends recent location-derived trace points to SpeedGuard's gateway for speed-limit lookup. Requests may include latitude, longitude, heading, heading tolerance, accuracy radius, and related request metadata. The current gateway endpoint is backed by Valhalla map-matching services.

Premium users may trigger a HERE-backed fallback through the SpeedGuard gateway. For that flow, the app sends an origin, a projected destination, heading, and forward distance to the SpeedGuard gateway, together with gateway protection headers and a RevenueCat app user identifier when available. The Android app code does not call HERE directly.

SpeedGuard does not use live foreground or background location data for ad targeting in the current Android app code.

5. Local storage on the device

The Android app uses local storage for app settings and runtime state. This can include onboarding completion, speed units, alert thresholds, alert style and volume, speed-limit announcement settings, battery prompt state, subscription tier, RevenueCat app user ID, a generated install token, and an active monitoring session snapshot.

The active monitoring session snapshot may include the last known location state, recent speed-related state, alert state, and speed-limit result information so monitoring can recover more reliably.

The app also maintains an in-memory debug log ring buffer that can be viewed or exported from the app. The debug logger includes redaction logic for sensitive values such as precise coordinates, road names, device tokens, and RevenueCat app user IDs.

6. Analytics, diagnostics, and crash reporting

The Android manifest disables Firebase Analytics and Crashlytics collection by default, and the app initializes those services after onboarding when collection is enabled for the build. The Firebase service can log screen views, monitoring start and stop events, purchase initiation and restore events, non-fatal errors, and subscription tier as an analytics property or crash-report attribute.

Crash reports and diagnostics may include device, app, error, and event context needed to diagnose reliability issues. The app code does not intentionally include precise route history in analytics events.

7. Advertising

The current Android app includes Google Mobile Ads banner support for free-tier users. Premium users are treated as ad-free in the app code. Ads are initialized after onboarding when ads are enabled, the user is on the free tier, and a banner ad unit is available.

Google Mobile Ads and related Google services may process ad request data, device identifiers, advertising identifiers, IP address, approximate location, and ad interaction data according to Google's policies and the user's device settings.

8. Subscriptions and payments

The Android app includes RevenueCat-backed monthly and yearly subscription handling for SpeedGuard Pro. Google Play and RevenueCat process purchases, subscriptions, restores, entitlements, paywall features, and customer-center features.

SpeedGuard may receive or store RevenueCat customer information such as app user ID, active entitlement IDs, active subscription product IDs, purchased product IDs, management URL, and expiration date metadata. SpeedGuard does not receive full payment card numbers from Google Play or RevenueCat.

9. Service providers and third parties

Based on the current Android repository, SpeedGuard may use these services or SDKs:

  • SpeedGuard gateway services for protected speed-limit lookup and request handling.
  • Valhalla-backed map matching for primary speed-limit lookup.
  • HERE Maps through the SpeedGuard gateway for premium fallback speed-limit lookup.
  • Firebase App Check with Play Integrity for gateway request protection.
  • Firebase Analytics and Firebase Crashlytics for analytics and diagnostics when enabled.
  • Google Mobile Ads for free-tier banner ads when enabled.
  • Google Play Billing and RevenueCat for subscriptions, entitlements, paywalls, and customer-center features.
  • Transistorsoft Background Geolocation SDK for Android location monitoring.

10. User choices

  • You can grant or revoke Android location and notification permissions through device settings.
  • You can stop monitoring from the app or foreground-service controls.
  • You can manage Google ad choices and advertising ID settings through Android and Google settings.
  • You can manage subscriptions through Google Play and, where available, RevenueCat customer-center features in the app.
  • You can contact us at info@vehiclespeedingguard.com for privacy questions or requests.

11. Security and retention

SpeedGuard uses HTTPS for gateway requests where supported, Firebase App Check for request protection, Android permissions for sensitive device access, and local redaction for debug log export. No transmission or storage method is completely secure.

Local settings and runtime state generally remain on the device until changed, cleared, or the app is removed. Server-side retention periods for SpeedGuard gateway data are not confirmed by the Android repository and should be reviewed before final publication.

12. Children

SpeedGuard is intended for licensed drivers and is not directed to children. If you believe a child provided personal information through SpeedGuard, contact us so we can review the issue.

13. Changes

We may update this Privacy Policy from time to time. When we make changes, we will update the effective date above.

14. Items requiring operator review

This draft relies on repository inspection only. 17920318 CANADA INC. should review live backend retention, Firebase console settings, AdMob settings, Play Console disclosures, RevenueCat offerings, HERE/Valhalla processing arrangements, regional legal requirements, and whether the production app build enables or disables optional collection flags.