Privacy

What we hold

For an account: your email address, a scrypt hash of your password (never the password), and a name if you give one. For a session: a SHA-256 hash of the session cookie, your browser's user-agent string, and timestamps.

For a sheet: the rows you upload, the questions you ask, and for each answer the full probability distribution, the confidence value and which model version produced it. We keep a count of row-questions used, per workspace, for billing.

Who sees your rows

To answer a question we send row content to TypeSafe's Jev model. We send only the source columns you ticked for that question — a column you unticked is never transmitted. Requests currently route through Netlify's AI Gateway.

We do not sell your data, and we do not use it to train anything.

The answer cache

Answers are cached so you are not billed twice for the same judgment. The cache is keyed by a SHA-256 hash of the row content, the question and the model version. The row content itself is not stored in the cache and cannot be recovered from it; only the hash and the resulting answer are. This cache is shared across accounts, which is what makes an identical row cost nothing the second time.

The public demo

The demo on the home page and at /try creates no account and stores no sheet. To rate limit it we store a salted SHA-256 hash of your IP address and a count of rows judged. The raw IP address is not stored. Those counters are deleted after two days.

Cookies

One cookie, column_session, which keeps you signed in. It is HTTP-only and same-site. There is no analytics, advertising or third-party tracking on this site.

Payments

Card details are handled entirely by Stripe and never reach our servers. We store the Stripe customer and subscription identifiers so we know which plan a workspace is on.

Deleting things

Deleting a sheet removes its rows, columns and answers. Signing out destroys that session. For deletion of an entire account, email us and we will remove it.