Direct answer

Delete the client material on a written list, after final payment. Keep your business records and the delivery record itself.

The request is usually made in good faith: the client wants their material contained, and delete everything sounds like the tidy version of that. Agree to the tidy version literally and you delete the one thing that protects you both: the record of what was delivered, when, and in what state. Months later, a dispute about what the work contained, a tax question about the income, or a claim that something was never delivered lands on the person who kept no proof. The working answer sorts your copies into three piles before anyone deletes anything. Client confidential material can go, on a written list, after final payment clears, confirmed with a dated deletion note. Your business records stay, because the law and your own protection both expect them. The delivery record stays, because deleting your only proof of delivery is the real risk hiding inside a reasonable sounding request. This page gives you the sort, the order, and the wording.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 18, 2026. First published November 18, 2026. The records quoted below are real and public, read back from the live service on November 18, 2026.

Step 1. Sort everything into three piles before you agree to anything

Pile one is client confidential material: their source files, their data, their internal documents, drafts built on their material, anything whose value is that it is theirs and not public. This pile can be deleted, and for genuinely sensitive material it often should be. Pile two is your business records: the agreement, the invoices, the payment records, your correspondence about scope and price. These are not copies of the work; they are the records of your business, they underpin your tax filings, and no delivery term should reach them. Pile three is the delivery record itself: what was delivered, the list of files and versions, the timestamps, the acceptance state. This pile is small, it contains the fact of delivery rather than the client material itself, and it is the pile that settles every later question about whether the work arrived and what it was. Most delete everything requests are really about pile one. The reply that works names all three piles, offers pile one properly, and keeps piles two and three without drama.

Step 2. Follow the order: final payment first, written list second, deletion third

Never agree to delete before final payment clears. While any payment is outstanding, your copies are part of your leverage and all of your protection, and a client who has your deletion and still owes you money has been handed a one sided position neither of you intended. The order that protects both sides is simple. One: delivery is made and accepted, and final payment clears in full. Two: the client sends the deletion list in writing, naming the categories of material to be deleted, so the scope is a list and not a phrase. Three: you delete the listed material from the places you control, and confirm with the dated deletion note in step 4. If the client needs deletion earlier for a genuine security reason, the middle door is a partial one: delete the most sensitive category now against the written list, with the rest following payment, and say exactly that in the reply. What never moves is the principle: deletion is a closing step of a finished, paid job, not an opening concession on a live one.

Step 3. Know the exceptions inside pile one, and say them out loud

Even inside the deletable pile there are honest exceptions, and naming them in advance is what makes your yes trustworthy. Backups: material inside routine backups may persist until those backups rotate, so state the rotation window, for example deleted from working storage now and from backups within 30 days as they cycle. Shared systems: copies inside email threads or collaboration tools the client themselves controls are the client copy to manage, and your deletion covers the storage you control. Legal holds: if a dispute or a legal duty to preserve exists, deletion pauses until it lifts, and saying so is compliance, not reluctance. None of these exceptions is a loophole to keep the work; each is a fact about how storage works, stated before deletion so the deletion note in the next step can be precise. A client with a real confidentiality need prefers a precise deletion over a sweeping promise that quietly cannot be true.

Step 4. Keep the delivery record as its own thing, and show the client what that means

The delivery record is not a copy of the work, and showing the client its shape usually ends the argument. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show what a delivery record holds:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read what is actually there: a status, a decider, a date, a release state, and step counts, 4 steps checked on the accepted record, 5 on the pending one. That is a record of the delivery event, not a stash of the client material, and it is the record that protects the client too: it proves what they received and accepted, which is their evidence if a third party ever questions the work. Offer it in those terms. The files go; the fact of delivery stays, for both of us. A client who still wants the record itself deleted after that explanation is asking you to work unprotected, and that is a different conversation, priced and decided as its own risk, never folded into a tidy up request.

Step 5. Confirm with a dated deletion note, and use this reply wording

