Privacy
No Sneaking Around
We do not skim, scrape, steal, look over your shoulder during a trig exam, or sneak off and speak secrets. WorkBench source 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.
SQL Lab2 Map and Table Probe Map views are rendered locally from the SQL Lab2 database, import metadata, and review state in this browser tab. Table names, field names, relationship candidates, join drafts, query text, and map layout data are not sent to a graph service, map service, AI service, backend database, or external schema processor.
Map layout preferences may be stored in this browser under
ana.sqlLab2.schemaMapLayout.v1 so the local schema view can
remember where you placed things.
- No hidden uploads.
- No server-side file processing.
- No live connector calls.
- No hidden external writes.
- Analytics events must not contain source contents.
- Analytics events must not contain schema-map table names, field names, relationship maps, query text, or layout data.
- No secret reuse of your source contents.
Site Analytics
Data WorkBench uses analytics on approved site pages, including WorkBench and SQL Lab, to understand traffic, usage, and page performance. Analytics is for the site itself. It is not a license to inspect, upload, sell, or reuse source files, pasted data, edits, diagnostics, exports, receipts, credentials, or file contents.
| Provider | Used For | Privacy / Product Link |
|---|---|---|
| Netlify Web Analytics | Counts visits and basic traffic from Netlify server logs. It helps us see which pages are being used and whether the site is reachable. | How Netlify Web Analytics works |
| Netlify Real User Monitoring | Measures page performance, including Web Vitals, so we can catch slow or broken pages. | Netlify Real User Monitoring |
| Google Analytics | Measures traffic and engagement on approved site pages, including WorkBench and SQL Lab. It helps us understand which screens people use, where traffic comes from, and whether the site is working well. It does not receive source files, pasted data, SQL text, table values, schema-map table names, field names, relationship maps, query text, diagnostics, exports, receipts, credentials, or file contents. Advertising features remain off. | How Google uses information from sites or apps that use its services |
Google Analytics uses cookies or similar browser storage only after analytics consent is accepted. Page tracking is sent without query strings so pasted payloads or source-like URL parameters do not become analytics data. Visitors can also reduce or block analytics measurement with browser privacy controls or Google Analytics opt-out tools.
Cookies And Consent
Google Analytics does not load until analytics consent is accepted. The consent banner gives Accept and Reject choices with the same prominence. You can change that choice below.
Advertising storage, ad personalization, remarketing, demographics, interests reports, and Google Signals are off for this site.
Analytics Settings
Google Analytics waits for your choice. Your analytics consent setting is stored locally in this browser and does not require an account.
Google Analytics setting is loading.
International Visitors
Data WorkBench is operated from the United States. Analytics providers may process analytics data in the United States or other countries where they operate. Google may process analytics data on our behalf under its service terms and policies.
California Privacy
We do not sell your WorkBench source contents. We do not use Google Analytics to receive source files, pasted data, SQL text, table values, diagnostics, exports, receipts, credentials, or file contents.
Privacy Questions
For privacy questions, email support@anaworkbench.com.
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.
SQL Lab2 Map is first-party interface code. It does not add a separate third-party graph library, map vendor, AI service, database service, or external schema processor.
| 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 |
| sql.js | SQL Lab local `.sql`, `.db`, `.sqlite`, and `.sqlite3` artifact review. It is loaded from a pinned CDN path when SQL Lab needs browser-local SQLite behavior. It does not add a backend database connection, credentials, or file upload path. | No separate privacy link listed here; see Credits for the runtime boundary. |
Loading library code is different from uploading your file contents. Data WorkBench does not send workbook contents, SQL artifacts, graphics, source text, schema-map layout data, table names, field names, relationship maps, edits, diagnostics, exports, or receipts to SheetJS or sql.js.
If This Changes
If future ads, connectors, cloud features, analytics providers, or additional third-party libraries change the privacy boundary, the product will say so here in plain language before that behavior is enabled. No quiet switcheroo.