Privacy

Last updated: 2026-09-30

What this covers

This policy covers the nifra.dev website and the hosted nifra docs MCP server at mcp.nifra.dev - the endpoint AI assistants connect to for Nifra's documentation, examples, and API types.

What we collect

Nifra does not require an account and does not intentionally collect identifying profile data. There are no sign-ups, cookies set by us, advertising identifiers, or behavioral profiles.

• The docs MCP server is stateless and read-only: it answers each request from a bundled documentation corpus and stores neither your queries nor their results.
• The application processes the query text needed to answer each request in memory and does not persist queries or results. Standard operational metadata (request path, status, and timestamp, and network metadata handled by the hosting provider) may be retained for up to 30 days to keep the service healthy, secure, and rate-limited. It is not used to profile users and is not sold.
• Traffic is served through a content delivery network and hosting provider. Those providers may receive network metadata to deliver and protect the service, and their handling of that metadata is governed by their own policies.

What the MCP tools can access

Every tool the server exposes (nifra_docs, nifra_example, nifra_types, nifra_learn, nifra_frontend, and the optional nifra_gallery widget) is read-only over public documentation. The server never reads your code, files, or any data from your machine or your AI assistant beyond the query text you send it.

Changes

If the site or the MCP server ever starts collecting anything beyond the above, this page will say so before the change ships.

Contact

Questions: open an issue on GitHub.