Privacy Policy
Learn how DevToolkit protects your data privacy, operates 100% offline client-side tool executions, and manages third-party advertising cookies for Google AdSense.
Data Handling Practices Summary
| Data Category | Examples & Payloads | Processing Location | Storage & Retention | Sharing & Third-Party Access |
|---|---|---|---|---|
| User Code & Tool Inputs | Source code, JSON payloads, JWTs, AES keys, passwords, PDF documents | 100% Local Browser Memory (RAM / WASM) | Transient (Cleared upon tab close or cache clear) | Zero server uploads. Never transmitted or shared. |
| Server Diagnostics | IP address, user-agent string, page request URLs, access timestamps | Edge Web Server Infrastructure | Temporary security audit logs | Internal security logs only. Never sold or rented. |
| Advertising Cookies (AdSense) | Ad interaction cookies, DoubleClick IDs, interest category cookies | Google Advertising Network | Controlled by browser preferences & Google Ads settings | Programmatic ad delivery via Google AdSense. |
| Local Preferences | Dark/Light theme selection, sidebar state, recent tool history | Client-side localStorage | Persistent locally on your device until manually cleared | First-party local storage only. Never transmitted. |
100% Private Guarantee
Your code, passwords, JWT tokens, and PDF documents are never sent over the network. All tool computations happen inside your web browser.
1. 100% Client-Side Processing & Zero Uploads
DevToolkit is architected with a strict privacy-first model. All developer tools—including JSON formatters, base64 encoders, hash generators, regex testers, and PDF processors—execute exclusively inside your local browser memory (JavaScript/WebAssembly). None of your source code, configuration files, text payloads, certificates, or uploaded PDF documents are ever transmitted to or stored on remote servers.
2. Server Logs & Automatic Diagnostics
When you access our website, standard web server logs may automatically record basic diagnostic metadata, such as your Internet Protocol (IP) address, user-agent header (browser type and operating system), requesting URL, and access timestamps. This data is used strictly for network security, abuse prevention, and infrastructure stability.
3. Google AdSense & Third-Party Advertising Cookies
We use Google AdSense to serve programmatic web advertisements to support our free developer tools and engineering blog. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to our website or other websites on the Internet. Google's use of advertising cookies (such as the DoubleClick cookie) enables it and its partners to serve contextually relevant and personalized ads to users.
4. Opting Out of Personalized Advertising
You can opt out of personalized advertising by Google at any time by visiting Google Ads Settings (https://www.google.com/settings/ads). Alternatively, you can opt out of third-party vendor cookies for personalized advertising by visiting the Network Advertising Initiative (NAI) opt-out portal at www.aboutads.info or Your Online Choices at www.youronlinechoices.com.
5. Cookie Control & Local Storage Management
Cookies are small text files stored on your device by your web browser. You can configure your browser settings to block all cookies, accept only first-party cookies, or delete stored cookies whenever you wish. Note that blocking essential cookies will not impact the core functionality of DevToolkit client-side tools.
6. Privacy Rights (GDPR & CCPA/CPRA Compliance)
Under regional privacy regulations including the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA/CPRA), users have rights to request access to personal data, request deletion, or restrict processing. DevToolkit does not sell, rent, or trade personal user information to third parties.
7. Links to Third-Party Sites
Our blog posts and tool documentation may contain links to external websites or reference documentation. DevToolkit is not responsible for the content, security practices, or privacy policies of third-party sites. We encourage users to review the privacy policies of any third-party websites they visit.
8. Privacy Questions & Policy Updates
We may periodically update this Privacy Policy to reflect technical enhancements or regulatory changes. Material updates will be indicated by the "Last modified" date. If you have questions about this policy, please reach out via our Contact Us page.