How it works

Data and privacy

What is sent

Only the redacted evidence packet you approve in a preview. It contains selected report fields, trace events, and short source excerpts around the failure. It never contains full files, full diffs, your repository, or image pixels; screenshots and videos are described by size and dimensions only. Run npx kwikqa analyze --local to see the summary KwikQA would build, without sending anything.

Where it goes

Plan	Path
Free, Pro, Max	Your machine → KwikQA service → OpenRouter → the model named in the preview
Bring your own key	Your machine → OpenRouter → your chosen model

The KwikQA service forwards the payload unchanged. It stores account, plan, and usage records and, for each request, its kind, model, status, token counts, cost, and a hash of the payload. It never stores the evidence, your source, or the model's answer. Security lists how long each record is kept.

What stays on your machine

Location	Contents
`.kwikqa/runs/`	Run records: diagnoses, proposals, outcomes, and reason codes.
`.kwikqa/repairs/`	Repair sessions and attempts.
`.kwikqa/validation-artifacts/`	Output of validation runs.
User config directory	Your CLI sign-in token, with owner-only permissions.

Your controls

Decline any request at its preview; nothing is sent.
Use --local to keep analysis entirely on your machine.
Use the bring-your-own-key plan to keep evidence off KwikQA's servers.
Export or delete your account data from Account.

The privacy policy has the full details.