How divisio handles your data

When you upload a CSV or Excel file, it's sent to our server for parsing only. The file is read into memory, converted to JSON, and returned to your browser — then immediately discarded. Nothing is written to disk, saved to a database, or stored anywhere on our end.

All your data lives in your browser tab. Close the tab (or refresh the page), and it's gone. We couldn't retrieve it even if we wanted to.

We collect anonymous interaction metadata to understand how the app is used and improve it. This includes:

• Page views and button clicks
• File metadata: row count and column count
• Algorithm choices and clustering parameters
• Feature usage: exports, filter operations, elbow method

We do not track your actual data values, column names, filter contents, or any of the numbers inside your files.

We don't use third-party cookies. The only things stored in your browser are:

• A random session ID (divisio_session_id) in localStorage — used to group analytics events within a session
• An authentication token if you sign in (managed by Supabase Auth)

You can clear these anytime via your browser's developer tools or storage settings.

Pro users can save clustering configurations — algorithm choice, number of clusters, selected columns, and filter rules. These are parameter presets only and contain none of your actual dataset content.

Saved configs are stored in our database (Supabase) tied to your account, and you can delete them at any time.