Privacy policy

Storage and Cloudflare: the connector stores your YNAB OAuth access and refresh tokens, YNAB user ID, read-only/write choice, and an undo journal of connector-performed writes (transaction IDs and the changed field values needed to reverse them). Cloudflare hosts the Worker and provides the Durable Objects and Workers KV storage used by the connector. Tokens and undo entries are encrypted with AES-GCM before they are written to Cloudflare KV.

Retention: encrypted token records, authorization grants, and undo entries are retained until you use the deletion page. Temporary OAuth consent and callback state expires automatically within 10 minutes.

Data delivery: when you make an MCP request, the connector exchanges OAuth and budget data with YNAB (including app.ynab.com for sign-in and api.ynab.com for API requests) and returns the result to the MCP client you connected. That client may receive budget data returned by the tool; its handling is governed by its own terms and privacy policy.

What it does not do: store your YNAB password, sell your data, use budget data for advertising, or persist ordinary budget results outside the encrypted token and undo records described above.

Deletion: use the deletion page to revoke this connector's grants and erase stored tokens and journal entries. You can also revoke the application from your YNAB account settings.

Contact: file an issue at github.com/oliverames/ynab-mcp-server.