# Privacy policy

Effective: 2026-08-17

404.directory provides contextual risk preflight for prediction-market actions and registered third-party tools, plus public web inspection and verification.

- Submitted URLs and optional expected text are used only to perform the requested tool call.
- The service does not require an account and does not use submitted data for advertising.
- The application does not intentionally persist tool inputs or results in a database. A risk preflight stores only the registered target snapshot, policy version, enumerated action, data-sensitivity class, execution mode, enumerated permissions, decision, evidence summaries, timestamps, and optional privacy-safe Agent attribution. It returns a one-time outcome token but stores only the token hash. A later outcome contains only bounded action/result enums and is labeled self-reported; it does not directly increase Trust.
- Prediction-market preflight stores only public market/rule/order-book fields, their snapshot hash, a bounded intended-action/notional/eligibility context, the decision and evidence summaries, timestamps, optional privacy-safe Agent attribution, and an optional bounded behavior outcome. It never stores wallet keys, order payloads, prompts, personal data, or free-form trading rationale.
- For Agent usage measurement the application may store activation stage, tool/provider name and version, success, finite error category, latency, result count, timestamps, safe client label, attribution source, external/internal classification, request ID, and irreversible HMAC digests of optional Agent and MCP session identifiers. Connect views and installer clicks are diagnostic only and do not count as Agent users. Raw Agent IDs, raw MCP session IDs, prompts, arguments, results, and raw IP addresses are not stored in product analytics. Infrastructure logs may retain request metadata such as timestamp, route, status, duration, request ID, and client IP for security and reliability; request bodies are not logged by the application.
- Fetching a submitted URL sends a request from 404.directory infrastructure to that public destination. The destination may process that request under its own policy.
- Do not submit private, internal, authenticated, personal, or sensitive URLs or content.

Security and privacy questions: use the project support channel associated with 404.directory.