Security

Data handling and security

Dorvy Tech can run inside your network. Here is what it needs, how it runs and what we commit to.

Updated 16 October 2026.

A road curving into a misty pine forest

In short

  • We need vehicle fields only. No registration number, no owner details.
  • It can run on your own servers. It needs no internet connection to match.
  • Your files are deleted when the work ends, or sooner if you ask.
  • We sign your NDA before you share anything.

What we need, and what we don't

What we need

  • Maker and model text, as on the RC
  • Fuel, cubic capacity (cc) and seats
  • Body type, emission norms, vehicle class and category
  • A row ID of your own, so you can join the results back to your records
  • For the comparison only: the insurer vehicle codes you use today

What we don't need

  • Registration number, chassis number, engine number, owner name, address, phone number, email address, policy number, or any KYC details.

Please remove these before you send a file. If a file reaches us with them, we delete it and ask for a clean copy.

Matching does not use the registration number at all. Without these fields, what you send describes a vehicle model, not a person.

Ways to run it

On your own servers

  • A service that runs on an ordinary CPU, on Linux or macOS. No GPU.
  • It makes no outbound network calls, so your data stays on your network.
  • By default it accepts connections only from the machine it runs on.
  • Calls from other machines need an API key, and keys are stored only as hashes.

Files, for the comparison and pilots

  • You send a file of vehicle fields. We run it on our own machine and send the results back.
  • Please send files encrypted, for example as a password-protected archive, with the password sent another way.
  • We don't upload your files to outside services, including AI services, unless you agree in writing.
  • We delete your files when the work ends, or sooner if you ask.
  • If your own rules don't allow RC-derived data to go to a vendor, run it on your own servers. Then nothing leaves your side.

Logs and traces

Every pick can be audited. Each request leaves a trace on the machine the service runs on.

A trace holds the vehicle fields received, the results and the details behind each pick.

Trace files can be read only by the account the service runs under. They are deleted after 30 days by default; you can change this.

The service log records IDs, timings and status, not vehicle or personal data.

If a registration number is sent anyway, the service can mask it in traces with one setting.

Our commitments

We don't sell RC lookups or resell RC data.

We never share one customer's data or files with another.

We don't use your data to improve the product without your written OK.

If we host it for you, it is hosted in India.

Starting a vendor review?

Send us your security checklist and we'll answer it item by item.

Send your checklist

To report a security issue, email [email protected] with “Security” in the subject.