Zum Inhalt springen

Privacy and access

Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

Zenodot MCP offers Library reads and Page and folder writes for linked Pro accounts.

  • API keys are generated randomly and shown only once. Zenodot stores only a one-way SHA-256 digest and a short display prefix.
  • Keys grant scopes: library:read for read tools and library:write for write tools. A key created through the app grants both. Keys can be revoked independently.
  • Keys expire after the selected 30, 90, or 365 day period, or can be set to Never.
  • Each MCP request re-checks that the account is linked, Pro, and has a recent entitlement sync.
  • Reads and writes are scoped to the authenticated account. Read cursors are signed and bound to the account and grant.
  • Requests are denied when an account is deleted, merged, or no longer has Pro access. Keys can also be explicitly revoked.

The MCP surface does not expose Chute Notes, historical snapshots, or Ask conversations. Write tools let a connected client with library:write create, change, and delete Pages and folders; deleting a folder also deletes its descendant folders and Pages. Treat write-capable keys like passwords with permission to change or erase your Library. A client, its model provider, or anyone who obtains the key could access Library data and, with write scope, alter it. Review the client’s permissions and privacy practices, protect the key, and revoke it immediately if compromised or no longer needed. Standard service logs must redact API keys and Page body text.