Privacy Policy

DRIVE&JOY mobile application (iOS) and the driveandjoy.cz website

Effective from: 9 September 2026 · Version 1.6

This policy explains what personal data we process in the DRIVE&JOY mobile application and on the driveandjoy.cz website, for what purpose, on what legal basis, how long we retain it, and what rights you have. Processing is carried out in accordance with Regulation (EU) 2016/679 (GDPR) and Czech Act No. 110/2019 Coll., on personal data processing.

1. Data Controller

The controller is a limited liability company (s.r.o.) registered in the Czech Commercial Register maintained by the Municipal Court in Prague, file no. C 451500.

For any questions regarding the protection of personal data and to exercise your rights, please contact us at the e-mail address above.

2. What data we process in the mobile application and for what purpose

We process only data that is necessary to provide the app's services, or that you voluntarily provide.

2.1 Registration and sign-in (account)

• E-mail address, password (the password is stored exclusively as a secure cryptographic hash).
• Purpose: creating and securing your user account, sign-in, password reset, e-mail verification.

2.2 Profile

• Display name, region, bio, location, profile picture (avatar).
• Preferences: preferred vehicle view, clothing size, riding style, preferred activity types, notification settings, profile visibility level, membership tier (Free / JOY+ / JOY+ PRO).
• Purpose: personalisation, displaying your profile to other users (to the extent set by your visibility settings), recommending relevant events.

2.3 Garage (vehicles)

• Vehicle data: make, model, year, purpose of use, power, torque, engine type, displacement, drivetrain, transmission, modifications, vehicle nickname, notes.
• Vehicle photos.
• Purpose: maintaining your personal garage, optionally sharing a vehicle within the club (according to visibility settings).

2.4 Event bookings

• Booking data: number of attendees, total amount, currency, vehicle data for the event, waiver acceptance timestamp, contact phone, notes.
• Attendee data: name, e-mail, date of birth for each attendee.
• Purpose: processing your event booking, preparing the attendee list, performance of the participation contract.

2.5 Payments

• Payment details (card number, etc.) are processed solely by the Stripe payment gateway. DRIVE&JOY never sees or stores the full payment card number (PAN). We store only the payment identifier (stripe_payment_intent_id), the payment status and the amount.
• Purpose: processing payment for a booking and any refunds.

2.6 Community (follows and "Family")

• Follows: "who follows whom" relationships.
• "Family" groups: group name, type, membership and invitation status.
• Purpose: the app's social features — connecting community members.

2.7 Saved events (wishlist)

• The list of events you have saved.
• Purpose: quick access to favourite events and recommendations.

2.8 Transactional e-mails

• Sending booking confirmations (including an .ics calendar invitation) via the Resend service.
• Together with the confirmation, the e-mail provider also receives the names of all co-participants listed in the booking and the contact phone number, because they form part of the e-mail body.
• Purpose: delivering confirmations and important booking information.

2.9 Technical monitoring (errors and usage events)

• The app records technical errors (error message text, technical trace — stack trace, screen name, app version, platform) and usage events linked to your account. An event carries the name of the screen or action and the app version; for controls on the car display it also records connecting and disconnecting the car, which tab you opened, which vehicle you selected, starting and ending a recording or a road trip from the car display, which notification was shown and which navigation app you handed a destination to (and whether the handover succeeded).
• Purpose: detecting and fixing bugs, monitoring stability and improving the app.
• Retention: records are kept for 90 days; they are deleted when you delete your account.

2.10 Location and ride telemetry

