1. Who is the controller
The controller of the VYPRAVO Booking application and the personal data described below is:
Blueridge s. r. o.
Karpatské námestie 7770/10A, 831 06 Bratislava – Rača, Slovakia
Company ID (IČO) 57 383 448
Contact for privacy questions: info@vypravo.online.
2. What VYPRAVO Booking is
VYPRAVO Booking is an internal admin application for the controller's own staff (dispatchers, managers) — it puts an existing admin backend (Portal) on their phones: dispatch, approvals, fleet and driver overview. The app is publicly listed on the App Store and Google Play for installation, but only a person with an existing account — created by the company's own administrator — can sign in. The app does not serve end customers or travellers and has no self-registration.
3. What data we process
| Data | What it is | Purpose |
|---|---|---|
| Account identifier | Username used to sign in, provisioned by the company administrator — not created via in-app sign-up | Authentication |
| Authentication / session tokens | Short-lived access token and a rotating refresh token (with reuse detection), stored in the OS Keychain (iOS) / Keystore (Android); optionally gated by device biometrics or passcode | Keeping the session signed in without re-entering the password |
| Device / push token | FCM token (Android) / APNs token (iOS), re-registered on every app start and on token refresh, removed at logout | Delivering push notifications (booking to approve, escalation, driver problem, vehicle handover done) |
| Operational data the admin views | Bookings, dispatch assignments, approvals, fleet and driver records already stored on the controller's own backend (Portal) | Displaying and letting the admin act on the controller's own operational data — the app's core purpose |
| Vehicle handover photos and video | Vehicle pickup/handover records (photos, video, odometer and fuel level) created by the driver in the VYPRAVO Jazdec driver app and stored on Portal | Viewing only, for the admin inside the Booking app — Booking uploads none of these files |
| Audit log entries | Who, from which device, which request, and what action was taken — recorded for every admin write made from the app | Security accountability for admin actions |
The app itself does not ask the end user for a name, e-mail address, or any profile field beyond the login identifier — if those exist at all, they belong to the account record the company administrator manages in the existing web admin, not something entered through this app.
Vehicle handover photos and video: these records are created by the driver in the VYPRAVO Jazdec app during vehicle pickup or handover. VYPRAVO Booking uploads none of them — the admin only views them inside the Booking app. Portal currently strips metadata, including location (EXIF/GPS), from receipt photos (expenses) and from chat photos exchanged with dispatch, but not yet from vehicle handover photos and video — that metadata stripping is planned but not yet deployed.
4. What the app does not do
- No tracking: no cross-app or cross-site tracking, no data-broker sharing, no advertising identifiers collected or used.
- No ads: the app shows no advertising.
- No selling of data: personal data is never sold or shared with third parties for their own purposes.
- No analytics or crash-reporting SDK: as of this document's date, no third-party analytics or diagnostics library is bundled. If one is added later, this document and both store listings must be updated before that release ships.
5. Legal basis
The legal basis for processing personal data in the VYPRAVO Booking application is:
- Performance of a contract / employment relationship (GDPR Art. 6(1)(b)) — access to the app as a work tool for admins/dispatchers.
- Legitimate interest (GDPR Art. 6(1)(f)) — security audit of admin actions and protection of operations against misuse.
6. Retention
- Audit log: 12 months for ordinary admin-write rows; money-related actions (payouts, cash) are kept 10 years, matching the existing accounting/legal retention already enforced for the web admin.
- Login attempts: login attempts including IP address – 90 days.
- Known devices: the device fingerprint used to recognise an already signed-in device is kept for 365 days.
- Vehicle handover photos and video: a scheduled deletion job for this media category exists but is not yet scheduled/enabled to run on a recurring basis. Only unfinished (incomplete) uploads are deleted, after 72 hours. Vehicle handover videos and photos are kept until the operator deletes them; automatic deletion after a set period is being prepared.
- Device / push tokens: re-registered on every app start and token refresh; removed (unregistered) at logout. Not retained beyond the device's active registration.
- Authentication tokens: short-lived access token; rotating refresh token with reuse detection, stored only in the device's Keychain/Keystore. "Log out everywhere" (Settings → Devices) revokes all of a user's refresh tokens immediately.
- Account deletion: accounts are created and removed by the company administrator in the existing VYPRAVO web admin, not by the end user or self-service in the app.
7. Recipients and processors
- Hosting: the app talks exclusively to the controller's own backend, hosted on its own VPS server located in the EU — no third-party cloud processor handles app data.
- Firebase Cloud Messaging (Google) and Apple Push Notification service (APNs): receive the device push token and a minimal notification payload for the sole purpose of delivering the push notification. The payload never contains names, phone numbers, amounts, plates or message text — only a type code, an entity id, a deep link and a realm marker. This is standard platform-level push delivery, not an advertising or analytics integration.
- No other third-party processor receives data from this app. The demo/review environment used by app-store reviewers additionally has no push credentials configured at all, so it cannot deliver to Google or Apple even for the review account.
8. International transfers
Operational data stays on the controller's own EU server. Handing the device push token to FCM/APNs (Google, Apple) may involve processing outside the EU within those providers' own push infrastructure, under their standard contractual safeguards (Google and Apple acting as processors for push-notification delivery).
9. Security
- All network traffic (login, API calls, push registration) uses HTTPS/TLS; outside debug builds, the iOS configuration requires HTTPS (App Transport Security).
- Sign-in requires the same existing two-factor authentication (TOTP) as the web admin — not simplified for the mobile app.
- Optional biometric unlock (Face ID / fingerprint) or device passcode on later launches — this does not replace sign-in, it only gates the token already stored on the device.
- Authentication tokens are stored exclusively in the OS Keychain (iOS) / Keystore (Android), never in a plain file or an off-device backup.
- No secrets or keys to the internal backend (Booking) are embedded in the app — that system is reachable only through the server, never directly from the device.
- Data is stored on the controller's own server (see section 7 — Recipients and processors); the controller is responsible for that server's technical security, including at-rest encryption, per the server's current configuration.
10. Your rights
Under the General Data Protection Regulation (GDPR) you have the right to access, correct, and erase your personal data, to restrict its processing, to data portability, and to object to processing based on legitimate interest. Since accounts are managed by your company's administrator, please direct requests to them first; if that is not possible, contact us directly using the details below. You also have the right to lodge a complaint with a supervisory authority — the Slovak Data Protection Authority (Úrad na ochranu osobných údajov SR).
11. Contact
Privacy questions: info@vypravo.online
Postal address: Karpatské námestie 7770/10A, 831 06 Bratislava – Rača, Slovakia
12. Changes to this policy
We may update this document from time to time, for example when the app's features change or a new third-party service is added. The effective date is shown in the page header above.