Privacy Policy

Last updated: August 1, 2026

Agent Interface (agentinterface.app) is a reference site about the agent-interface category — a definitional hub, a tracker of agent protocols, and written guides. It is operated by Wilderness One LLC. There are no accounts. There is nothing to sign into, and nothing you can submit. That makes this policy short.

1. What we do not collect

No names, no email addresses, no passwords, no payment details. We do not ask you to create an account because there isn't one. We do not accept uploads, comments, or any other user-submitted content. We do not hold API keys — the earlier version of this site let you supply your own provider keys, and that product was retired in July 2026 along with everything it stored.

2. What we do collect

Two anonymous traffic signals, both about how the page was reached rather than who you are:

• AI-crawler visits. When a bot from an AI or answer engine (GPTBot, PerplexityBot, ClaudeBot and similar) fetches a page, we record the bot's name, the path it requested, its user-agent string, and the country reported by our CDN. This tells us whether those engines are reading the site — they crawl before they cite.
• Page views. A small script records the path you viewed, the referring URL, your browser's user-agent string, and two random identifiers described in section 3.

We do not store your IP address in either case.

3. Identifiers stored in your browser

The page-view script generates two random identifiers and keeps them in your browser's own storage, not in cookies:

• cc_anon_id in localStorage — persists between visits so repeat visits aren't counted as new people. It is a random value; it is not derived from anything about you and is not linked to any identity.
• cc_session_id in sessionStorage — cleared when you close the tab.

Clearing your browser's site data for this domain erases both, and a fresh random value is generated on your next visit. Browsing in a private window prevents them persisting at all.

4. Who processes this

Cloudflare hosts the site and serves every request. Supabase stores the site's own content (the tracker and the guides) and receives the traffic signals above. There is no advertising network, no analytics vendor, and no third-party tracking script on any page.

5. How we use it

Only to understand whether the site is being read and found — which pages get traffic, and whether AI assistants are crawling and citing them. We do not sell or share this information, and it is not used to profile or target anyone.

6. Your choices

Because we hold no account and no identity, there is no account to export or delete. To remove the browser identifiers, clear site data for this domain. If you believe we hold information about you and want it removed, write to us and we will find and delete it. Depending on where you live you may have further rights under the GDPR or CCPA/CPRA; contact us to exercise them.

7. Retention

Traffic signals are kept in aggregate for trend analysis and are not tied to an identity, so they cannot meaningfully be traced back to a person.

8. Links out

The tracker and guides link to third-party projects, specifications and vendors. Once you follow a link you are on someone else's site under their policy, not ours.

9. Contact

Questions or requests: [email protected].

Governing data-protection framework: the State of California, United States (including the CCPA/CPRA), and applicable U.S. federal law. This is a plain-language policy, not a substitute for review by legal counsel.