Forms ask for information relevant to a project, contact, visit, support, warranty or parts request.
PRIVACY POLICY / DATA TRANSPARENCY
How We Handle Information You Share With Us.
This policy explains what information may be collected when you browse the website, configure a vehicle, submit a project inquiry, contact the team, request support or provide files — and how that information may be used.
This website package is still a preview.
The business’s legal identity, privacy contact, live backend, hosting and retention schedule have not been confirmed. Forms in this package do not send your entries to the business. Please do not enter sensitive or confidential information in the preview.
IN SHORT
The Main Things to Know.
Several interactive drafts can remain in your browser for a limited time or tab session.
Files selected in this preview are not uploaded; their content stays in your browser.
No analytics or advertising tag is configured in this package. Event hooks are not a connected analytics service.
Production systems, retention, legal contact and applicable privacy terms still need owner and legal review.
On this page
01 / WHO AND WHAT THIS COVERS
Who Is Responsible for This Website?
This preview identifies the brand as TURBO TOP. The legal entity that operates the production website has not been confirmed. The brand name may not be the legal entity that decides how information is processed.
Until those details are approved, this page is a development disclosure, not a complete production privacy notice. It covers the public website, product and Insights pages, Build Your Car, Request a Quote, Contact, factory-visit requests, Support, Warranty, Spare Parts, dealer and venue forms, event inquiries, file selection and request-related communications.
It does not govern a third-party website, social network, map, carrier or other service reached through a link. Those services publish their own privacy information.
02 / INFORMATION YOU PROVIDE
Information You Choose to Share.
Depending on the route and fields you complete, information may include your name, email address, phone or WhatsApp number, company, role, country or city, website, project requirements, product interest, quantity, timeline and any optional budget or message.
Project, quotation and vehicle configuration
A Request a Quote or Build Your Car flow may include buyer and project type, vehicle category or model, quantity, intended use, driver or venue context, configuration preferences, branding requests, delivery destination, timing, company details and a Build ID. These details help describe the proposed project and, if a live service is connected, may become an inquiry record for review and follow-up.
General contact and factory visits
A general message may include name, email, phone, company, country, subject, message and an optional attachment. A factory-visit request may include company, visitor type and count, preferred and alternative dates, visit purpose, product interest and optional travel guidance. The form does not request passport or government identification.
Technical support, warranty and spare parts
Support and warranty forms may ask for contact details, buyer type, model, vehicle or order reference, purchase or delivery details, issue category, symptoms, safety observations, modification or repair history and supporting files. Parts requests may ask for vehicle and part references, quantity, labels, connector or component details and reason for replacement.
Dealer, venue and event project forms
These preview forms may ask for company and contact details, country, business or venue type, sales channel, intended customers, fleet size, operating conditions, event dates, arrival requirements, brand or vehicle direction and project notes. They are planning forms in this package; their current submit handlers do not send the entries.
Searches and choices on the website
Insights and FAQ search terms may be placed in a page query string so a filtered results page can be reopened. Do not enter a name, email, phone number or confidential information into a search field or URL.
A field shown as optional is not required to use the form. Do not send information that is not needed to explain your question.
03 / FILES & PROJECT MATERIALS
Files You Select or Upload.
Project references can include vehicle photographs, drawings, venue layouts, logos, brand guides, artwork, PDFs, component labels, support videos or warranty evidence. Those materials may contain personal, commercial or confidential information.
The browser may show the selected file name and size for review, but the page does not transmit the file or store its contents on a server. Files in support and warranty flows remain selected only in the browser. In Build Your Car, limited file metadata such as name, size and type may be present in the saved browser draft; the file bytes are not saved there and must be reattached after a refresh.
When a production service is connected, files should be used only to review the request, evaluate a technical or commercial project, provide support or handle a warranty or parts inquiry. The production operator must configure private storage, access restrictions, file validation, malware scanning where implemented and a deletion schedule before accepting uploads.
Please avoid unnecessary sensitive personal information. Do not upload passports, government IDs, payment-card data or unrelated personal files. A submitted logo or project image is not automatically approved for marketing, publication or a case study. Separate permission is required for public use. No confidentiality agreement is created merely by selecting or submitting a file.
04 / WEBSITE USAGE
Technical Information Collected When You Use the Site.
A production web host and security service may process standard request information such as IP address, browser and device characteristics, operating system, referring page, pages requested, time and date, and error or security events. Approximate region may be inferred from network information by a service. This website does not request precise GPS location or use a browser geolocation permission.
The production hosting provider and its log settings are not yet identified in this preview. The local development server used to view this package is not a production hosting or logging configuration. Confirm the real host, log fields and retention before launch.
05 / PURPOSES & BUSINESS GROUNDS
Why Information May Be Used.
If a live service is configured, information may be used to understand a project, prepare or follow up on a quotation, route a general message, review a factory-visit request, identify a vehicle or part, assess technical or warranty information, communicate about a request, maintain business records, prevent misuse, protect the website and improve the buyer experience.
Project and support information may be organized in business systems so the relevant sales, project, support or technical staff can review it. The site does not automatically approve a quotation, warranty claim or commercial project based solely on form processing. A business team must review the request.
Where privacy law requires a legal basis, the responsible entity must determine and document the basis for each activity in the markets it serves. The entity, markets and processing arrangement have not been approved for this preview, so this draft does not assign a final legal basis.
An inquiry is not a marketing subscription. If product or company updates are offered, the option must be separate, optional and unchecked by default, with an applicable way to withdraw consent or unsubscribe.
No email delivery or CRM system is connected in this package. If a production service sends a receipt or response about a submitted inquiry, the operator should describe the live channel and actual service provider here. Marketing messages require a separate choice where required by applicable law.
The preview does not make an automated decision about quotation approval, warranty eligibility, vehicle fit or commercial acceptance. The interactive tools provide planning guidance; a responsible business reviewer must confirm any production decision.
06 / COOKIES & DEVICE STORAGE
Cookies and Browser Storage.
The current site code does not set first-party cookies or include a cookie-consent manager. It uses browser storage in a few interactive flows. Browser storage stays on the device/profile where the page is opened; it is not itself a submission to the company.
Build Your Car
The saved draft can contain the configuration and contact fields entered in the configurator, optional marketing preference, and selected-file metadata. File contents are not stored. The page removes an expired draft when the configurator next loads; removal may therefore happen later than the seven-day expiry if the visitor does not return.
Request a Quote
Selected project and vehicle choices can be saved so a buyer can return to an unfinished brief. Free-text and contact fields are kept separately in session storage for the current tab. File contents and consent confirmations are not saved with the draft.
Attribution and confirmations
The configurator may keep a sanitized landing-page path and approved campaign identifiers for the tab session. After a connected service accepts a request, a short-lived receipt may hold only a request type, server reference and time so the Thank You page can show a one-time confirmation.
Delivery-planner handoff
A short-lived planning handoff can carry a destination country or city, quantity, delivery preference and arrival date from the delivery planner into a project brief. The RFQ page consumes it once. It does not include a name or contact detail.
Support, warranty and parts forms show local previews and do not save form entries through their current handlers. Selecting a file in those forms does not persist the file. If you use a shared device, clear a draft in the relevant tool or clear this site’s storage through your browser settings. A private browsing session may also limit storage.
No advertising or analytics cookie is configured in this package. If a consent manager, analytics tag or advertising technology is added, the owner must update this notice and verify that the control actually changes network behavior.
07 / ANALYTICS & CAMPAIGN SOURCES
Analytics and Advertising Attribution.
This package does not load Google Analytics 4, Google Tag Manager, Google Ads conversion tags, Meta Pixel, Microsoft Ads tags or a remarketing service. Several page scripts expose non-personal event names and selected categories through an in-memory data layer or a browser event hook. Without an analytics or tag script connected, those hooks do not send the event to an analytics provider.
Event designs are intended to use broad categories such as project type, vehicle category, quantity band, route or step number. Names, emails, phone numbers, company details, free-text messages, order or vehicle references, Build IDs and file names should not be sent to ordinary analytics. The configurator’s event handler filters event properties and does not include entered text. Verify this again in the browser network panel whenever tags or conversions are added.
Some inquiry routes can read campaign parameters such as utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, gbraid and wbraid. These identifiers help describe a campaign source. In the preview, no live lead endpoint receives them. No Microsoft or Meta click identifier is currently configured for collection.
A production conversion should be recorded only after the connected server accepts a valid request, not simply because someone opened a Thank You URL. The site should not place contact details or free-text form answers in a URL. If advertising measurement, enhanced conversions or remarketing is later enabled, the owner must review consent, data sharing and regional requirements and revise this notice first.
08 / SYSTEMS & RECIPIENTS
Sharing and Service Providers.
The production website’s hosting, CRM, inquiry database, email provider, private file storage, security services and operational providers have not been selected or connected in this package. Do not treat a planned integration as an active recipient. Before a live form is enabled, list the actual provider names and processing roles here.
Web fonts are served from this website’s own assets. Loading a page does not request a Google Fonts stylesheet or font file from Google-hosted servers.
The current package contains no embedded Google Map, YouTube player, chat widget, CAPTCHA, social-media pixel or payment form. A link to an external site opens that service under its own terms. If the operator later embeds media or a map, that may cause a third-party request when the page loads or the embed is activated and this notice must be updated.
If live inquiry processing is enabled, information may be made available to service providers acting for the operator, relevant internal staff who need it to review the request, business partners involved in a requested project where necessary, logistics providers when needed for delivery, professional advisers or authorities where legally required. The actual recipients and safeguards must be confirmed before production. This draft does not make an unverified claim that information is never sold or shared under every applicable legal definition.
09 / INTERNATIONAL VISITORS
International Visitors and Cross-Border Processing.
The site is designed for buyers in multiple markets. When the production site, business systems or service providers are selected, information may be handled in countries other than the visitor’s country. The operator has not confirmed a production hosting region, CRM region, email infrastructure or transfer mechanism for this preview.
Do not assume that a specific adequacy decision, standard contractual clause, certification or other transfer mechanism applies. The responsible company must identify the actual locations and confirm any safeguards required by the laws that apply to its activities before launch.
10 / RETENTION & SECURITY
How Long Information Is Kept and How It Is Protected.
Browser draft periods are described above. The current preview has no production inquiry database, CRM, support system or upload storage, so no server-side retention period can be stated. Before launch, the operator should set and follow retention periods for unqualified inquiries, project and order records, support and warranty cases, marketing preferences, uploaded files, analytics and server logs. Records may need to be kept longer where contract, warranty, tax or legal obligations require it.
When production processing is enabled, reasonable technical and organizational safeguards should be selected for the information and service involved. These may include encrypted connections, role-based access, server-side validation, restricted file storage, malware scanning where implemented, backups and operational monitoring. This preview does not establish that a production backend or those controls are in place. No internet-based system can be guaranteed completely secure.
Production uploads should not be placed in a publicly browsable directory. Access should be limited to staff or providers who need a file for the related project, support, warranty or parts request; analytics users do not need access to customer attachments.
11 / YOUR CHOICES
Your Privacy Choices and Rights.
Depending on where you live and the laws that apply, you may have rights to request access to, correction of or deletion of personal information, or to request restriction, objection, portability or withdrawal of consent. Rights may be subject to legal exceptions, including records that must be kept for a contract, warranty, safety, tax or legal requirement.
The responsible entity and privacy request contact have not been supplied for this development preview. A production operator must publish a monitored contact route, verify requests proportionately and provide the rights required for each applicable market. A government ID should not be requested automatically; if extra verification is genuinely needed, explain why and request the minimum required.
Children’s privacy
This website is intended for adult buyers, business customers and people seeking product or project information. It is not designed to knowingly collect personal information directly from children. A young person should not submit a name, personal email, phone number or home address through a business inquiry form. If the operator learns that a child has sent personal information, it should follow a reviewed process to assess and address the request.
12 / LINKS & POLICY CHANGES
External Links, Legal Requests and Policy Updates.
External websites and platforms have their own privacy practices. Information may also be preserved or disclosed where required by applicable law or legal process, or where reasonably necessary to protect the rights, security and users of the website.
Information may be transferred as part of a merger, acquisition, restructuring, financing or sale of business assets, subject to applicable law. This section does not authorize a recipient to use information outside the applicable transaction or legal purpose.
The policy should be updated when the site’s forms, storage, service providers, advertising or analytics configuration, data uses or legal requirements change. The owner may provide additional notice for material changes where appropriate. An email notice for every wording change is not promised.
13 / PRIVACY CONTACT
Questions or Requests About Your Information?
Before publication, the operator must add its verified legal entity, privacy contact email or other monitored privacy-request channel, and registered address where required. Those details are not available in this preview.
No monitored privacy-request channel is configured for this preview. The Contact page forms are also local previews and do not send messages. Do not rely on this package to submit a privacy request; add a verified, monitored channel before production use.
Effective date, last-updated date and version are not set. Add them only after the responsible entity approves the final policy and its actual data flows.
This development draft is not a substitute for review by the company’s privacy and legal advisers. The final notice must match the deployed site, target markets, data systems, vendors, retention schedule and consent controls.
