Privacy
Last updated: 22 October 2026.
Who is responsible
The data controller for Cars by BSHK is Aleksandr Beshkenadze, acting as a private individual under the BSHK brand. Cars is independent of the vehicle marketplaces. For privacy requests, contact [email protected].
What we process and why
We process account and vehicle-selection data to provide the service you request (GDPR Article 6(1)(b)). This includes your name, email, optional username/avatar, email-verification state, password hash, passkey public credentials, sessions, authorized connections and API-key records. We never store your plain-text password or the private key of your passkey. Sessions may include your IP address and browser information.
Your private selections include requirements, chosen models and markets, saved listing details, notes, Keep/Skip/Check later decisions, and official checks you request. These may include supplied registration numbers, production dates and energy-scenario assumptions. We do not need sensitive personal information for vehicle research; do not enter medical details, identity documents or unrelated personal information in requirements or searches.
To record your acceptance of the service terms, we keep the document version, selected language, document fingerprint, acceptance time and method, and the relevant connection identifier. This record is linked to your account, is included in your data export and is removed from the active database when the account is deleted. Public archived terms contain no user acceptance records. Terms acceptance is separate from optional analytics consent.
We process limited request and security records under our legitimate interests in preventing abuse, protecting accounts, investigating errors and enforcing proportionate usage limits (Article 6(1)(f)). We limit these records to the security purposes described here and consider your rights when applying these safeguards. You may object to this processing; we will consider your circumstances and any applicable reasons for retaining a limited record.
Optional public-page analytics uses your consent (Article 6(1)(a)). Refusing analytics does not affect your account or selections. Accepting a privacy notice is not a separate condition for processing data necessary to provide your requested service.
Recipients and external requests
When an administrator invites someone, Cars stores the specified email address, issuing account identifier, invitation expiry and status, and the accepting account identifier and time when used. Invitations permit one ordinary account for the specified email. Invitation links expire after the administrator-selected period (7 days by default, up to 30 days) or when revoked or used.
Authentication, verification and recovery emails are delivered through Resend SMTP and include your email and a short-lived sign-in or recovery link. Accounts are stored in SQLite; restricted database backups use Cloudflare R2. Cloudflare also provides network delivery. Authorized administrators can access account and security records for support and security tasks.
Vehicle research may send vehicle-related queries and public review text to Exa and TypeSafe. ADEME receives catalogue queries; Dutch registration checks send the plate you supply to RDW. The separate Vehicle Data service receives model-catalogue searches. Fuel-price and annual-distance scenarios are calculated locally. Local VIN decoding uses a reference database on our server. When you authorize online VIN lookup, a cache miss or an explicit refresh sends the supplied VIN to the configured provider, currently bimmer.work for BMW and Mercedes-Benz factory data. We do not send your account credentials to that provider.
Server requests to supported marketplaces carry a random X-Cars-Request-Id. We keep its association with your account and connected app for abuse investigation. We do not forward your name, email, user ID, browser IP or OAuth credentials in these server requests. This does not guarantee the marketplace retains the request ID.
When a widget displays original vehicle photos, your browser loads them directly from the marketplace or its image provider. That provider receives your network request and IP address and may apply its own browser-storage policies. We suppress the referrer on these images. This direct image request is separate from the server requests described above.
Your connected AI client receives the tool results you authorize and handles them under its own policies. Public review evidence, quotations and processing provenance are shared across users; private selection notes and account details are not part of that shared corpus. Public listing descriptions can contain seller information; contact support about corrections or personal-data concerns in a source result.
Ask support for the current provider locations and applicable international-transfer safeguards. This notice does not promise that every provider processes data exclusively in the EEA.
How long we keep data
- Account records and private selections remain while you keep the account, until you delete it or request applicable erasure. You can change saved requirements and decisions during use. Shared public research is kept separately for evidence reuse and correction.
- Successful online VIN results, including the VIN, factory option codes, provider response and retrieval time, are cached under your account without an automatic expiry. They remain available after provider access expires, are included in your account export and are removed with your account. Your private VIN cache is not shared with other accounts.
- Browser sign-in cookies are session cookies: Cars does not give them a persistent expiry. Browser session-restoration features may preserve them. Server sessions expire within 7 days, with expiry refreshed while you use the service. Expired sessions and verification records are removed by scheduled cleanup. Email links expire in 10 minutes; passkey challenges in 5 minutes. OAuth access lasts 15 minutes; refresh credentials last up to 30 days unless revoked or linked access ends.
- Request logs are removed after 30 days; administrative audit records after 180 days. Logs contain time, method, destination hostname/path, status and duration, not page bodies or URL query strings. These records associated with an erased account are removed as part of account deletion.
- Expired usage counters, login intents, search-cache entries and security challenges are cleaned up. API keys expire after your chosen duration or end when revoked/deleted. Revocation markers remain while needed for the account's security.
- Optional event subscriptions expire within 24 hours unless renewed. They stop after revocation or deletion. Callback destinations and signing secrets are encrypted; delivery records expire after at most 30 days and are removed with the subscription/account.
- Restricted database backups expire after 30 days. A record removed from the active database may remain in an older backup until that backup expires. Backups are not used for routine account access. Separately retained pseudonymous account-deletion records last 35 days and must be reapplied before a restored database is made available. Deletions after the latest recorded backup/journal must also be checked before restoration.
Scheduled cleanup may add up to its next daily run to a stated expiry. Any exceptional legally required retention must be identified and explained when responding to your request; there is no blanket exception from deleting private selections.
Cookies and browser storage
Authentication cookies are HttpOnly, Secure on HTTPS, SameSite=Lax and restricted to the Cars host. They are used for login and security, separately from optional analytics. A short-lived OAuth state cookie may last 5–10 minutes, a passkey challenge 5 minutes, and a signed invitation activation cookie 10 minutes. Cars does not store authentication tokens in localStorage.
Your explicitly selected theme is stored in this browser until you change it or clear site data. Some client widgets keep your vehicle decisions in client widget state or a local browser fallback. These copies are under the browser/client's control; deleting an account also clears the Cars shortlist/admin draft keys available on that device, but cannot clear a different device or data held by your AI client.
Optional analytics and consent
May we use Umami to measure visits to public pages? It loads only with your permission. Sign-in, account and vehicle-selection pages are not tracked. You can change your choice at any time.
With permission we load Umami from umami.fourxxi.com for the homepage, connection guide and this privacy page. The supplied pageview contains public path, title and hostname, without query parameters, fragments, referrer, account identifiers or selection details. The server receives your network request/IP. Sign-in, account, administration, selection and chat widgets are excluded. Automatic tracking is disabled and the tracker is configured to respect Do Not Track.
Your browser choice is valid for 180 days. We retain a minimal consent receipt with choice, version and timestamps for that period; it is not linked to your account and is not included in analytics events. The current wording version is cars-analytics-v2. Analytics remains off if permission cannot be recorded. Use Analytics preferences in the footer to refuse or withdraw permission at any time. Withdrawal stops future requests but cannot recall a request already sent.
Your rights and account controls
In Your account you can download your account and selection data as JSON, revoke connections and keys, end sessions, and permanently delete your account. Export and deletion require a sign-in within the last 15 minutes. Deletion removes account credentials, selections, notes, saved checks, subscriptions and associated active records; it does not remove independently held public source documents or copies in your AI client.
You may request access, correction, erasure, restriction and, where applicable, portability of your personal data, object to processing based on legitimate interests, or withdraw optional consent without affecting earlier lawful processing. Email [email protected] from your account email; we may request proportionate information to verify your identity. Do not send passwords, API keys or sign-in links.
We normally respond within one month. If a permitted extension is necessary, we will explain it within that period. You can complain to a competent supervisory authority, including in the country where you live or work: EU/EEA data-protection authorities.
Account contact details are needed to provide and secure an account; you can browse public pages without one. Vehicle requirements you provide help answer your requested search. We do not make decisions that have legal or similarly significant effects on you through automated vehicle recommendations.