Privacy Policy

Last updated: 2026-05-08

ViteCode is a static site that generates AI coding agent template files in your browser. This page documents — concretely — what data the site touches and what it does not.

What we don't collect

• No email addresses. There is no signup form anywhere on the site.
• No account system. There is nothing to register for and nothing to log in to.
• No user data persisted on any server. ViteCode has no server — the site is static HTML served from Cloudflare Pages.
• No IP-based fingerprinting. ViteCode does not run any fingerprinting script.
• No analytics provider as of v1 (no Google Analytics, no Plausible, no Umami, nothing).

Cookies and localStorage

ViteCode uses two browser-local localStorage keys. Both stay in your browser and are never transmitted anywhere:

• vitecode:consent — stores your choice from the cookies-and-ads banner (granted or denied). Read on every page load to decide whether to load the AdSense script.
• vitecode:theme — stores your light/dark theme preference (light or dark). Read on every page load to set the data-theme attribute before paint.

Clearing your browser's site data for ViteCode removes both keys. The consent banner will reappear on your next visit if vitecode:consent is missing.

Advertising (Google AdSense)

ViteCode displays Google AdSense ads on most pages to keep the site free. The AdSense script loads only after you click "Accept" on the cookies-and-ads banner. If you click "Reject", adsbygoogle.js is never loaded at all and no ad requests are made from your browser to Google.

The /tools/* generator pages are ad-free regardless of your consent choice.

When AdSense is loaded, Google's own data practices apply to the network requests Google makes from your browser. Google's policies are documented at policies.google.com/technologies/ads.

Third-party advertising

ViteCode uses Google AdSense as its sole advertising vendor. When the AdSense script is loaded (i.e., after you click "Accept"), Google and its partners may set cookies and read web beacons in your browser to serve ads based on your prior visits to ViteCode and to other sites across the web. ViteCode itself does not set any of these cookies — they originate from Google's ad-serving domains and are subject to Google's policies, not ViteCode's.

Details of how Google uses cookies and similar technologies for advertising are at google.com/policies/technologies/ads. Google's overall privacy policy is at policies.google.com/privacy.

You can opt out of personalized advertising in three ways:

• Disable Google's personalized ads at google.com/settings/ads (covers Google's own ad network).
• Opt out of the Network Advertising Initiative member networks at optout.aboutads.info (Digital Advertising Alliance / NAI consumer choice page).
• Reject the cookies-and-ads banner on ViteCode itself, in which case the AdSense script never loads in your browser at all.

What you generate stays yours

Every template file (CLAUDE.md, AGENTS.md, .cursor/rules/*.mdc, .github/copilot-instructions.md, prompts, checklists) is computed in your browser from the form selections you make. Nothing is transmitted to a ViteCode server, because there is no ViteCode server. The generated output never leaves your machine until you copy it and paste it somewhere yourself.

Third-party links

ViteCode links to documentation hosted by other parties (Anthropic, OpenAI, Cursor, GitHub, Google). Those sites have their own privacy policies; ViteCode has no control over what they do once you click through.

Children

ViteCode is a developer tool and is not directed at children under 13. The site does not knowingly collect any personal information from anyone, regardless of age.

Changes

This policy may change as the site evolves. The latest version always lives at /privacy; the "Last updated" date at the top reflects the most recent revision. Material changes (e.g., adding analytics) will be reflected here before they go live.

Contact

ViteCode is operated anonymously and does not collect contact information. Issues and questions can be raised on the project's public issue tracker if one is linked from the site footer.