Reference
The processing boundary, stated precisely
Local processing does not mean the website is invisible to the internet. It means the public application files travel to your browser, then your dataset is parsed, profiled, transformed, and exported on your device.
What the server receives
Cloudflare serves the public site files and therefore handles standard web-request information needed to deliver them, such as the requested URL, IP address, user agent, and timing data. Those requests do not contain the contents of a dataset opened or pasted into the workbench.
What stays in the browser
File contents, pasted data, inferred schemas, quality profiles, detected PII, repairs, filters, and transformed working copies stay in browser memory. Downloads are created only when you choose an export action.
Local storage and third parties
The site stores only the selected light or dark theme in browser local storage. It does not use account cookies, third-party scripts, advertising pixels, or browser analytics. Its Content Security Policy blocks application network connections after the assets load.
When to use a stricter environment
Browser software still runs on your device and within your organization’s security environment. For highly regulated or exceptionally sensitive data, follow your organization’s approved tooling, device, retention, and review requirements.
Does Parse The Data upload files or pasted text?
No. The dataset is processed inside the browser tab, and the application has no upload endpoint or runtime connection for sending it to the site server.
Does the website receive any information at all?
Yes. Like any website, the delivery infrastructure receives ordinary requests for public site assets. Dataset contents are not included in those requests.
What persists after I close the tab?
The dataset and working copy are not intentionally persisted by the application. Only the light or dark theme preference is stored locally; files you explicitly download remain wherever your browser saves them.