CodeNeat

Privacy Policy

Last updated: March 2026

Your Data Never Leaves Your Browser

CodeNeat is designed with privacy as a core principle. All data processing — formatting, encoding, decoding, hashing, and validation — happens entirely in your browser using client-side JavaScript. We never send your code or data to any server.

AI Feature (Explain with AI)

When you use the “Explain with AI” feature, your input data is sent to Anthropic’s API for analysis. This data is processed in real-time and is not stored by CodeNeat. Please refer to Anthropic’s privacy policy for their data handling practices.

What We Collect

  • Analytics: We use Google Analytics to collect anonymous usage data (page views, tool usage counts). This helps us improve our tools. No personally identifiable information is collected.
  • Session Cookie: If you activate a Pro license, we store a session cookie ("codeneat-session") to maintain your Pro status. This cookie contains an encrypted token and no personal data.
  • No Tracking Cookies: We only use localStorage for your preferences (e.g., dark mode, recent tools).

Pro Subscriptions & Payments

Pro subscriptions are processed through Lemon Squeezy, our payment provider. When you purchase a Pro plan, Lemon Squeezy collects your email address and payment information. CodeNeat does not store your payment details. Please refer to Lemon Squeezy’s privacy policy for their data handling practices.

Advertising

Free users may see advertisements served by Google AdSense. Google may use cookies to serve ads based on your browsing history. Pro users do not see any advertisements. Learn more about Google’s advertising practices at Google’s Privacy & Terms.

Third-Party Services

  • Google Analytics — anonymous usage statistics
  • Google AdSense — advertising (free tier)
  • Anthropic — AI analysis (Explain with AI feature)
  • Lemon Squeezy — payment processing (Pro subscriptions)
  • Upstash — rate limiting and caching (no personal data stored)
  • Vercel — hosting provider

Contact

Questions about this policy? Open an issue on our GitHub repository.