DataForge_AI

Privacy Policy

Last updated: September 2026

What We Collect

Account info (email, OAuth provider) via Clerk, the CSV files you upload, the transformations you run in them, and the credit usage that goes with them.

How Your Files Are Handled

Your CSV is read in your browser and cached locally so a refresh doesn't lose your workspace. When you run a transformation, an AI inspection, or an Insight Brief, the rows involved are sent through our serverless function to the Claude API to produce the result.

We don't keep your file as a data warehouse. What a session stores is metadata (filename, columns, the operation you ran) plus a capped snapshot of the result — up to 200 rows and 60 columns — so you can reopen or re-export it later. The full dataset stays in your browser.

How Long We Keep It

Sessions are kept for a limited window based on your plan, then automatically purged:

  • Free and trial — up to 24 hours
  • Pro — up to 30 days

Deleting a session removes it from our servers straight away. A small read-only copy of its last result (the same 200-row cap) may stay in your own browser so the deleted entry remains viewable as locked — that copy never leaves your device, and clearing your browser data removes it.

The Anonymous Trial

Trying DataForge without an account doesn't require any personal details. The server issues an HttpOnly df_session cookie to scope your trial and counts your trial credits server-side. Clearing that cookie starts a fresh trial; signing up clears it and ends the anonymous association.

Cookies & Local Storage

We use Clerk's session cookies to keep you signed in, the trial cookie above, and your browser's local storage for preferences and the local file cache. We don't use advertising or cross-site tracking cookies.

Who Processes Your Data

Running the product involves these providers, each of which only sees what its job needs:

  • Clerk — sign-in and account identity
  • Anthropic (Claude) — produces transformations, inspections and briefs
  • Supabase — stores session metadata, snapshots and brief content
  • Vercel — hosting, and the Redis-backed store for credit balances and usage records
  • Google Fonts and jsDelivr — page fonts and the PDF export library

What We Don't Do

We don't sell your data. We don't use your uploaded files to train models. We don't share your files with anyone outside the processing pipeline needed to run your transformation.

Your Rights

You can delete individual sessions from the Sessions tab, and delete your account and related data at any time from Settings → Account. Once a session is deleted or has expired, it can't be reopened for editing — that's what the locked, read-only state in the Sessions tab reflects.

Contact

Questions about this policy: dataforge.support@gmail.com