Security
Security and data handling
Evaluations involve source code, live applications and student work. We built the platform to keep as little of it as possible, for as short a time as possible, and never to use it for anything except your evaluation.
Your data never trains models
We do not use customer content (code, URLs, files, rubrics, results) to train or fine-tune any model. Our AI model providers process requests under enterprise API terms that prohibit training on customer data.
Source code is not kept
Code you submit for review is placed in a workspace created for a single job. When the job finishes, successfully or not, the workspace and every file in it is deleted.
Every job is isolated
Browser sessions run in a dedicated, sandboxed container that is torn down after the job. No cookies, storage or files carry over between jobs or between customers.
Encrypted in transit and at rest
All traffic to and from Evals.sh uses TLS. Stored data is encrypted at rest by our cloud infrastructure using industry-standard AES-256 encryption.
Lifecycle
The life of an evaluation
Everything needed to run the job exists only for the length of the job. What remains afterwards is the report you asked for.
| Data | What happens to it |
|---|---|
| Submitted source code | Deleted when the job ends |
| Browser session, cookies, local storage | Deleted when the job ends |
| Model prompts and responses | Never used for training by us or our model providers |
| Scores, rationale and step logs | Kept in your account (90-day retention) |
| Evidence screenshots | Kept with the report (90-day retention) |
| Account details | Kept while your account is active |
You can request deletion of any report, or your whole account, at any time by emailing [email protected].
Controls
Platform and infrastructure controls
Enterprise-grade infrastructure
Evals.sh runs on major cloud infrastructure whose data centres are independently audited against standards including ISO/IEC 27001 and SOC 2. Physical security, redundancy and network protections are inherited from those providers.
Authentication
Accounts use email and password sign-in. Passwords are hashed with bcrypt and never stored in plain text. Sessions use short-lived tokens with HTTP-only refresh cookies.
Access to customer data
Every request is authenticated and scoped to the account that owns the data. Report share links are only created when you explicitly generate one.
Agent safety
The browser agent only visits the URLs you provide and acts only on your instructions. We recommend dedicated test accounts and test payment methods for any flow the agent signs into.
Responsible disclosure
Found a vulnerability?
Please report it privately to [email protected] with steps to reproduce. We acknowledge reports promptly, keep you updated while we fix the issue, and won't pursue action against good-faith research that avoids privacy violations and service disruption.