The deletion note is short and dated: On [date], following final payment on [date], I deleted the following categories of your material from the storage I control: [list]. Routine backups containing this material rotate out within [30] days. Retained, as business and delivery records: the agreement, invoices and payment records, and the delivery record for this job, which records what was delivered and accepted without holding your working files. The reply to the original request follows the same shape in miniature: Happy to delete your working material once the job closes. After final payment clears, send me the list of categories you want deleted and I will delete them from my storage and confirm with a dated note. I keep the agreement, the invoices, and the delivery record itself, as every business does, because those are the proof of the job for both of us. Every sentence is doing a job: yes to the real need, a clear order, a written list, and the retained piles named before anyone can call them a surprise.

Honest limits

This page is general information about handling a deletion request, not legal advice: a signed agreement or a data protection law may impose specific deletion or retention duties that govern over the defaults described here, and regulated material, health, financial, or personal data especially, deserves advice for your situation. If your existing contract already promises full deletion, that promise is the starting point and any change is a negotiation, not a unilateral carve out. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove deletion happened, which is why deletion rests on the written list and the dated note, and the delivery record rests on its own receipts.

Step 6. Set the term in the next agreement, so deletion is a clause and not a surprise

Every element of this page belongs in your standard terms as one short clause, agreed when nothing is sensitive yet. On final payment, the provider will delete the client working files listed in writing by the client from storage the provider controls, confirmed by a dated note, with backups rotating within a stated window. The provider retains the agreement, invoices, payment records, and the delivery record for the job. With that clause signed in advance, a deletion request stops being a test of trust at the end of a job and becomes a closing step both sides already expect. The clients who care most about confidentiality are the ones most reassured by seeing the term written down before the work starts, because it shows deletion was your practice, not a favour extracted at the end.

Frequently asked questions

My client asked me to delete all my copies of the work after I deliver it. Should I?

Delete one pile, keep two, and follow a strict order. Client confidential material, their files, data, and drafts built on their material, can be deleted, and often should be. Your business records, the agreement, invoices, and payment records, stay: they are your tax and business records, not copies of the work. The delivery record stays too, because it records what was delivered and accepted without holding the working files, and deleting your only proof of delivery is the real risk in the request. The order is final payment clears first, the client sends the deletion list in writing second, you delete the listed material from storage you control third, and confirm with a dated deletion note that names what was deleted and what was retained.

Can I keep any copies of client work for my records?

Yes, the records of the job, as distinct from the client material itself. Keep the agreement, the invoices, the payment records, the scope correspondence, and the delivery record showing what was delivered, when, and its acceptance state. Those are the documents that answer a tax question, a late payment claim, or a dispute about whether the work arrived, and keeping them is ordinary business practice the client also benefits from, since the same record proves what they received. What you do not keep under this heading is the client working material itself, their data and source files, once deletion has been agreed and the job is paid and closed. The line is between the fact of the job, which you keep, and the substance of their material, which you can delete.

What if my contract already says I will delete everything?

Then the contract is the starting point, and you honour it or renegotiate it openly, you do not quietly carve out exceptions after signing. Read the clause closely first: many deletion clauses cover client data and working files and were never drafted to reach invoices, tax records, or a delivery record, in which case keeping those is compliance, not breach. If the clause genuinely reaches everything, raise the retained records before delivery, in writing, and propose the narrow amendment: working material deleted on the written list after payment, business and delivery records retained. A client who refuses any retention at all is asking you to carry unprotected risk, and that belongs in the price or in a decision to decline, not in silent non compliance with a clause you signed.

When should deletion happen, before or after final payment?

After, always. Deletion is a closing step of a finished and paid job. Before final payment clears, your copies are part of your protection in the exact period when disagreements about the work are most likely, and deleting early hands the client a one sided position: your proof gone, their obligation outstanding. The sequence to state in your reply is delivery and acceptance, final payment cleared, the client deletion list in writing, deletion from the storage you control, and a dated note confirming it. If a client has a genuine security need for earlier deletion of one sensitive category, that can be done as a stated partial step against the written list, with the remainder following payment as agreed.

How does a job record help when a client asks me to delete my copies?

It separates the proof of delivery from the work itself, so you can delete the material without deleting the evidence. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and the delivery record holds the status, the decider, the date, and the step counts rather than a stash of client files, so it can be retained honestly while the working files are deleted on the written list. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next delivery on one record, so a deletion request at the end is a tidy up of files, never a threat to your proof: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related