Security

Website Privacy Behavior Auditor

Start with Owned website + approved privacy expectations. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.

Start with Start with your sources Try the demo

1/wkEvidence reports

FactoriesStart with your sources

IdleIllustrative run

Missing authHigh severity

Request: GET /api/invoices/inv_1042
Response: 200 OK

Evidence for the pull request200 OK

GET /api/invoices/inv_1042

Confirmed findings: 0
Draft pull requests: 0

Draft pull requestfix/invoice-session-checkmain

Require a session on GET /api/invoices/[id]

Integrations

0 integrations

Get started with Website Privacy Behavior Auditor

Pick an example, connect your tools, and review the first run.

Use template Try the demo

Set up the Website Privacy Behavior Auditor agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Compare observable browser requests and consent behavior with stated expectations. Investigate discrepancies, propose repairs, and recheck the browser-visible behavior after changes. 1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project. 2. List the first-party workflow templates. If `website-privacy-behavior-auditor` is listed, instantiate it with `--path.slug website-privacy-behavior-auditor` and start the run; otherwise create a project from this template at /new?template=website-privacy-behavior-auditor&preset=trial. 3. Share the run id, follow the run until it finishes, and summarize its outputs and changes. Ask me before spending FTAI or changing anything outside this repository.

Launch from Claude Code, Codex, Cursor, and other agents.

Related solutions

Integrations

Get started with Website Privacy Behavior Auditor