On this page
- Research question and scope
- Why deletion is a contract question
- Defining the audit fields
- Finding the deletion clause and the schedule
- Mapping the client data that must be deleted
- Separating deletion from retention obligations
- Checking backups and residual copies
- Asking for deletion evidence
- Following subcontractors and third-party services
- Checking account and billing ownership
- Limitations and threats to validity
- Reporting and next action
- Sources
- Related Research
Research question and scope
This audit asks whether an outsourced website maintenance vendor documents how it deletes client data when the contract ends. The unit of analysis is the deletion clause, the vendor's data-handling description, the exit checklist, and the evidence the client receives at handover. The retrieval date is recorded so the finding describes a specific version of the agreement. The audit does not test the vendor's storage systems directly, because a client review normally works from documents and a supervised confirmation.
The scope covers the production website, its database, uploaded files, form submissions, analytics exports, support tickets, and any working copies the vendor holds. It includes the vendor's own project management and backup systems, plus the third-party services the vendor uses to host or operate the site. The audit separates data the vendor controls from data the client owns directly in a platform account, because the exit path differs for each. It also records any legal retention obligation that may prevent immediate deletion.
Why deletion is a contract question
A maintenance relationship accumulates more client material than the website itself. The vendor may hold database exports, staging copies, design files, email threads, access credentials, and screenshots of customer records. When the relationship ends, each of those items needs a destination: deleted, returned, or retained under a stated rule. A contract that is silent on the point leaves the client dependent on the vendor's habits after the invoice stops.
The risk is not only a data breach. A former vendor may keep an old copy of a site that still contains personal data, a pricing page, or an unreleased product. That copy can surface in a backup, a portfolio, or a support request years later. Deletion is also part of a clean handover, because the next vendor needs to know which systems still contain client material. The audit turns a vague promise into a list of systems, dates, and evidence.
Defining the audit fields
The audit uses seven fields: data inventory, deletion trigger, retention exceptions, backup treatment, subcontractor coverage, deletion evidence, and account ownership. The data inventory names the categories the vendor holds and where each one lives. The deletion trigger states the event that starts the clock, such as the contract end date, the final invoice, or the client's written request. Retention exceptions name any category the vendor must keep and the rule that requires it. Each field is coded present, partial, or absent, and the coding note quotes the supporting clause.
Backup treatment explains whether copies age out on a schedule or need a separate deletion step, while subcontractor coverage names the other companies that hold client data and how their deletion is confirmed. Deletion evidence names the artifact the client receives, such as a signed certificate, a screenshot, or a date-stamped export. Account ownership names the client or vendor entity that controls each system and billing relationship. A clause that promises deletion but covers none of these fields is a statement of intent, not an exit procedure.
Finding the deletion clause and the schedule
Start with the master agreement, the data-processing addendum, and the statement of work. Search for delete, destroy, return, retention, transition, and exit. Record every document that makes a promise, including a security page that describes deletion practices the contract does not repeat. If the documents disagree, treat the signed agreement as the governing text and record the public claim as a discrepancy for the next review.
Then locate the schedule. A clause may say the vendor deletes data within thirty days of termination, or it may say the client must request deletion in writing. Those are different obligations, and the client needs to know which one applies. Check whether the clock starts at notice, at the end of the notice period, or at final payment. Put the date on a calendar with the owner responsible for confirming it, because an unclaimed deadline is easy to miss after the relationship has ended.
Mapping the client data that must be deleted
Build the inventory from systems rather than from document titles. List the database, media library, form submission store, support inbox, analytics account, backup destination, and project workspace. Ask for working copies as well as production systems, because a database dump or an old staging site is easy to overlook. For each system, record the vendor's role, the data categories it holds, and whether the client can access it directly. A system the client can open without the vendor is easier to close, but it still needs a decision.
Separating deletion from retention obligations
Not every record can be deleted on the last day. Tax rules, accounting practice, dispute holds, and sector regulation may require the vendor or the client to keep invoices, contracts, and certain transaction records for a stated period. The audit should name those categories and the rule behind each one, rather than treating every retained file as a failure. The client's counsel or finance team decides which obligations apply.
The important distinction is between a required record and a convenience copy. An invoice kept for accounting is different from a full database export kept because it is easier than deleting it. Ask the vendor to separate the two in the exit plan and to state the destruction date for each retained category. If a legal hold applies, record who issued it and when it is expected to end. A retention rule without an end date becomes permanent by default.
Checking backups and residual copies
Backups are the most common gap in a deletion claim. A vendor may delete the live database and still hold nightly copies for weeks or months. Ask how the backup rotation works, how long copies survive, and whether a deletion request reaches the backup system. If the vendor cannot remove individual records from backups, record the date when the last copy will age out and the method used to prevent a restore.
Residual copies also appear in snapshots, staging environments, and search indexes. Ask whether the vendor will remove the staging site, revoke preview links, and request removal of any indexed pages. Check whether a content delivery network or a third-party form service holds a copy that the vendor does not control. The exit plan should name each system and the person who confirms its deletion.
Asking for deletion evidence
A written assurance is weaker than an artifact. Ask for a deletion certificate that names the systems covered, the date of deletion, the person who performed it, and any category excluded under a retention rule. A certificate does not need to expose customer records. It needs enough detail that a later reviewer can tell what was deleted and what remains. If the vendor cannot issue a certificate, ask for a dated screenshot or a system-generated confirmation.
The client should also verify what it can see. Log in to the hosting panel, the form service, and the analytics account to confirm that the vendor's access has been removed and that the data is gone or scheduled for removal. Record the date and the account used. This step is not a substitute for the vendor's evidence, but it catches the case where access is revoked while a copy remains in a system the client forgot.
Following subcontractors and third-party services
A maintenance vendor often relies on other companies for hosting, backups, email, or monitoring. Each of those companies may hold client data under its own terms. Ask the vendor to list the subcontractors that touch the site and to confirm how each one handles deletion at the end of the arrangement. The list should match the subprocessor disclosure the vendor provides during the contract, if one exists.
For services the client owns directly, the exit step is a transfer of ownership rather than a deletion request. For services the vendor owns, the client needs a deletion confirmation or a migration plan. Check whether a subcontractor's retention policy outlasts the main contract and whether the vendor can compel deletion on the client's behalf. If the answer is unclear, record the dependency and ask for it in writing before the final invoice is approved.
Checking account and billing ownership
Deletion is harder when the vendor controls the account and the client does not. Ask who owns the hosting, domain, backup, analytics, and form accounts, and whether the client can open each one without the vendor. An account registered to the vendor may disappear when the relationship ends, taking the data and the recovery path with it. The audit records the owner, the billing relationship, and the recovery contact for each system.
Where the client owns the account, the exit step is to remove the vendor's access and confirm that no shared credentials remain. Where the vendor owns it, the client should request a full export before deletion and a written confirmation afterward. Check that multi-factor authentication is enabled on the accounts that remain. Ownership is not an administrative detail at exit, because it determines whether the client can verify the deletion at all.
Limitations and threats to validity
The audit works from documents and a supervised confirmation, so it describes the evidence the client can see rather than the vendor's internal storage. A vendor may delete data correctly and still produce a weak certificate, and the audit will score the evidence low. A single exit review cannot prove that every copy is gone. State that limit in the report.
The audit cannot decide which retention obligations apply to the client's business. That decision belongs to the client's counsel, finance team, or sector regulator, and it may change by record type and jurisdiction. Keep the technical findings separate from the legal decision about what must be kept. If the client has never mapped its obligations, the audit can expose the gap, but it should not invent a retention period on the client's behalf.
Reporting and next action
Report one row per system with the data category, owner, deletion trigger, retention exception, backup treatment, and evidence received. Quote the contract clause and the vendor's current description in an appendix, and note any difference between the two. Agree two changes with the vendor before the final payment: a dated deletion certificate covering every system in the inventory, and a client-held export of any data the client needs to keep. Keep the rows in the same order as the system inventory so a later reviewer can compare exits.
The NIST Special Publication 800-88 Revision 1 provides guidance on media sanitization and destruction. The NIST Privacy Framework describes how organizations can govern data handling across a lifecycle. The FTC's data security guidance explains why reasonable disposal belongs in a security program. The EU General Data Protection Regulation sets deletion and processor obligations where it applies. Keep the retrieval date with each link so a later reviewer can tell which version supported the coding.
Sources
The sources below describe data disposal, privacy governance, and security practice. They do not report a result for this sample, and each was checked on November 20, 2026. Use them to justify the fields in the audit, and keep the local vendor table separate from these references. Record the retrieval date beside each entry when the table is reused.
- NIST, Special Publication 800-88 Revision 1, Guidelines for Media Sanitization
- NIST, Privacy Framework
- FTC, Data Security
- EUR-Lex, Regulation (EU) 2016/679
- NIST, Special Publication 800-53 Revision 5
Related Research
- Auditing Whether an Outsourced Website Maintenance Vendor Documents Backup Frequency, Retention, and a Restore Test covers the copies that survive after live data is removed.
- Auditing Whether an Outsourced Website Design Vendor Discloses Subprocessors and Notifies Clients Before Adding One shows how to trace the other companies that may hold client data.
- Auditing Whether an Outsourced Website Vendor Documents the Handoff of Domain and DNS Control addresses the account transfer that sits beside data deletion.
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff