Privacy Policy
1. Who this is for
This Privacy Policy explains what the RoutePass Bus POS app (the “app”) does with information when you use it to run a bus trip. You are a conductor, driver, or other staff member, and the terminal is a work device given to you by your bus operator.
It covers this POS app only. The RoutePass passenger app has its own policy. Passengers do not sign in here.
2. Who we are
The RoutePass Bus POS app is developed and published by Zyrap, Sathyamangalam, Erode, Tamil Nadu, India (zyrap.com). Zyrap provides the RoutePass ticketing service. In this policy, “we”, “us” and “Zyrap” mean the publisher of the app. Your bus operator employs or engages you, assigns the terminal, and decides who works a trip.
Questions about your job, pay, or duty go to your operator. Questions about this app, or about personal data the app holds about you, go to Zyrap at the address in section 16.
3. Information the terminal handles
Sign-in. You enter a password so the terminal can sign in. After that, the app keeps a session on the device (an access token and a refresh token). The password is used only to sign this terminal in.
The trip. When you start a trip we record the bus, route, direction, and the driver and conductor on that trip (name and staff id). The device is tied to a bus and a bus service.
Tickets you sell. For each ticket we record the boarding stop, drop stop, ticket type (full, half, or luggage), fare, ticket number, payment mode (cash, UPI, card, or QR), and the amount. We do not collect card numbers, CVV codes, or UPI PINs on this terminal.
App tickets you verify. When a passenger shows a RoutePass ticket, you enter the 4-digit PIN. The terminal then shows the passenger name, fare, stops, and whether the ticket is paid, so you can confirm it and mark it boarded. The PIN and name are used only to match that ticket.
If the network drops. Routes can stay cached on the terminal, and tickets can wait on the device until they sync.
4. Data summary
This table matches the data safety declaration we make on Google Play.
| Data | What we collect | Shared with | Purpose |
|---|---|---|---|
| Name | Staff name on the trip. Passenger name only when you verify an app ticket. | Bus operator dashboard, RoutePass systems | Run the trip and match a ticket |
| Staff and device session | Staff id, bus assignment, access and refresh tokens on the device. | RoutePass systems, bus operator | Sign the terminal in |
| Location | Precise and approximate location while a trip is running. | Operator dashboard and the live map for that bus | Show the position of the bus |
| Financial info | Payment mode and amount. Not card numbers, CVV, or UPI PINs. | Bus operator, for collections | Record the ticket |
| App activity | Tickets, stops, fares, shift and day collections. | Operator dashboard | Ticketing and settlement |
Not collected: camera, microphone, contacts, SMS, photos, health data, files, and advertising id. We do not sell data or use it for advertising.
5. Location
The app asks for precise and approximate location. We use it while a trip is running: when you start or extend a trip, and to update the live position of that bus. Your operator sees that position on the RoutePass dashboard. Passengers on that bus can see the bus on the live map.
Location here is the position of the bus on a running trip. It is not a personal tracker for your time off the bus, and we do not use it to advertise to you. This app does not ask for Android’s separate background-location permission. When the trip ends, live updates for that trip stop.
6. Notifications and printing
If you leave them on, the terminal can notify you when a passenger books in the app or a ticket needs verification. You can turn ticket notifications off in the app settings. An alert may vibrate the device. From a notification you can print that ticket on the terminal’s printer. The printed slip stays on the device and the printer. We do not upload the paper slip as a separate copy.
7. How we use this information
- Sign the terminal in and keep the session.
- Run the trip, sell tickets, verify app tickets, and print a receipt.
- Sync tickets that were saved on the device while offline.
- Show you, and your operator, the collection for the shift and the day.
- Show the live position of the bus during the trip.
- Keep the service secure, limit leakage and disputes, and keep the records that tax and transport duties require.
We do not sell this information. We do not use it to build an advertising profile, and we do not use it to make an automated decision about your employment. Your operator may use collection and trip reports to run the bus service. That use is theirs.
8. Who can see it and who we share it with
- Your bus operator, and the people they authorise on the RoutePass owner dashboard: trips, tickets, collections, the crew on the trip, and the live position of the bus.
- Zyrap, and the systems that host RoutePass, so the terminal, the dashboard, and the passenger app stay in step. Those systems may be in India or elsewhere. Where information leaves India, it does so only as needed to run RoutePass.
- Passengers on your bus, who can see the live position of the bus on the map. They do not see your personal details.
- A bank, UPI app, or card network, only for a digital payment the passenger actually makes. This app records the mode and the amount. It does not store the card number or UPI PIN.
- A court, regulator, or other authority, if the law requires us to disclose it.
We do not share personal data with advertisers or data brokers.
9. What stays on the device
The terminal stores, on the device, the session, the selected bus, the shift, the trip, cached routes, tickets waiting to sync, your notification choice, and the split-stage setting for a route. Android backup of this app’s data is turned off. Ending the day or signing out clears the active session the app is built to clear. Anyone who can unlock a signed-in terminal can sell tickets, so keep the device with you.
10. Security
The terminal reaches RoutePass over an encrypted network connection (HTTPS) using a session token. Access to trip and collection data is limited to the signed-in terminal and to accounts your operator has authorised. We do not collect card numbers, CVV codes, or UPI PINs, so they cannot be exposed through this app. No method of storage or transmission is perfect. Treat the terminal the way you treat the day’s cash, and tell your operator at once if a terminal is lost or stolen so its session can be ended.
11. How long we keep it, and deletion
Ticket, fare, and collection records are kept for as long as we need them to run the service, settle your operator’s accounts, handle a dispute, and meet legal and tax record duties. Live location is kept for the running trip and for the operational history on your operator’s dashboard. Session tokens on the device stop being used when the session ends or the terminal is reassigned. We delete or de-identify information when we no longer need it, unless the law requires us to keep it.
How to ask for deletion. Staff accounts for this app are created and managed by your bus operator, not inside the app. To request deletion of your personal data, email the Grievance Officer in section 16 from the address linked to your staff account, or ask your operator to send the request. We will delete or de-identify your personal data, except records we must keep as described above. If we keep something, we will tell you what and why.
12. Your rights
Under the Digital Personal Data Protection Act, 2023, you may ask to access personal data about you, ask for a correction, ask for erasure, raise a grievance, and nominate another person to exercise these rights if you die or cannot exercise them yourself.
Tickets, fares, and collections are also your operator’s business records. We cannot erase those while the accounts, a dispute, or the law still require them. If we refuse a request for that reason, we will tell you why.
Write to the Grievance Officer below. We will respond within the time the Act and its rules require. You can also ask your bus operator, because they assign the terminal and hold the shift. If you stop using the terminal, your operator can end the session. The terminal cannot sell or verify tickets without the information this policy describes.
13. Children
This app is for bus staff. It is not directed at children, and we do not open an account for a child on it. A half-fare ticket is a fare category. It is not a child’s name, photo, or profile.
14. Permissions
| Permission | Why |
|---|---|
| Internet | Sign in, sync tickets, and update the trip. |
| Location, precise and approximate | Position of the bus on a running trip. |
| Notifications | New app tickets and verification, if you leave them on. |
| Vibration | Those alerts. |
The app may keep a foreground service so trip work can continue on the terminal. We do not ask for the camera, microphone, contacts, SMS, photos, or a separate background-location permission.
15. Changes to this policy
If this policy changes, we will post the new version on this page and change the date at the top. Continued use of the terminal after that date is use under the new version.
16. Contact
Grievance Officer, Zyrap
Soundarkumar
Email: soundarkumar@zyrap.com
Phone: +91 73589 97258
985/9, Nallur, Ganeshpuram, Punjai Puliampatti,
Sathyamangalam, Erode, Tamil Nadu 638459, India
https://zyrap.com
Write to the Grievance Officer about this app, about access, correction or deletion, or about a complaint. For anything about your job, pay, or roster, speak to your bus operator.