Jarby Privacy Notice

Effective: October 31, 2026. Version 1.6.

Where Jarby is today

Today Jarby holds only the operator's own data. We will not let anyone else sign up until every "Before anyone else is invited" item below is in place. If you are not the operator, those items describe how we treat your data.

Who we are

Jarby is operated by Jarby LLC, a Texas limited liability company, 10601 Clarence Dr., Suite 250, Frisco, TX 75033 (our registered agent's address). Privacy questions: support@jarby.app.

What we collect

• What you give us: your email address (from sign-in), settings you enter (cards, account and rewards-program names, recurring items, categories), files you import (such as a bank or budgeting-app export), and any feedback you send.
• If you join the waitlist: your email address, used only to tell you when you can join. We keep it until we invite you or you ask us to remove it, and we store no IP address or device details with it.
• What you let Plaid share with us: for the accounts you connect, the account names, types, last four digits and balances; transactions; and credit card statement details. Plaid's connection screen says Jarby and Plaid collect contact details: Plaid may collect them when you connect, but Jarby does not ask Plaid for them and does not keep them. Plaid's loan data can include a mortgage's property address; Jarby discards it and keeps only the credit card details.
• What the app records to run: sign-in and security events, how the app categorized your transactions, a record of each call we make to Plaid or Anthropic (time, type and result), a copy of what we send Anthropic for AI suggestions and what it returns, and error reports.

You sign in to your bank in Plaid's window and enter card details on Stripe's page, so we never receive your bank password or your full card number.

How we use it

We use your information to run the features you use (spending and cash-flow reports, categories, alerts, card comparisons and suggestions), to keep Jarby secure and working, to keep our card catalog accurate (below), and to meet legal obligations.

Some categories, insights and card suggestions are produced by AI (Anthropic's Claude) and are labelled in the app. AI can be wrong, so check before you act. Jarby does not make credit decisions.

Card catalog. To keep our card catalog accurate, the operator and the AI agents the operator runs (Anthropic's Claude) review samples of card transactions.

• Today: a sample shows merchant names as the bank reports them (sometimes the bank's own description), merchant and category codes, card products, and how many transactions and users. It never shows your name, your account or any code for you.
• Before anyone else is invited: merchants seen for fewer than 3 users are left out of every result, and the bank's own description is never shown.

We do not sell your data or share it for advertising, and we do not use it for advertising.

Companies that work for us

We share your information only with the companies below, which work for us, and as described under "Other disclosures".

• Plaid connects your accounts (see "Plaid" below). We give it an internal user ID, not your email, so it can tell users apart.
• Anthropic provides the AI in our app and the AI agents the operator uses to run Jarby.
• In the app: we send it transaction details (including the description as your bank shows it, which can name other people, for example on a transfer), account, card and rewards-program names, balances, totals, the contents of files you import, and feedback text with the page you are on and a short summary of your browser. Some of this happens automatically when new transactions arrive. We do not send your email address, full account numbers or bank access tokens, though text you write, an imported file or a bank's description may contain such details.
• The operator's AI agents can read all the information in "What we collect", your email address included, while they help run and maintain Jarby. These sessions run under Anthropic's consumer terms, with model training turned off. Anthropic keeps this data for up to 30 days. It may keep a session flagged for safety review for up to 2 years and use it to improve its models.
• Google handles sign-in. It learns that you sign in to Jarby; we send it none of your financial data.
• Stripe handles subscriptions. It receives your email address, an internal ID and the payment details you enter on its page; we send it no bank or transaction data. Today billing is in test mode and no card is charged.
• Sentry handles error monitoring. When the app hits an error, a report goes to Sentry. Before it is sent, we remove the request's contents and every email address, hide sign-in tokens in links, and identify you only by an internal user ID. The error message itself can sometimes include a piece of your data, such as a transaction description; we check reports for this and switch reporting off if it happens. About 1 in 20 page requests also sends timing data. Sentry's privacy policy: https://sentry.io/privacy/
• Resend will send our account emails (invitations and service notices). It receives your email address and the message. Today Jarby sends no email; this starts before anyone else is invited.
• Hosting. Jarby runs on a single server that the operator owns and runs, in the United States. Hosting is moving to jarby.app; this policy will be updated when that happens.

Other disclosures

We also make disclosures to other nonaffiliated companies for our everyday business purposes, such as to process transactions, maintain your account, and respond to court orders and legal investigations, and as permitted by law.

We do not share information about current or former customers with other companies for their own marketing or for any other purpose that would give you a right to opt out, and we do not reserve the right to. So there is nothing to opt out of.

Plaid

We use Plaid to connect your bank and card accounts. Plaid's End User Privacy Policy: https://plaid.com/legal/#end-user-privacy-policy.

When you disconnect a bank in Settings → Connections, we ask Plaid to end the connection, and you choose whether we delete that bank's accounts and transactions or keep them (shown as closed) until you delete them or your account. If Plaid does not confirm, we keep an encrypted copy of that bank token and keep asking for up to 60 days; then the copy is deleted, we can no longer end the connection ourselves, and the operator asks Plaid support to remove the Item by item_id. If the token cannot be read (a wrong key or damaged data), an encrypted copy is kept only to end the connection, on the same schedule. When Plaid tells us you stopped sharing a bank (in Plaid Portal or at your bank), or when Plaid tells us the connection no longer exists, we delete that bank's accounts and transactions, unless you had already disconnected it and chose to keep them. If several connections get that answer at once, or one gets it with no recent successful Plaid call on your connections (a sign of a setup error on our side), we hold the deletion, unless another of your bank connections that Jarby checks in the same run works normally, which shows the problem is with that connection and not with Jarby's setup; then we delete them. While a deletion is held, we record the hold and check again with Plaid automatically for up to 60 days, and delete once Plaid confirms the connection is gone. If Plaid can't confirm the connection is gone, we may not be able to delete it automatically: after 60 days we stop checking, nothing is deleted, and it stays in Settings → Connections, with the data we already have, until you delete it there. If that delete fails, the bank stays, shown as closed, and we try the delete again automatically for up to 60 days; you can also delete it yourself with Delete history.

• Today: we delete the raw records Plaid sent when you disconnect a bank, whichever you choose, and when Plaid tells us you stopped sharing it.
• Before anyone else is invited: we delete the raw records when you disconnect. When Plaid tells us you revoked access (in Plaid Portal or at your bank), it has the same effect as disconnecting with Delete.

Some banks report that you stopped sharing only as a connection that needs you to sign in again. We can't tell that apart from a changed password, so we delete nothing then. To be sure your history is gone, use Disconnect and delete, or Delete history, in Settings → Connections.

If you stop sharing just one account at a bank, some banks tell us and some don't. When we are told, we delete that account and its transactions and keep the bank's other accounts. To be sure, open that account's settings and choose Delete account under Lifecycle.

How long we keep it

The full schedule is in our Data Retention Policy.

Your choices

In Settings → Privacy you can:

• Download a copy of your main records. For anything not in the download, ask us.
• Correct most data in the app, or ask us to correct the rest.
• Delete your account. Your data leaves the live database at once, except an encrypted bank token we hold only to end the bank connection: the token at most 60 days, and the record of that connection (Plaid's ID for it, no token) at most 90 days: at day 80 the operator sends Plaid support the list of these connections to end, then deletes the records by hand, by day 90. We ask Plaid to end every connection, and we ask Stripe to delete your billing record. If Plaid does not confirm, we keep an encrypted copy of that bank token, stored without your user ID or email, and keep asking for up to 60 days; then the copy is deleted, we can no longer end the connection ourselves, and the operator asks Plaid support to remove the Item by item_id and deletes the record within 30 days, by day 90. If the bank token fails to decrypt (a wrong key or damaged data), we keep it too, encrypted and stored without your user ID or email, and end it on the same schedule: the token at most 60 days from its first failure, the record at most 90 days (sent to Plaid support at day 80 and deleted by hand by the operator by day 90). Backup copies are gone within about 30 days once older hand-made backups are cleared; until then some are kept longer, and logs are deleted as described above. Anthropic keeps data only as its terms allow.

If we withdraw your invite, you can still sign in with Google, for up to an hour at a time, only to download your data or delete your account; nothing else in Jarby opens. Deleting your account also deletes your invite record and ends that sign-in.

We answer requests within 30 days.

How we protect your information

Only the operator, and software the operator runs (including AI agents provided by Anthropic), can access your information. We have security practices and procedures in place to keep your information confidential as this notice describes. Bank access tokens are encrypted with AES-256-GCM when stored and are sent only to Plaid. Your data is encrypted when it is stored, on our servers and on the operator's computers.

Children

Jarby is not for anyone under 18, and we will not knowingly create an account for a minor. Before anyone else is invited, sign-up asks you to confirm you are 18 or older. If we learn an account belongs to someone under 18, we will delete it.

Changes

Before anyone else is invited, sign-up will record which version of this notice you saw and when you accepted it. We will update the date at the top when this notice changes. Before a material change to how we use or share data we already hold, we will tell you in the app or by email and ask for your consent. Earlier versions are available on request at support@jarby.app. This notice keeps applying after you close your account.