• Location data: geographic coordinates, speed, heading, altitude and measurement accuracy. We process location on a one-off basis to show events, routes and tracks near you, and continuously, including in the background with the screen locked, for as long as you have a ride recording or JOY Ride (co-pilot) mode running.
• Ride recording (telemetry): a time series of location and derived values (speed, acceleration / g-force, lap times on a circuit), ride distance and duration, ride summary and score, and where relevant a link to a JOY Roads route or a circuit. The detailed time series is stored as a data file in Supabase storage.
• Purpose: recording and analysing your drive, statistics and leaderboards, co-pilot navigation (JOY Ride) and ride debriefs (JOY Coach).
• Legal basis: Art. 6(1)(b) GDPR — providing a feature you switch on yourself.
• Retention: for the duration of your account, or until you delete the ride yourself; account deletion removes both the records and the stored data files.
• Background location tracking runs only while a ride recording is active and can be stopped at any time in the app or denied in your system settings. The rest of the app remains usable without location access.

2.11 Data from connected devices (Bluetooth)

• At your request the app connects over Bluetooth to an OBD-II diagnostic adapter in your vehicle or to an external GPS unit (e.g. RaceBox).
• Data processed: vehicle technical data from the adapter (RPM, speed, temperatures, engine load, etc.), more precise position and acceleration from the external unit, and the identifier of the last paired device stored locally on your phone.
• Purpose: enriching the ride recording with data straight from the vehicle.
• We use Bluetooth solely to connect to this accessory — not for advertising-related location determination or for scanning nearby devices.

2.12 Chat and messages

• Data processed: message content, attachments (photos and voice messages — an audio recording made with the device microphone), sender and recipient, timestamp, reactions, read status, muting and blocking of users, content reports.
• The app uses the microphone solely to record a voice message that you make and send yourself; recording runs only while you hold the microphone button. A finished voice message is stored and delivered like any other chat attachment.
• Purpose: delivering messages between community members, moderating reported content and operational safety.
• Messages are not end-to-end encrypted. Transmission is encrypted (TLS) and content is stored in the database; in justified cases (a content report) a moderator may access it. Deleted messages are removed from the view of conversation participants.
• Retention: for the duration of the conversation, or of your account.

2.13 Push notifications

• Data processed: the device token used for delivery (on iOS the Apple Push Notification service), platform and registration time; plus the content of the notifications sent and their read status.
• Purpose: delivering alerts (messages, events, reminders, social interactions) to the extent you configure in Notification settings.
• Legal basis: Art. 6(1)(f) GDPR — legitimate interest in operating the service; notifications can be turned off at any time in the app and in system settings.
• The notification content is passed to Apple. In order for a notification to be delivered, its text is sent to the Apple Push Notification service — for a chat message this means the sender's name and an excerpt of the message. If you would rather this did not happen, turn message notifications off in Notification settings, or configure your system to hide notification previews.
• Alongside notifications delivered through Apple, the app also shows local notifications that are composed on your device itself (the ride alerts described in section 2.22). These do not pass through our server or the Apple Push Notification service, so their content is not shared with Apple.
• The token is tied to a specific device and is deleted when the device signs out or the account is deleted.

2.14 JOY+ and JOY+ PRO subscriptions

• The subscription is purchased and billed through the App Store (Apple). The app does not receive your payment details — only whether you have an active subscription and until when.
• We use RevenueCat to manage subscriptions. Its library runs directly inside the app on your device, so RevenueCat processes not only the user identifier and purchase status but also your device IP address and device identifiers.
• Purpose: unlocking and renewing JOY+ premium features.
• Legal basis: Art. 6(1)(b) GDPR — performance of the subscription contract.

2.15 Club merchandise orders

• Data processed: order items, delivery and billing details, e-mail address, amount and payment status.
• Orders are fulfilled by Shopify (store and shipping); payment is processed by Stripe (including Apple Pay). We never see or store the full payment card number.
• Purpose: fulfilling and delivering your order, handling complaints, accounting and tax obligations.
• Legal basis: Art. 6(1)(b) GDPR — performance of the purchase contract; Art. 6(1)(c) for accounting records.

2.16 Map data, route calculation and place lookup

