RETROCONFIGURATOR: PRIVACY POLICY

Last updated: October 2026

The short version

RetroConfigurator runs entirely in your browser. The car configurator executes client-side via WebAssembly. Your build selections are never sent to or stored on a server by us, unless you choose to submit a build to the gallery (below). One nuance: a build's share link encodes your selections in the URL itself. Anyone you give the link to can see that build, and, like any URL, it appears in standard server/request logs when opened. We still store nothing about it.

What we collect

Nothing personal by default. We do not require an account and do not collect your build data unless you send it to us. Spec data (option codes, prices, etc.) is static and served as plain files. Our host keeps standard server logs (including IP address and user-agent) transiently for security and to operate the site. We also use Vercel Web Analytics to count page views and referrers in aggregate. It sets no cookies and stores nothing on your device, so it cannot follow you to other sites or build a profile of you.

What we store on your device

Only small local-storage keys in your own browser, never read by us or sent to us. After you close the welcome message we set retrospec.welcomed; after you dismiss the new-models banner, retrospec.modelsNoticeDismissed; and after you dismiss the moved-domain notice, retrospec.movedNoticeDismissed, so you aren't shown them again. If you use the visualizer and enter a Gemini API key, it is kept in retrospec.geminiKeyso you don't have to paste it every time. None of these holds an identifier. Clearing your browser storage removes them. This is separate from the advertising cookies described below, which are set by Google rather than by us.

Rendering your build

The visualizer is optional and uses your own Google Gemini API key. When you ask for a render, your browser sends the request directly to Google: a text description of your build, the reference photographs it selects, and any photo you choose to attach. None of it passes through or is stored by this site, and we never see your key or the image you get back. Google handles the request under its own Gemini API terms and privacy policy, tied to your key and your Google account. Don't attach photos you don't have the right to use.

Third-party services

This site displays advertising through Google AdSense and uses a social-share widget. Google, as a third-party vendor, uses cookies to serve ads based on your prior visits to this and other websites. Google and its partners may collect and use data under their own privacy policies, which we do not control. You can review Google’s practices and opt out of personalized advertising at policies.google.com/technologies/ads. The social networks you share to may likewise set their own cookies, and links such as “Buy me a coffee” take you to third-party sites governed by their policies.

Cookies & your choices

Where consent is required (EEA, UK, and Switzerland), it is collected by Google's certified consent management platform: a consent message appears on your first visit, and advertising cookies are used only according to the choice you make there. You can review, change, or withdraw your choice at any time via the “Privacy settings” link in the site footer, or right here:

Submitting a build to the gallery

If you choose Submit to the Gallery, we receive that build and nothing else: its share link (the car, year, body style and option codes), the angle and any scene you pick, and the optional build name and credit you type. No image is sent. It passes the same Cloudflare Turnstile check and per-IP rate limit described under Contributing data, and is then kept privately in our database (Upstash, through our host Vercel): the queue isn't public, and nobody but us sees it. You get a private link to your build's page. The key that lets it delete the build is part of the link, and we keep only a scrambled (hashed) copy, so we can't send it again. We use the build to draw it ourselves with AI and, if the render comes out right, publish it in the gallery with the build, the name and the credit; the image is stored with Vercel Blob. Your link deletes the build, its render and its gallery entry at any time, at once. A build we decide not to draw is deleted, and one we haven't drawn within 180 days is deleted automatically. Lost your link? Email admin@retroconfigurator.com with the build page's address.

Contributing data

If you submit a correction or a price, it's filed as an issue on our public GitHub repository, retroconfigurator/submissions. By default the site files it for you, so you need no GitHub account: the form sends what you typed to our server, which checks it and posts it through our submissions bot. To keep bots out, the form runs Cloudflare Turnstile, which Cloudflare processes under its privacy policy, and our server counts submissions per IP address to limit floods. That count is held in memory for at most ten minutes and never stored. What becomes public is what you typed, under the name you gave, or none. You can also file it yourself on GitHub, under your own account and GitHub's privacy statement.

Your rights (EU/UK and others)

Subject to applicable law you may request access to, correction of, or deletion of your personal data, object to or restrict certain processing, and lodge a complaint with your data-protection authority. To exercise any of these, write to admin@retroconfigurator.com. That address reaches the person responsible for this site, and requests are answered within one month as the GDPR requires. Because contributions are public and openly licensed, we can remove account identifiers, but factual data you contributed may remain in the open dataset.

Contact

Questions or requests about this policy (including data-subject requests): admin@retroconfigurator.com. See also our Terms of Use.

← back to RetroConfigurator