Privacy
A plain explanation of what happens to a file when you upload it to DocBit's data preparation tool.
DocBit's core workflow — uploading, editing, selecting columns, searching, filtering, sorting, grouping, calculating, and exporting — runs entirely in your browser using the File API. The dataset you upload is not sent to a server for this processing, and DocBit does not currently require an account, so there's no DocBit-hosted copy of your data tied to an identity.
DocBit does not use cookies or browser storage to save your dataset, and your working session — including edits, filters, and undo/redo history — exists only in memory in your current browser tab. Closing or reloading the tab clears it; nothing is retained on our end.
Loading the DocBit website itself involves a small number of third-party requests unrelated to your data — for example, web fonts and site imagery are served from external CDNs. Like most websites, our hosting infrastructure may automatically log basic technical information (such as IP address, browser type, and request timestamps) for security and reliability purposes. These requests happen when the page loads, separately from anything you upload or edit inside the tool.
DocBit's architecture is being kept ready for optional future features, such as an account-based Workspace for saving projects across sessions. Those features don't exist yet and aren't part of the current product — if and when they launch, this page will be updated to describe exactly what changes.
If anything here is unclear, the Support page is the best place to start.