Privacy.

We keep collection small, and this page lists all of it. Reading the site needs no account and sets nothing beyond the analytics below.

If you create a rider account

When you join the Guild, we store a small record in our database (Cloudflare D1): the handle and display name you choose, an optional bio, the email address or GitHub identity you signed in with, the flights you submit, the vouches you give and receive, your rank and the events that changed it, any device keys you register for the CLI, and a moderation note if we ever act on a report about your account. Your handle, published flights, rank, and vouches are public by design — a track record only works in the open. Your email is never shown. If you signed in with GitHub, your GitHub username is shown on your profile unless you switch it off in your profile settings; it is re-checked at each GitHub sign-in and hidden after 180 days without one.

You sign in with GitHub or with an email magic link that works once and expires in fifteen minutes; GitHub sign-in asks GitHub, with your permission, for your email address so we can reach you about your account. We keep you signed in with a cookie, ar_session, which is HttpOnly and not readable by scripts; the database stores only a hash of it, never the raw value. A second small cookie, ar_signedin, is readable by the page only to switch the header into its signed-in state — it is a yes/no flag, carries no identifier, and does no tracking.

The agentriders CLI

If you use the agentriders command-line tool to verify a flight, it reads your Claude Code session log on your own machine and uploads a metadata-only record — counts, model names, timestamps, a one-way session hash, and eval signals. Your prompts, your code, file contents, file paths, and commands never leave your machine. The tool prints the exact record before it sends anything, and the full detail is in the tool's PRIVACY document. It signs with a device key you can revoke at any time from your account.

The Flight Log corpus (public GitHub activity)

The Flight Log corpus lists public pull requests authored by AI coding agents, built from public GitHub data: the AIDev dataset, GH Archive, and the GitHub API — never scraped pages, never anything private. About the person who opened a pull request we store the GitHub login, the numeric account id, the avatar URL and, once the account has a flight on the record, the public profile fields GitHub shows on their profile: display name, bio, company, website, social links and the first line of a profile README, read through the API every 30 days and shown with the date they were read. No emails, no location, no activity beyond the pull requests themselves. Pages show computed numbers, short verbatim excerpts with links, and the name and profile text as attribution next to a person's own public work.

Anyone can opt out by signing in with GitHub: every flight by the account and its author page leave the site, the profile fields are deleted in the same step, and the pages answer 410. Repository owners can have a whole repository excluded the same way, within 48 hours. The corpus is not affiliated with GitHub, with any repository, or with any agent's maker.

Everything else

The site runs Google Analytics to count visits and see which pages get read; it sets cookies and sends usage data to Google (how Google uses that data). Block it and the site works exactly the same. There are no session recorders and no ad pixels.

Your animation preference is saved on your device so the site remembers when you pause visual motion. It is not used for tracking.

If you subscribe to the Flight Log, your email address goes to the newsletter provider and is used only to send it. Every issue has an unsubscribe link, and it works.

The site is served by Cloudflare, which processes the traffic data any host processes — IP addresses and request logs — to serve and protect the site.

Deleting your data

To be removed from the newsletter list, unsubscribe from any issue. To delete your rider account and the data tied to it — and to have your published flights taken down from the public record — email us at [email protected]. Published flights also live in a public Git repository; removing an account does not erase Git history, so say the word and we remove the files there too.

AgentRiders is operated by Permanent Ventures Inc.