Privacy and data rights

What the rider service processes

Departure and trip-planning searches are processed to answer the current request. Otranspo does not persist unsuccessful or abandoned searches and does not send exact origins, destinations, coordinates, notes, or itinerary details to analytics.

Saved places, stops, trips, and recent journeys are kept only in the current browser. They are not synchronized to an Otranspo account.

A signed-in rider may submit a report. The report is private by default and is reviewed before a sufficiently large aggregate can appear publicly.

Analytics and cookies

Essential session, language, security, and offline-cache storage support requested features. Optional analytics remains off unless the rider gives explicit consent. Correcting an analytics configuration never enables tracking by itself.

The service does not sell rider data. Infrastructure processors receive only the minimum data needed to operate the service under their configured agreements.

Access, export, correction, withdrawal, and deletion

Signed-in riders can use the authenticated privacy endpoints to export or delete account-linked Otranspo records. A deletion request preserves only legally or operationally required audit evidence in de-identified form.

Do not place sensitive journey or safety information in a general contact message. Use the authorized privacy contact shown on the contact page for a rights request.

Retention

Private submitted reports are retained for up to 365 days unless an active safety review, appeal, or legal hold requires a documented extension. Idempotency and abuse-prevention records expire after 24 hours. Operational feed observations are not rider records.

Browser-only saved information remains until the rider removes it, clears site data, or the browser evicts it.