What should you do when a model reference is withdrawn?

Record the request and assign a responsible owner

Imagine an illustrative accessories campaign using an authorized photograph of a real adult model. The person later asks the brand to stop using that reference. A designer sees the request, but scheduled posts and another contractor's image exports still depend on it. The first task is to connect the request to actual work, not generate a replacement face immediately.

Record when the request arrived, the identity of the reference and the stated scope in a suitable private location. Assign the rights or privacy owner to assess the agreement and applicable obligations. This guide is an operational checklist, not a legal determination that every permission has the same withdrawal or retention consequences.

First clarify whether the person requests no new campaigns, removal of named public placements, deletion of stored data, or several of these. Do not interpret an unclear message as permission to continue or as an instruction to erase all records immediately. Preserve the request privately and ask the owner to resolve its scope. Creative staff can apply an interim hold without inventing a universal legal outcome.

Hold new uses while the scope is reviewed

Record affected task identifiers and their current states before doing anything else. Do not submit a replacement request just because the original is slow or uncertain. A queued or processing provider request, a completed output and a scheduled publication are different objects. Check available task controls or support; do not promise that an in-flight request can always be cancelled or recalled.

The ICO’s valid-consent guidance concerns UK GDPR consent. Its withdrawal guidance says processing relying on consent must stop after withdrawal, while prior consent-based processing is not retrospectively unlawful. It warns against switching basis to continue that same processing; retention for a different purpose can require a separate justified basis. Both pages were checked October 21, 2026 and carry an under-review notice.

Those conditions are not a determination that every image agreement, region or legal basis follows one deletion process. The responsible owner must identify the applicable framework, processing purpose, agreements and any separate retention duties. The hold-and-inventory steps here are operational recommendations while that assessment is made.

Build a reference-change response table

List external copies as well as CartVisual results: editor projects, shared folders, retailer media and advertising accounts. An output may have been cropped or renamed, so use the campaign lineage and thumbnails to locate it. Mark unknown destinations for investigation instead of reporting the response complete.

Build the inventory from the source-to-output lineage, not the current library alone. In the present implementation, generation records can retain their own source or identity snapshots. Deleting the saved model entry therefore cannot be reported as deleting those job snapshots or files already downloaded by another team.

Act on decisions without claiming automatic removal

Fictional response exercise, not an executed takedown: the accessories team finds a running task, a completed square image, a scheduled ad and a retailer crop. The operator records the running task as unresolved until its state is known. The creative owner holds the square image from new use. The ad publisher records the actual scheduling change. The retailer owner requests or makes the required replacement and checks the retailer’s response.

If the saved reference is deleted but the retailer crop remains visible, report the two states separately. “Library entry removed” is a verifiable local observation; “all uses withdrawn” is unsupported while the external placement is unresolved. A support ticket is evidence of a request, not of completed removal.

Use authorized operators in each actual system. Do not publish a person’s identity documents in screenshots; follow the private-support evidence boundary. Retain only the request and action evidence the responsible owner instructs you to keep, with its purpose and access restrictions.

Approve a replacement and close the usage record

A replacement needs its own authorized source, public role and output review. Do not blend the withdrawn image into a new face to preserve familiarity. Record a new reference identifier and connect only the newly approved uses to it; the version handoff method helps keep the two lineages separate.

Close each inventory row with the owner’s required action, actual observation and outstanding limitation. A row may be completed while another remains pending; do not hide the remaining retailer, contractor or archive question behind one global green status. This checklist neither guarantees third-party erasure nor determines legal compliance.

Reference-change response record

Copy this external record for one actual asset and destination. Fill it from real observations; leave unknown items pending. The empty cells are not completed checks.