Duesback Privacy Policy

Version 1.0.

Effective date: September 26, 2026

Duesback is operated by an individual doing business as "Duesback". This policy explains what we receive, what we keep, and what we do with it. It is written to be read, not skimmed. If anything is unclear, email hello@duesback.com.

The short version

Your Muse sends us bank transactions when you ask it to audit your bills. We read them, find recurring charges and fees, and send findings back. We do not store the transactions.
We keep recurring-charge signatures (merchant, cadence, typical amount, dates), the findings we gave you, the outcomes Muse reported, and the fees we charged.
We keep your email, a hashed version of your API key, and the Stripe payment references for fees you paid. We never see a card number. If you enable autopay, Stripe stores the card and we keep only its Stripe reference; disabling autopay removes it.
We delete everything within 30 days after you disconnect, or sooner if you ask.
We never sell your data. We never share it with advertisers.
Duesback is not affiliated with Meta.

1. What we receive from Muse

When you ask Muse to run an audit, Muse sends a request to https://duesback.com that contains bank transactions from your connected account, typically the last 12 months. Each transaction has a date, an amount, the description your bank shows, and, when Plaid provides them, a cleaned merchant name, a category and an account identifier. Muse asks for your approval before it sends this data.

We process the transactions in memory to find recurring charges and fees. We then discard them. We do not write raw transactions to a database, a log or a backup. Our hosting logs record request metadata and our own log lines, not request bodies.

When Muse acts on a finding, it sends us an outcome report: which finding, what action, whether it succeeded, the new amount or refund amount, and a short free-text note of evidence, such as a confirmation number or what the representative said. Muse writes that note and we store it. If Muse includes personal details in the note, we hold those until deletion.

We do not receive your bank login, your Plaid credentials or your Muse account credentials. Requests reach us from Muse's own environment, so the IP addresses we see belong to Meta's infrastructure, not to your device.

2. What we store

Data	Why	Where it comes from
Email address	Sign-in, receipts, notices	You, at sign-up
API key hash and key prefix	To authenticate Muse's requests. We store a SHA-256 hash of the key combined with a secret pepper, never the key itself	Generated at sign-up
Stripe Checkout session, payment and (autopay only) payment method IDs	To match a fee to its payment and, if you enabled autopay, to charge it. These are Stripe references, not card details	Stripe
Date and time you accepted the fee consent	Proof of consent	Sign-up page
Recurring-charge signatures	Merchant (normalized and display name), cadence, typical amount, first and last charge dates, number of charges. Also a summary of bank fees: type, count, total, last date	Derived from each audit
Findings	The problems we flagged, with short evidence lines such as "Charged $15.49 on the 12th for 9 months", the playbook used and the estimated saving	Derived from each audit
Outcomes	What Muse reported after acting, and our verification result	Muse
Fee charges	Amount, date, reason, Stripe payment intent ID, status	Our billing
Usage events	Which tools were called and when. No transaction data	Our server
Account status and timestamps	Created, activated, disconnected	Our server

Signatures let us re-audit without asking for old data again, detect price increases, and verify outcomes. That is the only reason we keep them.

3. What we do not store

Raw transactions.
Account numbers, routing numbers or balances.
Bank, Plaid or Muse credentials.
Card numbers, expiry dates or security codes. Stripe holds those.
Your name, postal address, phone number or date of birth. We do not ask for them. Stripe's payment page may ask for a name or billing ZIP code; that goes to Stripe, not to us.

4. How we use data

To run audits and return findings and playbooks to your Muse.
To verify outcomes and charge success fees.
To send you receipts, dispute responses and service notices.
To count how the service is used (which tools are called, how often) so we can decide whether to keep building it.
To answer your requests and fix bugs.

We do not use your data for advertising. We do not build profiles of you for anyone else. We do not train models on your data.

5. Model calls

To classify merchants our fixed tables do not recognize, we send short snippets to a language model through OpenRouter. A snippet contains the merchant text as it appears on the transaction, a sample amount, and nothing else. We do not send your email, your account identifiers, your API key, your Duesback user ID or full transactions. OpenRouter routes the call to a model provider. The provider is OpenRouter, routing to Anthropic Claude models; the snippets carry no name, email, account number or identifier.

6. Who we share data with (sub-processors)

We use a small number of providers to run the service. Each one sees only what it needs.

Provider	Role	What it sees
Cloudflare	Hosting (Workers, D1 database), DNS, email routing	All server traffic and the stored data listed above. Cloudflare access logs may hold request metadata and Meta-side IP addresses for a short period
Stripe	Payments	Your email, whatever you enter on Stripe's Checkout page when you pay a fee, and each fee payment
Resend	Transactional email	Your email address and the contents of receipts and notices
OpenRouter	Model calls for merchant classification	Merchant text and sample amounts only, as described in section 5

We do not share data with anyone else except when the law requires it, to protect our rights or safety, or with your explicit consent. If we move the service into a company, or if Duesback is ever acquired, your data would move with it under this policy, and we would tell you first.

7. We do not sell data

We do not sell personal data. We do not share it for cross-context behavioral advertising. We have no data brokers, no ad networks and no affiliate data deals.

8. Retention

While connected: we keep the data in section 2 for as long as your account is active.
After you disconnect: we delete your signatures, findings, outcomes, usage events and API key hash within 30 days. To disconnect, tell Muse "Duesback, disconnect" (which revokes your key), then remove the connector in Muse, or email hello@duesback.com, or email hello@duesback.com. Removing the connector in Muse alone does not tell us; we cannot see your Muse settings.
On request: we delete sooner if you ask.
What we keep longer: fee charge records and receipts, for tax and accounting purposes, for up to 7 years. These contain your email, the merchant, the amounts and the fee. They do not contain transactions. Stripe keeps its own records under its own policy.
Backups: Cloudflare D1 keeps point-in-time backups for up to 30 days. Deleted data can persist in those backups until they expire.

9. Security

All traffic uses HTTPS. Data at rest in Cloudflare D1 is encrypted.
API keys are stored only as SHA-256 hashes with a secret pepper. If our database leaked, the keys in it would not work.
Card details never touch our servers. Stripe's Checkout page handles them, one fee at a time; nothing is stored for later.
Your Muse stores the API key in its Secure Credentials Store. Give the key to Muse only through that flow, never in plain chat.
Access to production is limited to the operator, protected by two-factor authentication.

No system is perfectly secure. If we discover a breach that affects your data, we will email you without undue delay after confirming it and tell you what happened and what we are doing.

10. Your rights

Whoever you are and wherever you live, you can ask us to:

Access: tell you what we hold about you.
Export: send you a copy in JSON.
Delete: erase your data, subject to the accounting records noted in section 8.
Correct: fix a wrong email or a wrong finding.

Email hello@duesback.com from the address on your account. We answer within 30 days, usually much sooner. We do not charge for these requests and we do not treat you differently for making them.

California residents. Duesback is currently below the thresholds at which the CCPA/CPRA applies to a business (annual revenue, number of consumers, and share of revenue from selling data). We honor access, deletion, correction and export requests from everyone anyway, and we do not sell or share personal information as those laws define it.

11. Children

Duesback is for adults. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, email us and we will delete it.

12. Cookies and the website

The duesback.com website sets no cookies of its own; there is no sign-in. Stripe sets its own cookies on its payment form. We do not run third-party analytics or ad trackers.

13. Changes to this policy

We will post changes here and update the effective date. If a change reduces your rights or expands what we collect, we will email you at least 14 days before it takes effect.

14. Contact

Duesback hello@duesback.com https://duesback.com