Data handling

The engineering answer, in plain terms. The legal versions: Privacy Policy · DPA.

The one-sentence version

Your code goes to your model provider under your key for the duration of a review call; what wrokin keeps is where findings were and what happened to them — never the findings' prose, never your code.

What we store

• Finding locations — file path, line range, severity, category, and which provider/model surfaced it. This is the telemetry the public quality numbers are computed from.
• Outcomes — whether a flagged line later changed before merge (rework), 👍/👎 reactions, and /w wrong verdicts with the reason the human typed.
• Run records — role, status, timing, token counts per agent run, for your dashboard and quota metering.
• Account & installation data — GitHub account identifiers, installed repositories, plan status.

What we never store

• Your code. Diffs and file contents are read at run time, sent to your chosen provider for the call, and not persisted by us.
• Finding prose. The text of a review lives in the PR comment in your repo — where it is yours — not in our database.
• Your keys, readable. See custody below.

BYOK key custody

• Keys are AES-GCM encrypted at rest, scoped to your installation, never logged, and never displayed again after entry — the dashboard shows only a …last4 hint.
• Every model call an agent makes on your repos uses your key against your provider — your bill, your rate limits, your provider relationship. We add no token markup.
• Handing over a key is deliberately a human decision — one of the product's two human checkpoints. An agent onboarding via the setup API only holds key material a human chose to give it, on a token that expires in an hour.
• Uninstalling the GitHub App revokes access instantly; keys are deleted from the dashboard.

Where processing happens

• BYOK agents (review, security audit, triage) run on our infrastructure but spend your key — the code goes provider-ward only for the call.
• Warden (repo posture) is deterministic code: no model call, nothing leaves at all.
• Hunter/Builder (private preview) execute on your GitHub Actions runners; the managed guidance calls run on wrokin's own model keys, metered to us.

Machine-readable summary of all of this: llms.txt · capabilities.json. Questions: contact@bytesbrains.com.