Security & your data

What Harpoon stores#

• Anonymous analyses: nothing is persisted — the report is computed, returned, and gone.
• Saved analyses: the engine's result (findings, score, timings) plus the raw HAR, gzip-compressed in object storage.
• Deployments can auto-delete raw HARs after a set age (HAR_RETENTION_DAYS) while keeping the analysis; plan retention and the free tier's three-analysis cap prune whole runs — see plans.

What the AI model ever sees#

One rule governs every model call: the deterministic engine discovers findings, the model only explains them. It receives the engine's findings, score, and page metadata — never the raw HAR, bodies, headers, cookies, or free-typed user text. The API key exists only server-side behind a single gateway with per-organization rate limits, a monthly spend cap, prompt redaction, and an audit log. Details in the AI report guide.

How secrets are handled#

• Capture credentials and SCM tokens are sealed with AES-256-GCM at rest and are write-only — no API returns them, no page displays them, no log prints them. You can only overwrite or delete them.
• Captured HARs are redacted before storage, with a leak guard that scans capture output for vault values.
• Request logs scrub Authorization and Cookie headers and mask share-link tokens; report bodies and HAR content are never logged.

The capture browser#

The browser that captures pages visits URLs users choose, so it's treated as hostile territory: it runs as an unprivileged user with Chromium's sandbox on, is refused access to localhost/private/metadata addresses on every request hop, and is capped in count and memory so it can't exhaust the host.

Deleting your data#

Deleting an analysis removes its stored HAR, report, exports, and any public link pointing at it. For full organization/account deletion, email support via the docs hub contact — a self-serve deletion flow is on the roadmap.