1. Information We Collect
We collect account details, subscriptions, actions and outcomes you save. Saved imports include transaction dates, signed amounts, currencies, account and card associations, short source excerpts, document fingerprints, parser versions and correction history. Purchases create provider receipts and entitlement records. Optional bank connections, forwarded emails and receipt uploads also provide their selected account, transaction or document content.
Mobile PDF and photo scanning runs locally, with optional Apple on-device model assistance. It does not upload the raw document to cloud AI. Saving reviewed evidence sends its records and excerpts to Convex. Web parsing starts locally. If you choose to archive extracted PDF evidence, all readable text from that selected PDF, including personal details, is saved to your private account with page locations; the original PDF bytes stay on your device. Archived text is not classified financial evidence. Separately chosen cloud extraction and other web AI tools can send content to Anthropic.
Operational events record fixed import, action and outcome codes and coarse counts or duration buckets. They are linked to your account for access control, omit merchant names, amounts, excerpts and credentials, and are retained for up to 30 days before scheduled cleanup. They are included in account export and deletion.
2. How We Use Your Information
- To provide and improve our AI-generated cancellation and negotiation scripts
- To process payments securely via Stripe
- To authenticate your account via Clerk
- To send you important service updates (no marketing without consent)
3. Data Sharing
We do not sell your personal data. We share data only with:
- Anthropic — Selected cloud extraction, forwarded email processing and web AI tools; not the mobile local scanner
- Stripe and Gumroad — Payment processing where offered
- Clerk — Authentication
- Convex — Database and backend hosting
- Resend — Transactional and cancellation email delivery
- Plaid — Bank connection and transaction processing when you connect a bank
- PostHog (earlier releases) — Earlier web analytics used account identifiers and event properties. New operational events stay in our private backend. Historical provider-held records may require separate cleanup; contact us for help.
4. Data Security
Connected access tokens are encrypted at rest and credentials stay on the server. Account evidence is private and kept separately from the public provider knowledge graph. HTTPS protects data in transit. Avoid including unnecessary sensitive details in excerpts, chat or support requests.
5. Your Rights
You can export account data from Settings, with credentials removed. Large exports collect pages over an interval, so concurrent edits may affect later pages. Deletion removes or anonymizes account records, including import corrections, action outcomes and purchase records, and attempts connected-provider, stored-file and Clerk cleanup. The deletion receipt identifies pending or failed cleanup. Copies held by payment or other providers follow their own retention requirements. Contact privacy@trimspend.com for help.
6. Cookies
We use essential cookies for authentication and session management. Earlier releases also used PostHog analytics persistence. Browser settings let you remove those cookies or stored analytics data. We do not use advertising cookies.
7. Contact
For privacy questions, email privacy@trimspend.com.