Last updated: May 2026
Short version: PrivBatch collects nothing. No analytics, no cookies, no tracking. Your files never leave your computer. Processing happens entirely inside your browser.
Nothing. PrivBatch does not collect, store, or transmit any personal data, file content, usage analytics, or telemetry of any kind. There are no cookies, no tracking pixels, no third-party analytics scripts.
All file conversion, formatting, and parsing happens entirely inside your web browser using client-side JavaScript. Your files are:
This is not a marketing claim - it is an architectural fact. The tool pages contain no upload mechanisms, no server-side code that receives your files, and no API endpoints that handle your data. Your browser does all the work locally.
When you enter your license key, your browser contacts Gumroad's verification API (api.gumroad.com). Gumroad returns information about your purchase: product name, purchase email, purchaser ID, sale timestamp, and order number. We store only your license key and email - the email is used to display "Licensed to:" on generated PDFs as proof of authenticity. We do not retain any other fields from the response or transmit this information anywhere. PrivBatch has no servers that store user data of any kind.
PrivBatch loads the following resources from third-party CDNs to power its tools. These requests are made by your browser and are subject to those providers' own privacy policies:
Each provider sees your IP address and which resource you requested - standard for any web request. None receive your file data or form input.
PrivBatch sets no cookies. We use browser localStorage for the following:
privbatch_license: your license key and the purchase email returned by Gumroad. The email is shown on generated PDFs as "Licensed to:" proof of authenticity. Only present after you enter a valid license key.privbatch_tier: a mirror of your tier (free / pro / business) for fast UI gating.privbatch_limit_hits: a small integer counter tracking how many times you have hit the Free tier batch limit, so an upgrade prompt can appear after the third hit. Resets to zero when dismissed.pb_theme: your dark / light mode preference.pb_prove_it: whether you have enabled Prove It mode, so it stays on across tool pages.pb_bundle_banner_seen: whether you have seen the Bundle Mode introduction (so we do not show it twice).pb_history: a list of your last 5 tool operations (tool name, timestamp, byte count) used to populate the "Recent" menu in tool toolbars. Contains no file content, no form values, no personal data.pb_fixer_day, pb_fixer_count: anonymous daily quota counters for the Free tier File Detective limit. Reset on the next calendar day.That is the complete list. All keys are prefixed privbatch_ or pb_ for easy identification in DevTools > Application > Local Storage. We never store your data, your files, your form input, or any personal information beyond your purchase email.
We also use sessionStorage for transient state during your visit:
privbatch_profile: your loaded profile data (company name, controller details) used to prefill GDPR Suite forms.privbatch_job: job-naming state for the current GDPR Pack workflow.privbatch_srcmap: source-identity mapping used by the audit-log chain feature.privbatch_bundle_active: whether Bundle Mode is currently active in this tab.privbatch_bundle_count: file count mirror used by the beforeunload warning.privbatch_last_input: the last input filename, used by the source-chain feature in the audit log.All sessionStorage clears when you close the tab. The complete list is visible in DevTools > Application > Session Storage - all keys are prefixed privbatch_ or pb_.
PrivBatch processes no personal data on any server and transmits no user data to any third party (license key validation excepted). As a result, you do not need a Data Processing Agreement to use PrivBatch's tools - there is no processor relationship to govern.
Pro Business includes the GDPR Documentation Suite: a Data Processing Agreement template generator, Consent Receipt records (Article 7 GDPR), and Article 30 Record of Processing Activities generation. Plus Bundle Mode for queuing multi-tool work into one audit-ready ZIP. All generated locally in your browser - your data never reaches our servers because we do not have servers that handle your data.
Pro Business users can also generate a per-conversion compliance certificate from the four batch converter tools (CSV ⇔ JSON, XML ⇔ JSON, Excel → JSON, SQL → JSON). The certificate is a local record showing the conversion happened entirely in your browser - useful as evidence that no data was transmitted during processing. This is separate from the GDPR Documentation Suite described above, which generates downstream legal documents (Data Processing Agreements, Consent Receipts, Records of Processing Activities).