Wrapt for YNAB privacy policy

Last Updated: October 12, 2026

Wrapt for YNAB is a connector that lets an AI assistant such as Claude work with your YNAB plans (budgets): entering receipts, reviewing imported transactions, covering overspent categories, tracking purchases someone will pay back, and tidying up accounts. This policy explains what it does with the data it gets from the YNAB API.

What it uses your YNAB data for

Only to do what you ask of it through your assistant. When you ask, it reads your plans, accounts, categories, payees, transactions and category moves from YNAB, and it creates, changes, approves or deletes transactions, moves money between categories, sets reimbursement flags and reconciles accounts. Receipts it is sure about, including ones you forward by email, are added unapproved for you to approve in YNAB; every other change is made only after you confirm it. It never sells your data, shows you ads, or uses your data for analytics, profiling or training any model.

What it stores

Transactions and balances are read from YNAB when needed and not kept, apart from the record of changes described below, and receipts you share in a chat are not kept. The server stores only what it needs to remember between requests, each item tied to the YNAB plan it belongs to:

• a record of each change made through the connector, so it can tell who did what when several people share a plan: who made it (for a forwarded email, whose address it came to and its sender), when, on which plan, what was asked for, and what was changed, which can include the transactions' dates, payees, amounts, categories and memos, and changes that failed; it is kept for a year;
• which YNAB account each card is, by the card's last four digits;
• the payee names you prefer for the names your bank uses;
• which YNAB flags you chose to mean a purchase is waiting to be paid back and paid back, who has paid you back before, and money in you said was not a payment back;
• which categories you chose to cover overspending from, the moves it made, and a copy of YNAB's category move history that is replaced at most once a day;
• past months' overspending you chose to leave as it is, and how much of a past month's card overspending you paid off through it, so it knows what is still owed;
• when you last tidied up and reconciled each account through it;
• for receipts you forward by email: your own forwarding address (a code added to the inbox address), the addresses you forward from, and the plan and account you chose for them; the sender, subject and date of each email, what was read from the receipt (merchant, date, total, memo, items with their categories, and the card's last four digits), and what was done with it, so you and the others on your YNAB sign-in can check what was entered from each email before approving it, and so the same email is never entered twice; the email itself is not kept. Mail sent to an address that belongs to no one is never read: only its sender, the code it was sent to and when are kept, for 90 days, and shown to the server's owner and to the people whose receipts from that sender have already reached them;
• your YNAB sign-in: your YNAB user id and the access and refresh tokens YNAB issued for you, stored encrypted;
• who you are, since several people can share one YNAB sign-in: the name and email you give when signing in, and the default plan you picked when approving the connector;
• your sessions with the connector, whose tokens are stored only as one-way hashes;
• when you sign in on the install page to download the Skill, a cookie in your browser naming your YNAB user id, which ends after 12 hours; that sign-in asks YNAB only who you are, and the tokens YNAB issues for it are not kept;
• a count of recent requests to the sign-in pages by network address, used to block repeated guessing; it resets after ten minutes.

It never asks for, handles or stores the username, password or other credentials of any bank or financial account, or your YNAB password. It reaches YNAB only with the tokens YNAB issued when you signed in.

How it is secured

The hosted connector is reached only over HTTPS, and nothing can be read or changed through it without signing in to YNAB. Each person's requests use the YNAB sign-in they signed in through, so they reach only that sign-in's plans; people who share a YNAB sign-in share its plans, as they do in YNAB. Forwarded receipts reach the server only with the email service's own secret, and are entered only from the addresses the owner of the forwarding address chose, when their mail passes the sender check, using that person's own YNAB sign-in. Session tokens and sign-in codes are stored only as hashes, codes work once, and tokens expire and are replaced regularly. Your YNAB tokens are encrypted (AES-256-GCM) with a key kept in the hosting provider's encrypted settings, apart from the database, so a copy of the database alone can't use them. Keys and tokens are never logged or shown.

Who else handles it

Your YNAB data is never passed to any third party without your knowledge. These services handle it so the connector can work, and for no other purpose:

• Your AI assistant (such as Claude, by Anthropic) receives the YNAB data you ask it to look at, because that is how it answers you.
• Vercel hosts the server, and Turso holds the database described above.
• For receipts you forward by email, CloudMailin receives the email and passes it to the server, and the Anthropic API reads it, along with your plan's category names, to pull out the receipt.

How long it keeps it

What is listed under What it stores is kept while you use the connector, so it can keep remembering your choices, and until you ask for it to be deleted; the record of changes is deleted once it is a year old, when the next change is made through the connector. Sign-in codes stop working after five minutes, access tokens after an hour, and unused sessions after 30 days. Your YNAB tokens are kept until you remove the connector's access in YNAB's settings (they are then deleted the next time the connector tries to renew them) or ask for deletion; YNAB's access tokens expire after two hours and are renewed only while you use the connector.

Deleting your data

To have everything stored about you and your plans deleted, ask wraptforynab@icloud.com. It will be deleted within 30 days, and you will be told when it is done. You can also stop the connector's access at any time by removing it from your assistant, and by removing its access in YNAB's settings.

Changes to this policy

If the connector starts using a kind of YNAB data this policy does not describe, or uses your data in a new way, this policy will be updated and you will be asked to agree before that happens. The date at the top shows when it last changed.