Privacy policy

This explains what Rahdari collects about you and the vehicles you enquire about, why, who else sees it, and what you can ask us to do with it.

Last updated 1 September 2026. We will say on this line whenever it changes.

1. Who is responsible

Rahdari operates this platform and decides how the information described here is handled. Any question about this policy, or any request under section 8, should go to the contact page.

2. What we collect

Account details you give us. Your name, email address, and optionally a phone number, designation, office, district and state. Your email address is also your sign-in name.

What you do here. The vehicle numbers you enquire about, when you enquired, the vehicles you have added for watching and their settings, and the alerts generated for you. Every chargeable action is recorded against your account so your balance can be explained back to you.

Vehicle movement records. Crossing records obtained for the vehicles you enquire about, described in full under where the data comes from. These identify a vehicle, not a person.

Payment records. What you bought, when, for how much, and the reference our payment provider returns. We never see or store your card, UPI or bank details — those are handled entirely by the payment provider.

Delivery settings. If you connect Telegram, the chat identifier needed to send you alerts. If you connect a spreadsheet for exports, its identifier.

Technical records. A session cookie that keeps you signed in, and ordinary server logs including error diagnostics. We do not run advertising or third-party analytics trackers.

3. Why we hold it

  • To give you the service you signed up for: running your enquiries, watching the vehicles you chose, and sending the alerts you asked for.
  • To keep your account secure and let you back in when you forget your password.
  • To bill correctly, to show you where your credits went, and to keep the financial records the law requires us to keep.
  • To keep the platform working — diagnosing faults, preventing abuse, and enforcing our terms.
  • To comply with a legal obligation, or to respond to a lawful request from an authority entitled to make one.

We do not sell your information, and we do not use it to build advertising profiles.

4. Who else sees it

Only the providers we need to run the service, and only what each one needs:

  • Our hosting and database provider, which stores the data and runs the application.
  • Our payment provider, which takes the payment and returns a reference. Your card and bank details go to them, not to us.
  • The upstream data infrastructure, which receives the vehicle number being enquired about in order to return records for it.
  • Telegram, but only if you connect it, and only to deliver the alerts you configured.
  • Your own spreadsheet provider, if you have configured an export destination of your own.
  • The administrator of your organisation’s account, where your account was created or is managed by one.

We may also disclose information where we are required to by law, or where it is necessary to establish, exercise or defend a legal claim.

5. How long we keep it

Operational records — crossing records, enquiry logs and alert history — are kept for a limited period and then deleted automatically. The exact period is set per record type by the administrator, and where an export destination is configured, records are copied out before deletion so your own copy survives.

Account details are kept while your account exists. Financial records — payments, credit movements and balances — are kept for as long as tax and accounting law requires, which is longer than the rest, and are not deleted on request while that obligation stands.

6. How it is protected

Access is restricted to your own account: the database enforces, at row level, that one account cannot read another’s data. Traffic is encrypted in transit. Passwords are stored only as salted hashes by our authentication provider — we never see them, and nobody here can tell you your password or will ever ask for it.

No system is perfectly secure. If we discover a breach affecting your information we will tell you and the relevant authority as required by law.

7. Vehicle data and individuals

Vehicle movement records relate to vehicles. They may nonetheless become personal information in your hands — for example where a vehicle is operated by an identifiable individual. Where that is so, you are responsible for handling it lawfully, for having a lawful basis for your enquiry, and for complying with data protection law in your own use of it. Our terms require it and our logs record who enquired about what.

8. Your rights

Subject to the exceptions the law allows, you may ask us to: give you a copy of the information we hold about you; correct it where it is wrong or incomplete; delete it where we no longer have a reason to keep it; or tell you who we have shared it with.

Write to the contact page saying which of these you want. We will verify that the request comes from you — we will not act on a request we cannot tie to the account — and answer within the period the law allows. There is no charge for a reasonable request.

If you are not satisfied with how we have handled a request, you may complain to the data protection authority with jurisdiction over you.

9. Children

This is a business platform and is not intended for anyone under 18. We do not knowingly create accounts for children, and will delete any we find.

10. Changes to this policy

We may update this policy as the service changes. The date at the top always reflects the current version. Where a change materially affects how we handle your information, we will tell account holders directly rather than relying on you to re-read this page.