VELRO Privacy Policy

Effective ۱۱ سنبله ۱۴۰۵ — 2 September 2026 · Operated by Linumic · Contact: aminhashemi979@gmail.com

VELRO is an intercity ride-booking service for Kabul, Parwan and Ghorband: one app for passengers, one for drivers, and a server that connects them. This page says what we collect, why, who sees it, and how you can see or delete it.

1. What we collect

• Phone number and name. Your number is your identity on VELRO; the sign-in code goes to it by SMS or Telegram. Linumic staff may receive their code by email.
• Location. Passengers: once, at the moment of asking or booking, to confirm you are inside the service area. Drivers: continuously while online or on a trip, so the passenger can see the car on the map and the driver receives road warnings. Going offline stops it.
• Driver documents. Photographs of the tazkira, the driving licence and the vehicle permit, the number plate and vehicle details, and a profile photo — to verify who is behind the wheel.
• Trips. Requests, fare offers, bookings, the agreed fare, the boarding code, ratings, cancellations and their reasons, and any safety report or complaint you file.
• Technical data. A device token for notifications; crash reports (app version, device model, error text — no name or number); and request logs (time and IP address) for security.

2. What it is used for

To make the trip happen: so passenger and driver can find and call each other; to verify drivers; to account for fares and commission; to act on safety reports; and to find and fix app failures. It is not used for advertising.

3. Who sees it

• The other side of your trip. A passenger sees their driver's name, photo, number plate and phone number. A driver sees their passenger's phone number and booking number, not their name.
• Linumic staff running operations and support, to the extent their work requires.
• Service providers. Sign-in codes are delivered through Twilio (SMS), Telegram, or Google (email). The VELRO server is hosted by Hetzner in Europe. A database backup is stored nightly in Linumic's Google Drive.

Your data is not sold and is not given to advertisers.

4. How long it is kept

For as long as your account is active. Sign-in codes expire within minutes. Backups stay on the server for 14 days, and copies are kept for disaster recovery. If you ask for your account to be deleted, account data is removed and only what is needed for fare accounting is kept, without your name.

5. Your rights

You can ask what we hold about you, correct it, or ask for it to be deleted — from inside the app ("Get help") or by email to aminhashemi979@gmail.com. You can withdraw location permission in your phone's settings at any time; without it, a passenger cannot ask for a ride.

6. Security

All traffic between the apps and the server is encrypted (HTTPS). Sign-in codes are stored hashed, never in plain text. Driver documents are visible only to authorised staff and are never cached by browsers or proxies.

7. Changes

If this policy changes, the new version appears here with a new date.