Privacy Policy

Introduction

This Privacy Policy explains how AutoScope Labs Inc. ("AutoScope," "we," "us," or "our") collects, uses, stores, shares, and protects information in connection with the AutoScope platform, including connected-vehicle tracking and the RoadHawk LPR Network, and AutoScope's websites, applications, APIs, and related services (the "Service").

AutoScope is used by law enforcement agencies, government entities, approved private organizations, and their authorized users.

Vehicle owners also interact with the Service when they authorize law enforcement to access their vehicle's location.

Customer agencies control many of the records made available through the Service.

This Policy does not replace an agency's own privacy, records-management, disclosure, or retention obligations.

Information We Process

Account and Authentication Information

Name, email address, organization or agency affiliation, user and authentication identifiers, account status, roles, and permissions.

Connected Vehicle Information

With the vehicle owner's authorization, vehicle identification number (VIN), year, make, model, and color; license plate and plate state; incident type, such as stolen vehicle or Silver Alert; incident or case number; and live GPS location and location history obtained from the owner's connected vehicle service.

Vehicle Owner Information

Information an owner provides or that is generated when the owner authorizes access, including consent and authorization records, timestamps, and the connected-vehicle service used.

Owners sign in through their vehicle manufacturer's authorization process; AutoScope receives the resulting access authorization and does not receive or store the owner's password.

Search and Audit Information

Search inputs, case or incident numbers, justifications, filters, timestamps, user and agency identity, results-access activity, and other actions recorded for accountability.

Device, Browser, and Security Information

IP address, user agent or browser and device details, session and authentication information, device location where a user enables location-based features such as nearby alerts, and mobile notification tokens.

Hosted Detection and Alert Information

License plate or vehicle information, images, timestamps, location, camera or source information, alert records, notes, and attachments processed or stored in AutoScope-managed systems.

Integrated or Federated Information

Information obtained from agency-controlled or third-party systems when an authorized user searches, views, or receives information through an integration.

Operational and Diagnostic Information

Application logs, error records, performance information, security events, and service activity used to operate and protect the Service.

Governance and Organization Records

Authorized-representative information, Memoranda of Understanding, Terms of Use acceptances, attestations, sharing elections, signatures, timestamps, and related audit records.

Billing and Support Information

Billing contact information, subscription status, support communications, and transaction references where applicable.

Payment providers may process payment-card details under their own policies; AutoScope need not receive full card details.

Sources of Information

We receive information from users and their organizations; from vehicle owners who authorize access; from vehicle manufacturers and connected-vehicle services, once an owner authorizes it; from systems connected or configured by an agency; from service providers supporting the Service; and automatically through use of the Service.

Some information displayed in AutoScope remains in an agency-controlled or third-party source system and is not stored by AutoScope as a hosted record.

How We Use Information

• To provide, authenticate, administer, and support the Service.
• To locate vehicles that owners have authorized for tracking, and to display their location and location history to authorized users.
• To send alerts to authorized users near a tracked or wanted vehicle.
• To process searches and display detections, alerts, images, and related information.
• To enforce agency permissions, sharing elections, roles, subscriptions, and security controls.
• To send authorized service, security, governance, email, and push notifications.
• To maintain audit trails, investigate misuse, and support legal and policy compliance.
• To monitor, troubleshoot, secure, and improve reliability and performance.
• To comply with law, valid legal process, contracts, and enforceable requests from authorized customer organizations.

AutoScope does not sell personal information.

We do not use Agency Data or vehicle owner information for unrelated advertising or grant ourselves a general right to commercially exploit it.

Agency Control, Owner Consent, and Sharing

Agencies control access to and sharing of their data through their agreements, administrator settings, governance elections, partner selections, and other configured permissions.

AutoScope processes and discloses Agency Data as directed or authorized by the controlling agency, as needed to provide and secure the Service, or as required by law.

An agency's election does not permit sharing beyond the access actually authorized and implemented.

Federated data also remains subject to the source agency's authority and the source provider's controls.

AutoScope does not override an agency's legal obligations, public-records duties, retention rules, or restrictions imposed by a source system.

Connected-vehicle location is accessed only after the vehicle owner authorizes it.

Once a vehicle is connected, its location is visible to authorized users in the connecting agency.

Access ends when tracking is deactivated, including when the vehicle is recovered or the owner withdraws consent.

Service Providers and Other Disclosures

We may provide information to service providers that perform functions for the Service, including cloud infrastructure and storage, connected-vehicle data services, authentication, database and security services, email and push notifications, billing, communications, and technical support.

