Skip to content

How Data Analysis App protects your data.

You are handing over a file you did not want to share with anyone. Here is exactly what happens to it, in the order it happens.

1. Access

Every project belongs to exactly one account. Access is enforced in the database itself through row-level security, not only in the application — so a bug in our code cannot expose another customer's project, because the database refuses the query regardless of what the application asks for.

Uploaded files are held in private storage. They are never publicly addressable, and links to them are signed and short-lived.

2. Storage

Files are encrypted in transit and at rest. Source files, the cleaned data derived from them, and generated outputs are stored separately, so a share link to a report never grants access to the spreadsheet behind it.

We keep the file you uploaded unchanged. Cleaning and repair produce a new copy; the original is never overwritten.

3. Processing

Analysis runs in isolated environments with no network access and no credentials. Code generated during an analysis cannot reach the internet, cannot read another project, and has no access to our infrastructure.

Content inside your files is treated as data, never as instructions. A spreadsheet cell containing text that looks like a command to our system is analysed as text — it cannot direct the analysis or cause anything to be sent anywhere.

4. What language models see

Models see the structure of your data, not the contents of it: column names, types, statistical profiles, and masked samples. Identifying a column as email addresses does not require sending the addresses.

Where a value must be shown to a model, sensitive fields are masked first.

5. Human access

People at Data Analysis App do not browse customer projects. There are exactly two circumstances in which a person sees your data: you purchase Human Verification, or you explicitly grant access when contacting support about a specific project.

That support checkbox is unchecked by default and scoped to the one project. Every grant is recorded and expires.

6. Retention

Source files are kept for 30 days by default, and you can shorten that or delete them at any point from your account. A project you never claimed with an account is removed after 7 days.

Deleting a project removes it from your account immediately and purges the underlying objects within 30 days.

7. Deletion

Deleting your account removes your projects, uploaded files, generated outputs, saved recipes and profile. It runs as a job rather than a flag: objects are removed from storage, then the records, then the account itself.

Some transaction records are retained where we are legally required to keep them. The privacy policy states which, and why.

8. Who else touches it

Running Data Analysis App means using other companies. These are the ones that can touch your data, and the privacy policy describes what each does.

Payments
Stripe
Email
a transactional email provider, for sign-in codes and receipts
Analytics
Google Analytics and Vercel Web Analytics
Error monitoring
Sentry

Processing takes place in the United States.

9. Reporting an issue

Found a vulnerability? Tell us through the contact form, choosing Security. We acknowledge within two business days.

We will not pursue legal action against anyone who reports a genuine issue in good faith and gives us reasonable time to fix it before disclosing it.