Where your data goes, and who touches it.

Where is our data processed?

In the delivery centers named in your contract, and nowhere else. We operate in the United States and India. Which of those handles your program is a contractual term you set, not an operational detail we decide later. If your procurement requires US-only processing, say so and we will scope it that way.

Can review be performed onshore?

Yes. Where a program requires it, we stand up review capacity in Texas and commit to it in writing. We would rather have that conversation during evaluation than discover a restriction after award.

Do reviewers see anything beyond the image?

Reviewers see the vehicle image, the region of interest and the fields required to disposition the transaction. Access is role-separated on least privilege: a plate reviewer does not hold jurisdiction-review permissions on the same transaction, and neither holds supervisor adjudication rights. That separation is what makes the double-blind method real rather than nominal.

How is registration data handled?

Registered-owner and vehicle registration data is regulated under the Driver’s Privacy Protection Act. We treat it as purpose-limited: it is used for the permitted toll and violation processing purpose defined in your agreement, accessed only by staff whose role requires it, and never repurposed, resold or retained beyond the term we agree. Where a workflow requires DMV or registration lookups, we support your authorised process rather than asserting independent access to restricted networks.

What can leave the workstation?

Nothing. Review workstations have no local storage available to the user, no removable media, and no ability to print, email or upload from the review environment. Personal devices are not permitted on the review floor.

How long do you keep our data?

For the retention period your contract specifies, then it is purged on a documented schedule with confirmation back to you. If you want zero retention beyond the processing window, that is a valid answer and we will build to it.

What happens if something goes wrong?

A named US-based program lead is your escalation path, not a ticket queue. Incident notification timelines, severity definitions and the reporting format are agreed in the contract before it starts, so nobody is negotiating those terms during an actual incident.

Can we audit you?

Yes, and we would rather you did. Every action against a transaction is logged and exportable. You can assign audits against our reviewers at any time, sample our output independently, and request site access to a delivery center under the terms of your agreement.

Who owns the work product?

You do. Your images, your transactions, your dispositions and the audit record of all of it. We hold no residual rights and we do not use client data to train anything.

Evaluators are usually asked to score security on documents, not on conversations. These are the documents we will provide during your evaluation, on request, before any award.

• Data flow and residency statement. Where your data goes, which systems touch it, which delivery centers process it, and where it rests at each stage.
• Access control matrix. Every role that can see your data, what each role can and cannot do, and how separation of duties is enforced in the review workflow.
• Retention and destruction schedule. How long each data class is held, how it is purged, and how destruction is confirmed back to you.
• Incident response commitments. Severity definitions, notification timelines, escalation contacts and reporting format, agreed in advance.
• Personnel screening and training summary. What screening is performed, what training is required before live queue access, and how access is revoked.
• Onshore handling scope, where required. If your program restricts processing to US soil, the specific scope, location and staffing committed to it.