Private Local Data Analysis in the Browser

SQL for Files is built around client-side processing. Files are loaded into DuckDB WASM in your browser, SQL runs locally, and query results are rendered locally in the page.

• Added CSV, JSON, and Parquet file contents.
• Tables created inside the browser DuckDB session.
• Query text and query history stored by the app.
• Saved table data when you choose local persistence.

When persistence is used, data is stored in browser storage such as IndexedDB. That is useful for continuing later, but it also means anyone with access to the same browser profile may be able to access saved work.

Use export/import backups when you want to move work between browsers, and clear browser storage if you do not want data retained on the device.

• Use a trusted device and browser profile.
• Avoid shared computers for confidential files.
• Clear local data after one-off sensitive analysis.
• Review exports before sending them elsewhere.
• Prefer aggregated results when sharing outputs with others.

Local processing reduces upload risk, but it does not replace device security, browser profile hygiene, file access controls, or organizational data handling policies. Treat the browser as part of your local workstation security boundary.