• When a map is displayed (events, JOY Roads routes, co-pilot) your device requests map tiles from Mapbox, which in doing so processes your device's IP address and the coordinates of the displayed viewport. Map backgrounds load the same way on public pages of the website that show a map (for example a shared ride record).
• For route calculation (ride planner, route navigation) our server passes the actual coordinates of the start, destination and waypoints to Mapbox. In this case your device does not contact the provider directly.
• To convert coordinates into a place name (and back) our server passes the coordinates to Mapy.com (Seznam.cz).
• If you choose navigation in an external app — on the phone or on the car display via CarPlay — your device (not our server) opens Apple Maps, Google Maps, Waze or Mapy.cz and passes it the destination coordinates, and for a road trip also the coordinates of the waypoints along the route. (Apple Maps and Waze do not support waypoints, so they receive the coordinates of the next stop instead.) The provider of the chosen app therefore sees your device's IP address and where you are heading; from that point its own policy applies and it acts as an independent controller of that data. The app remembers your choice on the phone, so it does not ask again; you can change it in Settings → CarPlay. Until you choose one, the car display asks every time — only the "Navigate on" button on a stop notification falls back to Apple Maps without asking.
• Purpose: rendering the map, calculating and displaying a route, determining the start and destination places.

2.17 Artificial intelligence features (Wingman, JOY Coach, ride planner, ride summary)

Four features of the app use a language model operated by an external provider. The app never contacts the provider directly — the request is always sent by our server, so your IP address does not reach the provider. We do not pass on your name, e-mail address, account identifier or geographic coordinates.

Providers: primarily Google (Gemini model), with Anthropic (Claude model) as a fallback if Google is unavailable. Both process data in the USA (see section 7). Under our terms, neither may use the data we send to train their models.

What each feature sends:

• Wingman (in-app advisor) — your question (free text, up to 300 characters), several previous questions and answers from the conversation, and a summary of your profile in the app: vehicles in your garage (make, model, year, type, mileage, roadworthiness-test and vignette dates), your ride statistics and last five rides (date, circuit, number of laps, best lap, distance, top speed), event bookings, saved route plans, membership tier, region, riding style, and which screen you are currently viewing. We do not send your vehicle's nickname or notes, its modifications, its estimated value, or your saved (favourite) events.
• JOY Coach (circuit ride analysis, JOY+ PRO only) — the circuit name and numbers from the telemetry: lap times, best lap, achievable time, points along the track where time is lost and the speeds there, and the data source (phone / RaceBox). No identifier, date or coordinates.
• Ride planner — the name of the town of the start and destination (we do not send coordinates to the model; a geocoding service converts them to a name first — see 2.16), the time budget, riding style, break preferences and your free-text wish (up to 200 characters).
• Shareable ride summary — figures from a completed road ride, from which the model composes a few sentences.

Purpose: providing a feature you invoke yourself — an advisor answer, a ride analysis, a route suggestion, summary text.

Legal basis: Article 6(1)(b) GDPR — providing a feature you request yourself. You do not have to use any of these features; the rest of the app works unchanged.

Retention: Wingman conversations (questions and answers) 90 days; the technical record of a model call (without content — only the feature, model, token count, cost and response time) 90 days, with the model's answer itself deleted from it after 24 hours; a JOY Coach ride analysis is stored with the ride and is deleted together with it; a generated route plan is kept for 30 days unless you save it. Everything is also deleted when your account is deleted.

Decision-making: none of these features makes automated decisions about you within the meaning of Article 22 GDPR — they have no effect on your membership, pricing or access to services.

2.18 Vehicle listings ("For sale")

• Data processed: details of the listed vehicle (make, model, year, mileage, price, description, location), photographs and the contact details you provide in the listing.
• Purpose: publishing the listing to other members and enabling contact between seller and buyer.
• Legal basis: Article 6(1)(b) GDPR — providing a feature you invoke yourself.
• A listing is public. A shared link to a listing is accessible to people without an account (see section 3.6).

2.19 Membership card and verification at a partner

