Privacy
No Sneaking Around
We do not skim, scrape, steal, look over your shoulder during a trig exam, or sneak off and speak secrets. All data is processed locally in your browser.
Local Processing Promise
During normal WorkBench use, source files, previews, edits, diagnostics, graphics handling, exports, receipts, and save-back choices stay in the browser session. The static WorkBench runtime does not have a Data WorkBench backend to upload your files to.
- No analytics.
- No hidden uploads.
- No server-side file processing.
- No live connector calls.
- No hidden external writes.
- No secret reuse of your source contents.
External Libraries
External libraries are vetted before use and reviewed as the WorkBench changes. This list should change whenever the runtime dependency list changes. We are grateful to have quality work to build on.
| Library | Used For | Privacy Link |
|---|---|---|
| SheetJS Community Edition |
XLS, XLSX, XLSM, and XLSB workbook intake, sheet inspection, and
XLSX export-copy paths. It is lazy-loaded when workbook
functionality is requested. WorkBench may request SheetJS code
from the configured CDN first, then use the vendored local
fallback at apps/web/vendor/sheetjs/.
|
SheetJS privacy policy |
Loading library code is different from uploading your file contents. Data WorkBench does not send workbook contents, graphics, source text, edits, diagnostics, exports, or receipts to SheetJS.
If This Changes
If future ads, connectors, cloud features, or additional third-party libraries change the privacy boundary, the product should say so in plain language before that behavior is enabled. No quiet switcheroo.