Spaces

Rider privacy checklist for transit chats

This checklist helps transit teams protect rider details in chat, such as card numbers, travel patterns, photos and safety reports. It is for operators who let an AI agent answer riders.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Riders share more than they realise. A single message can reveal where someone lives, which stop they use at night, their child's school route, a medical condition that needs a ramp, or a travel card number. In a transit chat, details like these are easy to collect and easy to leave lying around.

Go through the points below with whoever sets up your agent and whoever reads the chats. Decide what you need, what you do not, and who may see it. The less you ask for, the less you have to protect, and the more riders trust you with the things that matter.

Tick each one as you go. 0 of 10 done.

[ ] Ask only for the details needed to answer, such as route, stop and time.
[ ] Never ask a rider to type a full card or bank number into chat.
[ ] Use only the last four digits of a travel card to find an account.
[ ] Keep a rider's home and regular journeys out of any reply to someone else.
[ ] Limit who on your team can read safety and harassment chats.
[ ] Check ID with a staff member before returning valuable lost property.
[ ] Treat photos of injuries, vehicles or other riders with care.
[ ] Do not repeat a rider's accessibility or health needs outside the chat.
[ ] Set a time after which old chats are removed, and write it down.
[ ] Tell riders in plain words how their chat details are used.

Safety reports need extra care

A rider describing harassment on a night bus is telling you something private and painful. The chat should reach a trained person quickly, and only the people who need to act on it should see it. Do not copy the details into general team chats or shared inboxes.

If a rider asks you to keep their report quiet, tell them honestly what you can and cannot do. If you must share it with the police or a regulator, say so rather than promising secrecy you cannot keep.

Small habits that protect riders

Most privacy failures are small, everyday slips and not break-ins.

  • Lock the screens where chats are read.
  • Do not paste rider chats into personal notes.
  • Use first names and a case number in handover notes where you can.
  • Remove staff who change roles from the chat team.

FAQ

Is it safe to ask for a travel card number in chat?

Ask only for the last four digits or a card reference, and use a secure staff process for anything more. A full card number should not travel through a chat.

Can we share a rider's complaint with the driver involved?

Share the facts needed to investigate, such as date, time and route, but think carefully about names and personal details. Your complaints policy and local rules should guide what is passed on.

How long should we keep rider chats?

Keep them only as long as you need them for service, complaints and legal reasons, then remove them. Write the time down, tell your team, and follow it consistently.

More free tools for city bus and rail transit operators

Read the guide: Answer rider questions about routes, passes and lost property.