• The membership card in Apple Wallet is generated on our server and contains your name, membership number and membership tier; Apple stores it in the wallet on your device.
• When redeeming a partner discount, the partner verifies that the card is valid. Our service returns only the member's name, membership number and whether the membership is valid — the partner receives no other data (no e-mail, garage or rides).
• Purpose: proving membership and claiming member benefits.
• Legal basis: Article 6(1)(b) GDPR — performance of the membership contract.

2.20 Weather forecast

• We show a weather forecast for events, circuits and routes. The request is sent directly by your device to Open-Meteo, which therefore receives your device IP address and the coordinates of the event or route (not your current location).
• The precipitation radar, by contrast, is fetched by our server from public data of the Czech Hydrometeorological Institute; nothing about you is passed to that provider.
• Purpose: displaying the weather for an event, circuit or route.
• Legal basis: Article 6(1)(f) GDPR — legitimate interest in the usefulness of the service.

2.21 What we do NOT use in the app, and what is worth knowing

• We use no cookies and no advertising tracking, no advertising SDKs, and we do not share data with advertising networks or data brokers. That is why the app never asks for tracking permission (App Tracking Transparency).
• We use no third-party analytics or crash reporting. Technical errors and usage events (section 2.9) are stored solely in our own database.
• We do not use your data to train artificial intelligence models, and we contractually prohibit the model providers from doing so as well (section 2.17).
• The app does, however, contain third-party components loaded from their servers, which therefore receive your device's IP address: Google Fonts, the Stripe payment component, the YouTube (Google) player and video thumbnails, the RevenueCat subscription library and Mapbox map data.
• Thumbnail images in the news feed are loaded directly from the servers of the individual publishers (Czech and international motoring media), which therefore receive your device's IP address and the address of the page requesting the image. The article texts themselves pass through our server — so publishers do not learn what you read in the app, but they do record that their image was requested.

2.22 CarPlay (controls on the car display)

• So that the app can be controlled from the car display even when it is not running on your phone at all, the app stores in your device's memory a short summary: the fact that you are signed in, your account identifier and membership tier, the vehicle you last drove and the vehicles in your garage, the catalogue of circuits, your nearest destinations (name, place, date, coordinates and the address of the photo) and the route you last selected including its stops. This data never leaves the device and access tokens are never stored in it. The personal part of the summary is deleted when you sign out; only the catalogue of circuits remains on the device, and that is a public list, not your data.
• Destination photos (events and routes) are downloaded by your device from the address stored with that event or route — usually from our own storage — and saved into the app's storage on the phone so that they appear in the car immediately. They are deleted on sign-out together with the rest of the summary.
• A ride recording started from the car display processes location data in the same way and for the same purpose as a recording started on the phone (section 2.10). It is, however, written by the native part of the app: the track points are saved to a file in the phone's memory even if you never open the app, and they are uploaded the next time you launch it. It is a working file: once the ride is complete (uploaded, or discarded), it is deleted from the phone. Section 2.10 applies otherwise.
• The car display can also start a road trip along a selected route (JOY Ride). Tapping it wakes the app on the phone, which then starts the trip; until that happens, all that is stored on the device is a note of which route you chose (valid for at most 10 minutes, then it expires, and it is deleted on sign-out as well).
• While you drive, the app shows you notifications: the start of a route, an approaching stop, arrival at a stop, leaving the route and returning to it, completing the route, the outcome of saving the ride ("Ride saved" / "Saving failed") and the warning "Coolant ≥ 105 °C". That last one is not derived from location but from the engine temperature reported by a connected OBD adapter (section 2.11); the others are composed from the location data we already process under section 2.10. All of these notifications are local — they are composed on your device and do not pass through our server or the Apple Push Notification service (unlike the notifications described in section 2.13). Besides the car display they also appear on the phone whenever you do not have the app open. The arrival notification carries a button that passes the coordinates of the next stop to your chosen navigation app (see section 2.16). We record a usage event under section 2.9 when a notification is shown and when that button is used; nothing extra is passed to the navigation app because of it.
• Live figures from the ride in progress — speed, engine revolutions, lap number and the gap to your fastest lap, distance covered, coolant and oil temperature, the next stop and the distance remaining — are shown by the app in a Live Activity (each surface shows only as many of them as fit): besides the phone's lock screen, now also on the car display and in the Smart Stack of a paired Apple Watch. This is not new processing — the content is composed on your device, nothing is sent to our servers for it and we use no push service to update it. It is worth knowing, though, that these figures are visible to anyone who looks at the car display or at your watch.
• Voice announcements in the car are synthesised speech; in the car the app does not listen or record anything and does not use the microphone for this.
• In Settings → CarPlay you can turn off the voice (ride status, lap times) and the Warnings group — that is, the "Off route / Back on route" and "Coolant ≥ 105 °C" notifications. That switch does not govern the stop notifications or the ride outcome — those are turned off in the system notification settings.
• Legal basis: Article 6(1)(b) GDPR — providing a feature you switch on yourself.
• Retention: the summary and the downloaded destination photos stay on the device while you remain signed in and are deleted when you sign out. Recorded track points are stored as a ride recording under section 2.10.