These providers may process information only for the services they provide to us and under applicable contractual and security obligations.

Connected-Vehicle Services

AutoScope connects to vehicle manufacturers' connected services through a third-party connected-vehicle data platform.

When an owner authorizes access, the owner signs in through that platform's authorization process, and vehicle data is delivered to AutoScope through it.

The platform's handling of that data is governed by its own privacy policy, which is presented to the owner during sign-in.

AutoScope selects connected-vehicle providers that maintain recognized independent security certifications.

We may also disclose information when reasonably necessary to comply with law or valid legal process; protect users, agencies, vehicle owners, AutoScope, or the public; investigate fraud, misuse, or security incidents; enforce applicable agreements; or complete a corporate transaction subject to appropriate protections.

Where an agency controls the requested records, we may refer the request to that agency when permitted.

Data Storage and Retention

Retention depends on the type of information, where it is maintained, applicable law, agency policy, contract, and configuration.

Connected Vehicle Location Data

Location access ends when tracking is deactivated. Location history collected during an active incident is retained for [30] days after deactivation, unless a shorter period is required by law, agency policy, or contract, or a longer period is required by law or a legal hold.

AutoScope-Hosted LPR Detection Data

Covered Connecticut-hosted LPR detection data is retained for no more than 21 days where that requirement applies. Outside Connecticut, AutoScope-hosted detection data may generally be retained for up to 30 days.

A shorter period may apply when required by law, agency policy, contract, or configuration.

AutoScope-Hosted Alerts

Hosted alert records and associated images follow the same regional retention limits as AutoScope-hosted detections: no more than 21 days where the Connecticut requirement applies and generally up to 30 days outside Connecticut.

A shorter period may apply when required by law, agency policy, contract, configuration, or an authorized agency deletion request.

Federated or Source-System Data

Information queried or displayed from an agency-controlled or third-party system may remain in that source system. Its retention is controlled by the applicable agency or provider, not by AutoScope's hosted-data schedule.

Search Information and Results

AutoScope may temporarily process or cache information needed to return a search, while audit metadata about the search may be kept longer for security, accountability, and compliance.

A source-system result may remain subject to the source system's retention rules.

Accounts, Governance, Audit, Security, Billing, and Operational Records

These records may be retained longer when reasonably necessary for administration, accountability, security, dispute resolution, legal compliance, or enforcement of agreements.

Deletion and Backups

When information is deleted from active systems, limited residual copies may remain temporarily in backups or logs until they are overwritten or deleted under applicable procedures, unless preservation is required by law or a legal hold.

Account Deletion, Deactivation, and Agency Records

Users may request account deletion through the Service's account-deletion process or by contacting support.

Deleting an individual account does not necessarily delete agency-controlled records, audit entries, governance records, alerts, or other information that an agency or AutoScope must retain for security, legal, contractual, or accountability purposes.

Requests concerning agency-controlled records may be referred to the applicable agency.

Vehicle owners may withdraw consent at any time by contacting the investigating agency or AutoScope support, which ends location access for that vehicle.

Owners can also revoke access through their vehicle manufacturer's connected-service account settings.

Security

We use administrative, technical, and organizational safeguards designed to protect information. These include:

• Access controls: Individual accounts tied to agency-issued email addresses, role-based permissions, and agency-controlled sharing settings, so users can access only the data they are authorized to see.
• Authentication protections: Password-protected accounts, each tied to a verified agency email address.
• Encryption: Data is encrypted at rest using AES-256 and in transit using TLS.
• Audit logging: Searches, record access, exports, and changes to sharing settings are logged and available to agencies for supervision and review.
• Owner credential protection: Vehicle owners sign in through the connected-vehicle provider's authorization process. AutoScope does not receive or store owners' passwords.
• Restricted internal access: AutoScope personnel access customer data only as needed to operate, secure, and support the Service.
• Monitoring: Ongoing monitoring of systems for security events and misuse.
• Vendor due diligence: Connected-vehicle data providers each maintain SOC 2 Type 2 reports.
• Incident response: We maintain procedures to investigate and respond to security incidents, and will notify affected agencies and individuals as required by law.

Changes to This Policy

We may update this Policy to reflect changes in the Service, law, or our practices.

We will post the revised Policy with a new effective date and provide additional notice when required by law or an applicable agreement.

Changes to the AutoScope Terms of Use, an agency's Memorandum of Understanding, attestations, or governance elections will be handled under the applicable agency process.

Contact Us