Six user submission mistakes a lookalike desk makes, and the safeguard for each

A celebrity lookalike desk receives photos and claims from readers. Most mistakes made with them are handling errors, not errors about faces: repeating a claim, assessing it, or keeping it when the desk should not. Six recur. Each section below names the mistake, why it hurts and the safeguard, and the table routes a message to the first row that fits.

Mistake one: engaging with a request that deserves none

For example, a reader sends a photo of a stranger taken on a train and asks the desk to say which actor the stranger resembles. Answering, even to decline politely, tells the sender that the desk read and understood the message and turns a silent decision into an exchange.

The safeguard is a brief refusal that does not confirm or debate the claim, followed by deletion. A threat or description of a crime belongs with the appropriate authorities, not in a website archive, and should not be kept as the desk's own record.

• Rule of thumb: Refuse briefly, avoid discussion, and delete.

Mistake two: repeating the name or pairing in the refusal

A reply such as "we cannot say your neighbor looks like a named actor" restates the pairing. The sender already knows the submission; the desk's copy is a new written claim under its name that can be stored, forwarded or captured in a screenshot, and it names a private person in the process.

The safeguard is to decline by category: "we do not assess resemblances between private people and public figures." Ordinary image mistakes reach a desk in volume, so the standing reply must cover everyday cases, not only unusual ones.

• Rule of thumb: Refuse the category, not the named pair.

Mistake three: treating a public profile as permission

A photograph on a public profile is visible to everyone, but visibility is access, not permission. Three separate questions are in play. The photographer or poster usually holds the copyright, and a copyright holder can send a takedown notice under the DMCA (17 U.S.C. § 512) if the desk republishes the picture.

The person pictured has a separate claim. State right-of-publicity laws, such as California Civil Code § 3344 and New York Civil Rights Law §§ 50-51, restrict commercial use of a name or likeness without consent, with exceptions that differ by state. Our state-by-state guide to right of publicity sets out the differences.

The third is consent. As with consent from only one side of the frame, a sender can speak for the person in their own photograph, not for the second person named in the message. The submission rules apply that limit clause by clause.

Images of children need a stricter line. The FTC's COPPA rule (16 CFR Part 312) governs online collection of personal information from children under 13, and photographs of children count. A desk should refuse any submission that shows a child and delete it without naming the child.

• Rule of thumb: Public visibility does not grant permission.

Mistake four: asking for more identifying detail

A desk that cannot judge a submission is tempted to ask where the photo was taken, who the person is or whether another picture exists. Each question collects details about someone outside the conversation, and a late answer enlarges the record after the desk has already decided it wants no more.

The safeguard is to decide from what arrived or decline. Fairness does not require a longer email thread, and needing another person's image, background or location is the signal to stop.

• Rule of thumb: Do not ask for details about someone outside the exchange.

Mistake five: giving a verdict on the pair

A reply that says "the eyes are similar, the jaw is not" feels harmless. It is a verdict, and it adds confidence to the sender's first impression. Two photographs supplied without their capture conditions cannot establish a resemblance.

The safeguard is to explain the mechanism, not the pair. Image conditions limit what a side-by-side can show, and that general limit is the whole answer. Do not name shared traits or suggest another test.

• Rule of thumb: Explain the mechanism, not the submitted pair.

Mistake six: keeping what was refused

Refused files saved "just in case" become a store of faces and names about people who were never asked. If the desk runs a face-matching tool on uploads, it may also hold biometric data. Illinois's Biometric Information Privacy Act (740 ILCS 14) requires a holder of face-geometry scans to publish a retention schedule and destroy them when their purpose is met or within three years of the person's last interaction, whichever is first.

California residents can also ask a business to delete their personal information under the CCPA. A workable policy, for example: delete refused files the same day, empty the mail trash, and keep a log line with only the date and refusal category. Whether a state law reaches a given desk depends on its facts, so confirm with counsel.

Confirm the action in plain language by telling the sender the file has been deleted. That direct assurance settles the sender more effectively than a policy reference. The desk's published user submissions policy should say the same thing.

• Rule of thumb: Refusal means deletion, followed by confirmation.