3. What data we process on the driveandjoy.cz website

On the public driveandjoy.cz website we process personal data in three situations: data you submit yourself through forms (3.1–3.3), anonymous visitor statistics (3.4), and content that app members choose to share (3.6). The website does not require a user account.

3.1 Contact form

• Data processed: name, e-mail address, phone number (optional), the content of your message.
• Purpose: receiving and handling your enquiry or request and any follow-up communication with you.
• Legal basis: Art. 6(1)(f) GDPR — legitimate interest (to respond to the enquiry and manage communication). If the enquiry is aimed at concluding a contract, Art. 6(1)(b) applies — steps taken prior to entering into a contract.
• Retention: for the period necessary to handle the enquiry and a reasonable period thereafter for any follow-up communication; the data is then erased, unless a legal retention period requires otherwise.
• Recipients: Supabase (storing the message in the database), Resend (sending the e-mail with the message content to our address), Vercel (website hosting and delivery).

3.2 Event registration

• Data processed: name, e-mail address, phone number, vehicle details (make, model, year of manufacture, power, registration plate / licence plate), number of people, information about your experience, a note, and confirmation of consent to the processing of personal data (GDPR acknowledgement).
• Purpose: processing your registration for a specific event, preparing the attendee list, event-related communication and sending a registration confirmation.
• Legal basis: Art. 6(1)(b) GDPR — performance of the participation contract, or steps taken prior to entering into a contract at your request. Your confirmation serves as evidence that you were informed of the processing terms.
• Retention: for the period necessary to organise the event and settle your participation; data with accounting or tax relevance is then retained for the period set by statutory time limits (see Section 5).
• Recipients: Supabase (database), Resend (confirmation e-mail), Vercel (website hosting), and where relevant the organiser of the specific event (to the extent necessary for the attendee list).

3.3 Mobile app updates (beta invitation, release announcement)

• Data processed: e-mail address; the wording and time of the consent given; a cryptographic fingerprint of your IP address (SHA-256 with a secret server key — the readable IP address is not stored); a truncated browser identifier (user-agent); a single-use confirmation link and the time your e-mail address was confirmed (double opt-in).
• Purpose: sending information about the DRIVE&JOY mobile app by e-mail — beta invitation, release announcement and app news. The IP fingerprint, browser identifier and the wording and time of consent serve as evidence that consent was given (Section 7 of Czech Act No. 480/2004 Coll.) and to protect the form against abuse (rate limiting).
• Legal basis: Art. 6(1)(a) GDPR — consent given by ticking the box in the form and confirmed by clicking the link in the e-mail. Without confirmation we send you no further e-mails. You may withdraw consent at any time (see Section 8); withdrawal does not affect the lawfulness of processing before withdrawal.
• Retention: until you withdraw consent or until we stop sending app updates. We send no further e-mails to unconfirmed addresses (no click on the link).
• Recipients: Supabase (database), Resend (sending e-mails), Vercel (website hosting).

