On Tuesday, a customer emails you: Please delete my account and everything you have on me. You do it quickly, because it's the right thing to do and you'd like to be someone who answers privacy requests the same day. You wipe the profile, the usage logs and the saved preferences. You send a polite confirmation.

On Thursday, a Stripe dispute arrives for the charge from three weeks ago.

You open the evidence form and find that most of what would have won it is gone. You erased it yourself, in good faith, two days earlier. Nobody did anything wrong, and you still lose.

This happens more often than merchants admit. Wanting to be a good steward of someone's data and needing to defend yourself against that same person's dispute can feel like opposite impulses. They aren't, but you have to decide how to reconcile them before the email arrives.

Why deletion requests and disputes cluster together

A deletion request is often a sign that someone is mentally closing a chapter. They've decided they're done with you, and wiping the account is part of walking away. A chargeback is sometimes the next step, because it's the only way they know to get the money back.

The two events aren't always connected. Many people ask for deletion out of plain privacy hygiene. But when they do arrive together, the order matters. If the deletion comes first, your evidence is thinner by the time the dispute lands. If you treat every deletion request as an immediate, total purge, you've built a process that quietly removes your defense exactly when you're most likely to need it.

A dispute is decided on documentation: who the customer was, what they agreed to, what they received, and what they did with it. Delete all of that, and the reviewer sees a charge with no story around it. Reviewers tend to resolve a blank file in the cardholder's favor, because the cardholder is the one with a story.

What privacy law actually asks of you

This is not legal advice, and your jurisdiction and situation matter. But the broad shape is worth knowing, because it's less absolute than most people assume.

Under the EU's GDPR, the right to erasure in Article 17 is real but not unlimited. Article 17(3)(e) says the right doesn't apply to the extent that processing is necessary for the establishment, exercise or defence of legal claims. A pending or foreseeable payment dispute is a plausible example of exactly that. Separately, many jurisdictions require you to keep financial and tax records for a set period regardless of what a customer asks. Several other privacy regimes, including California's, contain comparable carve-outs for completing a transaction and complying with legal obligations.

The same laws also impose principles pointing the other way. GDPR's data minimization and storage limitation principles mean you shouldn't keep everything forever, and you shouldn't keep data you have no reason to keep. So the honest position isn't "keep it all" or "delete it all." It's: keep the narrow set of records you can justify, for a bounded period, for a stated purpose, and delete the rest.

The idea: separate the profile from the proof

Most of what you store about a customer is profile data: preferences, browsing behavior, marketing tags, extra personal details, content they created. Almost none of it helps in a dispute.

A small slice is transaction proof: the record that a specific payment happened, who authorized it, what they were sold, and that it was delivered or used. That slice is what a reviewer reads.

If your system treats these as one lump, a deletion request forces a choice between destroying your defense and ignoring the customer. If you've already split them, the choice goes away. You erase the profile completely and keep a small, locked-down transaction file with a documented reason and an end date.

In practice, the transaction file might hold:

  • The charge ID, amount, date and billing descriptor
  • The order or plan details and the price shown at checkout
  • The timestamp of acceptance of your terms, and which version
  • Proof of delivery or access (a shipment record, or a dated login or usage event)
  • Your correspondence about the sale, including the deletion request itself

You don't need their browsing history, their uploaded files or their full activity feed. Keeping less is both safer for them and cleaner for you.

Why the deletion request is itself evidence

There's a quieter point here. If a customer says "delete my account" and doesn't mention a problem with the purchase, that email is a data point. It can show they knew the account existed, had used it, and chose to close it rather than raise a complaint. It may also show the date they stopped using the product.

Keep that message and your reply. It becomes part of the timeline.

The flip side is that a deletion request sent after a dispute is a different situation. If you already know a dispute is open, you have a clearer, documented basis for holding relevant records while it's resolved. Tell the customer what you're deleting now and what you're retaining, and why. Plain, calm wording usually works. Something like: "We've deleted your profile and activity data. We're keeping your payment and order records for a limited period, as we may need them to respond to a payment dispute or meet legal obligations. They'll be deleted on [date]."

That reply is honest, and it also reads well to a reviewer if it ever lands in the file.

Your next moves

  • Today, write your retention split. On one page, list what you store about a customer and sort each item into "profile" or "transaction proof." Anything you can't justify keeping for a dispute or a legal duty is a candidate for earlier deletion.
  • Add a pause step to your deletion workflow. Before anyone is wiped, check Stripe for an open dispute, an inquiry or an early fraud warning on that customer. If one exists, don't purge the transaction proof yet.
  • Export the proof before you delete the profile. When a deletion request arrives, save the charge record, the terms-acceptance timestamp, the delivery or usage evidence and the email thread into a single locked folder, then proceed with the rest.
  • Set a retention clock. Pick a period that covers how long cardholders can dispute a charge (often a few months, but it depends on the card network and issuer) and put an automatic deletion date on that folder. Write the date down.
  • Reply to deletion requests in plain words. Tell the person what's gone and what's kept, and why. Have your privacy contact or a lawyer review the template once, then reuse it.

The one-week window nobody plans for

The cruel part of this scenario is how little time you have. Stripe's response deadline for a dispute is often as short as a week or so from the notice, and your evidence has to be assembled in that window. If you discover only then that the records are gone, there's nothing to rebuild.

That is why the split matters more than any single piece of evidence. A process that preserves the narrow proof by default means a deletion request on Tuesday doesn't cost you a dispute on Thursday, and it doesn't cost the customer any privacy they were entitled to.

Where Argeback fits

The pattern underneath all of this is that the best chargeback defense is assembled before anyone is angry, and deadlines punish whatever you postponed. Argeback pulls your Stripe disputes into one place, drafts a response from the evidence you actually have, and files it before the 7-day deadline, all from your phone. It works best when the transaction proof is already there to draw on, which is why the habit of keeping a small, deliberate evidence file is worth building whether or not you ever use it. If you'd like help turning that file into a filed response on a day you're nowhere near a laptop, you can see how it works at argeback.lumenlabs.works.