Your finances · Understood
Your money, finally explained.
SpendCopilot connects to your financial accounts, organizes what's happening, and helps you understand where your money goes and what to do next.
SpendCopilot connects to your financial accounts, organizes what's happening, and helps you understand where your money goes and what to do next.
Most finance apps explain your spending after the moment has passed. SpendCopilot shows you the position you're actually in right now — so the next decision is an informed one rather than a postmortem.
Log something in plain language and your picture updates immediately. No waiting for the bank to settle.
Bank connectivity is built: SpendCopilot links an institution through Plaid and imports its pending and posted transactions. What comes next is breadth — checking, savings, credit cards, loans and investments pulled into one number for what you own, what you owe, and the difference.
That work isn't done. The first release connects a single institution, and there is no net-worth view in the app yet.
One field already takes what you spent in plain language — "$48.24 gas", "spent 8.96 at the market for buns and ice cream" — and turns it into a budgeted event, deterministically and without a model in the loop. The Copilot extends that same field from logging to asking.
It is designed and specified, and it is not built. The constraint it will ship under is already settled: deterministic systems own the financial truth, and the Copilot may only explain results it did not compute.
What you reported and what the bank later posts are two observations of the same purchase. SpendCopilot matches them, keeps both records, and counts the event exactly once — so the total never quietly doubles.
Amounts drift between authorization and posting, and the posting date is often not the day you actually spent it. Both are handled explicitly instead of being papered over.
$20.00 · Groceries
Budget date: Aug 18
EXACT MARKET · $20.00
Posted: Aug 18
Counted once. No change to projected surplus.
Your budget date and category remain unchanged.
The most reliable way to protect financial data is not to keep it. SpendCopilot's backend stores a deliberately small amount: enough to sign you in and keep your bank connection working, and nothing more. Everything below is a description of what the system actually does.
Sign-in uses passkeys (WebAuthn) with Face ID or Touch ID. There is no password to phish, reuse or leak. Only the public key and its metadata are stored on our side.
All API traffic runs over TLS. The database is encrypted at rest with AES-256-GCM under Cloudflare-managed keys, and API keys are held as encrypted Worker Secrets — never in source or in the database.
Bank connections are made through Plaid. Your bank login happens inside Plaid and we never see it. Transactions are fetched on demand and passed straight through to your device — the backend stores no transactions, balances or account numbers.
Account deletion erases every record tied to your account across all tables and revokes your Plaid connection at Plaid. You get a deletion receipt; only a de-identified hash is retained, to prove the deletion happened. The endpoint is live today; the in-app control ships with the app.
No advertising identifiers, no ad networks, no cross-app tracking, no profiling. We do not sell your data and we do not use it for advertising.
Consent is recorded at the points where data handling begins — account creation and bank linking — along with the exact policy version you agreed to. You can retrieve your consent records at any time.
We don't claim security certifications we don't hold. The full detail — the complete inventory of what is stored, retention periods, and how to exercise your rights — is in the SpendCopilot privacy policy.
It isn't on the App Store yet, and we won't pretend otherwise. Leave your email and you'll get one message when it's available — nothing else.
One email at launch. Every message has one-click unsubscribe. We store the address and which page you signed up from, and nothing else — see the privacy policy.