Privacy Policy

This Privacy Policy describes how VEHICOTEK public website experiences may collect, use, disclose, and protect information through the storefront, company pages, product pages, installer pathways, account access routes, warranty and protection routes, and contact workflows.

This page is drafted for the current repository state. Production provider names, retention periods, dedicated contacts, and legally required disclosures must be finalized before relying on this page as legal advice or a final public policy.

Depending on which public route or account workflow you use, VEHICOTEK may collect the following categories of information:

Normal website operation may create technical information such as IP address, browser type, device information, request timestamps, diagnostics, security logs, and error information. The committed storefront also uses the session-only browser storage key vehicotek_intro_played to avoid replaying the homepage intro during the same browser session.

• Present product, installer, warranty, protection, company, contact, and account experiences.
• Route inquiries to the correct product, installer, account, warranty, claim, protection benefit, business, or general support pathway.
• Validate form input and reduce unnecessary sensitive information in general contact messages.
• Prepare installer applications, owner verification, warranty registration, claim preparation, and support workflows where those routes exist.
• Maintain security, debug issues, protect accounts, and improve website reliability.
• Comply with applicable legal, operational, accounting, or dispute obligations when approved systems exist.

VEHICOTEK may share information with service providers, professional installer participants, account and authentication providers, support providers, fulfillment or commerce providers, warranty reviewers, legal or compliance advisors, and public authorities when required or permitted by applicable law. Provider names and final sharing details must be confirmed before production publication.

Owner and installer account routes may use authentication/session endpoints in configured environments. The current storefront treats browser-stored roles, permissions, sessions, and cart counts as development-only state and not as a production authorization boundary.

Installer application routes may ask for business name, contact details, service area, capabilities, application status, and supporting business information. Approved backend workflows must govern application review, organization records, invitations, memberships, roles, approval, suspension, and audit records.

Warranty registration, lookup, claim, transfer, and protection benefit pathways may involve vehicle identifiers, installation records, product information, installer context, photos, documents, ownership contact information, and status information. The repository currently separates these public preparation pages from backend warranty and claim implementation.

Future commerce workflows may involve cart, order, pricing, fulfillment, payment, tax, returns, and order-support information. Medusa owns authoritative commerce records, while payment processors own payment-processor transaction state. The F2F-B public pages do not implement cart, checkout, Stripe, or payment processing.

The current committed storefront does not include analytics scripts, marketing pixels, advertising tags, or a cookie preference center. The cookie audit currently identifies the homepage intro sessionStorage key and notes that framework or backend session cookies may exist in configured environments.

See the Cookie Notice for the current storefront audit.

VEHICOTEK should retain information only as long as necessary for the purposes described in this policy, including account management, installer application review, warranty and claim administration, customer support, security, legal compliance, accounting, and dispute handling. Exact retention periods require legal and operational approval.

VEHICOTEK should use reasonable administrative, technical, and organizational safeguards appropriate to the information and workflow involved. No website can guarantee absolute security, and users should avoid submitting passwords, verification codes, full payment-card numbers, government identifiers, or unnecessary sensitive information through general contact forms.

Depending on your location and applicable law, you may have rights to request access, correction, deletion, portability, restriction, objection, or withdrawal of consent. These rights are not identical everywhere and may be subject to verification, exceptions, and retention obligations. Use the Contact page to start a privacy request until a dedicated privacy contact is approved.

VEHICOTEK public pages are designed for automotive product, installer, owner, warranty, and business workflows and are not directed to children. If child-related data handling becomes relevant, the policy and product requirements must be reviewed before implementation.

Provider locations, hosting regions, support locations, and data transfer mechanisms are not finalized in the committed repository. Cross-border processing disclosures and safeguards must be reviewed before production use.

The current storefront references Medusa-backed account and commerce concepts in configured environments. No committed analytics abstraction, tracking script, or marketing cookie provider is present. Future analytics, email, payment, maps, support, hosting, or OMS providers must be documented before production launch.

VEHICOTEK may update this Privacy Policy as product, account, installer, warranty, support, and commerce systems evolve. The page should show an updated effective date when finalized changes are published.

Until dedicated privacy contact information is approved, privacy questions should begin through the Contact VEHICOTEK page and should avoid unnecessary sensitive details.