SpeedGuard Privacy Policy

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 monitoring stops when SpeedGuard leaves the foreground or the iPhone locks. With an active Premium subscription and Always Location access, a user-started session may continue while the app is in the background or the screen is off. Monitoring can always 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.

Valhalla-backed map matching detects the current road and may provide speed-limit information used for display, alerts, and announcements.

For Premium subscribers, SpeedGuard may also use HERE Technologies (HERE) to verify the current road and its speed limit. The app sends these requests only to the SpeedGuard gateway, never directly to HERE. A Premium request may include up to 12 recent trace points (latitude, longitude, and, when available, heading, GPS accuracy, and timestamp), the current heading, the random installation token, Firebase App Check proof, and the pseudonymous RevenueCat app user identifier. The gateway sends that RevenueCat identifier to RevenueCat to confirm an active Premium entitlement and may use it for rate limiting.

After the entitlement check, the gateway sends HERE recent trace coordinates and, depending on the matching method, the related timestamps and headings. The gateway does not forward the installation token, App Check proof, RevenueCat identifier, or GPS accuracy to HERE, and HERE receives the request from SpeedGuard's servers rather than from your device. HERE returns road and speed-limit information that SpeedGuard uses for display, alerts, and announcements, and processes request data under its own terms and privacy policy.

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.
• A pseudonymous RevenueCat app user identifier used to provide and restore Premium and, for Premium speed-limit requests, to verify entitlement through the SpeedGuard gateway.
• Firebase installation and analytics identifiers used for app security, configured analytics, crashes, and diagnostics.
• 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. Optional Automatic Drive Reports connects its reporting identifiers to the confirmed recipient address and vehicle or driver label. Other functionality does not intentionally connect these identifiers to a 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 and UMP successfully resolves consent without denying analytics, configured Firebase Analytics may process allowlisted information such as app launches, screen views, monitoring start and stop events, feature use, ad reliability, purchase initiation, coarse completed-drive bands, 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, or device tokens. Failed allowlisted events may remain temporarily in a bounded local queue until a later delivery attempt.

After consent, Firebase Remote Config may fetch bounded feature and reliability settings such as Performance collection, ad recovery, and gateway timeout or backoff profiles. It is fetched once during app bootstrap rather than updated in realtime during a drive. Remote Config can show or hide the in-app free-trial promotion, but it cannot create a trial; any free trial is offered and managed by the App Store.

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.

Purchases and Subscriptions

SpeedGuard offers monthly and yearly auto-renewing Premium subscriptions through Apple's App Store. The monthly plan may start with a free three-day introductory trial for eligible App Store accounts. Apple decides eligibility, and the subscription renews at the regular monthly price unless canceled before the trial ends. Apple processes payment and payment-card details; SpeedGuard does not receive full payment-card information. RevenueCat helps the app display, verify, restore, and manage Premium access.

Apple and RevenueCat may process a pseudonymous app user identifier, product identifier, purchase or subscription status, trial or introductory-period status, transaction history, renewal and expiration dates, and related entitlement information. SpeedGuard uses this information for app functionality and analytics, including restoring Premium and authorizing Premium services. Purchase History is treated as linked to the user because it can be associated with an App Store account, device, or persistent pseudonymous identifier. It is not used for tracking.

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.

Firebase Performance may record allowlisted timing traces for app bootstrap, monitoring start, Statistics loading, Valhalla, and HERE. Trace attributes are bounded and do not intentionally include coordinates, routes, road names, tokens, exact drive identifiers, or free-form values.

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.

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. Without separate Automatic Drive Reports opt-in, complete summaries remain on the device, are available to every user, and support History, Drive Details, and Insights. After consent, a separate exact-once analytics event may send only coarse bands for duration, distance, score, GPS coverage, speed-limit coverage, and confidence plus tier, background mode, and unit. It does not send the local drive identifier or full summary. The app may also record bounded product-interaction events for tutorial use, threshold bands, post-drive summary views, and whether a qualifying drive is the first or a repeat within seven days. These events do not include a local drive identifier, exact threshold, coordinates, routes, or the full summary. Product Interaction and Performance Data in the App Store disclosure cover these bounded events.

Private Backup, Transfer, and CSV Export

Every user can manually export completed-drive summaries and portable settings as an encrypted backup protected by a passphrase they choose, and restore that backup on another iPhone or Android phone. The file is created on the device; 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 and agreement acceptance, and Automatic Drive Reports configuration. 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. The iOS Files picker and share sheet let users choose where files go, including iCloud Drive, another 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 or the app is removed. Temporary export files stay inside the app. They are removed when saving finishes or is cancelled; files handed to the share sheet are cleaned after 24 hours, when SpeedGuard next starts or creates an export.

