triptopcar

Privacy policy

Draft. The operator's legal details, retention periods and the final wording must be confirmed by a lawyer.

TripTopCar (triptopcar.com) is a platform where local rental companies in the countries listed on the site offer cars for rent. This page describes what data the site collects and why.

Visitors

  • Cookies: pr_locale stores the chosen language; pr_last_search and pr_recent_cars store your last search and recently viewed vehicles (30 days), used for recommendations on the home page.
  • Browser storage (localStorage): favorites; pr_consent stores your analytics choice; pr_attribution stores the ad source of your visit (UTM tags, gclid, yclid, Google Analytics and Yandex Metrica client IDs, landing page, referrer).
  • Yandex Metrica analytics (see the section below).

Renters (booking request)

  • The booking form collects your first and last name, phone, email, dates and time, pick-up and return location, extras and comment. If you are signed in, the booking is linked to your account.
  • Together with the booking we save the ad source of the visit (pr_attribution, see above).
  • Accounts store name, email, phone, Telegram username, city/district/address and avatar if you provide them; the password is stored only as a hash.
  • Actions of hosts and administrators in the cabinets are recorded in an activity log (who, what, when).

Hosts (vehicle owners)

  • The host sign-up form collects name, company name, phone, email, Telegram, city and fleet size.
  • Hosts upload photos of their vehicles; files are stored in Cloudflare R2.
  • Contracts, clients and payments that a host records in their cabinet are stored in the platform database.

Who receives the data

  • The host of the vehicle you book sees your booking with the name, phone, email and comment. They confirm it and contact you. Each host sees only bookings for their own vehicles.
  • Platform administrators have access to bookings, accounts and logs.
  • Emails (booking confirmation, status change, password reset, contracts) are sent through Brevo.
  • If you connect Telegram in your profile, notifications are sent through the Telegram Bot API.
  • Online chat: messages are answered by an AI assistant (Cloudflare Workers AI) using only the public information of the site. The conversation is kept for 30 days after the last message; the pr_chat cookie links it to your browser. If you leave a phone number, email or messenger username in the chat, the conversation is sent to the managers' Telegram chat so they can contact you.
  • The site and database run on Cloudflare (Workers, D1, R2).

Analytics and how to opt out

  • The site uses Yandex Metrica (counter 113667973) with click map and Session Replay (webvisor), to understand what is inconvenient and improve the service.
  • On your first visit a banner asks for your choice. Choosing “Decline” saves this in your browser and disables the counter on all subsequent pages. To change your choice, clear the site data in your browser and the banner will appear again.

Storage and deletion

  • The session cookie pr_session lives 7 days, the password reset link 5 minutes, and search cookies 30 days.
  • Retention periods for bookings, accounts and logs are not set in the code. The operator determines them.
  • To access, correct or delete your data, contact the operator. The contact for such requests is determined by the operator; until it is published, you can reach the host of your booking.