1. Scope and Our Role
This Policy applies to the SmartCheck website, support channels, mobile application, and related license plate recognition, vehicle matching, patrol logging, and handoff features.
For website, account, contract, and support information, the provider of the Service acts as the controller or primary business operator. For vehicle-related metadata processed by organizational customers through the Service, the provider of the Service may act as a service provider, processor, or entrusted processor depending on the contract and applicable law.
2. Information We Collect
We may collect or generate the following categories of information:
- Names, email addresses, organization names, location names, billing details, and other registration information
- Device identifiers, operating system data, application version, sign-in state, language settings, and usage logs
- OCR results, confidence values, timestamps, optional location data, patrol records, confirmation state, and other text metadata
- On-device evidence images and local retention settings, where those images are processed and stored on the device only
- Vehicle allow lists, block lists, comments, handoff notes, audit logs, and support-related records
- Inquiry contents, reply history, error logs, and security investigation information
3. Purposes of Use
We use the information above to provide authentication, organization setup, billing support, patrol workflows, vehicle matching, support, quality improvement, security monitoring, legal compliance, and important notices.
4. Sources and Permissions
We collect information that you submit directly, information provided during contracting or support, data obtained through mobile device permissions, and logs generated automatically when the Service is used.
Camera and location access follow the permission settings of the operating system. Evidence images are intended to remain on-device only and are not automatically sent to the cloud. If a user chooses to use sharing or text-sync functions, metadata such as recognition results, recognition time, optional location data, and organization context may be synchronized based on explicit user action or consent.
5. Processors, Service Providers, and International Transfers
Evidence images and thumbnails are not intended to be uploaded to or stored in cloud infrastructure.
If a user enables sharing or text-sync functions through an explicit action or consent flow, account data, organization data, recognition results, timestamps, optional location data, and related text metadata may be transmitted to cloud infrastructure. The current implementation includes services such as Supabase Auth and Postgres.
We may also use hosting, CDN, email, monitoring, billing, and operational vendors. Information may be processed or stored outside the country where the user or customer is located.
We do not sell personal information for advertising resale purposes.
6. Retention and Deletion
Retention periods depend on the type of data, contract terms, organizational settings, legal obligations, security needs, and backup operations.
On-device evidence images may remain only within the application container until deleted by the user, purged by retention settings, sign-out, full local data deletion, or application removal.
Cloud data is intended to be limited to user-triggered text metadata synchronization and may remain for a limited period after contract termination where needed for billing, legal compliance, dispute resolution, security, or backup integrity.
7. ALPR Data, Sharing, and Public-Sector Style Controls
Vehicle-related text metadata such as plate strings, recognition results, timestamps, optional location data, and patrol records are used to support patrol operations, matching, handoff, and auditability. On-device evidence images are intended to remain local to the device and outside the default cloud-sharing contract. Because this information can be operationally sensitive, customers are responsible for defining authorized users, access scopes, retention schedules, sharing restrictions, and review procedures.
Where U.S. ALPR laws or customer policies require a public written policy, audit trail, correction channel, or specific retention and destruction controls, we provide infrastructure features only. The customer remains responsible for publishing and operating the required policy and procedures.
We may disclose information where required by law, court order, regulatory request, emergency safety needs, or reasonable fraud or abuse investigation.
8. Your Rights
Subject to applicable law, you may request access, correction, deletion, restriction, objection, portability, or withdrawal of consent regarding your personal information.
If the request concerns organizational customer data, we may direct the request to the relevant administrator or require organizational verification before acting.
9. Security and Incident Response
We implement reasonable administrative, technical, and organizational safeguards, including access control, authentication, encryption, logging, and least-privilege practices. No method of transmission or storage is completely secure.
If a privacy or security incident occurs, we will investigate, contain, remediate, and notify or report as required by applicable law.
10. Policy Changes
We may update this Policy to reflect legal changes, regional deployment changes, new service providers, feature updates, or security controls. Material updates will be communicated through a reasonable notice method on the site or in the app.