Privacy policy.
Updated October 11, 2026
What Docsy does
Docsy operates a public documentation retrieval service with an open-source MCP plugin at docsy.remcp.site. Our public MCP and REST tools help coding assistants find source-linked library documentation. Public read-only searches do not require an account.
Information processed
When you use public tools, we process library names, versions, search terms and necessary network/request information to answer the request, detect abuse and keep the service operational. Web, proxy and hosting infrastructure may temporarily record IP addresses, request paths, timestamps, user agents and diagnostic errors. Avoid sending secrets, proprietary code or personal information in queries.
If you sign in with Google through Firebase Authentication, we process an account identifier and profile details such as name, email address and avatar supplied by Google. We associate API keys with your account and store hashes of API keys, not plaintext key values. Authenticated use can generate per-user usage statistics, including client, operation and library counts.
How information is used
We use this information to retrieve documentation, operate the public catalogue, secure access, control rate limits, diagnose failures and show usage statistics. Aggregated tool and library usage is recorded for analytics and capacity planning. We do not intentionally retain the free-text body of documentation questions in our usage-statistics tables. Some request details can still occur in temporary infrastructure or diagnostic logs.
Hosting, processors and backups
Docsy uses self-hosted infrastructure and PostgreSQL; Cloudflare helps deliver and protect the public site; Firebase/Google provides optional authentication. The documentation index and operational backups may be stored with hosting and backup providers including Hetzner Storage Box. If you follow original-source links, those third-party sites handle your visit under their own policies.
Retention and security
Operational logs, authenticated profiles, usage aggregates, indexes and backups have different retention periods. We retain them only as needed for service operation, security, troubleshooting, recovery and applicable obligations. Backup copies can remain until their rotation cycle completes. Connections to the public service use HTTPS, and access to account-specific actions requires authentication.
Your choices and requests
Use public anonymous retrieval without signing in, or revoke your personal API keys from the dashboard. For an account-data access or deletion request, visit support to arrange a private channel. Do not post account identifiers, credentials or other sensitive information in public GitHub issues.
Updates and contact
Changes to this policy appear here with a revised date. The Docsy MCP plugin is developed openly at github.com/antonbaider/docsy-plugin. See the support page for project contact options.