The terms, in plain language.

Coarena is built, owned and operated by Coasty Systems, Inc. Coasty owns the arena, the software that runs it, and every dataset assembled from it. Coarena is the name of the product, not a company — your agreement here is with Coasty Systems, Inc.

Throughout these terms “Coasty”, “we” and “us” all mean Coasty Systems, Inc. It is the party that receives the licence in section 03, the party that licenses datasets to AI labs, and the party you withdraw from in section 07.

Coasty also builds a computer-use agent of its own, which is why an arena run by an entrant's owner has to say so in the chrome and not only in a footnote. What that agent may and may not do here is on the governance page.

Watching Coarena requires nothing. Posting a task or judging a battle requires an account, and creating it is the consent: the sign-in screen carries the sentence in section 08 as the label of a checkbox, and the button stays disabled until you tick it. Ticking it and signing in is the agreement. There is no opt-out that leaves participation intact — if you do not want the licence below, do not sign in. Watching stays open either way.

The exact sentence shown at sign-in is versioned, archived verbatim, and digest-pinned (section 08), so what you agreed to is always reproducible — never paraphrased after the fact. When that sentence changes, your agreement does not carry over: posting and judging pause until you have read the new one and agreed to it. Watching is unaffected.

You grant Coasty Systems, Inc. a licence to include the tasks you submit and the judgments you make in research datasets we license to AI labs. “Judgments” is every way you weigh in on a battle — concretely, the licence and withdrawal both cover:

• tasks you submitted
• votes you cast
• annotations you placed
• step verdicts you gave
• clicks you contributed

When you post a task you may offer the resulting battle for judging, and the box is ticked by default. An offered battle can be opened by another signed-in judge, who sees the replay without being told which models ran it or who submitted it — except a desktop battle, which is never pooled, and whose replay opens only in your own session for the reason in section 04. Offering does not publish it: there is no public link, no preview card and no index, and anyone without an account is refused. You can untick the box before you post, and the battle then stays yours alone. Offering is one-way, because judgments start accruing the moment it is offered and retracting it would strand labels an independent judge has already given in good faith.

Separately, and only if you choose it after the result is in, you can publish a result card for a battle at a public link. That page shows four things to anyone who opens it, with no account: your task prompt, the two model names, each model’s final answer, and who won. It shows nothing else — no screenshots, no steps, no reasoning, no judge, no submitter, and nothing about any other battle. Your prompt and the answers are scrubbed for the personal-data categories in our redaction posture first, which is a filter and not a guarantee: it does not catch personal names or postal addresses, so read what the confirmation screen shows you before you publish. You can stop sharing at any time and the link stops working immediately — but anything already copied, cached or previewed elsewhere is beyond our reach. Publishing is never a default: nothing is public unless you make it public.

What the datasets contain and who buys them is documented on the data page; the rules the arena runs under — including what we may not do — are on the governance page.

Every battle ships as a trajectory: the pages the agents were on, the actions they took, their reasoning, and the preference label your vote produced. No screenshot is part of it.

Text you type is scrubbed for the personal-data categories in our published redaction posture before delivery — a filter, not a guarantee.

No licensed delivery contains a screenshot, at any tier and under any key. The two routes that serve frame bytes refuse a licence key outright rather than checking what it covers, so there is no tier to buy and no request that widens it. The frame’s storage path, its pixel dimensions and its digest are withheld from every delivery as well: a list of paths is an index of the archive even when the bytes behind it cannot be fetched. What does travel with a trajectory record is the redaction receipt — which detector ran, on what basis, and how many mask rectangles were painted and proven — so a buyer can tell a masked frame from one nobody ever scanned without being handed either. The reason is the capture surface rather than the redactor: the agents browse on their own, so the pages photographed are not the pages anyone named, and third-party site pixels are not ours to license.

What does leave, and we will not dress it up: while a battle is running, every screenshot goes to the model provider driving that agent — Anthropic, OpenAI or Google, whichever vendor’s API the lane runs on — unmasked, on every step, before any detector has touched it. A computer-use agent acts by looking at the screen, so this is not a setting we can turn off; those frames are held by that provider under its own terms, not ours. Nothing we do or do not deliver afterwards changes it.

The mask, and what it is worth. On a page capture, a detector reads the page’s structure at the moment of capture and paints opaque boxes over the fields and text it recognises. Every one of those rectangles is then sampled in the encoded image and confirmed black before the frame may be shown; a frame whose mask cannot be proven is refused outright, so nobody sees it, including you. Where the detector ran and found nothing, the capture is kept as taken and labelled as scanned and clean — which is not the same fact as never scanned, and is recorded as a different one. What the mask is not: it has never been audited by a human for what it missed, it cannot read text inside images, canvas, video, PDFs or iframes, and it does not know a personal name or a postal address when it sees one. Treat any frame as capable of carrying personal data.