Optional Automatic Drive Reports

Automatic Drive Reports is an optional Premium feature available on iOS starting with version 1.13. Setup requires separate acceptance of the reporting notice, one recipient email address confirmed through an email link, one vehicle or driver label, an IANA time zone, and a six-digit management PIN. Setup and report emails are in English. Reports are scheduled for 7 AM in the selected time zone; days without completed drives are skipped. Delayed uploads may appear in a later report.

When enabled, the app sends only an allowlisted subset of derived completed-drive statistics, including drive identifiers and timestamps, duration, distance, speed aggregates, coverage, compliance, event counts, and scores. Reports contain no coordinates, routes, road names, raw GPS samples, or live location. SpeedGuard associates the reporting installation and subscription identity with the confirmed recipient and label. Postmark processes the recipient address, label, and email content to deliver confirmation, daily report, and recovery messages. Email open and click tracking are disabled.

The PIN verifier, lockout state, management capability, and reporting installation identity remain in device-only iOS Keychain storage available after first unlock. An installation marker excluded from backups detects reinstall and discards stale reporting credentials. The PIN itself is not sent to the reporting server. Reset links carry short-lived tokens; these are not stored in persistent JavaScript storage or intentionally included in logs.

You can pause reports, request PIN recovery, or delete cloud reporting data after Premium expires or reporting is disabled. Deleting local history also queues deletion of corresponding uploaded report data. Offline deletion requests are retained until acknowledged. Uninstalling removes local access but does not itself delete cloud reporting data or recall emails already delivered; use the in-app deletion control or contact us. Recipients can pause future emails using the unsubscribe link.

Unconfirmed configurations and queued server drive payloads are retained for up to 7 days. Payloads are removed after successful or ambiguous delivery attempts; duplicate-operation receipts may remain for 35 days, suspended configurations for 30 days, delivery metadata for 90 days, and setup or confirmation abuse-prevention counters for 7 days. Cloud deletion removes eligible active-system data immediately on successful processing, with a published 24-hour objective. Encrypted backups have a maximum 30-day retention and require deletion-ledger replay before restored service resumes. Minimal deletion and no-send suppression records are retained to prevent deleted data or unwanted emails from returning. Received emails remain under the recipient and email provider’s control.

Other Information Stored on the Device

The app may store:

• Speed unit, separate Free/Premium alert-threshold profiles, other alert preferences, language, and announcement preferences.
• Onboarding, current User Agreement acceptance, permission-introduction state, and first-run Dashboard tutorial completion or skip 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, the cached subscription tier, and the pseudonymous RevenueCat app user identifier.
• Whether a qualifying drive has made the account eligible to see the in-app free-trial promotion, a product-analytics retry queue of no more than 100 events and durable once-only analytics markers.

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.
• Provide, verify, manage, and restore Premium subscription access.
• Verify app integrity, protect gateway services, prevent abuse, and enforce rate limits.
• 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, rate limiting, and abuse prevention.
• Valhalla-backed services for road detection, map matching, and supported speed-limit results.
• HERE Technologies for Premium road matching and speed-limit verification, using recent trace coordinates and related timing and heading data that the SpeedGuard gateway forwards.
• Firebase and Google for App Check, configured analytics, Performance, Remote Config, crash reporting, diagnostics, UMP, and eligible non-personalized AdMob banners.
• Apple and RevenueCat for App Store subscription purchase processing, entitlement verification, restoration, and subscription management.
• Postmark for optional reporting emails, confirmation, recovery, and delivery suppression.
• 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. Free monitoring uses While In Use access. Premium may request Always access when a user starts monitoring so the session can continue in the background or with the screen off.

You can:

• Stop monitoring at any time in the app.
• Change or revoke Location access in iOS Settings.
• Manage or cancel a subscription in App Store account settings and restore a qualifying subscription in SpeedGuard using the same App Store account.
• Open Privacy choices in Settings to revisit UMP privacy options when offered. Analytics queues remain closed while consent is unresolved and are discarded when analytics consent is denied. Advertising permissions remain denied.
• 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 info@vehiclespeedingguard.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, or anonymous installation identifier. 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, 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, 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

• Apple Privacy Policy
• RevenueCat Privacy Policy
• Google Privacy Policy
• Firebase Privacy and Security
• HERE Privacy Policy

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.