01Website and support requests

You do not need an account to view the landing page. The website has no personal data collection forms, advertising trackers or integrated visitor analytics.

When you load a page, the server and delivery infrastructure receive technical request information, including your IP address, the page address and browser information. This is needed to deliver content and may appear in infrastructure logs.

If you contact the developer by email or Telegram, the contact details and message you provide are used to respond. Please only include information needed to resolve your question.

02App data

RideBus processes your selected city, preferences and information needed for requested features such as viewing schedules, finding stops, planning routes and saving favourites. Some preferences and cached schedules are stored on your device.

Requests to schedule and map servers include request parameters and technical connection information. Depending on your app version, diagnostic services may receive error reports, app version, device information and performance data to help fix failures.

03Location and permissions

Location access requires system permission and is used for nearby features, such as finding nearby stops and showing your position on a map. When you request directions, coordinates of selected points may be sent to the routing service.

You can revoke permission in your device settings. Manually selecting a city or stop and viewing available schedules do not require location permission. Notification permission can also be managed in device settings.

04Optional passenger mode

In versions with passenger mode, location sharing requires a separate action by the user. Granting location permission alone does not enable this mode.

While the mode is enabled and the app is in the foreground, coordinates, accuracy, speed, heading, observation time, the selected city and route, and a random session identifier may be sent to the RideBus server. This information is used to estimate public transport movement. The session identifier is not your name, phone number or email address.

Sending stops when you disable the mode, revoke permission or move the app to the background. Disabling the mode stops new transmissions and does not itself delete information already sent.

05Third-party services

Some features may require map, routing, authentication, notification and diagnostic services, including Google Firebase. These providers process the data they need under their own terms and privacy policies.

Links to Google Play, GitHub and Telegram lead to external websites. Once you follow a link, that service’s rules apply. Please review them before providing data.

06Managing your data

You can change device permissions, disable optional features and clear local app data using your operating system. Clearing local data does not automatically remove data already sent to servers or third-party services.

Contact the developer at the address below about access, correction or deletion of transmitted data. Specify the feature and app version you used; do not send passwords or access codes. Whether a request can be fulfilled depends on identifying which data relates to you and on applicable requirements.

07Policy updates

The current policy is published on this page with its update date. It may be revised when features or data processing change. For features requiring separate consent, review the information in the app before enabling them.