Privacy & licensing

The Free Agentic Publication Digester (FAPD) publishes a static website. This page states, for humans and for AI agents alike, exactly what that means for visitors — and under what terms the content may be reused.

What this site does not do

The one thing that is recorded

Like effectively every hosted service, the web server infrastructure serving this site keeps standard access logs — the requesting IP address, requested URL, timestamp, response code, and User-Agent — used solely for security monitoring and abuse prevention (for example, rate-limiting and intrusion detection), retained briefly under routine log rotation, and shared with no one. TLS certificates are issued by Let's Encrypt; certificate issuance is public by design (Certificate Transparency logs), like every HTTPS site's.

The MCP service. Requests to https://fapd.info/mcp pass through the same web server logs described above. The MCP service itself logs, for each request, the time, the protocol method, the tool or resource name, the response status and size, the processing time, and the client's self-reported software name, and an opaque request identifier the web server assigns to each request so the two logs can be matched up. It does not log your IP address, the arguments you sent, or the content of any request or response. The web server in front of it keeps a separate access log for /mcp (address, time, method, status, size, software name, the same request identifier; never a request body) used for rate limiting and to block addresses that send many rejected requests in a short time; those blocks expire on their own. Logs rotate on the same schedule.

That is the entire data story. There is nothing else to disclose.

Licensing

The attribution ask mirrors our own citation ethic: for factual claims, cite the underlying official source each digest item links to; cite FAPD for the aggregation. Machine-readable reuse notes ride in /llms.txt.

Our own outbound activity

The crawler that gathers this site's source material has its own transparency page: Our crawler.

Contact

The project contact address appears in every request our crawler makes and in the repository metadata.