Last updated: 8 July 2026

Effective date: 8 July 2026

Infocus Point EOOD operates Reysko, an accessibility-first public-transit application for multiple cities. Reysko is available as a mobile application for iOS and Android. This Privacy Policy explains how personal information is collected, used, and protected when you use Reysko.

By using Reysko, you consent to the collection and use of your personal information as described in this Privacy Policy. Where consent is required for specific features, such as enabling arrival notifications, you will be asked before that information is collected.

1. Data controller

   The data controller for Reysko is:

   Infocus Point EOOD
   operating Reysko as part of: Access In Focus
   Registered address: Sofia, 1324, 34 Filipovsko shose str
   EIK (company registration number): 208807193
   Email: contact@accessinfocus.com

   For any questions about how your personal data is handled, use the email above.

2. Information collected and how it is used

   Reysko is designed to collect as little personal information as possible. Most of the app’s data stays on your device and is never sent off it. The categories below describe what is collected and why.

   Location: When you grant location permission, Reysko uses your location only on the device to (a) sort nearby transit stops by distance, (b) guide you to a stop with the walk-to-stop compass, and continue speaking distance and arrival cues during a walk even if you lock the screen (see Spoken walking guidance, below), and (c) during an active “Ride to stop” session, register a single geofence around the destination stop you chose so the app can notify you when you arrive. Your location is never transmitted off your device, never stored on a server, and never shared with third parties.

   Saved stops and preferences: When you save a stop, change the interface language, or toggle settings, those choices are stored locally on your device (in the app’s private storage).

   Arrival notifications (optional): When you turn on arrival alerts in the mobile app’s Settings, Reysko requests permission to use location in the background and to send notifications. With both granted, the app registers a small set of geofences around your saved stops on the device. When you enter one, the operating system wakes the app briefly and Reysko fires a local notification with the stop name. No location data is sent off the device, and the notification is generated entirely on the device. Reysko does not use server-based push.

   Spoken walking guidance: If you lock your screen during an active walk to a stop, Reysko can keep your location active in the background so it can speak distance and arrival cues out loud. On Android this uses a foreground service, shown by an ongoing notification; on iOS it uses the system background-location indicator. It runs only during an active walk, stops when you arrive or leave the walk screen, plays only when the in-app voice is on and no screen reader is active, and can be turned off in Settings under Walking. Your location is used on the device for this and is not sent off it. On Android, the app may also ask for permission to ignore battery optimization so this guidance and ride arrival alerts keep working reliably when the screen is locked; this is a device permission and collects no data.

   Trip planner search: When you type a place name into the trip planner, that search text is sent to the geocoding service Photon (see Third-party services) to convert the text into coordinates. No identifying information about you is sent, only the text you typed.

   Search history: Reysko remembers your recent searches in your local storage so it can re-suggest them. It is never sent off your device and you can clear it at any time from the app menu.

   Anonymous usage analytics: The app uses Aptabase (see Third-party services), an EU-based, privacy-first analytics service, to understand aggregate usage and to demonstrate Reysko’s reach to sponsors and public bodies. The data is anonymous: Aptabase stores no device identifier and derives a temporary id from a hash that rotates every day, so you cannot be recognised from one day to the next and the data cannot be linked to you. Reysko records counts and simple categories only, such as app opens, trips planned, guided “Go” trips started and completed, stops and lines saved, your app version and operating system, an approximate region, and whether a screen reader (VoiceOver or TalkBack) is active. Reysko never records what you search for, place names, addresses, or coordinates. This is not advertising and not cross-app tracking, and it uses no advertising identifier. Because it is anonymous, there is no personal data tied to you to access or delete; you can still turn it off at any time in Settings, under General, where it is on by default.

   If your information is needed for any new purpose, you will be asked for consent first. Your data will only be used for the purposes you were told about, unless the law requires something different.

