busevi.rsPublic transport in Serbia and the region

Privacy policy

Privacy policy

What data we collect, how we use cookies and what your rights are

  • 31 August 2026Last updated

1. What data we collect

  • Data you send us yourself. If you contact us (e.g. an error report or a question), we process the data you provide — such as your e-mail address and the content of the message — solely in order to reply.
  • "Rider's voice". If you leave a comment, complaint, report, praise or suggestion, your entry (the text, optionally a name and a line number) is shown publicly on the site. The name is optional — without it the entry is anonymous; please do not enter personal data. Alongside the entry we temporarily record the IP address to protect against abuse (limiting the number of entries). Entries are reviewed by the administration, which may remove them or reply to them.
  • Technical data. Like most sites, the server may temporarily record standard technical data (IP address, device and browser type, time of access) for security and stability.
  • Location (mobile app only). If you tap "Nearby stops" or "My location" in the planner, the app — with your explicit permission through the system dialog — reads the current device location in order to find stops around you or fill in the origin. The location is used only at that moment: it is sent to our server solely to calculate the nearest stops or the route and is not stored either on the device or on the server, nor is it used for tracking. You can withdraw the permission in the device settings at any time; the app then works without those features.
  • Saved items (mobile app only). Lines and stops you mark with a heart are stored only locally on your device and are not sent to us.
  • Service-change notifications (mobile app only). If you turn on notifications in the app, our server stores a device notification identifier (push token), the platform (Android/iOS) and the city you selected — solely to send you a notification about a service change in that city. The identifier is not linked to a name, phone number or account. Notifications are delivered through Google Firebase Cloud Messaging. When you turn notifications off in the app, the identifier is deleted from our server.
  • Search and journey planner. The terms you type into search and the points you choose in the planner (the address or coordinates of the origin and destination) are sent to our server solely to calculate the result; we do not link them to you or keep them as history. To turn an address into coordinates our server uses the public OpenStreetMap Nominatim service — the request is sent by our server, so that service does not see your IP address. A route you share as a link carries the origin and destination in the link itself.
  • We do not require registration and do not collect sensitive personal data for using the site or the app.

2. Cookies

3. Third-party services

  • Visit statistics (Google Analytics). We use Google Analytics to measure the number of visits and how the site is used, strictly in aggregate (anonymous) form. This data helps us improve the site and is not used to identify an individual. You can prevent the collection by blocking cookies in your browser or with the Google Analytics Opt-out add-on.
  • Advertising (Google and partners). To serve ads on the site we use Google and other ad networks (partners). As third parties, these companies may use cookies, web beacons and other technologies to collect technical data during your visit in order to show you more relevant ads. Google uses special cookies (such as the DART cookie) that allow it to serve ads based on your visits to this and other sites on the internet. You can turn off personalised advertising in the Google ad settings, and third-party advertising cookies also at www.aboutads.info. More about how Google uses data is in Google's policy.
  • Ads in the mobile app (Google AdMob). The current version of the app (1.0) does NOT show ads and does not request an advertising identifier. When ads are enabled, they will be served through Google AdMob. AdMob may process technical device data and the advertising identifier (Advertising ID on Android, IDFA on iOS) in order to serve and measure ads. Where regulation requires it, the app asks for your consent through Google's form before showing ads; you can change that choice later through "Privacy settings" in the app menu. You can reset or limit the advertising identifier in the device settings (Android: Google → Ads; iOS: Privacy → Tracking). More about how Google uses data: Google's policy.
  • Maps. The map display uses OpenStreetMap data (via OpenFreeMap); when a map loads, your device communicates with their servers to fetch the map tiles.

4. Purpose and legal basis of processing

5. Data retention

6. Your rights

Deleting data from the mobile app

7. Security

8. Changes to this policy

9. Contact