Your file is decoded and parsed in the browser tab, its rows are discarded once aggregates are computed, and nothing is transmitted anywhere. There is no account, no server component, and no runtime network request.
During profiling
The file is read from the local file input, decoded, and parsed in the tab. Rows exist in memory only long enough to build the column aggregates and a SHA-256 digest of the contents, then they are released. Nothing writes rows to storage.
What persists locally
The browser's IndexedDB holds the project: headers, structural aggregates, digests, file metadata, committed mappings, consumer policies, findings, dispositions, notes, and the event history. It does not hold source rows or raw example values. Clearing site data for this origin deletes all of it, and there is no copy anywhere else.
Worked example
After loading the bundled sample, storage holds the string quantity, the fact that the column profiled as integer with a maximum observed length of one, and a digest of the whole file. It does not hold 2, 1, 4, or 3. That is the entire distinction: structure is kept, contents are not.
What leaves
Only what you explicitly export, and only to your own download folder: a checkpoint JSON, individual CSV registers, or the passive review packet. Each contains structural evidence rather than source rows. You control who receives those files.
Method and limits
This boundary is about the application, not about your device. A downloaded export is an ordinary file with ordinary exposure, and a shared machine, a synced download folder, or a browser profile that other people use are all outside the tool's control. Column names themselves can be sensitive in some organisations; a header such as settlement_account is stored as text like any other.
Do this in the app
Open the workbench and check the Settings view: it names the storage backend in use and offers a full local reset that clears the project from this browser.
Related reading
- Security modelThe threat model behind these choices.
- Offline and account freeWhat a browser-local desk hands back to you.
- Review packetWhat an export does and does not contain.
Website requests and support
Cloudflare serves the website and receives ordinary connection information, such as your IP address and requested page, to deliver and protect it. The workbench does not upload your imported files or saved projects. If you email support, your message and email address are received so I can respond. Avoid sending confidential project data.