Read-only access
Your accounts are connected read-only. Trupence can’t move money, make payments, or change anything at your bank.
Your bank password stays with your bank
You sign in with your bank, or through Quiltt’s secure connection window. Trupence never sees or stores your bank username, password, or security codes.
Walled off by design
The database itself enforces that every record belongs to one account or household. A query can’t return someone else’s data, even by mistake.
Never sold
We don’t sell or rent your personal data, and we don’t show ads. See our Privacy Policy for exactly who processes your data and why.
Trupence uses Quiltt, a financial data platform that works with data providers such as Finicity, a Mastercard company, to connect to your bank, card, and loan accounts.
When you add an account, a secure window opens. Many banks let you sign in on their own website and approve access there. For others, you sign in inside the connection window run by Quiltt and its data provider. Either way, your credentials go to your bank or the data provider, never to Trupence. Trupence receives read-only access to your balances and transactions.
No. Trupence has no ability to transfer money, pay bills, or change anything at your bank. It can only read balances and transactions.
Open the Accounts screen and disconnect the institution. We stop receiving new data from it. Deleting your Trupence account disconnects all of your institutions at once.
No. We don’t sell or rent your personal information, use it for advertising, or use your financial data to market other companies’ products. Our Privacy Policy lists every service provider that processes your data and what each one receives.
They’re read on our own servers, without any outside document-scanning service. The file is deleted as soon as the figures are extracted. We keep only the numbers you see in the app, like employer name, pay, taxes, and deductions, and you can edit or delete them at any time.
- In transit: every connection between your device, our servers, and Quiltt uses TLS encryption.
- At rest: our database runs on Google Cloud, which encrypts stored data. Two-factor secrets get an extra layer of AES-256-GCM encryption in our application.
- Isolation: row-level security in the database ties every record to its owner. Only you, and your household partner if you share a household, can read your data.
Go to Settings and choose Delete account. We remove your accounts, transactions, budgets, goals, plans, and settings, and we ask Quiltt to delete the profile that holds your bank connections. Deletion is permanent.
- Passkeys: sign in with Face ID, Touch ID, Windows Hello, or a security key. No password to steal.
- Sign in with Google: uses your Google account, including the 2-Step Verification you’ve set up there.
- Email and password: two-factor authentication is required, using an authenticator app or a one-time code sent by email.
- Aggregation: Quiltt, with Finicity for account data and FinGoal for transaction enrichment. Access is read-only.
- Hosting: the API and background jobs run on Google Cloud Run, with PostgreSQL on Cloud SQL. The web app and this site run on Cloudflare.
- Tenant isolation: PostgreSQL row-level security is enabled and forced on every financial table, scoped to the signed-in user or their household.
- Credentials: passwords are hashed with bcrypt. TOTP secrets are encrypted with AES-256-GCM. Email codes and password-reset tokens are stored only as SHA-256 hashes and expire quickly.
- Passkeys: WebAuthn with user verification required.
- Webhooks: Quiltt sync events are verified with HMAC signatures and rejected if they’re stale.
- Documents: payroll PDFs are parsed in-process and deleted right after extraction.
Found a vulnerability? Please email legal@trupence.com.