This policy explains how Parsing Tools (parsing.tools), operated by Parsing Tools, handles personal data. It is written to meet the GDPR, UK GDPR and Brazil's LGPD.
1. What you type stays on your device
The tools on this site run in your browser. Values you enter are not sent to or stored on our servers. When the site remembers preferences or drafts it uses your browser's local storage, which you can clear at any time.
2. Consent (Google Consent Mode v2)
Until you choose, all measurement and advertising signals are denied by default (ad_storage, ad_user_data, ad_personalization, analytics_storage). Your choice is stored locally and can be changed anytime in (also in the footer). This site currently uses nothing that requires consent, so no cookie notice is shown.
3. Audience measurement
If we enable audience measurement, we will use Cloudflare Web Analytics, which measures visits in aggregate, without cookies and without identifying you.
4. Advertising
This site does not show ads at the moment. If we start showing Google AdSense ads, they will respect your consent choice and this policy will be updated first.
5. Hosting and technical logs
The site is served by Cloudflare, which processes technical connection data (IP address, browser, time) to deliver pages and prevent abuse. We do not use it to identify you.
6. Your rights
You may request access, correction or deletion of personal data and withdraw consent at any time. Since we do not store what you type, clearing your browser storage removes it. Contact: the contact channel listed on this site.
7. Site-specific information
Text you paste, type or load from a file is processed by JavaScript in your browser tab (large inputs and regular expressions run in a Web Worker in the same tab). No tool on this site sends that text to a server, and there is no "save online" feature.
To survive a reload, each tool keeps its current input in sessionStorage, which your browser clears when you close the tab. The JWT decoder, the hash generator and the paste box on the home page are excluded: tokens, secrets and text to hash are kept in memory only.
"Copy link" encodes the input into the part of the URL after #. Browsers do not send that part to the server; anyone you give the link to can read the content, so do not share links that contain secrets.
The server sends a Content-Security-Policy whose connect-src is 'self', so scripts on these pages cannot open connections to any other host. The exact policy is shown on the "Verify privacy" page.