Travel and payment data
How transit fare cards and payment accounts create travel records
OMNY and Los Angeles TAP illustrate different layers of transit data: fare transactions, linked accounts, app permissions and program eligibility. Optional registration does not mean no ride records.
Sources checked .

A fare account and a fare transaction are different layers
OMNY's terms say an account is optional for using its fare-payment system. Creating an account adds personal information and access to older transaction history. Paying without registering does not establish that the payment system keeps no transaction record. OMNY: optional account and fare-payment terms
OMNY's FAQ describes one year of trip and charge history in an account and seven days of trip history without an account. Those are customer-access windows, not a promise to delete underlying records after those periods. OMNY: cash cards, history windows and same-method benefits
Phone-location permission is separate from paying a fare
OMNY's privacy policy covers payment, account and online-activity information. Optional website/app current-location collection requires consent and can be withdrawn through permissions. The policy also describes payment information from tapping a bank card or phone. Turning off an optional location feature is not the same operation as stopping fare processing. OMNY: collection, permission, disclosure and retention
Tokenization describes a specific payment-data treatment
Los Angeles TAP's bank-card FAQ says card information is tokenized and that its system logs rides rather than identity for that payment feature. Its account and program practices are a separate scope. This feature description should not be turned into a guarantee that every TAP account, program or trip is unidentifiable. Los Angeles TAP: tokenization, registration and deletion consequences
TAP's privacy notice separately describes information supplied for personalized cards and balance protection. It permits specified disclosures for legal obligations, court orders, consent, program eligibility, interoperability and authorized vendors with confidentiality duties. Los Angeles TAP: personal data, sharing and qualified deletion
An app can add planning and account information
TAP's app guide describes account card management, transaction history, trip planning, nearby options and saved favorites. Guest mode allows some functions without signing in. Cash added through an app-linked PayNearMe barcode is still credited to a TAP account; cash payment alone does not describe the account relationship. Los Angeles TAP: app, guest mode and Help Request
Not sold does not mean never disclosed
OMNY says it will not sell personal information, while allowing specified affiliate, vendor, compliance and legal disclosures. Retention follows applicable New York or federal requirements. Its policy gives no single universal deletion period here and does not cover every other MTA app or service. OMNY: collection, permission, disclosure and retention
Registration has useful benefits and privacy tradeoffs
The OMNY Card page describes cash/card purchase or reload at machines and retailers. Linking a card enables online reload, automatic reload and balance protection. Review those features before choosing an account relationship rather than assuming registration is required for every ride. OMNY: card purchase/reload and registration tradeoffs
Questions and answers
Does one year of visible history mean records are kept for exactly one year?
The FAQ describes a viewing window, not a universal retention or erasure rule. OMNY: cash cards, history windows and same-method benefits
Is every transit system governed by this OMNY policy?
No. The policy itself limits its scope to OMNY services. OMNY: collection, permission, disclosure and retention
Does guest mode mean all TAP app functions work without an account?
TAP says guest mode enables some functions. Los Angeles TAP: app, guest mode and Help Request
Sources and scope
Eight primary sources checked 10-24-2026. OMNY's policy header says revised 06-10-2026 while its separate effective-date section says 04-07-2026; those dates are not treated as interchangeable. TAP's current displayed privacy notice is dated 06-30-2022. Policy descriptions are not independent technical audits. Account history, location permissions, fare transactions and eligibility programs are kept separate; examples are not generalized to every transit operator.
- OMNY Card, cash/card, linked account and balance protection. Checked 10-24-2026.
- Detailed information on OMNY, current public documentation. Checked 10-24-2026.
- Privacy Policy, header revised 06-10-2026; separate section 17 effective date 04-07-2026. Checked 10-24-2026.
- Terms of Service, revised 06-10-2026, selected account and payment provisions. Checked 10-24-2026.
- TAP App FAQs, selected planning, account cash, guest and deletion passages. Checked 10-24-2026.
- TAP FAQs, selected bank-card logging, balance protection and deletion passages. Checked 10-24-2026.
- Privacy Notice, last updated 06-30-2022, current displayed notice. Checked 10-24-2026.



