Privacy Policy

What this Service is built for

json. offers free developer utilities such as JSON formatting, validation, minifying, tree viewing, Base64 conversion, and JWT payload inspection. Most tool processing runs in your browser so your editor contents are not sent to our servers for those operations.

Do not paste passwords, API keys, private keys, tokens, or other secrets into any tool or form.

Information we may collect

• Contact form data — if you send a message, we store your name, email address, and message so we can reply.
• Basic usage signals — we may record aggregated page-view counts (path + day) for our admin dashboard, and standard server or host logs such as IP address, user agent, and request timing for security and reliability.
• Preference cookies — small values for theme (light/dark) and cookie-consent choice. These are not used to build advertising profiles by us.
• Admin account data — if you are an authorized operator, we store your admin email and a hashed password for signing into the private admin area.

Tool editor text (JSON, Base64, JWT strings, etc.) is processed locally in the browser for public tools and is not intentionally uploaded as part of those tool actions.

How we use data

We use the limited data above to:

• Respond to contact requests
• Operate, secure, and improve the Service
• Understand which pages are used (aggregate counts)
• Remember UI preferences you choose
• Authenticate admin users

We do not sell your personal information. We do not use public tool editor contents as a dataset for training models.

Cookies and similar storage

We use browser storage/cookies for essential preferences (theme and consent). If you enable advertising later, third-party networks such as Google AdSense may set their own cookies under their policies. You can clear or block cookies in your browser; some preferences may reset.

Advertising

Ad regions on the site are controlled from our admin panel. When an ad unit is enabled and a valid network snippet is configured on a live domain, that network may collect data according to its own terms. Review Google Advertising Privacy & Terms if Google ads are shown. On local development we only show layout placeholders — real ads are not served from localhost.

Third-party services

Hosting, databases, and deployment providers (for example Vercel and Supabase, when used) may process technical data needed to run the Service under their own privacy terms. Open-source libraries we ship in the browser retain their respective licenses; using the Service does not transfer ownership of those libraries.

Retention

Contact messages are kept until we handle them or you ask for removal. Aggregate page-view rows may be kept for operational reporting. Admin credentials remain while the account is active. Hosting logs follow the retention practices of our providers.

Your choices

To request deletion or correction of a contact submission, use the Contact page and include enough detail for us to find the record (email used and approximate date). You may also clear local preferences from your browser.

Security

We use HTTPS, security headers, rate limits on sensitive endpoints, sandboxed/controlled ad rendering where applicable, and hashed admin passwords. No online service can guarantee perfect security; please avoid sharing sensitive material with the tools.

Children

The Service is aimed at general developer use and is not directed at children under 13. We do not knowingly collect personal information from children.

Policy updates

We may revise this page when the product or our practices change. The "Last updated" date at the top will change when we do. Continued use after an update means you accept the revised policy.

Contact

Questions about privacy for json.? Reach us through the Contact page. Related legal terms are in our Terms & Conditions.