Privacy Policy
Last updated: October 2026 • Plain language, zero legal jargon
When you paste or upload JSON, JWT tokens, certificates, passwords, database dumps, or sensitive code into DevToolKit, none of that data is ever sent to our servers. Every single operation — from formatting, minification, YAML conversion, to cryptographic SHA/MD5 hashing — executes entirely inside your device's web browser via JavaScript.
1. Data We Do Not Collect
- Your Input Payloads: We do not log, inspect, store, or transmit your input or output strings.
- Personal Identifiable Information (PII): We do not require accounts, logins, email addresses, or phone numbers.
- Sensitive Tokens: Bearer tokens, private keys, and JWT signatures remain strictly in your browser session memory.
2. Local Browser Storage
We use your browser's local storage (localStorage) strictly for storing non-sensitive user preferences:
- Your active color theme preference (dark vs. light).
- Editor layout preferences (such as auto-indent size).
You can clear these preferences at any time by clearing your browser cache or site storage.
3. Third-Party Scripts & Sponsors
To keep our servers operational and free for developers worldwide, we partner with developer-centric privacy-respecting networks and direct sponsors:
- EthicalAds: We may load ads from EthicalAds, a developer ad network that does not track users across websites, does not use retargeting cookies, and targets ads solely based on page context (e.g., developer tools).
- Affiliate Links & Direct Sponsors: Some tool pages show curated recommendations (e.g., Supabase, DigitalOcean, Railway). If you sign up through these links, we may receive a referral commission at no additional cost to you.
- Third-Party Isolation: Third-party ad scripts are strictly prohibited from accessing editor state or input memory.
4. Questions & Security Inquiries
If you have questions about our privacy model or wish to inspect our code verification process, visit our Contact Page or check our Architecture & About Page.