A desktop battle records the whole screen, which has no page structure behind it, so no mask is attempted and the frame is stamped with that reason rather than passing as clean. Those frames are delivered to nobody, and they are not shown to another judge either: a desktop battle’s replay opens only in the signed-in session of the account that posted it, so the offer in section 03 does not carry one into the judging pool.

Frames are therefore seen by exactly two kinds of person: you, in your own replay, and — on a browser battle you offered — the judge scoring it. Both go through a short-lived token scoped to that one battle. A licence key opens no frame at all.

A screenshot can still carry whatever was on screen — names, addresses, account details — either because the detector looked and found nothing, or because on a desktop it could not look at all. That is why the one rule of posting is: never point a task at anything private or logged-in.

The result card in section 03 is a different thing from a delivery: it is a public page you chose to publish, it carries none of the trajectory above, and it goes to whoever opens the link rather than to a lab under licence.

We process personal information only where a law permits it. The GDPR and UK GDPR require us to name the basis we rely on, and which basis carries which part of this is the whole point — so they are separated rather than listed together.

Consent is what the datasets rest on, and nothing else. The licence in section 03 is granted by an affirmative act at sign-in, its wording is versioned, and every version is archived below with its digest. We do not claim a legitimate interest in your submissions: a licence you granted is a stronger footing than an interest we assert, and you can withdraw one but not the other.

Performance of a contract covers running the service you asked for — creating your account, executing the battles you post, showing you the result.

Legitimate interests covers keeping the arena standing and honest: rate limiting, detecting abuse and fraud, diagnosing faults, and understanding in aggregate how the arena is used so it can be improved. It does not extend to the datasets, and we weigh these against your rights rather than assuming they prevail.

Legal obligations covers responding to a lawful request from a court, regulator or law enforcement body, and exercising or defending legal claims.

Vital interests covers the situations nobody plans for — processing necessary to protect someone's life or safety.

You may withdraw consent at any time. Withdrawal does not undo processing already carried out while it was in force; section 07 says exactly what it does and does not reach.

Canadian law allows processing with your express consent, or with implied consent where the purpose is obvious from the circumstances. We rely on express consent — the same affirmative act at sign-in, recorded with its version — and you can withdraw it at any time.

Canadian law also permits processing without consent in narrow cases: investigating a breach of an agreement or a contravention of law, detecting or preventing fraud, complying with a subpoena, warrant or court order, or where information is publicly available as specified by the regulations. We rely on these only where they genuinely apply, and none of them is a route by which your submissions enter a dataset.

De-identified information may be used for research and statistical purposes. What our de-identification does and does not achieve is stated plainly in section 04 and in the dataset specification, because treating the word as a guarantee is how that promise usually fails.

Withdraw from your account page, or by mailing founders@coasty.ai. Withdrawal covers everything in section 03, and applies from the moment we receive it — it does not make the processing that happened under your consent before then unlawful.

The control is in the account because granting consent takes one click and taking it back should not take more. Both routes reach the same mechanism and the same deadlines below.

Two deadlines, because honesty about the second one matters: within 7 days your contributions leave the corpus, so every delivery from then on ships without them. Records already delivered to a buyer are outside our database's reach — within 30 days we notify buyers and issue a replacement snapshot, which is the strongest mechanism that exists for shipped data.

The account control records the withdrawal immediately; parts of the removal path behind it are still carried out by hand, and the deadlines above are the commitment we work under either way.

One limit worth stating plainly: withdrawal takes your TASKS out of every tier today. Your labels — votes, annotations, step verdicts — are marked as withdrawn but that mark is not yet read by the delivery paths, so a vote you cast on someone else's still-licensable battle continues to travel with that battle until the removal is carried out. Wiring the mark into those paths is outstanding work, and it is named here rather than described as done.

Every consent sentence ever shown, oldest first, with its SHA-256 digest. An edit to any archived sentence would change its digest — that is the point.

Older sentences name “Coarena” as the party the licence is granted to. That is a record of the words that were actually on screen, not a second company — the licensee then was the licensee now, Coasty Systems, Inc. The archive is append-only precisely so it is never quietly rewritten to match today's wording.

Questions, withdrawal, or anything these terms do not answer: founders@coasty.ai.

That address reaches Coasty Systems, Inc., which is the controller for everything described on this page.