Version 2026-11-01 · Effective November 1, 2026
What we collect, and the shorter list of what we do with it.
This policy covers VIN Index: vinindex.ai, the dealer subdomains and custom domains we publish on, our dashboard, and our agent endpoint.
It is worth being precise about roles up front, because we sit on both sides of one and that shapes every answer below.
For a dealership's own account and business information, we are the organization responsible. For a car shopper who submits an inquiry on a dealer's listing page, the dealership is the organization responsible, and we handle that inquiry on their instructions in order to deliver it to them. If you are a shopper with a question about your inquiry, the dealership you contacted is the right first stop, and we will help them answer you.
If you are visiting our own marketing site rather than a dealership's pages, the parts that matter most to you are section 4, which explains the visitor identification service we use there, and section 16, which explains how to switch it off.
This page also serves as the notice given at or before the point of collection under California law.
Contents
- 1. What we collect from a dealer
- 2. What we take from your inventory feed
- 3. What we collect when someone submits an inquiry
- 4. What we log about visits, and what we deliberately do not
- 5. Credit bands, and what we are not
- 6. Why we use what we collect
- 7. What we never do with any of it
- 8. Who else processes it
- 9. Where information is held
- 10. How long we keep it
- 11. Your rights, and how to exercise them
- 12. US state privacy rights
- 13. Security, and what happens if we get it wrong
- 14. Children
- 15. Changes to this policy
- 16. Opting out of visitor identification, and our sales email
1. What we collect from a dealer
When a dealership signs up and uses the service, we collect:
- Account details: the work email that owns the account and a password, which is stored hashed by our authentication provider and is never visible to us.
- Business profile: dealership name, street address, city, region, postal code, phone, website, brand, and where applicable the dealer licence or registration number. Some of this is prefilled from a one-time read of your own public website, which you consent to at signup.
- Geographic coordinates derived once from the business address you give us, so your listings carry a correct location and market comparisons are regional rather than national. These describe a dealership, not a person, and we do not collect the precise location of any individual.
- Feed connection details, including the host and credentials for the inventory source you nominate.
- Billing information: your plan, billing period, currency, and a customer identifier from our payment processor. Card numbers go to the processor directly and are never stored on our systems.
- Your consent record: which version of the terms and this policy you accepted, and when.
- Configuration you enter, including lead destination, branding, and on paid plans your lender rate settings.
- Answer-page evidence and controls: business facts and supporting sources you supply or confirm, publishing authorization and pause settings, generated pages and revisions, and measurements used to check their discovery and factual accuracy.
- Public business-fact checks on eligible paid plans: profile and directory URLs, observed business names, addresses, phone numbers, websites, closure status and department hours, source snapshots, scan dates, confidence and identity-match evidence, and your confirmations or dismissals. Checks may include business-profile sources cited in AI answers. We exclude inventory and vehicle-detail URLs.
2. What we take from your inventory feed
We ingest the vehicle records your feed sends: VIN, stock number, specification, mileage, price, description, and photographs, which we re-host so they load quickly and stay available. We store a snapshot of each feed payload so we can tell what changed and avoid reprocessing what did not.
This is business data about vehicles, not personal information about people. If your feed contains personal information, for example a salesperson's name in a free-text description, it is published as part of that listing, so do not put anything in a feed you would not want on a public page.
3. What we collect when someone submits an inquiry
A lead form on a dealer's listing page collects the name, email, phone, and message the shopper enters, along with the vehicle they were looking at and how they arrived.
We store that inquiry and deliver it to the dealership, by email or to their CRM. The dealership decides how it is then used and how long they keep it. We keep our copy so the dealer has a record and so delivery failures can be retried and audited.
We do not sell inquiries, broker them, share them with any other dealership, or use them to market anything of our own. This is not only a policy: charging for or reselling leads would break the model the whole product is built on.
4. What we log about visits, and what we deliberately do not
The point of this product is telling a dealer that AI systems are reading and citing their inventory. That takes measurement, so it is worth stating exactly how much.
When a page on a dealer surface is requested, we may write one row recording: which dealer, which vehicle, what kind of visitor it was (a crawler, a verified agent, a person arriving from an AI answer, or an agent tool call), which AI platform it is attributable to, the referring URL, the path, the browser or bot user agent string, and the time.
We do not log IP addresses. There is no column for one. On dealer surfaces we do not build a profile of a visitor, we do not track anyone across sites, and we do not run advertising or identification tags. The one third-party tag there is Google Analytics, described below.
On dealer surfaces, apart from the referral cookie and Google Analytics described below, one first-party cookie is used, and only for attribution. When an AI crawler or a verified agent fetches a vehicle page, we set a cookie named __ai_ref that holds the name of that platform and nothing else. It lives for five minutes, it is read once and then cleared, and its only job is to connect the AI system that looked at a page to the person who arrives moments later with no referring URL. It carries no identifier and cannot be read by JavaScript or by another site.
One more first-party cookie can be set on any of our pages, but only when you arrive through a referral link, which is a link carrying a dealership's referral code. We then set a cookie named vi_ref that holds that code and nothing else, for 30 days, so that if you sign up, the dealership that referred you receives the free month our referral program promises. It says nothing about you, and it cannot be read by JavaScript or by another site.
We also run Google Analytics, and it is worth being plain about where. It runs on our own marketing site at vinindex.ai, and on the pages we publish for dealerships, measured in two separate properties so the two never mix. It sets its own cookies, which let it tell a returning browser from a new one, and lets us see which pages people land on, where they arrived from, and how they move through the pages. On dealership pages we use it to learn how shoppers use the pages we build, so we can make them better. There it does not load at all if your browser sends a Global Privacy Control signal. It is not in the dealer dashboard, and nothing it collects is shown to a dealer or used in any figure we report to one. We have switched off Google Signals and ad personalization on both properties, so it cannot be used to build advertising audiences or to follow anyone across other sites.
On vinindex.ai, including our marketing pages, signup, and the dealer dashboard, we also use PostHog to understand how people use the product: which pages they view, what they click, where a signup stalls, and which dashboard features dealers use. When you are signed in, those events are linked to your account and email address. PostHog may also record replays of sessions to help us fix confusing screens, with everything typed into forms masked. PostHog acts only on our instructions, never runs on a dealership's pages, and nothing it records is shown to a dealer or used in any figure we report to one.
Many of the visits to those pages are not people at all but the email security services that open every link in an email before it reaches the inbox. So that our numbers count people rather than those scanners, our servers check whether a visit to vinindex.ai comes from a network those services use. The address is checked and not kept. When it matches, we set a first-party cookie named vi_net that holds only that label, such as scanner_ip, for one day, and our analytics mark that browser's activity as a scanner's. The same label stops those services from removing a report a dealership has not asked us to remove.
Our marketing pages also run a website visitor identification service provided by Instantly, our sales email provider, through its Leadsy tag, which uses RB2B to do the identifying. We use it so that when someone from a dealership looks at our site, we can find out who they are and follow up with them about VIN Index. When the tag loads, RB2B receives the page you are on, the page that referred you, your browser details, and your IP address, and sets its own cookies; its script also looks up your approximate location from your IP address through a geolocation service. RB2B matches that against information it holds or obtains from its own sources, and may send us a name, work email address, job title, employer, and a professional profile link. Those details go into Instantly so we can contact you.
That service is confined much more tightly than Google Analytics. It never runs on a dealership's pages, in the dealer dashboard, on the private pages we prepare for individual dealerships, or on our privacy choices page. It does not load at all if your browser sends a Global Privacy Control signal, or if you have opted out on our privacy choices page. Section 16 explains how.
5. Credit bands, and what we are not
Some pages let a shopper pick a credit band, such as excellent or rebuilding, to see a realistic estimated monthly payment. That selection is something the shopper tells us about themselves in order to get useful arithmetic back. It is not a credit check.
We do not pull your credit. We do not obtain, request, or receive a consumer report or a credit score about you from anyone, we are not a consumer reporting agency, and choosing a band has no effect of any kind on your credit. Nothing on this platform runs a credit application.
A self-selected band is never attached to your identity in anything we publish or analyse. Where we report on shopping patterns, credit band appears only as an aggregate dimension across many people and is never joined to a name, an email, or an inquiry.
6. Why we use what we collect
We use the information above to do the things the service exists to do, and not for other purposes:
- To publish a dealership's inventory across its listing pages, agent endpoint, category pages, and syndication feeds.
- To deliver buyer inquiries to the dealership they were sent to.
- To show a dealership which AI systems read and cited their inventory and answer pages.
- To select, generate, publish and maintain answer pages on paid plans, unless the dealership pauses or withdraws automatic publishing, and to check public business facts against dealership-confirmed information so the dealership can investigate discrepancies.
- To bill for a plan, and to send service messages about an account.
- To recognise business visitors to our own marketing site and contact them about VIN Index, as described in sections 4 and 16. This never uses information from a dealer surface, a buyer inquiry, or the dealer dashboard.
- To keep the platform working and secure, including detecting abuse and diagnosing failures.
- To meet legal, tax, and record-keeping obligations.
7. What we never do with any of it
Some of these are commercially tempting, which is why they are written down.
- We never sell or share personal information collected on a dealer surface, in a buyer inquiry, or through the dealer dashboard. The visitor identification service on our own marketing site may count as a sale or sharing under some US state laws; we treat it as one, and section 16 explains how to opt out of it.
- We never use personal information to serve you targeted advertising, and we never upload it to an advertising platform to build an audience.
- We never publish a dealer's lender rates or rate sheets, in any form. Not as an aggregate, not as a market study, not anonymized. They are calculator input and nothing else.
- Buyer inquiry data never reaches any published dataset, report, or study we produce. Where we publish research about AI shopping behaviour, it is built from aggregated and de-identified request patterns, never from inquiry records.
- Free-text a person typed, such as a natural-language search, is never republished verbatim. Only extracted patterns are used.
- We never send buyer personal information to a language model. The enrichment step that writes listing copy sees vehicle and market data only.
- We do not use personal information to make automated decisions that produce legal or similarly significant effects about anyone.
8. Who else processes it
We use a small set of service providers, each for a stated purpose and under an agreement that limits them to it. None of them is permitted to use the information for their own purposes.
- Supabase: database and authentication. Holds dealer accounts, inventory, inquiries, and analytics.
- Vercel: application hosting and content delivery for every page we serve.
- Cloudflare R2: storage for re-hosted vehicle photographs and generated syndication feed files.
- Stripe: payment processing and subscription billing. Card data goes to Stripe and not to us.
- Resend: transactional email, including delivering inquiries to dealerships.
- Anthropic: generating listing copy and answer pages from vehicle, market, and dealership business facts, and extracting public business-profile facts for discrepancy checks. Never buyer personal information.
- Firecrawl: the signup read of a dealer's public website to prefill their profile, plus bounded recurring search discovery of public business-profile sources for discrepancy checks. Never inventory scraping.
- MarketCheck: VIN decoding and market context for vehicles.
- Google Analytics: measuring how people use our own marketing site and, in a separate property, the pages we publish for dealerships. Not present in the dashboard.
- PostHog: product analytics and error reporting on vinindex.ai and in the dealer dashboard, and a record of the requests we send to language models and what they return, so we can check quality and cost. Those requests carry vehicle, market, and dealership business data and public search questions, never buyer personal information. Not present on dealership pages.
- RB2B, through Instantly's Leadsy tag: identifying business visitors to our own marketing site. Unlike the providers above, RB2B combines what its tag observes with information from its own sources, so we do not describe it as acting only on our instructions. Not present on dealership pages, in the dashboard, or for anyone who has opted out.
- Instantly: sending our own sales email, including to visitors identified on our marketing site. Never used to contact buyers or anyone who submitted an inquiry to a dealership.
- Google Maps Platform: converting a dealership address to coordinates at signup and looking up public business-profile facts for recurring discrepancy checks.
- The NHTSA vPIC database: public VIN validation.
9. Where information is held
Our infrastructure and our service providers operate in Canada and the United States, and information may be processed in either country. While it is in another country it is subject to the laws of that country, including lawful access by its courts and authorities.
Where information leaves the country it was collected in, it stays protected by our agreements with those providers and remains subject to this policy. We remain accountable for it.
10. How long we keep it
We keep information only as long as it serves the purpose it was collected for, or as long as the law requires. In practice that means:
- Dealer account, profile, and configuration data: for as long as the account is open, then for up to seven years, which is the tax and business-record retention period that applies to us.
- Consent records: for as long as the account is open and for seven years afterwards, because the point of a consent record is being able to show what was agreed and when.
- Buyer inquiries: kept for the dealership's use while their account is open, and deleted on request from the dealership or the individual.
- Feed snapshots: kept only while they are useful for detecting what changed, and then discarded.
- Answer-page evidence, revisions, publishing authorizations, and public-fact check records: kept while needed to operate the account, maintain published facts, and explain publishing or discrepancy decisions. Account and consent records then follow the retention periods above; deletion requests follow section 11.
- Visit rows: kept in detail for 24 months, then retained only in aggregate, which carries no identifiers by construction.
- Billing records: for the seven-year period tax law requires.
- Details of a marketing-site visitor identified by our visitor identification service: for up to 24 months after our last contact with that person, or until they ask us to delete them. If you unsubscribe or ask us to delete your details, we keep only your email address on a suppression list, because that list is how we make sure you are not contacted again.
11. Your rights, and how to exercise them
Write to hello@vinindex.ai and mark it for the Privacy Officer. That address reaches the person accountable for privacy here, and it is the route for every request described in this section and the next. A postal address is available on request.
You can ask us for access to the personal information we hold about you, ask us to correct anything inaccurate, ask us to delete it, ask for a portable copy, and withdraw a consent you previously gave, subject to the limits the law puts on each of those. Withdrawing consent may mean we can no longer provide part of the service, and we will tell you plainly if that is the case rather than letting it fail quietly.
We acknowledge requests within 10 business days. We respond substantively within 30 days for requests under Canadian federal privacy law, and within 45 days for requests under a US state privacy law, with one further extension where the statute allows it and we tell you why. We do not charge for this.
We need to be able to tell it is you. We verify a request against information we already hold rather than asking you for new identity documents, and if we genuinely cannot verify you we will say so rather than handing your information to someone else.
If you think we have got something wrong, tell us and we will look at it again. You can also complain to the Office of the Privacy Commissioner of Canada, or to your state Attorney General, and you do not have to come to us first.
12. US state privacy rights
If you live in California, Virginia, Colorado, Connecticut, Texas, Utah, Oregon, Montana, or another state with a comprehensive privacy law, this section sets out what those laws give you and how our practices map onto their defined terms.
The categories of personal information we collect, in the statutory vocabulary, are: identifiers (name, email address, phone number, account identifier); customer records information (name, address, phone number); commercial information (plan, billing history, and the vehicle someone inquired about); internet or other electronic network activity information (the path requested, the referring URL, and the user agent string); and professional information (a person's role at a dealership). We collect these from you directly, from a dealership that gave them to us, from a dealer's inventory feed, from signup and recurring reads of public business-profile sources and a dealer's own contact or about pages, from the request itself when a page is fetched, and, for visitors to our own marketing site, from our visitor identification provider.
We do not collect biometric information, precise geolocation of an individual, sensory data, education records, or protected classification characteristics. The only inference we hold about anyone is the one our visitor identification provider makes about who a marketing-site visitor is and where they work, and we do not use it to make any decision about that person beyond whether to contact them. The only category of sensitive personal information we hold is a dealer account credential, used solely to log that dealer in. We do not use or disclose sensitive personal information for any purpose beyond providing the service, so the right to limit its use has nothing to act on here.
You have the right to know and access what we hold, to correct it, to delete it, to obtain a portable copy, and to opt out of sale, sharing, targeted advertising, and profiling.
On sale and sharing: in the preceding 12 months, the only personal information we may have sold or shared is what the visitor identification tag on our own marketing site collects, which is identifiers and internet or other electronic network activity information, disclosed to RB2B and Instantly. We treat that as a sale, and as sharing for cross-context behavioural advertising, under every state law that could define it as one. You can opt out on our privacy choices page at vinindex.ai/privacy/choices, linked in the footer of every page as "Do not sell or share my personal information", or by writing to us. We honour a Global Privacy Control signal as a valid opt-out: when your browser sends one, the tag does not load.
On targeted advertising and profiling: we do not use personal information for targeted advertising, we run no third-party advertising trackers, and we do not profile anyone in furtherance of decisions that produce legal or similarly significant effects. Google Analytics runs on our marketing site and on dealership pages with Google Signals and ad personalization turned off, so it is not used for advertising.
If we refuse a request, we will tell you why, and you may appeal by replying to that decision. We will respond to an appeal in writing within 45 days. If we deny the appeal we will give you a way to complain to your state Attorney General.
An authorized agent may make a request for you if you give them written permission and we can verify it. We will never deny you a service, charge you a different price, or give you a lower quality of service because you exercised a privacy right.
We do not knowingly sell or share the personal information of anyone under 16. Our marketing site is directed at dealership staff, and we have no actual knowledge of having identified anyone under 16.
13. Security, and what happens if we get it wrong
Access to the database is denied by default and granted per row, so one dealer's data is not reachable from another dealer's session. Administrative credentials are used only on the server and are never sent to a browser. Traffic is encrypted in transit. Passwords are stored hashed. Webhooks we send are signed so the receiver can verify them.
No system is perfectly secure, and we will not claim otherwise.
If a breach of our safeguards creates a real risk of significant harm to you, we will notify you and report it to the Office of the Privacy Commissioner of Canada, and to any US state regulator the law requires, as soon as feasible. We keep a record of every breach of security safeguards for at least 24 months, whether or not it was reportable, and we will give that record to the Commissioner on request.
14. Children
This service is for dealerships and for adults shopping for a vehicle. It is not directed to children, and we do not knowingly collect information from them. If you believe a child has given us information, tell us and we will delete it.
15. Changes to this policy
This policy carries a version. When we make a substantive change we publish a new version and ask dealers to accept it. The version a dealer accepted, and when, is recorded on their account.
We review this page at least once every 12 months and update the version stamp when we do, so the date at the top is a date someone actually looked, not the date the file was created.
16. Opting out of visitor identification, and our sales email
You can stop our visitor identification service from running for you in either of two ways. Set a Global Privacy Control signal in your browser, and the tag will not load on any of our pages. Or use the "Do not sell or share my personal information" link in the footer of every page, which takes you to vinindex.ai/privacy/choices.
The privacy choices page stores your decision in a first-party cookie named vi_optout, which lasts two years and does nothing except stop the tag from loading. It applies to the browser you set it in. To opt out across every device, or to have us delete the details we already hold about you, write to us at the address below.
If we have emailed you because you were identified on our site, every message we send includes a way to unsubscribe, and we stop within 10 business days of your request. We only email people about VIN Index in their capacity at a business, and we never use this route to contact car shoppers.
Opting out never affects a dealership's pages, their listings, or anything a dealer customer receives from us.
Privacy questions and requests
Write to hello@vinindex.ai, marked for the Privacy Officer. That is the designated contact accountable for privacy at VIN Index, and it is where access, correction, deletion, portability, and appeal requests should go. A postal address is available on request.
You can also complain to the Office of the Privacy Commissioner of Canada, or to your state Attorney General, without contacting us first.
This page describes our own practices. Each dealership publishing through us has its own privacy practices for the information you send it directly.
Version 2026-11-01 · Effective November 1, 2026