Privacy Policy
DevToolKit is built on a fundamental principle: we collect absolutely ZERO user data. No tracking, no cookies, no analytics, no accounts. Your privacy is not a feature — it's our architecture.
Last updated: August 4, 2026
Our Core Promise
DevToolKit does NOT collect, store, transmit, sell, or share any personal information, usage data, file contents, tool inputs, tool outputs, or any other form of user data. We have no database of users, no user profiles, and no tracking systems.
Our Six Zero Commitments
Every claim below is a verifiable technical fact, not a marketing promise.
Zero Server Uploads
Your files and data are NEVER uploaded to any server. All processing happens exclusively inside your browser using JavaScript, Web Workers, and WebAssembly.
Zero Tracking & Analytics
We do NOT use Google Analytics, Facebook Pixel, Hotjar, or any other tracking scripts. No user behavior is monitored, recorded, or analyzed.
Zero Cookies
DevToolKit does NOT set any cookies — no session cookies, no persistent cookies, no third-party cookies. Your only locally stored preference is theme (light/dark) in localStorage.
Zero Fingerprinting
We do NOT collect browser fingerprints, device identifiers, IP addresses, geolocation, or any form of unique user identification.
Zero Account Required
No sign-up, no login, no email collection. You use all tools completely anonymously — we have no concept of "users" in our system.
Zero Data Retention
Since no data ever reaches our servers, there is nothing to store, nothing to delete, and nothing to breach. Your data exists ONLY in your browser's memory and is discarded when you close the tab.
Technical Details
How our privacy architecture works under the hood.
How does client-side processing work?
When you use a DevToolKit tool (e.g., format JSON, merge PDFs, generate hashes), all computation is performed by JavaScript running directly in your browser tab. Your files are read into browser memory using the File API, processed using client-side libraries (pdf-lib, sql-formatter, etc.), and the result is generated locally. The entire pipeline — input → processing → output — happens on YOUR device.
What about Web Workers and WebAssembly (WASM)?
For heavy operations like PDF processing, we use Web Workers (background browser threads) and WebAssembly modules. These run inside your browser's sandbox — they have NO network access and cannot communicate with any external server. They are simply a performance optimization to keep the UI responsive.
Do any tools send data to a server?
Some tools marked as "Backend" (such as Image Compressor and Resize Image) use our processing API for operations that require server-side libraries (e.g., Pillow for advanced image processing). In these cases, your files are sent over an encrypted HTTPS connection, processed immediately in memory, and the result is returned. Files are NEVER stored on disk and are immediately purged from server memory after processing. No logs of file content are kept.
What data is stored in localStorage?
The ONLY data stored locally is your theme preference ("light" or "dark"). This is a single string value stored in your browser's localStorage. No tool inputs, outputs, or usage history is persisted. You can clear this at any time via your browser settings.
Do you use any Content Delivery Networks (CDNs)?
Our application is served via standard web hosting. Standard HTTP access logs (IP address, timestamp, requested URL) may be recorded by our hosting provider for security and uptime monitoring purposes. These logs do NOT contain any user-submitted data, file contents, or tool inputs.
What We Do NOT Collect
Open Source Transparency
Don't take our word for it — verify it yourself. DevToolKit is open source. You can inspect every line of code to confirm that no data is collected, no network requests are made from tool processing functions, and no tracking scripts are included.
Use your browser's DevTools (F12 → Network tab) while using any tool to confirm zero outbound network requests during processing.
Children's Privacy
Since DevToolKit does not collect ANY personal data from ANY user, we are inherently compliant with COPPA (Children's Online Privacy Protection Act) and equivalent global regulations. There is no data to protect because no data is collected.
GDPR, CCPA & International Compliance
DevToolKit's zero-collection architecture means we are inherently compliant with:
- GDPR (EU General Data Protection Regulation) — No personal data is processed.
- CCPA (California Consumer Privacy Act) — No personal information is sold or shared.
- LGPD (Brazil), PIPA (South Korea), PDPA (Thailand/Singapore) — No personal data is collected in any jurisdiction.
Since no user data exists in our systems, there is nothing to access, rectify, delete, or port. GDPR rights (Articles 15–20) are satisfied by design.
Changes to This Policy
If we ever modify this privacy policy, the updated version will be posted on this page with a revised "Last updated" date. We will never change our core commitment to zero data collection without prominently notifying users on the homepage.
Contact Us
If you have any questions about this privacy policy or our zero-collection practices, please contact us: