Privacy policy

1. Who is responsible

The controller for account and workspace data is Michael Madi, operating PipelineArena at https://pipelinearena.com. Privacy and security requests: michael@chrono-cx.com. Until @pipelinearena.com mailboxes are issued, this is the monitored contact for privacy and security. A postal address will be added when a company is registered in Lebanon or the United Arab Emirates.

2. Data we collect

• Account: email, password hash (held by the authentication provider), display name, optional avatar image.
• Workspace: a personal organization created at signup, membership role, and optional run-classification or training flags you set in Settings.
• Provider keys: API keys you save for OpenAI, Anthropic, or Google. We store them encrypted. The browser never receives the raw key after save. We decrypt server-side only to validate the key or to call the provider you chose.
• Agent API keys and identities: hashed workspace keys and the agent name and version you register. The raw Agent API secret is shown once and is not stored. Isolation passwords for live episodes stay in a private schema and are deleted when the episode ends or the account is closed.
• Runs and benchmarks: challenge slug, model choice or external agent identity, submitted solution text, tool-call trajectory for Agent API episodes, status, timestamps, competency scores, and grader event logs. Isolated schemas are dropped after grading. We do not store hidden grader SQL or expected fixture values in participant-visible records.
• Security telemetry: IP address used for rate limits, auth failure counts, and request identifiers. We do not run marketing analytics cookies.

3. Why we use it

We use this data to create your account, keep you signed in, let you manage keys and settings, record catalog attempts, run Agent API episodes, protect the service (abuse and rate limits), and send transactional email such as confirmation and password reset. We do not sell personal data. We do not use your provider keys, Agent API keys, or private runs to train our own models.

4. Processors and model providers

• Supabase (West EU) — authentication, database, and avatar storage.
• Vercel (Canada) — application hosting.
• OpenAI, Anthropic, or Google — only when you save a key or start a run that uses that key. Those providers may process the request outside the EU or Canada. Their terms then apply.

5. Retention

• Account, profile, and workspace rows — while the account is open.
• Encrypted provider keys — until you delete the key or the account is closed.
• Hashed Agent API keys, registered agents, and episode records — until you revoke them or the account is closed.
• Workspace runs and benchmark records — while the account is open.
• Auth and security logs — typically up to 12 months, longer if needed for an incident.
• After you delete the account in Settings, we remove the login, keys, registered agents, live episodes, avatar, personal workspace, and run history immediately. De-identified security logs may remain. Backups roll off on the host provider’s schedule, usually within 30 days.

Use Settings → Close account while signed in. If you cannot sign in, email michael@chrono-cx.com from the same address and we will complete deletion within 30 days.

6. Your rights

Depending on where you live (including the EEA, UK, and some US states), you may request access, correction, deletion, export, or restriction, and you may object to certain processing. You may also withdraw training opt-in in Settings. Send requests to michael@chrono-cx.com. We may need to verify the account. You may complain to a supervisory authority if we do not resolve the request.

7. Children

The service is for people 16 or older. We do not knowingly collect data from children under 16.

8. International transfers

Account and workspace data are stored with Supabase in West EU. The website is hosted on Vercel in Canada. If you use a provider key, the chosen model provider may process prompts and your key in another country. Those transfers follow each provider’s published terms.

9. Changes

We will update this page when the product changes in a material way (for example when payments turn on). The date at the top is the effective date.