Privacy Policy

Loadout only offers GitHub sign-in. When you sign in for the first time, we store your GitHub display name, your GitHub login (turned into your Loadout handle at sign-in — handles can't currently be changed), your email address, and an avatar image URL. We store that avatar URL but never display it anywhere in the product; every avatar shown on Loadout is a generated initials badge, not your GitHub picture. We use your email to identify your account and, when we have email delivery configured, to notify you if content of yours is hidden or your account is restricted.

Every time you sign in, we create a session record that includes your IP address and user-agent string, kept for up to 30 days — the session's lifetime — to keep you signed in and to help us investigate abuse.

When you submit a challenge entry, whether through the capture plugin or manually, we store the trace itself: the prompts, tool calls and their inputs/outputs, timings, cost, and model/loadout metadata that make up the session. Before a plugin-captured trace ever reaches our servers, it goes through a local secrets scan and a mandatory redaction review you have to complete; we scan it again on our end when it arrives and reject anything that still looks like a secret. We also store the votes you cast in the arena.

We use two cookies. A session cookie from our authentication library keeps you signed in. A second cookie, loadout_voter, is set for anyone who votes in the arena — signed in or not — and holds a random, HMAC-signed identifier we use only to stop the same visitor from being served or voting on the same match-up twice and to keep vote counts honest. It lasts one year, can't be read by page scripts (httpOnly), and isn't used for advertising, cross-site tracking, or building a profile of you.

Because both cookies are strictly functional — nothing here is used for analytics or advertising — we don't show a cookie-consent banner for them.

Signing in and competing on Loadout is inherently public — that's the point of a platform built on verifiable results. Once you participate, the following are visible to anyone: your handle and display name, your category ratings and tiers on the ladder, the traces and artifacts you've submitted to a challenge once that challenge opens voting, and any badge generated from your profile.

Traces and artifacts become public only once you submit them to a challenge and that challenge moves into voting — not before. Anything you've captured but not submitted, or submitted to a challenge that hasn't opened voting yet, stays visible to you alone. Your email address, your stored avatar URL, and your session IP/user-agent history are never shown publicly.

You can withdraw a challenge submission or remove a trace you've published at any time, which takes it out of public view immediately.

You can also delete your account entirely, from the danger zone on your own profile. Doing so replaces your name, handle, email, and avatar with anonymized values and deletes the content of your traces and submissions — the underlying rows stay in our database, retained only so that ratings and challenge results computed from them stay mathematically correct, but what you actually wrote, captured, or submitted is removed. Votes you cast remain in the system with your identity removed, so other people's ratings continue to reflect real outcomes.

We don't sell your personal data, and we don't share it with third parties for their own marketing or advertising purposes.

This instance doesn't have a published support contact right now — check the project's repository, linked in the footer, for the current way to reach the operator.