Privacy & Data Protection

Privacy Policy

Last Updated: October 2026. API Toolkit is built from the ground up as a local-first developer platform where your JSON data stays inside your browser.

1. Zero Server-Side Storage of Tool Inputs

When you use the JSON Formatter & Validator or the JSON Diff & Comparison tool, the data you type, paste, format, validate, or compare is processed 100% locally inside your web browser using standard JavaScript APIs (JSON.parse and JSON.stringify).

  • We do not transmit your JSON payloads to our backend servers.
  • We do not store, log, or cache your JSON documents in any database or server log file.
  • Closing or refreshing your browser tab immediately clears the workspace memory.

2. Server Access Logs & Technical Metadata

Like standard web servers, our hosting infrastructure records basic HTTP request metadata when you load a web page (such as the requested URL path, HTTP status code, timestamp, user-agent string, and IP address) strictly for operational security, error diagnostics, and abuse prevention. Because your JSON inputs are never sent in HTTP requests, they never appear in server access logs.

3. Cookies & Optional Advertising

All core formatting, validation, and comparison features work without registering an account or accepting tracking cookies. By default, third-party advertising scripts are disabled (ADSENSE_ENABLED=false). If Google AdSense is enabled in production to support free hosting, clearly labeled non-intrusive ad slots may load Google AdSense scripts subject to regional consent requirements, and never have access to the JSON payloads inside your editors.

4. Future Optional Accounts & Subscriptions

If optional premium features (such as saved workspaces or team collaboration) are introduced in the future, any personal account information (such as your email address and billing status) will only be collected when you explicitly register, and payment processing will be handled by PCI-compliant payment providers.

5. Security Controls

All pages are served with strict Content Security Policy (CSP) headers, XSS protections, and HTTPS transport encryption in production. If you have questions about our privacy practices or security architecture, please review our documentation or reach out via the repository contact channel.