Security & data

What we hold

• Dispute materials you export and send us. The dispute record or screenshots from your Stripe Dashboard (dispute and charge IDs, amount, reason, due-by date, and the customer name, email, and billing details Stripe shows), the receipt or invoice, access and usage logs, account and license records, delivery emails, customer communication threads, and your policy pages.
• Your business contact details — name, business name, email address, and our correspondence with you.
• Billing records — fee invoices for won disputes and their payment status.

Materials sent for one dispute are used for that dispute only: no marketing to your customers, no profiling, no combining across merchants, no sale or sharing, and no AI training on your data.

What we never accept

Your Stripe password, your secret API key (sk_), restricted API keys, bank credentials, full card numbers or your customers' full payment details, or access to your inbox or helpdesk. We do not ask for them and will refuse them if offered, on any path. In the case application, file names, form fields and the contents of text files (.csv, .txt, .eml) are checked and anything that looks like one is blocked — it isn't stored, and we tell you what to remove. PDFs, images and zip files aren't checked automatically, so look them over before you upload.

Where it lives

Function	Provider	What they process
Website hosting and email routing	Cloudflare	Site requests; incoming email to our addresses, in transit
Case application: hosting, database, and file storage	Cloudflare (Workers, D1 database, R2 file storage)	Your account email and sign-in records; your case details, case status, notes, and fee invoice records (D1); the case files you upload (R2, private storage)
Email inbox	Google (Gmail)	Email you send us, including attached case files
Outgoing email	Resend	Messages we send you (no case files)
AI-assisted packet assembly, under human review	Anthropic (Claude models), via its commercial API	Case materials in transit while a packet is assembled; no training on our data under the API terms we use
Invoices and payment	Stripe	Billing records; your card details never reach us

Encryption

Data is encrypted in transit. Data stored in our case application — the D1 database and R2 file storage — is also encrypted at rest by Cloudflare, which encrypts all D1 and R2 data with AES-256. That at-rest statement covers the application stores only: the email path (files you attach to mail) is protected in transit and sits in the Gmail inbox named above until it is deleted under the procedure below. Access is limited to the people and systems working on your packets. No system is perfectly secure; we notify you within 48 hours if we learn of unauthorized access to your data.

The website

This site sets no cookies and loads no third-party scripts, fonts, or analytics — every file it loads comes from this domain. The free Dispute Evidence Checker runs entirely in your browser: your checklist answers, dates, and score stay on your device. The site sends a small number of anonymous usage events (page viewed, checker started, result shown, with the dispute category) to our own application, never to an analytics company; the full list is in Privacy Policy §2.

Deletion — promise and mechanism

Promise	How it is actually done
Case files deleted within 30 days after the case closes	In the case application, a scheduled job purges closed cases once their 30-day clock runs out and records the purge in an audit row. For material that reached us by email, a written procedure is run by hand at case close: delete every thread and attachment for the case in the inbox, empty them from Trash, and delete any downloaded copies on every machine that touched the case.
All remaining data deleted within 30 days after the agreement ends	Done by hand under the same written procedure; there is no automated path for this yet.
Early deletion on request, confirmed in writing within 2 business days	Done by hand under the same written procedure, started the same day the request arrives. Ask at hello@thechargebackdesk.com.
What we keep	Invoices and the signed agreement, for accounting and legal records. Nothing else.
Your copy	The delivered packet is yours to keep; deleting our copy does not affect yours.

A case closes when you report Stripe's decision, when we refuse or you withdraw the case, or automatically if the outcome is never reported (90 days after submission, or after the response deadline passes on a delivered packet). We email you before the deletion clock runs out.

Legal requests

We disclose data only where we believe in good faith the law requires it (for example, a valid subpoena or court order) or where it is necessary to protect the safety, rights, or property of others. Where legally permitted, we tell you first.

Credentials, if a connected path is ever offered

Today the service works from exports only. If we later offer an optional connected path, it will work only through a restricted key that you create in your own Stripe Dashboard, limited to five permission areas — read and write for disputes and dispute files; read-only for charges, customers, and events — and that you can revoke at any time. That key would be a credential we hold, so before the connected path is offered the Privacy Policy will be updated to say how it is stored, used, and deleted. Even then, nothing is submitted without your explicit approval of that case.

Report a security issue

If you find a vulnerability in this site or in the case application, email hello@thechargebackdesk.com with "Security issue" in the subject line. A person reads it, and we reply to say what we found and what we changed. Please do not include anyone's personal data in the report; a description and steps to reproduce are enough. We have no bug-bounty program and will not pretend to.