Effective date: September 14, 2026
This Privacy Policy explains how 17920318 CANADA INC., operating SpeedGuard ("SpeedGuard," "we," "us," or "our"), handles information when you use the SpeedGuard mobile app.
SpeedGuard is a driving aid that uses your device location to measure speed, look up posted speed limits, and alert you when you exceed the applicable alert threshold for your subscription tier. SpeedGuard does not sell personal data or sensitive personal data.
Depending on how you use the app, SpeedGuard may process:
SpeedGuard accesses device location when you grant location permission and start monitoring, or when your selected car connects after you explicitly enable Bluetooth automatic monitoring. This may include:
We use this data to:
SpeedGuard may process location while the app is minimized or the screen is off after you start monitoring manually or explicitly enable Bluetooth automatic monitoring. Monitoring can be stopped from the app or the foreground-service notification.
Premium users on supported Android devices may select one paired car and opt into automatic monitoring. With the required permissions, a Bluetooth car connection can start monitoring even when the app is closed or the screen is off. GPS monitoring is not kept active merely to wait for a car connection. Automatic monitoring stops after the car has disconnected for two minutes and fresh GPS readings confirm one minute stationary. If GPS cannot confirm this, monitoring continues and a Stop reminder appears after five disconnected minutes.
The selected car's Bluetooth identity and name, connection timing, and ride suppression state remain on your phone and are not included in analytics, drive summaries, or Automatic Drive Reports. “I'm a passenger” stops monitoring, discards the current automatic trip from completed-drive history and reporting, and suppresses restarting for the ride. Removing the selected car or resetting app settings disables Bluetooth automation and removes the car association. Standard location processing and speed-limit lookup disclosures still apply while an automatic monitoring session is active.
To identify posted speed limits, SpeedGuard sends location-derived road lookup data to SpeedGuard backend services. These requests may include:
x-device-token header, when available, for coarse diagnostics and rate-limiting. This token is not proof of identity, app authenticity, or subscription entitlement.X-Firebase-AppCheck header for gateway authentication.Free-tier speed-limit lookup uses the SpeedGuard gateway and Valhalla map-matching backend. For Premium users, Valhalla detects road/segment candidates, while user-facing speed-limit authority comes from HERE through the gateway after App Check and RevenueCat entitlement verification. HERE is not called directly by the mobile app.
These services process location-derived road data to return speed-limit information. SpeedGuard does not use location data for advertising targeting.
SpeedGuard stores some data locally on your device using app storage, including:
Completed-drive summaries do not contain coordinates, route traces, raw GPS samples, or road names. They remain on your device unless you choose to export or share them, or explicitly enable Automatic Drive Reports as described below. After agreement acceptance, Firebase Analytics may receive a drive_completed event containing coarse duration, distance, score, GPS-coverage, and speed-limit-coverage bands plus subscription tier, unit, and foreground/background mode. It does not receive coordinates, route traces, road names, exact timestamps, exact drive values, or drive/session identifiers. Local summaries are used to provide app functionality and are generally removed when you uninstall the app, subject to Android platform behavior. Copies you exported or shared are not removed by uninstalling SpeedGuard.
Completed-drive distance, speed, stop, braking, acceleration, compliance, and score values are GPS-based estimates. They may be incomplete or inaccurate when GPS quality, sampling continuity, or trusted speed-limit coverage is limited and should not be treated as a verified vehicle record or safety determination.
All Android users can manually export completed-drive summaries and portable settings as an encrypted backup protected by a passphrase they choose, and import that backup on another Android phone. SpeedGuard does not receive the backup or passphrase and cannot recover a forgotten passphrase. Backups exclude active monitoring data, coordinates, routes, raw GPS, road names, credentials, subscriptions, permissions, consent/agreement acceptance, Automatic Drive Reports configuration and Bluetooth car pairing. Newly imported drives are not uploaded through Automatic Drive Reports.
Users can also export an unencrypted CSV containing their derived drive statistics. Anyone receiving that CSV can read it. Android's file picker and share sheet let users choose where files go, including a cloud storage provider or another app. Those providers and recipients control their copies under their own terms and privacy practices. SpeedGuard cannot delete those copies when local history is deleted, app data is cleared or the app is uninstalled. Unshared temporary export files are removed when cancelled; temporary files handed to another app are cleaned after 24 hours when SpeedGuard next starts or creates an export.
Android Premium users may choose to send one confirmed recipient a daily email containing previous-day totals and compact per-drive derived statistics. Setup requires a recipient email address, a vehicle or driver label, an IANA timezone, a device-local control PIN, and feature-specific acceptance. We confirm control of the email address, but we do not verify the recipient's identity, parental relationship, employer role, legal authority, or relationship to the driver. The person configuring reports is responsible for obtaining any consent or authority required by law.
If enabled, SpeedGuard reporting services may process:
Automatic Drive Reports do not upload or include coordinates, route traces, raw GPS samples, road names, maps, or live location. Reports are not continuous tracking and SpeedGuard does not provide a recipient account, fleet dashboard, or cross-device trip view. Reports begin only after email confirmation, are sent at approximately 7:00 AM in the configured timezone for the previous local day, and are skipped on days with no eligible completed drives. The confirmed recipient can unsubscribe and can receive a PIN-recovery link.
Clearing app data or uninstalling SpeedGuard removes local reporting controls and queued data from that device, but is not itself a request to delete an already configured cloud report subscription. Use the protected in-app cloud deletion control before clearing/uninstalling when possible. A recipient can use an unsubscribe link in a report email to stop future messages.
We use Postmark to deliver confirmation, recovery, and report emails with open and link tracking disabled by our configuration. Postmark may still process the recipient address, message content, IP/network information, and delivery/bounce/complaint metadata as an email service provider. Provider suppressions are used to avoid sending to addresses that bounced, complained, or unsubscribed.
After the current User Agreement is accepted, SpeedGuard may initialize Firebase Analytics, Firebase Crashlytics, Firebase Performance Monitoring, and Firebase Remote Config if enabled for the build. These services may process:
We use this information to understand app quality, diagnose crashes, improve reliability, and measure feature usage. We do not include coordinates, route history, road names, exact drive/session identifiers, customer identifiers, ad-unit IDs, or secrets in these analytics events or custom performance traces. Remote Config does not change speed-limit authority, alert thresholds, subscription access, or credentials.
If TikTok App Events SDK is enabled for an Android build, it initializes only after the User Agreement/app-use gate is satisfied. TikTok may process install, launch/retention, app event, advertising/device identifier, and purchase/subscription event data for advertising measurement and campaign optimization. SpeedGuard does not intentionally send email addresses, phone numbers, external user IDs, precise route history, or location-derived road data to TikTok.
Free-tier users may see banner ads if advertising is enabled and production AdMob IDs are configured. Google AdMob and related Google advertising services may process device identifiers, advertising identifiers, approximate location, IP address, ad interaction data, and other data as described by Google's policies.
TikTok App Events SDK, when enabled, may process advertising/device identifiers and app event data for attribution, measurement, and campaign optimization. It is not used by SpeedGuard to send foreground or background location data for ad targeting.
Ads are not shown to premium users. SpeedGuard does not use foreground or background location data for ad targeting.
SpeedGuard uses RevenueCat and Google Play Billing to manage subscriptions. Purchase processing is handled by Google Play and RevenueCat. SpeedGuard may receive or process:
SpeedGuard does not receive your full payment card number from Google Play or RevenueCat.
If TikTok App Events SDK is enabled, Google Play Billing purchase and subscription events may be shared with TikTok for advertising measurement and campaign optimization.
When the app communicates with SpeedGuard services or third-party SDKs, basic network and device information may be processed automatically, such as:
We use information to:
We may share information with service providers that help operate SpeedGuard, including:
These providers process data according to their own terms and privacy policies and/or as service providers for app functionality. We may also disclose information if required by law, to protect rights and safety, or as part of a merger, acquisition, or business transfer.
We do not sell personal data or sensitive personal data.
SpeedGuard may request:
You can manage permissions in Android system settings. If required permissions are disabled, monitoring may not work.
Local settings, active monitoring state, temporary trusted road-limit continuity/cache data, and the install token are retained on your device until you clear app data or uninstall the app. Completed-drive summaries remain on your device until you delete an individual drive, use Clear All History, clear app data, or uninstall the app. Persistent repeat-route speed-limit segment caching is not enabled in production unless segment-cache persistence is restored in a future build.
SpeedGuard backend logs and diagnostics are retained only as long as reasonably needed for service operation, security, debugging, rate-limiting, and legal compliance.
For Automatic Drive Reports, unconfirmed configurations, queued drive events, and keyed setup/confirmation abuse-prevention counters are retained for up to 7 days. Drive-event payloads are removed immediately after a successful or ambiguous terminal delivery attempt. Idempotency operation receipts are retained for up to 35 days, suspended configurations for up to 30 days, and delivery metadata for up to 90 days. A protected deletion request removes report configuration and report data from active systems within 24 hours. Encrypted backups expire within 30 days, and deletion records are replayed before a backup restore is permitted to serve report data. Provider suppression records may be retained as reasonably necessary to honor unsubscribe, bounce, and complaint no-send obligations.
Firebase, AdMob, Google Play, RevenueCat, HERE, TikTok, and Postmark may retain data according to their own policies and your account or device settings.
You can:
Privacy requests: info@vehiclespeedingguard.com
Because SpeedGuard does not require an in-app account, some app data exists only on your device and cannot be accessed by us unless you send it to us or it is included in diagnostics handled by a provider.
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.
SpeedGuard uses HTTPS for network requests where supported and uses Android platform permissions to control access to sensitive device data. No method of transmission or storage is completely secure, but we use reasonable technical and organizational measures to protect information.
SpeedGuard and its service providers may process information in the United States and other countries where we or our providers operate. Data protection laws in these locations may differ from those in your country or region.
You can review the policies of key providers here:
We may update this Privacy Policy from time to time. When we make changes, we will update the effective date above. If changes are material, we may provide additional notice in the app or through the store listing where appropriate.
Developer / legal entity: 17920318 CANADA INC.
Website: Speedguard.net
Privacy contact: info@vehiclespeedingguard.com