Your data is yours.

What we collect

• Account data — the email and credentials you use to sign in, and your API keys (stored hashed, never in plaintext).
• Datasets you upload — the classifier inputs, model outputs, scores, slices, and any gold labels you submit. This is the data the experimentation loop runs on.
• Operational metadata — run status, token usage for billing, and structured request logs (tenant, route, status, duration). We never log API keys, password hashes, or raw upload bytes.

How we use it

Solely to operate the service: to run your propose→evaluate→ certify loop, to score predictions you request, to enforce quotas, and to bill usage. We do not sell data, and we do not train shared models on one customer's data for another customer's benefit.

Isolation

Each tenant's datasets, runs, and labels are stored under a per-tenant namespace and scoped by tenant on every read. API access is bearer-token authenticated; a token only ever resolves to its own tenant.

Retention & deletion

You can delete a dataset at any time, and we honour deletion requests for your uploaded data and labels on the schedule you set. When you close an account we remove your data within a bounded window. Audit records that make a result reproducible (pre-registration digests, gold-snapshot hashes, run manifests) are retained without the underlying raw text where you have asked for the raw data to be removed.

Sub-processors

We use a small number of infrastructure providers (hosting, database, object storage) and an LLM provider to run the platform models. We will keep an up-to-date list available on request and notify design partners of material changes under their agreement.

Your choices

You can export your audit artifacts, request a copy or deletion of your data, and opt into a private deployment (see Security) where your data never leaves your environment.

Contact

Privacy questions and data requests: kodycoppock@gmail.com.