Privacy Policy & Data Handling Disclosure
Last updated: 2026-11-10. Local-first execution and transparent storage controls.
1. Zero Server-Side Storage of Tool Inputs
All prompts, token volume parameters, environment variable templates, and JSON payloads entered into our utilities (LLM Token Cost Ledger, MCP Config Builder, llms.txt Generator, and JSON Schema Converter) are processed exclusively within your web browser's local memory. We never transmit or store your tool inputs on any backend server.
2. Google Analytics 4 (GA4), Cookies & Advertising Compliance
We use Google Analytics 4 (gtag.js with anonymize_ip: true) and privacy-preserving edge metrics to understand aggregate page views and tool interaction events (such as copy actions and model catalog syncs) without ever logging prompt contents or configuration secrets. When analytics or third-party display advertising (such as Google AdSense) are active on the site:
- Google Analytics uses first-party cookies to report anonymous traffic and usage trends; you can opt out at any time using the Google Analytics Opt-out Browser Add-on.
- Third-party vendors, including Google, may use cookies to serve ads based on a user's prior visits to this website or other websites.
- Users may opt out of personalized advertising by visiting Google Ads Settings.
- UI preferences and interaction counters reside solely in your browser's
localStorageand can be purged below.
3. Local Browser Storage Controls
For questions regarding benchmark accuracy or privacy practices, refer to our Methodology page. Use the control below to clear all local browser state: