Privacy
Last updated April 7, 2026
Your files stay on your machine
The desktop app reads spreadsheets directly from your local disk. Files are never uploaded to our servers, mirrored to any cloud service, or copied outside of your folder. There is no sync layer, no staging bucket, and no backup we control.
What the agent sends to model providers
When you ask the agent a question, it sends column schemas, row counts, and query results to the model provider you configured (Anthropic, OpenAI, Google, or a local Ollama instance). It does not send your full rows or raw cell data. Every tool call the agent makes is visible in the chat panel so you can audit exactly what was transmitted.
API keys
Your model API key is stored in your operating system’s native keychain (macOS Keychain). It is never sent to TableFuse servers. The key is used exclusively for direct requests from your machine to your chosen model provider.
Web preview
The browser-based preview requires uploading files to our server for the duration of your session. Uploaded files are held in memory and deleted when the session ends. We do not persist, index, or train on uploaded data. The web preview uses a TableFuse-managed API key, so you do not need to provide your own.
Analytics
The landing page uses Vercel Analytics, which collects anonymous page-view data (no cookies, no personal identifiers). The desktop app does not phone home or collect usage telemetry.
Contact
Questions about privacy? Open an issue on GitHub.