Privacy

Privacy policy.

CSVita is a local-first CSV workbench. Your file stays on your computer, and the app has no account, no cloud service and no telemetry.

Last updated

  • × No account. Nothing to sign in to.
  • × No cloud. Your CSV is never uploaded.
  • × No telemetry. No analytics, crash reports or usage tracking.
  • × No advertising. No trackers and no profiling.

CSVita does not have a server, an account system, analytics, or a crash-reporting service. It does not send your file, its path, its contents, or your usage anywhere. Everything it remembers is stored on the same Windows account that runs the app, and you can delete it.

What CSVita handles

  • Your CSV or TSV. CSVita opens the file where it already lives, reads it to draw the grid, and writes back to that same file when you save. It never imports your rows into a database of its own.
  • Optional sidecar metadata. Column types, widths, hidden columns, the tab label and select options are written to filename.csv.meta.json beside the CSV. It is a display and schema file, not a copy of the row data, but it can contain column names, select option labels and colour choices.
  • App state. csvita.sqlite remembers recent file paths, open tabs and per-file view state: search text, filter values, sort rules, grouping and colour rules. Colour rules can include column names and the cell values you coloured. dialogs.json remembers the last folder used by the Open and Save dialogs.
  • Save scratch files. A save writes a temporary .csvita-*.tmp file beside the CSV, then renames it into place. A crash can leave one behind; it is safe to delete when CSVita is not running.
  • Temporary query files. When a large sort or filter outgrows memory, DuckDB may spill to a scratch folder under your local app data or temp directory. These are query scratch files, not an application database, and they can contain data from the query; they can be deleted when CSVita is closed.
  • Clipboard and exports. Copying rows writes them to the Windows clipboard. Export writes a new file where you choose. Both happen only when you ask.

What leaves your computer

Nothing is sent to the publisher. CSVita has no account, no cloud sync, no telemetry, no analytics, no advertising and no crash reporter. Its file features work offline.

Two things are outside that statement. A link in a cell is handed to Windows only when you click it, and then to your default browser or mail app; CSVita accepts only http, https and mailto links, and the destination site handles the request under its own policy. Installing from the Microsoft Store, receiving updates, or running Windows may involve Microsoft services and diagnostics under Microsoft's privacy statement.

If the Microsoft WebView2 runtime is missing, the NSIS installer may download it from Microsoft during installation. That request belongs to the installer and Microsoft, not to your use of a CSV.

Where it is stored

Local files Local only
Your data
Your CSV or TSV — the path you opened
filename.csv.meta.json — beside the CSV, hidden on Windows
CSVita's state
%APPDATA%\CSVita\csvita.sqlite — recent files, tabs, view state, colour rules
%APPDATA%\CSVita\dialogs.json — last folder used
%LOCALAPPDATA%\csvita\duckdb-tmp — temporary query spill files

Paths are typical for a Windows account. If a folder cannot be written, CSVita keeps working without that state.

How long it stays, and how to delete it

CSVita keeps this state until you delete it. None of it is needed to open a CSV: deleting the state folder costs you convenience and never changes your file.

  1. Clear the recent list in CSVita if you only want to forget file paths.
  2. Close CSVita, then delete %APPDATA%\CSVita to remove its state.
  3. Delete %LOCALAPPDATA%\csvita\duckdb-tmp or %TEMP%\csvita-duckdb-tmp if either exists.
  4. Delete any .csvita-*.tmp files left beside a CSV after a crash.
  5. Delete any filename.csv.meta.json files you no longer want. They are hidden on Windows.
  6. Uninstall CSVita from Windows Settings if you no longer need the app.

Your CSV files are not part of the app's state folder, and uninstalling CSVita does not remove the CSV files you opened.

Security

CSVita relies on Windows file permissions. It does not encrypt your CSV or its own state files, so anyone who can sign in as you or read those folders can read them. Keep your Windows account protected and use disk encryption if that matters for your data.

CSVita treats cell contents as untrusted text. Values are rendered as text, not executed, and links are opened only after the scheme is checked.

This website

This site does not set cookies, run analytics or profile visitors. It is served by Cloudflare Workers, which processes standard request data such as an IP address and user agent to deliver pages and protect the service under Cloudflare's privacy policy. The page loads only its own CSS, JavaScript and icon files; there are no third-party fonts, scripts or trackers.

Changes and contact

If this policy changes, the date at the top changes with it. Material changes will be stated here before they apply.

Questions about this policy or CSVita's data handling: use the support contact on the CSVita Microsoft Store listing.

Open the Microsoft Store listing