3.4 Visitor statistics (cookieless analytics)

• To measure traffic we use our own tool that uses no cookies or other identifiers stored on your device and performs no cross-site tracking.
• Data processed: the page visited (URL), approximate country, device type and the source of the visit (referrer). Your IP address and browser identifier (user-agent) are not stored in a readable form — a cryptographic fingerprint is derived from them (SHA-256). The fingerprint is computed with a daily salt and a secret server key; without the secret key the fingerprint cannot be linked back to the visitor. It is used only to roughly distinguish visits within a single day. An automatic filter excludes access by bots and search engines.
• Purpose: anonymous visitor statistics and improving the website's content and performance.
• Legal basis: Art. 6(1)(f) GDPR — legitimate interest in measuring the website's performance and security. Because no cookies or personal identifiers are stored on your device, no cookie consent is required for this tool (no cookie banner).
• Retention: only in the form of aggregated, anonymised statistical data.
• Alongside our own tool, the website runs Vercel Web Analytics provided by our hosting provider. It likewise uses no cookies; it processes the page address, device type, country and source of the visit.
• Recipients: Supabase (storing the anonymous records), Vercel (website hosting and Vercel Web Analytics).

3.5 Website technical error logging

• If a technical error occurs while the website is displayed, we record the error message text, a technical trace (stack trace), the page address and the website version. The record contains no name, e-mail address or other direct identifier of the visitor.
• Purpose: detecting and fixing technical defects and ensuring the website works properly.
• Legal basis: Art. 6(1)(f) GDPR — legitimate interest in the functionality and security of the website.
• Retention: 90 days.
• Recipients: Supabase (storing the records).

3.6 App members' content published on the website

• App members can choose to share certain content via a link. Such a link is then publicly accessible without signing in, and the content is displayed on driveandjoy.cz.
• What can be shared: a ride record (summary and route map), a vehicle listing (including the details the member entered), a vehicle profile, a route plan and a public member profile — always to the extent the member configures in the app.
• The data displayed may include the member's name or nickname, photographs and vehicle details. For a ride record, the start and end of the route are trimmed so that a home address cannot be inferred from the map.
• Purpose: allowing members to share their own content outside the app.
• Legal basis: Article 6(1)(b) GDPR — providing a feature the member invokes. Sharing can be revoked in the app at any time, which disables the link.
• Recipients: Vercel (website hosting and delivery), Supabase (database), Mapbox (map background for a shared ride record).

4. Legal basis for processing (Article 6 GDPR)

The detailed legal basis for each web processing activity is stated directly with it in Section 3.

5. Data retention

• Account, profile, garage, community and wishlist data is retained for the duration of your account. After account deletion it is erased (except for data we are legally required to retain).
• Booking and payment data is retained for the period required by accounting and tax legislation (Act No. 563/1991 Coll., on accounting; Act No. 235/2004 Coll., on VAT) — up to 10 years.
• Data from website forms (contact form, event registration, beta invitation request) is retained for the period necessary to fulfil the relevant purpose; data with accounting or tax relevance is then retained under the statutory time limits above. Specific periods are stated with each processing activity in Section 3.
• Ride recordings (telemetry), including the stored data files, are retained for the duration of your account, or until you delete the ride yourself.
• Chat messages and attachments are retained for the duration of the conversation, or of your account.
• Push notification tokens are deleted when the device signs out or the account is deleted.
• Technical error and usage event records (app and website) are retained for 90 days; records linked to an account are also deleted when the account is deleted.
• Wingman conversations (questions and answers) are retained for 90 days.
• The technical record of a language-model call (feature, model, token count, cost, response time — without content) is retained for 90 days; the model's answer itself is deleted from it after 24 hours.
• A JOY Coach ride analysis is stored with the ride and deleted together with it. A generated route plan that you do not save is deleted after 30 days.
• Data stored on the device for the car display (the summary of destinations and vehicles, downloaded destination photos) is deleted when you sign out of the app; this data never leaves the device.
• Transactional e-mails are retained for the period necessary at the e-mail service provider.

