Rebuilding image rights records in a creator studio agency handoff case

What to take away

This case is illustrative — Juniper Frame Studio and Northstar Social stand in for a real studio and a real agency — but the records, the law, and the takedown routes below are the ones that apply to any creator studio agency handoff case. Every step is one a studio can repeat with its own documents.

The handoff problem

Juniper Frame Studio ends its relationship with Northstar Social. The agency created several social accounts under an employee's address, stored masters in a personal cloud folder, and sent approvals through chat. The studio has releases in email, but filenames do not match the delivered images.

Northstar supplies a ZIP file containing 1,840 images, 420 short videos, two spreadsheets, and many exports named final. Some folders contain identity documents. Three scheduled posts are due within four days.

The law behind these records

Image rights records are only useful if they point to the legal instruments that create and limit them. In the United States, copyright in a photograph or video is registered with the U.S. Copyright Office, and registration is what lets a creator sue for infringement and ask for statutory damages on a US work. For removal, the standard route is a DMCA §512 notice sent to the platform's designated agent, the agent listed in the Copyright Office's DMCA Designated Agent Directory, identifying the work, the infringing copy, and the complainant's authority to act.

A release is a contract, and it is read against the person's right of publicity, which in the United States is state law. California Civil Code §3344 and New York Civil Rights Law §§50–51 are the best-known examples, and the rules differ from state to state. A usable release names the person, the specific uses, media, territory, and term, the compensation, whether it can be revoked, and the signature and date, with a parent or guardian signing for anyone under 18. Juniper checks every record against those elements instead of treating a filename as proof.

Privacy law sits alongside this. California's CCPA, as amended by the CPRA, gives people the right to know, delete, and correct personal information, which can include images of identifiable people, and for audiences in the EU the GDPR adds a right to erasure. Juniper records which regime applies to which asset rather than applying one rule everywhere.

First-day controls

Juniper pauses the three posts because nobody can connect the exact versions to current approval. It keeps routine, already-cleared posts running. The studio preserves account screens, administrator lists, recovery methods, connected apps, scheduled content, and export logs before making changes.

The team creates an inventory:

Recovering durable ownership

The studio uses each service's official business transfer or administrator process. It does not pose as the agency employee. Northstar adds two named studio administrators, updates authorized recovery routes, transfers billing where supported, and supplies a list of integrations and active sessions.

Google's Workspace administrator help explains how an admin removes a user and transfers that user's Drive files and calendar data to someone else, and Meta Business Portfolio admin roles do the equivalent for Facebook and Instagram pages and ad accounts. Juniper treats both as the model for a handover: ownership moves through the platform's own admin tools as a documented role change, before anything is deleted.

Sorting the assets

Juniper unpacks the export into a restricted intake area and keeps the received ZIP unchanged. It groups exact duplicates, calculates file hashes, and compares near-duplicates visually. No candidate master is deleted during the review.

Each accepted source receives an asset ID. Working edits and platform exports receive version records. The studio links each asset to the creator, present owner, recognizable people, project, release, license, and approval evidence. Identity documents move to a separate restricted repository; the library holds reference IDs.

The two spreadsheets disagree about expiration dates. Reviewers compare them with signed documents and record the controlling date or an unresolved status. They do not average dates or select the longer term for convenience.

Reconstructing approvals

The producer exports relevant chat threads under the agency agreement and indexes each message by sender, date, asset version, proposed use, and conditions. A message saying "looks good" beside a contact sheet is not applied to every crop. The three paused posts receive fresh review after the exact files, captions, products, audiences, and channels are identified.

The agency agreement decides much of this. Juniper reads its termination, assignment, and intellectual-property sections and records the answers: who owns the deliverables, what license the studio keeps, what the agency must return or delete, what transition help it owes, and which state's law governs. Those answers set the deadlines for the rest of the handoff.

Two posts are approved. The third uses a portrait whose release covers an editorial feature, not paid skincare advertising. Juniper replaces it with a product-only image rather than seeking a rushed broad waiver.

Consent can also change. A release may allow revocation, a license may expire, and a person may withdraw permission for uses that have not happened yet. When a signed release is disputed, Juniper stops new publication of the affected asset, keeps the documents and correspondence, and records the question as unresolved until the paperwork or the person's written confirmation settles it.

Building the archive

Juniper selects source masters, executed agreements, approval records, publication evidence, account-transfer records, and the original handoff package for controlled retention. It defines a retention date and access level for each category. Draft exports and duplicate delivery files receive a shorter schedule.

The National Archives describes digital preservation practices that include recorded fixity, tracked file actions, separate public-use copies, sustainable formats, and regular audits. Juniper is not a federal archive, but it adopts proportionate versions of those practices: checksums for retained masters, an action log, separate delivery copies, and scheduled restoration samples.

Completing the exit

Northstar returns the remaining records listed in the contract and identifies files it must retain for a defined legal or accounting reason. It confirms deletion of other client copies after the agreed verification period. Juniper revokes agency roles, direct shares, sessions, API keys, connected apps, devices, and recovery methods. Credentials known to agency staff are rotated.

The closing record lists completed transfers, removed access, retained exceptions, failed imports, unresolved rights questions, and responsible owners. Juniper samples twenty assets and restores five archived records before accepting the handoff.

Takedown routes that work

Three routes do most of the work. Platform reporting tools handle copyright, privacy, and impersonation complaints fastest, but they leave the uploader free to repost. A DMCA §512 notice to the platform's designated agent obliges the platform to act on infringing copies, and it must come from the copyright owner or an authorized agent, identify the work and the copy, and carry the required good-faith and accuracy statements. A right-of-publicity demand under the applicable state statute goes to the publisher itself, and it is the route that reaches a use the copyright owner licensed but the person in the image never agreed to.

Non-consensual distribution often sits outside copyright altogether, because the uploader may own the copyright. There, the platform's privacy, harassment, and non-consensual imagery policies plus a state-law right-of-publicity claim do the work, and the studio's record of consent, or of its absence, is the evidence that decides the case. Juniper files each request from the studio's own account, quoting the asset ID, the release scope, and the registration record, so the recipient can match the complaint to a document rather than to a story.

Result

The studio recovers durable account control and a searchable rights record without claiming that every historical use was authorized. It keeps fourteen assets restricted pending document review and assigns deadlines rather than quietly returning them to circulation.

Common questions

Why not delete the agency accounts immediately?

Immediate deletion could strand files, recovery controls, logs, drafts, and evidence. The studio first preserves and transfers authorized business records, then removes access.

Did a hash establish copyright ownership?

No. It helped distinguish file contents. Ownership required separate evidence.

Did the export spreadsheet prove release scope?

No. Reviewers checked it against executed documents and recorded conflicts.

Was every old asset cleared?

No. Unresolved assets remained restricted with named questions and review dates.