Please use GitHub's private vulnerability reporting flow from the repository's Security tab. Do not include credentials, API keys, private telemetry, prompts, model output, or exploit details in a public issue.

Include the affected version or commit, the impact, reproduction steps, and any suggested mitigation. Reports will be assessed as promptly as maintainers are available. A fix and coordinated disclosure plan will be prepared before public details are posted when the issue is confirmed.

If private vulnerability reporting is not enabled for the repository, open a public issue containing only a request for a private reporting channel. Do not include vulnerability details in that issue.

Until AgentLens publishes its first stable release, security fixes target the latest commit on the default branch. After releases begin, the latest release will receive fixes; older pre-release snapshots are unsupported.

AgentLens telemetry can contain prompts, model output, tool inputs, errors, and other sensitive application data. Operators are responsible for minimizing and redacting collected data, restricting access to the collector, using HTTPS, and setting an appropriate retention policy.

• Project API keys are bearer capabilities. Store them in a secret manager and revoke them if exposure is suspected.
• The Supabase service-role key is server-only and must never be included in a browser bundle or SDK configuration.
• Production session and provisioning secrets must be strong, stable values.
• Do not rely on repository history rewriting as credential revocation. Rotate a leaked credential first.

See docs/database.md for the database isolation and RLS posture. This policy describes the intended controls; it is not a claim of formal security certification.

Collection, minimization, retention, and incident-response guidance for agent telemetry is documented in docs/privacy.md.