Privacy and data storage

Who operates PRGgo

The operator and data controller is ALTAMENTE, s.r.o., company ID 27936210, Padovská 585/6, 109 00 Prague 10, Czech Republic. Contact: info@prggo.com. PRGgo is an independent application for the PID transport network.

Your device and storage choices

Essential local storage keeps your privacy choice, colour theme, saved routes and requested reminders. Search history is stored on this device, independently of optional offline storage. You can disable or delete it below the search form. Disabling history deletes it. IndexedDB “nacas-pid” keeps at most 40 origin–destination pairs and 100 stops; the interface shows the last 10 journey searches. It is not synchronised between devices.

Saving journey results for offline use is optional. You can accept all, accept essential storage only, or customise your choice. Rejecting optional storage deletes saved offline results while preserving independently enabled history. Essential application files are cached by the service worker. Your privacy choice is stored locally; you can change it in the application footer. Optional data remains until deletion, withdrawal of consent or expiry of the stored consent at the next app launch.

Search, location and maps

The server processes the stops and time you request to find a journey. Location is requested only after your action and browser permission. For “My location”, coordinates are sent to the server and TomTom Routing API to verify walking access to specific platforms. The results remain in server memory for at most about 30 minutes; precise coordinates are not saved in search history. Location remains in the open app until it is closed or the origin changes. We do not record a continuous movement history. See TomTom's privacy information.

Opening a map requests tiles from OpenStreetMap. The provider receives your IP address and the requested map area. See the OpenStreetMap Foundation privacy policy.

Our advertising banners

PRGgo displays banners managed by its operator. Selection uses the page language, placement, validity dates and priority. We do not build advertising profiles or send your search history to advertisers. The server stores aggregate impression and click counts by banner, language, placement and day. At least half of a banner must be visible for one second to count an impression. A short-lived signed token prevents the same impression or click from being counted repeatedly; it identifies a displayed banner, not a person. No advertising identifier is saved on your device. A clicked advertiser link opens that advertiser's website, where its own privacy terms apply. Advertising administrators use a necessary, host-only secure login cookie, with an absolute lifetime of eight hours and a 30-minute inactivity limit.

Operational information and notifications

Technical server logs may contain IP addresses, times, URLs and response status. They support security, diagnosis and availability; normal web log retention is seven days. Request rate limits use IP addresses briefly in memory. Hosting uses OVH infrastructure. We do not sell search history.

When you enable service monitoring, the server keeps the push subscription, monitored service and expiry. A departure reminder also stores the selected journey legs and lead time, without your location coordinates. You can cancel it in Saved. Expired reminders are removed by a task running about every 30 seconds. Reminders follow an available departure estimate, otherwise the timetable. Calendar files are created in your browser and do not automatically update after saving. Notifications use your browser or operating system's push provider, which may process data outside the EEA under its terms and safeguards. You can remove monitoring in the app and revoke notification permission on your device. Expired delay watches are removed by daily cleanup no later than approximately 31 days after expiry. Backups may contain older records; the latest three daily archives are retained.

Travel-time and delay statistics describe vehicles and services, not passengers. The server also keeps aggregate counts of searched direct journey sections by origin, destination, line, weekday and departure minute to improve future caching. These counts contain no device identifier, IP address or GPS coordinates. Unused aggregates follow the configured 30-day retention. Published samples do not contain individual searches.

Purposes and your rights

Processing your request or a notification you request provides the service you asked for. Security and essential diagnostics serve the operator's legitimate interest in secure operation. Optional offline result storage is based on your revocable consent. Essential storage supports functions you request. We do not make solely automated decisions with legal or similarly significant effects on you.

Depending on the circumstances, you may request access, rectification, erasure, restriction or portability, object to processing, and withdraw consent without affecting the lawfulness of earlier processing. Contact info@prggo.com. You may complain to the Czech Office for Personal Data Protection. Locally stored data can be removed directly on your device.

Updated 12 October 2026. Privacy settings are in the footer of the PRGgo app.