Privacy Policy
Last Updated: October 31, 2025
Summary (TL;DR)
- Zero data collection - Everything stays in your browser
 - No servers - Client-side only application
 - No tracking - No analytics, cookies, or monitoring
 - No accounts - Use anonymously, no registration
 - Optional history - Stored locally in IndexedDB (your device only)
 
Your code is your business. We never see it, store it, or share it.
Overview
CodeClean is a privacy-first, client-side-only application designed to protect your data and respect your privacy. This policy describes our data practices and your privacy rights.
Core Privacy Principles
1. Local-First Architecture
What We Collect: Nothing.
Where Your Data Lives: Entirely in your browser.
CodeClean operates as a 100% client-side application. This means:
- All code formatting, validation, and processing happens in your browser
 - Your code never leaves your device
 - We have no servers to store or process your code
 - There is no backend that could access your data
 - Your sensitive code (API keys, private files, etc.) stays completely private
 
2. Browser Storage (Optional)
What We Store: Only data you explicitly create through tool usage.
Where It's Stored: Your browser's IndexedDB (device-specific, not synced).
What's Stored:
- Tool History: Recent formatting operations you've performed
 - User Preferences: Theme (dark/light mode), settings
 - Timestamps: When you used tools (for history sorting)
 
Important Notes:
- History is device-specific and cannot be synced across browsers or devices
 - You can clear history anytime using the "Clear All" button in the History panel
 - All history is deleted when you clear your browser data
 - Maximum 20 history items per tool (oldest automatically removed)
 
3. No Third-Party Data Sharing
Who Gets Your Data: Nobody.
CodeClean does NOT:
- Send your code to any third-party services
 - Use analytics or tracking scripts
 - Share data with advertisers
 - Integrate with marketing platforms
 - Track your behavior or usage patterns
 - Store logs on servers
 - Use cookies for tracking
 
Data Flows
Tool Usage Flow
- You paste/upload code → Stays in browser memory
 - You click "Format" → Processed by browser JavaScript
 - You see results → Displayed from browser memory
 - You click "Copy" → Copied to your clipboard (browser API)
 - Optional: Save to history → Stored in IndexedDB (local only)
 - You close the page → Browser memory cleared
 
At no point does your code leave your device.
Share Button Flow
When you click "Share Results":
- URL generation: Tool state is encoded into a URL query parameter
 - Clipboard copy: The URL is copied to your clipboard (browser API)
 - No server upload: The URL itself contains the encoded data
 - Recipient restoration: When someone opens the URL, their browser decodes the data locally
 
Important: Share URLs can be long. Anyone with the URL can view the encoded code. Don't share URLs containing sensitive data publicly.
Your Privacy Rights
Right to Access
All your data is visible in:
- History Panel on each tool page (shows all saved history)
 - Browser DevTools → Application → IndexedDB → 
codeclean-history 
Right to Delete
You can delete your data anytime:
- Clear specific history item: Click delete icon on history item
 - Clear all history for a tool: Click "Clear All" in History panel
 - Clear all app data: Clear browser data (Ctrl+Shift+Del)
 
Security
Since CodeClean runs entirely in your browser, your data security depends on:
- Your device security: Keep your device and browser updated
 - Browser security: Use a modern, updated browser (Chrome, Firefox, Safari, Edge)
 - HTTPS connection: CodeClean is served over HTTPS (encrypted connection)
 
Because CodeClean is client-side only, we cannot see your code, log your activity, recover lost data, or be involved in data breaches (there's no server to breach).
Contact
For privacy questions or concerns, please use the contact information provided on our About page.
Transparency Commitment
CodeClean is built with transparency in mind. You can:
- Verify no server-side data collection occurs (all processing is client-side)
 - Audit data storage (IndexedDB only, visible in browser DevTools)
 - Inspect network requests (none to our servers for code processing)
 - Review our privacy-first architecture
 
We believe in privacy through transparency.