3. Third-party services

   Reysko uses the following third-party services to deliver core features. Use of these services involves transferring limited data to them. Each provider has its own privacy policy.

   • Google Maps SDK (mobile map tiles): when the mobile app displays the orientation map on the walk-to-stop screen, your IP address and tile coordinates are sent to Google to fetch the map images. Subject to the Google Privacy Policy and Google Terms of Service.
   • Device geocoder and Photon at komoot.io (trip planner address search and “Where am I” lookups): when you use the trip planner, the place names you type are sent to photon.komoot.io to convert them into coordinates and place suggestions. For the “Where am I” features (in the Stops list, the shake-to-announce gesture, and during Walk to stop and Ride to stop), your current coordinates are turned into a street address. This reverse lookup uses your device’s built-in geocoder first (Apple’s CLGeocoder on iOS, Google Play Services on Android), and falls back to photon.komoot.io only when the device geocoder returns nothing. These requests carry no Reysko user identifier and no information about your trip; they are one-shot real-time lookups. Subject to komoot’s privacy policy, the Apple Privacy Policy, and the Google Privacy Policy.
   • Open-Meteo (weather, optional): the Stops screen can show a short current-conditions line. When it is on, an approximate location rounded to about one kilometre is sent to open-meteo.com to fetch the current temperature and a short-term forecast for your area. The request carries no Reysko user identifier, and the rounded location is not precise enough to identify a specific address. The line is on by default and can be turned off in Settings. Subject to the Open-Meteo terms.
   • Sofia public-transit feed at gtfs.sofiatraffic.bg: Reysko fetches the city’s published timetable and real-time arrivals feed. This is a one-way download, and no information about you is sent.
   • Soniox (voice search, Bulgarian on iPhone only): when you search by voice in Bulgarian on an iPhone, where Apple’s built-in speech recognition has no on-device Bulgarian, the audio of your spoken search is streamed to soniox.com to be transcribed to text in real time. This is the only case where your voice audio leaves the device: on Android, and for English on iPhone, your phone’s own on-device recognition is used and the audio never leaves your device. The request uses a short-lived, single-use key and carries no Reysko user identifier. Voice search is optional and runs only when you tap the microphone. Subject to the Soniox privacy policy.
   • Expo update service at u.expo.dev: when the mobile app starts, it checks Expo’s update service to see if a new code bundle is available for your platform and app version. Only the platform, the app’s runtime version, and the inherent HTTPS metadata (your device IP, a User-Agent) are sent. No identifying information about you is sent. Subject to the Expo Privacy Policy.
   • Aptabase (anonymous mobile analytics): when analytics is on (the default, and switchable off in Settings), the mobile app sends anonymous event counts to Aptabase (operated by Sumbit Labs Ltd), processed in the European Union. Aptabase stores no device identifier; it derives a daily-rotating anonymous id, uses your IP address briefly on the server to estimate an approximate region and then discards it, and stores no IP address. The data contains nothing that identifies you and is never used for advertising. Subject to the Aptabase Privacy Policy.
   • Apple Push Notification Service and Google Firebase Cloud Messaging (optional): if you enable arrival alerts, your device registers a notification token with Apple’s or Google’s notification service so the operating system can deliver local notifications reliably. Reysko itself does not send server-side push messages. Subject to Apple’s privacy policy and the Google Privacy Policy.
   • Cloudflare: the Reysko website is served through Cloudflare Pages. Cloudflare may process your IP address and request metadata for routing, security, and abuse prevention. Subject to the Cloudflare Privacy Policy.

   Use of these services may involve transferring data outside the European Economic Area, including to the United States. Each provider operates under safeguards required by EU data-protection law.

4. Sharing of information

   Personal information is not sold or rented to third parties. It is shared only when needed for the providers listed in Third-party services, and each of those providers must use the information only for the agreed purpose and keep it only for as long as necessary.

   Information may also be disclosed in order to comply with laws or legal processes, to protect legal rights, or to respond to claims that Reysko or its content affects the rights of others.

   If Reysko is involved in a merger, acquisition, or similar change of control, personal information may be transferred to the new organisation as part of that process.

5. Your data protection rights

   Under the EU General Data Protection Regulation (GDPR) and Bulgarian data-protection law, you have the right to:

   • Access the personal data held about you
   • Ask for incorrect data to be corrected
   • Ask for your data to be deleted
   • Restrict or object to how your data is used
   • Receive a copy of your data in a usable format (data portability)
   • Withdraw consent where processing is based on consent
   • Lodge a complaint with the Bulgarian Commission for Personal Data Protection (KZLD) or your local data-protection authority

   To use any of these rights, email contact@accessinfocus.com. Requests will be handled in line with legal obligations.

   The anonymous usage analytics described above holds no data that can identify you, so there is no personal record of it to access, correct, or delete; you can stop it at any time from Settings.

   If you do not provide certain information, some parts of Reysko may not work as intended, for example, arrival notifications without location and notification permission.

6. Cookies and local storage

   The website’s hosting provider (Cloudflare) may set its own functional and security cookies needed to route requests and prevent abuse. These are not used for tracking.

   The mobile app does not use cookies. It uses the operating system’s standard private application storage for the same kinds of preferences described above. The mobile app’s anonymous usage analytics (described above) uses no cookies and no advertising identifier.

7. Security measures

   Reasonable technical and organisational steps are taken to help protect personal information from loss, misuse, or unauthorised access. All communication between Reysko and its servers is encrypted in transit (HTTPS). Account passwords are stored as a salted hash by the authentication provider and are never visible to the operator.

   However, no method of transmission or storage is completely secure. Any information you send to Reysko is shared at your own risk.

8. Children’s privacy

   Reysko is rated for general audiences and does not knowingly collect personal information from children under the age of 14 without verifiable parental consent.

9. Third-party links and external services

   Reysko may link to third-party sites or services that are not operated or controlled here. Their privacy practices are different and are not covered by this Privacy Policy.

   You are encouraged to read the privacy policies of any external sites you visit. No responsibility is taken for the content, policies, or practices of those services.

10. Changes to this Privacy Policy

    This Privacy Policy may be updated from time to time. When changes are made, the revised version will be posted on this page with an updated “Last updated” date.

    If the changes are significant, a notice may be shown in Reysko. Continued use of Reysko after the new version takes effect means you accept the updated policy.

11. Grievance or data protection contact

    If you have questions or concerns about how your personal data is handled, email contact@accessinfocus.com. Efforts will be made to review and resolve issues in line with applicable data protection laws.