6. Recipients of data (processors and other recipients)

We share your data only with the following recipients. Those who process it on our behalf do so under data processing agreements; the others (club partners, event organisers and the navigation app you choose yourself) act as independent controllers. The Sent by column indicates whether the request is sent by our server (in which case the recipient does not see your IP address) or directly by your device.

7. Transfers to third countries

Some recipients (Google, Anthropic, Resend, Apple, Vercel, RevenueCat, Shopify, Mapbox and possibly Stripe) may process data in the USA, or in Canada (Shopify — a country covered by an adequacy decision). Supabase processes data in the EU, Open-Meteo in Germany and Seznam.cz in the Czech Republic. Such transfers are carried out on the basis of the Standard Contractual Clauses (SCC) approved by the European Commission, or on the basis of an adequacy decision (EU–US Data Privacy Framework). This ensures an adequate level of protection for your data. The exception is the navigation app you choose yourself (section 2.16): the coordinates are passed to it directly by your device on your instruction and its provider acts as an independent controller — our agreements and clauses do not cover that transfer, and the chosen app's own policy applies.

8. Your rights

In relation to your personal data you have the following rights:

• Right of access (Art. 15) — to obtain information about what data we process.
• Right to rectification (Art. 16) — to have inaccurate data corrected.
• Right to erasure (Art. 17) — the "right to be forgotten" (unless a legal retention obligation prevents it).
• Right to restriction of processing (Art. 18).
• Right to data portability (Art. 20).
• Right to object (Art. 21) to processing based on legitimate interest.
• Right to withdraw consent (Art. 7(3)) — where processing is based on consent.

You can exercise these rights by e-mailing the controller's address in Section 1 (info@driveandjoy.cz). Most in-app data can be managed directly in the app (editing your profile, deleting a vehicle, cancelling a booking, deleting your account); for data submitted via the website, please contact us at the address above to have it corrected or erased.

9. Cookies, tracking and third-party components

The DRIVE&JOY mobile app uses no cookies, no advertising SDKs and no third-party analytics or crash reporting, and does not track you across other companies' apps and websites. Local device storage is used only to run the app — sign-in (session token), caching of displayed content and temporary storage of an unsent ride recording until it can be uploaded.

The app does, however, load components from third-party servers (Google Fonts, the Stripe payment component, the YouTube player and video thumbnails, the RevenueCat subscription library, Mapbox map data and thumbnail images in the news feed). Those providers therefore receive your device's IP address and technical details about it; some of them may use their own cookies or similar identifiers in the process. Details are in section 2.21.

The driveandjoy.cz website uses no advertising cookies. Traffic is measured using our own tool without cookies and using Vercel Web Analytics, which likewise uses no cookies and stores no personal identifiers on your device (see Section 3.4) — which is why the website does not display a cookie consent banner. Third-party components also load on the website (fonts, the map background for shared content, the payment component), which receive your device's IP address.

10. Security

We take appropriate technical and organisational measures to protect your data: encrypted transmission (HTTPS/TLS), password hashing, database-level access control (Row Level Security), and segregation of payment data at a certified provider (Stripe, PCI-DSS).

11. Changes to this policy

We may update this policy from time to time. We will notify you of material changes in the app or by e-mail. The current version is always available at this address.

12. Contact and complaints

For questions, contact us at info@driveandjoy.cz.

You also have the right to lodge a complaint with the supervisory authority:

Office for Personal Data Protection (ÚOOÚ)

Pplk. Sochora 27, 170 00 Prague 7, Czech Republic

www.uoou.cz