This policy explains which information Vindex may process, why it is needed, how it is protected, and which choices may be available.
The practical commitments behind Vindex information handling.
Information is used for defined product, security, support, and legal purposes.
Personal and organization information is restricted by role and operational need.
Supported correction processes help address inaccurate account or vehicle-linked information.
Information is retained according to service, security, contractual, and legal needs.
The information involved depends on the service, account, vehicle record, and interaction.
This can include profile details, contact information, support messages, organization settings, workshop records, inspection evidence, and information submitted during transactions.
Vindex may process VINs, specifications, mileage, events, service, ownership periods, inspections, and source attribution. Vehicle records are not automatically personal data, but context can make them personal.
Security and product operation may require logs, device details, approximate location, language, session, and interaction information.
Sharing, individual choices, safeguards, and processing locations depend on purpose and applicable requirements.
Information may be shared with authorized users, participating providers, infrastructure vendors, professional advisers, or authorities when the purpose and legal basis allow it.
Depending on location, you may request access, correction, deletion, restriction, portability, or objection. Some information must be retained or cannot be changed where records require integrity.
Vindex uses technical and organizational safeguards. Processing locations and transfer mechanisms may vary as infrastructure and partnerships develop.
Depending on location, you may request access, correction, deletion, restriction, portability, or objection. Some information must be retained or cannot be changed where records require integrity.
Vehicle transparency does not require unnecessary exposure of personal information. Access and retention should follow purpose, permission, and legal requirements.
Specific practices can vary by service, market, account type, and data source.
Have a privacy question or request?
Describe the account, record, or right involved without sending passwords or unnecessary identity documents.
Privacy contact