SkyTrade LPR

License plate recognition. Under your control.

Bring plate recognition, vehicle alerts and incident review into one operating environment, with clear rules for who can access your data, how long it is retained and which agencies you choose to share with.

  • Agency-controlled access
  • Approved sharing
  • Defined retention
  • Clear audit records
Vehicle record Review required
Rear view of a white sedan with plate R7X 482 on a city street with construction buildings in the background.
R7X 482 Plate read
Captured
5:41 PM
Location
Market St, camera 04
Match
Agency-approved list
Human review
Workflow preview: vehicle capture, alert review and recorded action.

Operational outcomes

Turn plate reads into useful action.

Find relevant vehicles.

Search authorized plate records and review the supporting image, time and location.

Get the right alert.

Route relevant vehicle matches to the appropriate team using approved lists and workflows.

Review what happened.

Open the associated record, check the information and document the next action.

An automated match is a lead for human review, not a finding of wrongdoing.

Agency control

Your agency sets the rules.

Local control needs clear answers about access, sharing, retention and accountability. Put those answers into the operating requirements for your deployment.

Data ownership and use.

Set out ownership of plate records, images and derived data, together with the purposes for which SkyTrade and its technology providers may process them.

Sharing by agreement.

Define approved recipients, the information they may access and who authorizes each relationship. Make changes to future access part of the agency's approval process.

Retention by policy.

Establish retention and deletion requirements for records and images, with clear treatment of preserved evidence, audit logs and backups.

Accountable access.

Define named users, role permissions and controlled provider support access, with a clear record of the searches and changes included in your deployment's audit scope.

Product workflow

From plate read to agency action.

Follow a relevant vehicle record from capture through review, with the supporting information available at each step.

  1. Capture the record.

    Bring the plate image, time and camera location into the review workflow.

  2. Identify a relevant match.

    Surface a match against an agency-approved list or rule supported by the deployment.

  3. Review the information.

    Give an authorized user the record and context needed to check the match.

  4. Record the action.

    Document the review outcome and agreed next step in the supported workflow.

Deployment

Build on the cameras you have.

Reuse what fits

Start with a review of your existing cameras and sites. Reuse suitable equipment where image quality, placement and supported interfaces meet the requirements, and add hardware where needed.

A defined delivery scope

Your deployment scope sets out site assessment, integration, data-control requirements, training and support, with clear responsibilities for delivery and ongoing operation.

Frequently asked questions

Questions from agency teams.

Answers for police, sheriff, IT and procurement teams.

Who can access our data?

Your deployment plan identifies authorized agency users, approved outside recipients and the provider personnel who need controlled support access. It also sets out their permissions and the activity included in audit records.

Can we share with neighboring agencies?

The proposed sharing model is based on named participants and explicit agency approval. Your plan sets out the supported access controls, the information covered and the rules for onward use.

Can we use our existing cameras?

Suitable existing equipment can be considered first. Image quality, placement, lighting, supported interfaces and connectivity determine whether a camera can meet the requirements or needs replacement.

How are retention and deletion handled?

Your plan specifies supported retention and deletion behavior for records, images, audit logs and backups, including how preserved evidence and required records are handled.

What happens when the contract ends?

Your deployment plan sets out contract-end provisions for data export, deletion and equipment, including how preserved evidence and required records are handled. These provisions belong in the agreed contract terms.

Is the technology already deployed?

Yes. The underlying license plate recognition technology has been deployed in operational environments, and we provide the agreed integration, training, and support for your agency's program.

Deployment inquiry

Plan an LPR deployment around your agency's requirements.

Tell us what your agency needs to achieve. We will review your camera estate, operating requirements and data-control priorities, then outline the proposed deployment and next steps.

  • Camera and site fit
  • Data-control requirements
  • Proposed scope and costs

We will use these details to respond to your inquiry. Privacy policy