Read-only connections
Email access is requested with read scopes, and the only Plaid product requested is Transactions. The app has no ability to send email, move money, or initiate payments.
Security & privacy
Every statement on this page is written to match what the product actually does. We make no certification, audit, or “bank-grade security” claims.
Email access is requested with read scopes, and the only Plaid product requested is Transactions. The app has no ability to send email, move money, or initiate payments.
Your mailbox content, transactions and findings are not sold, rented, or shared with data brokers or advertisers.
Connected-account data is used only to identify potentially recoverable value for you, and to operate and support the service.
You enter bank credentials with your institution inside Plaid Link, not with us. Provider access tokens are held server-side and are never sent to the browser.
The app stores the structured facts that describe a finding — merchant, amount, dates, status, a reference and a short evidence snippet — rather than retaining full email bodies.
Disconnecting a source stops further access immediately. A deletion request removes your findings, evidence, imported transactions and connection records.
Connecting a bank or card account is optional. Without it, Lost Money Detective can still review your email history — but it cannot confirm whether promised money ever arrived.
Plaid Inc. is an independent service that connects apps to financial institutions. When you choose to link an account, Lost Money Detective opens Plaid Link. You pick your institution and sign in with Plaid and your institution, not with us. We never see or store your online banking username or password.
If your institution and Plaid complete the connection, Plaid returns an access token to our servers. We use it to request the information you consented to share:
Transactions is the only Plaid product requested. We do not request or use Balance, Auth, Identity, Assets, Liabilities, Investments, Income, or any payments product.
That information is used for one purpose: to reconcile promised or issued value found in your other authorized evidence against credits that actually posted to your accounts. It is not used for advertising, credit decisions, scoring, or resale.
The access token is stored server-side only and is never exposed to the browser. Disconnecting an account in the app asks Plaid to revoke our access, removes the stored token, and deletes the imported transaction data associated with it. If the revocation call to Plaid does not succeed immediately, the retry request is saved server-side first and retried automatically, and the app tells you the revocation has not confirmed yet rather than reporting a success that did not happen. Plaid’s own handling of your data is governed by Plaid’s End User Privacy Policy.
Bank connections are only available in the app when the owner of this deployment has configured live Plaid credentials. Until then, the connection screen says so plainly rather than pretending to work. We do not claim any Plaid production approval status on this site.
Data is stored in a managed Postgres database with row-level security, so each account can only read its own records. Traffic is encrypted in transit with TLS, and our database and storage providers encrypt data at rest. We do not claim any independent security certification or audit.
Email evidence is reduced to structured fields plus a short snippet. You can set snippet retention to 30, 90 or 365 days in the app, and you can delete stored snippets at any time while keeping the amounts and dates that describe a finding.
Deleting your data in the app removes findings, evidence and snippets, imported transactions, scan records and checkpoints, connection records, server-side access tokens, notifications and recovery notes. Routine backups age out on their normal cycle, and we may keep limited records where a law requires it.
We publish this so there is no ambiguity about which parts of Lost Money Detective operate on real data.
Provider access tokens are held server-side only, never sent to the browser, and are additionally encrypted at the application layer when an encryption key is configured for the deployment.