Back to App

Legal & Privacy

Privacy Policy

CSV AI Analyzer is designed with privacy as a core principle. We believe your data is yours and should stay that way.

What we DON'T store:

  • Your CSV files or any data you upload
  • Your API keys on our servers
  • Analysis results or chat history
  • Any personally identifiable information

How Your Data is Processed

All data processing happens 100% in your browser. Here's how it works:

  1. You upload a CSV file → it stays in your browser's memory
  2. When you request AI analysis → only a summary is sent to the AI provider
  3. Your API key stays in your browser (see below) → it is sent only to the AI provider you chose, never to us
  4. When you close the browser tab → all data is gone

Third-Party Services

When you use AI features, your browser sends requests directly to the AI provider you selected in the API settings (OpenAI, Anthropic, Google, Mistral, another compatible provider, or your own custom endpoint). Depending on the feature, a request contains:

  • Summary, charts and suggested questions: column names and types, per-column statistics, a few example values and the first 5 rows
  • Anomaly detection: the same summary plus the first 50 rows
  • Chat: the summary, your question and your recent questions and answers
  • Your API key, in the request headers

Long cell values are cut to 200 characters. These requests are processed under your provider's own terms and privacy policy; review its data retention rules before analyzing sensitive data. With a custom endpoint on your own machine, nothing leaves it.

API Key Security

This site uses no cookies. What it stores in your browser:

  • Your API key, never in clear text: it is encrypted (AES-GCM) with a browser key that cannot be exported, kept in IndexedDB. The encrypted key stays in sessionStorage for the current tab only, erased when you close it. If you tick "Remember on this device", it goes to IndexedDB instead and stays until you press Clear or clear site data
  • Preferences, in localStorage: provider, model, response language, custom endpoint and theme
  • The key is never sent to this site: it only travels, over HTTPS, to the AI provider you selected. A custom endpoint must use HTTPS, or plain HTTP on this computer (Ollama, LM Studio)
  • A dump of the browser's storage only shows encrypted bytes, but code running in this page, or a malicious browser extension, can still have the browser decrypt the key: avoid "Remember" on shared computers

Contact

If you have any questions about our privacy practices, please open an issue on our GitHub repository.

Last updated: October 2026