Privacy notice.

When you send a sourcing request

The form collects your name, company, email address, phone or WhatsApp number, destination country and port, selected models, vehicle quantity, budget, steering preference, purchasing timeline and any message you provide.

The saved inquiry also includes its reference, submission and contact-consent time, a random browser session identifier, and the referring source or campaign tags available when you submit. The showroom operator can add follow-up notes and update the inquiry status in the protected dealer portal.

You must agree to be contacted about your request before the form can be submitted. This permission concerns your sourcing inquiry. Allowing optional browsing analytics is a separate choice.

How inquiry information is used

Your contact details and purchasing requirements help the operator review your request, prepare a sourcing quotation and follow up on the proposed vehicles, destination and export arrangements. The portal also shows inquiry totals, requested models, destination markets, referring sources and conversion stages.

Submitting the form saves an inquiry in the site database and returns a reference. It does not place an order or make a payment.

Optional showroom analytics

The browser sends activity events only after you choose “Allow analytics.” These events cover page views, model views, adding a model to the shortlist, starting a request and successful inquiry submission. They contain a random session identifier, page path, relevant model identifier, campaign tags and a destination selection where supplied. The event payload does not include your name, email address, phone number or free-text inquiry message.

Choose “Essential only” to browse without sending these optional events. You can reopen “Cookie preferences” in the showroom footer to change the choice. Changing it stops future optional browser events; it does not automatically erase events already saved.

For consenting activity, the server uses the connection IP to estimate the country using a local DB-IP Lite database. It stores a masked network range and a pseudonymous IP hash that changes daily, rather than the full IP in the analytics database. Country estimates may reflect a VPN or proxy location rather than your physical location. No visitor IP is sent to the geolocation provider for lookups.

The server evaluates browser user-agent and automation signals, and event frequency, to exclude detected crawlers and unusual sessions from accepted traffic counts. It keeps the exclusion reason for review. Detection is imperfect and accepted traffic is not a guarantee of a human visitor. Campaign and referring-source labels identify acquisition channels, not verified personal identities.

Preferences stored in your browser

The showroom uses local browser storage to remember your saved models, appearance mode and analytics preference. Session storage holds the random session identifier and campaign attribution used for a browsing session or inquiry. You can remove these values using your browser’s site-data controls.

Clearing browser storage removes those local preferences. An inquiry already submitted remains in the server database.

Storage and retention

Inquiry and activity records are stored in the site's server database. Inquiry information is available to the operator through the protected dealer portal, including its inquiry-export feature. New visitor analytics and filtering records are automatically removed after 90 days through scheduled or opportunistic maintenance. Server security logs and backups have separate retention policies.

No automatic deletion schedule is configured for commercial inquiries or legacy activity collected before the new analytics system. Browser session storage and local preferences have separate lifetimes controlled by your browser.

Questions or information changes

Use the sourcing form in the showroom to request a correction, ask about information associated with an inquiry or request its removal. Include your inquiry reference and enough context for the operator to identify the request. A browser preference change alone does not send such a request.