Cashcraft Privacy Policy
Last updated: 19 November 2026
This policy explains what Cashcraft collects, what it does with it, who can see it, and how to delete it. It is written to be read, not skimmed past. If anything here is unclear, ask us at hello@cashcraft.app.
Who runs Cashcraft
Cashcraft (cashcraft.app) is run by Cashcraft LLC, a Colorado limited liability company owned and run by one person, Matthew Francis. In this policy, "we" means Cashcraft LLC and the software it runs to operate the service. Contact: hello@cashcraft.app.
Our formal privacy notice under federal financial privacy law (the "GLBA privacy notice") is published next to this policy. It says the same things in the government's standard format.
The short version
- Your data is locked on your device before it reaches us. We store only scrambled (encrypted) data and pass your changes between your devices. We do not hold your key, so we cannot read what we store.
- Your key is locked by a recovery code you keep and by the device you sign in on. When you set up, you get the recovery code and tick a box to say you saved it. Your passkey signs you in; it does not unlock your key.
- If you lose your recovery code and every device you are signed in on, everything you typed is gone. We cannot get it back for you, and neither can anyone else. There is no recovery service.
- You can use Cashcraft without a bank link. You type in what you want to track, or import a file, and it goes to us encrypted, or, if you use Cashcraft without an account, stays on your device. During early access, bank sync is open only to households we invite; a bank connected during early access stays free for as long as you keep your account and Cashcraft offers bank sync.
- Bank sync is optional. If you use it, your bank data passes through our server on its way to you, is sealed on arrival, and is never stored readable. Section 2 says what that means.
- We can still see some facts about your data: how many records, when they changed, and which bank you use. Apart from the moment in section 2, we never see amounts, names, balances or payees.
- Every figure is worked out on your device, not on our servers.
- We never sell your data. We never use your bank data to target ads or offers at you.
- Nobody can open your account and look at it as you. There is no support access: nobody at Cashcraft can look at your data for you.
- If you share a household with someone, you share the same plan.
- You can export everything and delete everything, at any time.
1. What we collect
What we can read
This is the list of what is not scrambled. We can read it because we need it to run the service.
- Your email address and how you sign in: the public part of each passkey and of your device's keys, with a record of when they changed, and your private keys locked so only your passkey or recovery code opens them (we can't).
- For each device you sign in on, the browser and system it reports (for example "Chrome on Mac") and when it was added. You see this list in Settings.
- Which household you belong to, who else is in it, which households you are a member of and which one you started. People in the same household can see each other's sign-in email. For an invite you send: its role, when it was sent and how many times, and the invited address, kept encrypted, plus a fingerprint of it used to find the invite when that person signs in (someone who already knows an address could check it against the fingerprint). Our server sees the address when it sends the invite email.
- Facts about your data, not its contents. For each record: an id, which kind of record it is (for example your accounts and your transactions), when it was created, changed or deleted, and its size, rounded up to the next 64 bytes. From that we can see how many records you have and when they change. We cannot see what is in them.
- The agreements you gave: to the Terms and this policy, and before each bank connection.
- If you ask to approve a new device, the browser name that device says it is, and when.
- If you use bank sync: which bank each connection is with (the bank's name, which comes from Plaid's connection window and is stored), whether each connection is working or needs reconnecting and when it last synced, a record of each bank connection made (when, and which login made it, so we can count the free connections), records of when you opened your bank's connection window (kept for 2 days, to limit how often it can be opened), when each bank transaction arrived, whether it moved from pending to posted, and which of your entries a bank transaction was matched to (by id only).
- The date your household was created, and when it was last active. Each day you open the app on a device, that device tells us once, and we add one to a count for your household for that day and note the day as its last use. The count holds no screens and no content, and it is deleted when your household is deleted.
- If you use Cashcraft without an account, your household stays on your device and we never receive it. Once a day, when you open the app, it sends us two dates: the first day it sent us this count, and today. The app sends nothing else with them: no id and no content. We add one to a count for that pair of dates, which tells us how many people come back. The count holds only the two dates and the number, and we keep it. Like every request the app makes to our server, this one also carries your IP address and browser type, which our database provider's request logs record (see request logs, below). Our own server uses your IP address for a moment to limit how often the count can be sent, and does not store it.
- Request logs. Our hosting provider, Vercel, and our database provider, Supabase, each keep logs of the requests they receive: what was asked for, when, your IP address and your browser type. Supabase's logs cover every request the app makes to our server, whether or not you have an account, and Supabase sets how long they are kept. We can read these logs; they never hold your financial data, which reaches our server only encrypted (bank sync aside, section 2). When the app checks whether bank sync is open to you, our server also uses your IP address for a moment to limit how often that can be asked, and does not store it. Our own server code logs only technical identifiers and counts, never your financial data or email address.
- Page views on our public pages. When you open one of our public pages (the home page, the pages that explain Cashcraft, and these policies), the page tells Vercel's analytics which page it was (its address with any codes removed), the page that linked you here when you first arrive, the time, your approximate location (country, region and city, which Vercel works out from your IP address), and your browser, operating system and device type. It sets no cookie. Vercel tells visits apart with a code made from the request, which it discards after 24 hours, and shows us only totals. Nothing is sent from inside the app.
- Feedback you send us from the app. Your message, the app's version, which screen you sent it from and your browser type, plus your email address if you let us reply. It is emailed to us and kept in our email inbox, not stored on our server. Please don't put passwords or account numbers in it.
- When you connect a bank, your browser loads Plaid's connection script from Plaid. The site's fonts come from our own server, not from Google.
We use no advertising trackers. The only analytics are the page-view counts on our public pages and the counts of opens described above.
What we cannot read
Everything below is encrypted on your device before it is sent. We store it, but we cannot open it:
- your accounts: names, types, balances and the groups you put them in;
- your transactions, typed, imported or from a bank: dates, amounts, merchants and notes;
- your income, bills and planned lines, and the notes you add to a transaction;
- the history you import from statements or spreadsheets.
Bank data is the exception in one respect only: it passes through our server on its way to you and is sealed on arrival (section 2).
2. Bank sync: bank data passes through our server
Bank sync is optional, and you can use Cashcraft without it. None of this applies to you unless you connect a bank.
Bank data passes through our server on its way to you, is sealed on arrival, and is never stored readable.
We use Plaid Inc. to connect to your bank. You sign in to your bank through Plaid, not through us, and we never see your bank password. Plaid collects and processes your data under its own End User Privacy Policy: https://plaid.com/legal/#end-user-privacy-policy. Plaid also uses your data for its own purposes, which its policy describes. Please read it.
How your bank data reaches you.
- Plaid sends your account balances and transactions to our server. Cashcraft asks Plaid for the transactions product only: it reads your accounts (names, types, the last four digits and the current balance) and your transactions (date, amount, description and whether pending). It does not ask for holdings or investment activity, loans or other products. Plaid's answers carry more fields (categories, locations, available balances); those are thrown away on arrival and never kept. Plaid sends data when you first connect (up to 24 months back), when Plaid says new data is ready, and when our schedule checks every 30 minutes.
- For the time it takes to handle that one delivery, your bank data is readable on our server. Our server seals it, as it arrives, to a key that belongs to your household. The readable copy is not saved to our database and not written to our logs.
- Only the sealed copy is stored. Your devices fetch it and open it with your key.
Why this exists. The bank sends data to us, not to your device, and it cannot be sent in a form only your key opens. So the data has to be readable at the point it is received.
What we still see. We see how many bank transactions arrive, when, which bank they came from and whether they are pending or posted. After the sealing we never see amounts, names, balances or payees. We also see the name of the bank, which Plaid's connection window gives us and we store. During the moment of delivery the data is readable on our server, as above.
Who can reach your bank data. Our server keeps the connection key Plaid gives us and can use it at any time. It is encrypted before it is stored, with a separate key held outside the database. That connection key lets our server ask Plaid for your bank data, including up to 24 months of history. We use it only to bring your data to your devices.
Where it passes. Our bank-sync server runs at Supabase, the company that also runs our database and sign-in. Vercel, our hosting provider, only delivers the app's files to your browser. Your bank data, and the rest of your financial data, never pass through Vercel.
When you first use Cashcraft, we ask you to agree to the Terms and this policy. Before each bank connection, we show you what Plaid sends us and ask you to agree. We record each agreement: who, which version of the text, and when.
Disconnecting. You can disconnect a bank at any time: in Settings, open Banks and choose Disconnect, or open one of its accounts and choose Disconnect. We then tell Plaid to end the connection, and the stored connection key is deleted, together with that bank's sealed records. Only an owner or an editor of a household can connect or disconnect a bank.
3. How we use your data
Only to provide Cashcraft to you:
- To store your encrypted data and pass changes between your devices.
- To bring in your bank data, if you use bank sync (section 2).
- To sign you in and send you sign-in emails, and invite emails when we send an invite for you.
- To fix problems you ask us about, and to check that changes to the app work, using test data and not yours.
- To keep the service secure and to meet our legal duties.
Your balances, net worth, plan and projections are worked out on your device, from your decrypted data. Our servers do not calculate them and never see them.
We do not use your bank data for marketing, ads or offers, ours or anyone else's. If we ever want to use it any other way, we will ask you first, separately, and you can say no.
Your plan is your own. You write your income and bills. The app may suggest lines, such as a bill it noticed in your transactions. A suggestion changes nothing until you accept it, and you can dismiss it. Suggestions are worked out on your device.
Spreadsheets. Cashcraft does not read any spreadsheet of yours. If you import a file, it is read on your device and sent to us encrypted.
4. Who we share it with
We never sell your data. We share it only with the companies that run parts of Cashcraft for us:
| Company | What they do | What they receive |
|---|---|---|
| Plaid | Connects your bank, if you use bank sync | Your bank connection (section 2). Plaid also uses your data for its own purposes under its own policy |
| Supabase | Our database, sign-in, passkey checks and bank-sync server | Your encrypted data, which it cannot read, and the readable list in section 1, including the request details its logs keep, such as your IP address and browser type; if you use bank sync, your bank data in readable form for the moment in section 2 |
| Vercel | Hosts the website: it delivers the app's files to your browser | Requests for those files, with ordinary request details such as your IP address and browser type, and page views on our public pages (section 1). None of your financial data, bank data included, passes through it |
| Resend | Sends sign-in emails, household invite emails, and the feedback you send us from the app | Your email address, and, when we email an invite, the address of the person invited, who invited them and the role; the feedback you send, as described in section 1 |
| Anthropic (the company that makes Claude) | AI tools the administrator uses to maintain Cashcraft | Only what the administrator can see (section 5), never your encrypted data. We have turned off the setting that lets it use our account's conversations to train its models |
We also share data if the law requires it (for example a valid court order), or to protect you or others from fraud or harm. Because we cannot read what we store, a court order can get from us only what we can read (section 1) and the encrypted copy.
Your household. If you invite someone into your household, or join theirs, you both see the same accounts and plan. Each person has a role: an owner can invite and remove people, change roles and delete the household; an editor can change the plan, accounts and banks; a viewer can only look. Each of you signs in separately and has your own key. Your household shares one household key, which each member's key opens.
- An owner invites a person by their email address. The invite is a link: we email it to that address, or you copy it and send it yourself. It carries nothing secret. To join, the person signs in with that address and types a six-digit code you tell them in person or by phone. The invite works once and expires after 48 hours.
- When someone leaves or is removed, their access is removed at once, and the remaining members' devices change the keys the next time they open your household, so the person cannot read anything added afterward. They cannot forget what they already read.
5. What the administrator can and cannot see
Nobody can open your account and look at it as you. The old "view as the user" tool is gone as a standing tool.
The administrator (Matthew Francis) can see what section 1 calls readable: your email address, the facts about your data, the agreements, and the sign-in and household records. He cannot read your accounts, transactions, plan or notes, because he does not have your key. The software and AI tools used to maintain Cashcraft, including Anthropic's (section 4), can see no more than he can.
Operator access is logged. Each time the administrator makes a read through our operator command-line tool, one line is added to a log kept on his computer: the time (UTC), which session ran it, whether it was the live or the test service, the command, and the household. The line never holds the query text or any of your data. Writes and releases are not logged as reads, and the checks our release process runs on its own are not in this log.
There is no support access. If you ask us for help, nobody at Cashcraft can look at your data for you.
What deletion and account help look like without a view. You can delete your household and your account in the app; deleting needs no access to your data. If you have lost access and cannot use the app, write to hello@cashcraft.app and we will handle the deletion by hand. We cannot restore your data or reset your key. If you lose your passkeys and have nothing else to prove it is you, we reset your passkeys by hand after we have checked who is asking, and you sign in by email and make a new one; that does not give us, or you, your data back.
A limit you should know about. We cannot read your data because the app locks it on your device with a key we never hold. But the app itself is delivered from our servers. Someone who controls those servers, including us, could change the app to capture your key the next time you open it. A locked-down app cannot protect against that. We do not do this and have no reason to. A web app cannot fully prove to you that it is running the build it should. To make a changed app harder to slip in, the site sends a Content-Security-Policy that stops scripts from anywhere but its own files and Plaid's connection script. We do not yet add integrity checks to every script, and we do not yet publish a fingerprint (hash) of each release for you to compare. The release this policy was published with is 678f829.
6. How we protect your data
What we do:
- Your connection to Cashcraft is encrypted (HTTPS).
- End-to-end encryption. Your device makes your keys and encrypts your data with them (AES-256) before it leaves. We never hold your key. Your key is locked two ways, and either opens it: a recovery code you keep, and the device you signed in on. A new device gets in with your recovery code or by approval from another device of yours that is already signed in. Your passkey signs you in; it does not unlock your key.
- Your bank password never reaches us. The connection key Plaid gives us stays on our server and is never sent to your browser. It is encrypted before it is stored, with a key held outside the database.
- Database rules on every table let each user reach only their own household's records.
- Every session ends after 7 days. Signing out ends your session on the device you sign out on and removes that device's key and saved records. In Settings, "Sign out of all devices" ends every session of yours at once.
- If you lose a device, you can remove it in Settings (Your devices). Removing a device makes a new recovery code and new keys for you, so the removed device opens nothing saved after that; what it already holds stays on it until it signs out there. If your recovery code is stolen, or you think someone saw it, the same new-code step replaces it, after you confirm it is you. A new recovery code ends your other devices' sessions and removes the old code.
- Signing in and a second factor. You sign in with a passkey, or with an email: we send a link and a six-digit code. After your first email sign-in the app offers you a passkey (Face ID, a fingerprint or your device PIN); you can choose "Remind me later" or "Don't ask again". A passkey counts as two-factor sign-in on its own, and if you have one, an email sign-in also needs it before you can change anything. If you have no passkey, the email alone is not enough to change anything: the session must also prove a second factor. On a browser that already holds your household, that proof is the key kept in that browser, and you type nothing. On a new browser it is approval from another of your signed-in devices, your recovery code, or a code from an authenticator app you set up in Settings. Until you prove one, the app opens your household read only: nothing that changes it is offered and nothing is sent, and the database refuses every record or bank connection that session tries to write. Deleting, removing a bank, exporting, inviting or removing people, changing a role, undoing changes and making a new recovery code each ask for a passkey confirmed in the last five minutes or, for a person with no passkey, for your recovery code. Signing in and unlocking are separate: unlocking your data always needs a key (your recovery code, a device you are signed in on, or approval from one), so an email link alone does not open it on a new browser.
- Our database host (Supabase) and our web host (Vercel) say in their security documentation that they encrypt stored data and data in transit. For your data that is a second layer, because it is already encrypted before it gets to them.
What you do:
- Your device holds an unlocked working copy of your data. If someone gets into your unlocked device, or malware runs on it, they can read it. Keep your device secure.
- Your passkey app is part of your security. A passkey that syncs through your Apple or Google account, or a password manager, opens your sign-in to whoever controls that account. Keep that account secure.
- Your device keeps your records as encrypted data and opens them only in memory, and the device key cannot be exported. Signing out clears the device key, the saved records and your session.
No system is perfectly secure, and we do not promise that ours is. If a security problem affects your data, we will tell you (section 10).
7. If you lose your key
If you lose your recovery code and every device you are signed in on, everything you typed is gone for good. That means your plan, notes and any transactions you entered. We cannot reset it, recover it or reveal it, and no one else can. There is no recovery service, from us or from anyone. If you use bank sync, the bank data can be pulled again from Plaid (up to 24 months back) into a new key. Nothing you typed can.
Any one of these gets you back in: a device you are still signed in on, your recovery code, or approval from another signed-in device of yours. You lose everything only when all of them are gone.
To avoid that:
- Save your recovery code when you set up, somewhere safe and away from your device. Anyone who has it can open your data, so keep it as private as a password. We show it once, and the app asks you to tick a box saying you saved it before setup finishes; it does not check that you did.
- Add a second passkey or sign in on a second device.
- Export a copy now and then (section 9).
- If you use Safari outside the home-screen app, the browser may clear what it saved after a week unused. You then use your passkey or recovery code to get back in.
Your recovery code. At setup the app shows you your recovery code once, in seven groups of four, and asks you to tick "I saved my recovery code" before setup finishes. It is never shown again. If you lose it, or think it was exposed, make a new one in Settings under Sign-in (see section 6); you need to confirm it is you, with a passkey or with the current code (or, if you have no passkey, with an authenticator app confirmed over a day ago). A person with no passkey, no authenticator app that old and no code cannot make one, and is told to contact us.
8. How long we keep it
- While your account is open, we keep your encrypted data so the app works, including your history. Records you delete are kept as deleted markers for 90 days, then purged. The database also keeps each earlier version of a record, still encrypted, for 30 days, or until someone is removed from the household, so you can undo changes; older ones are purged each day.
- If you delete your account in the app, your encrypted data, your keys on our side and your bank connections are removed from our database right away, as long as no one else is in your household. If you share a household, see section 9. After you delete your account we keep the record of what you agreed to and when, with no financial data, as proof of your consent, for two years, and then delete it. The record of each bank connection you made stays as an anonymous count, a date with nothing that ties it to you, because our bank-data provider still counts it.
- Before each change to the database's structure, we save a copy of it on the administrator's computer, so the change can be undone if it goes wrong. A copy holds what the database holds: your records, still encrypted, and the details we can read (section 1). Each copy is deleted after 30 days. If you delete your account, your encrypted data can stay in a copy made before you deleted it until that copy is deleted, 30 days at most. Supabase's free plan does not make project backups and we run no other backup. Your devices keep your records as encrypted data and you can export a backup from the app (section 9); if the database were lost, we could put back only what the latest copy, your devices or your exports hold.
- If nobody opens your household for two years, the database deletes it, ending its bank connections at Plaid first, and deletes the sign-in of each of its members who belongs to no other household. The database records a warning 30 days before; we do not yet have a way to email that warning, so today the deletion happens at the deadline without an email. Opening the app any time before then starts the two years again.
9. Your choices: export, delete, disconnect
- Export everything. In the app you can download all your data as JSON or CSV, or as an encrypted backup. It is decrypted on your device and saved to a file, so it does not go through us in readable form. It asks you to confirm it is you first, with your passkey or, if you have none, your recovery code.
- Delete your account: in the app, open Settings, then Your data, then the Danger zone, and choose Delete my account and data. This tells Plaid to end every bank connection, then deletes your encrypted data, your keys on our side and your sign-in. If you share a household with someone, you leave it first: leaving removes your access and the remaining members' devices change the keys; the household and its data stay for them. A person with a passkey confirms with it; a person with no passkey types their recovery code.
- Ask us to delete it for you: if you have lost access, write to hello@cashcraft.app and we will handle it by hand and tell you when it is done.
- Disconnect a bank: in Banks, or from one of its accounts, choose Disconnect. This tells Plaid to end the connection, and we delete that bank's sealed records and links. Transactions you already confirmed are your own records and stay, unless you switch on "Delete its history too" in the same dialog.
- Ask what we have: email us and we will tell you what we hold about you. For the readable list in section 1 we can tell you exactly. For the rest we can tell you that it exists and how big it is, not what it says.
- Your browser's copy: the app keeps a working copy of your data on your device. Signing out clears your device key, the saved records and your session.
10. If something goes wrong
If your data is exposed in a security incident, we will notify you, and the authorities where the law requires it, as fast as we can and within the deadlines the law sets.
If someone takes our database, what they get of your content is encrypted, and they cannot read it without your key.
11. Age
Cashcraft is for people 18 and older. We ask you to confirm this before you use it. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, tell us and we will delete it.
12. Changes to this policy
If we change this policy, we will update the date at the top and tell you in the app before the change applies. If a change means sharing your data in a new way, we will tell you first and, where you have a right to say no, give you the chance.