Harness Dojo runs this site. This page says what we collect when you use it, why, and how long we keep it. We do not sell your data and we do not show ads.
What we collect
- GitHub account. When you sign in, GitHub gives us your numeric user ID, your login name and your avatar URL. We ask for the
read:userscope only. We do not get your email, your repositories or your password. - Code you run. The harness source you Run or Submit, the problem and configuration it ran against, and the results.
- Traces. Every model request and response your harness makes, with token counts, latency, cost and errors.
- IP address. Used for rate limits and daily Submit limits, including for Runs without an account.
- Cookies. A session cookie when signed in, an anonymous identity cookie so you can reopen your own Runs, a security token that blocks forged requests, and a short-lived cookie that protects the sign-in flow. They are HttpOnly and used only for this site. We do not use tracking or advertising cookies.
- Browser storage. Your editor draft and the ID of your latest execution stay in your browser's local storage so a refresh does not lose your work.
- Usage. Which pages you open, how long you are actively on them (a tab that is in the background or idle does not count), where you arrived from, and when you Run or Submit and how it scored. It is linked to your account when you are signed in and to your anonymous identity cookie when you are not. It stays on our own server. We do not use a third-party analytics service.
- Operational logs. Server logs with request status, execution and task IDs. Credentials are removed before logging.
Who else sees it
- The model provider (OpenAI). The prompts your harness builds are sent to the pinned model to produce responses. Do not put secrets or personal data in your harness.
- GitHub handles sign-in.
- Hosting. The website is served by Vercel. The API and database run on our own server.
Your executions are visible to you only. We may disclose data if the law requires it.
How long we keep it
- Executions, source and traces: 30 days after they finish.
- Usage records: 13 months.
- Database backups: 14 days.
- Sessions: expire after 30 days, or when you sign out.
- Account record (GitHub ID, login, avatar): until you ask us to delete it.
- Totals such as daily spend and usage counters, and minimal records that stop an old request from being replayed, are kept after the content they refer to is deleted.
Your choices
You can use Run without an account. You can sign out at any time. To get a copy of your data, or to delete your account and executions, email sai@turilabs.in. You can also revoke Harness Dojo's access in your GitHub settings under Applications.
Changes
If this page changes, we update the effective date above. See also the terms.