TikTok bans synthetic private individuals
TikTok prohibits realistic synthetic media of real private individuals outright, so a label is not a defence. A consent-first workflow for real-person likeness.
Nearly every AI content policy anyone has read in the last two years works the same way: make what you want, disclose it, and the disclosure resolves the problem. Two years of platform announcements have trained the reflex that labelling is the answer. TikTok has one category where it is not the answer, and where reaching for it means you have already lost.
Per TikTok's own newsroom material on AI-generated content, realistic synthetic media depicting real private individuals is prohibited. Not labelled. Not restricted. Not eligible for reduced distribution. Prohibited, and the label does not change that. This is a rule about whether the content may exist on the platform, and the disclosure machinery sits entirely downstream of it.
A gate, not a label
The distinction is structural and it changes where the decision belongs in your process.
A labelling rule is a publishing decision. You make the asset, then you decide what to attach to it. If you get it wrong you fix the attachment. The asset is fine.
A prohibition is a generation decision. If the output is a realistic synthetic depiction of a real private individual, there is no attachment that makes it publishable, and the money and time that went into producing it are spent. The only place to catch it is before you generate, which is upstream of every part of the compliance process most teams have built.
That is the whole practical point. Everything else in this post follows from moving the check earlier.
TikTok is not doing something eccentric here. It also reads C2PA Content Credentials on upload and applies its own invisible watermarking, and it sits on the C2PA steering committee, so it has a fuller labelling apparatus than most platforms. The prohibition exists alongside all of that, which tells you the two mechanisms are answering different questions. Provenance answers "what is this." The prohibition answers "may this exist here."
The line between private and public, and why you should not stand on it
The rule turns on the person being a private individual. Public figures are handled under a different set of rules — restrictions around endorsements and political content rather than a flat prohibition.
Do not build your workflow on the assumption that you can classify people accurately. The categories are the platform's, applied by the platform, and the boundary is genuinely hard: a person with 40,000 followers, a local business owner, an employee who appears in company marketing, a semi-known figure in one professional niche. Nobody outside the platform can predict where each of those lands, and getting it wrong is not a labelling error, it is a removal.
The workable posture is to treat everyone as private unless they are unambiguously a public figure, and then note that "unambiguously public" only moves you into a different set of restrictions, not into permission. Neither path leads to "generate freely."
There is a second trap in the same area. A great deal of likeness thinking is calibrated on fame, because right-of-publicity law historically attached to the commercial value in a well-known identity. Regulation has been moving the opposite way. Denmark's copyright amendment, as described in the European Parliamentary Research Service briefing, is drafted to cover all natural persons rather than only recognisable ones, and platform rules like this one point the same direction. The instinct that says "nobody knows who this is, so there is no claim" is aging badly on both the legal and the platform side.
Consent-first, in the order the steps actually have to happen
The failure mode I see most often is a pipeline where consent is a publishing gate. Someone checks for a release just before the asset ships. That ordering fails against a generation-side prohibition, because by then the prohibited thing has been made.
Reordered:
- Classify the input before you generate. For every asset, one field: does a real, identifiable person's likeness or voice appear anywhere in the inputs? Reference photo, face scan, voice sample, a prompt that names a person. This is the only question that routes everything downstream, and it takes seconds to answer at brief stage and is unanswerable six weeks later.
- Get consent covering the specific use, before generation. Not a generic model release. What is being generated, in what contexts it may appear, for how long, and whether it may be modified. Usage rights in creator contracts is the practical drafting version. Retroactive consent is the thing that is not available when a takedown has already landed.
- Bind the consent to the asset, not to the project. One consent record, one list of asset IDs it covers. Projects sprawl; a consent that covers "the Q3 campaign" answers nothing when a specific clip is challenged.
- Default speculative work to invented presenters. Anything exploratory, any concept test, any pitch mock-up should use a presenter who is not a replica of a specific real person. Knowing whether a given asset is a stock avatar, a digital twin or a generated character is the entire audit, and those three sit in three different risk positions.
- Keep a revocation path. People change their minds, leave companies and die. If you cannot answer "which live assets contain this person" in one query, you cannot honour a withdrawal.
The table version, for pasting into a brief:
| What is in the input | What you need before generating | Publishable on TikTok |
|---|---|---|
| No real person | Nothing extra | Yes, subject to normal disclosure |
| A generated character resembling nobody specific | Nothing extra | Yes, subject to normal disclosure |
| A real person, filmed, not replicated | Normal talent release | Yes |
| A real private individual, realistically replicated | Consent does not cure the platform rule | No |
| A public figure, realistically replicated | Consent plus category-specific restrictions | Restricted, not open |
Note what the fourth row says. Consent is necessary and it is not sufficient. A signed release from a private individual answers the legal question and does not answer the platform question, and the platform question is the one that removes your video.
The voice half, which almost nobody checks
Likeness tooling is overwhelmingly built around faces. Detection systems look for faces. Consent forms describe appearance. Review processes screen video frames.
Voice is the gap that is not covered by any of that, and it is legally the faster-moving half. Tennessee's ELVIS Act added voice as a protected personal right effective 1 July 2024, including exposure for tool providers. California's AB 2602, effective 1 January 2025, makes replica clauses in performer contracts unenforceable without a specific description of the intended use and representation for the performer. At federal level the TAKE IT DOWN Act's platform duties took effect on 19 May 2026, with a 48-hour notice-and-removal obligation, and FTC enforcement began the same day.
What is not law, and is routinely written about as though it were: the NO FAKES Act. It advanced out of Senate Judiciary on 18 June 2026 as S.4591 and remains a bill. There is still no federal right of publicity in the US, which is why the answer to "is this allowed" is genuinely different across state lines. Voice likeness law for creator marketing covers that terrain.
If you clone voices at all, run the same five-step ordering above on voice inputs. A cloned voice of a private individual is the same object as a cloned face for the purposes of the rule at the top of this post.
FAQ
Does adding an AI label make a synthetic depiction of a real person acceptable?
Not for a private individual on TikTok. The prohibition is a rule about whether the content is permitted, and disclosure operates on content that is already permitted. This is the single most common misreading of platform AI policy, because every other rule people have encountered works the other way round.
What if the person consented in writing?
Consent addresses the legal exposure — right of publicity, digital-replica statutes, contract. It does not override a platform's content rule. Both have to clear. Plan for the possibility that a fully consented, fully lawful asset is still not distributable on a given platform, and decide that before production rather than after.
Does this apply to a licensed avatar of a real person?
A licensed likeness is a consented replica, so the legal side is addressed. The platform side depends on how the platform classifies the depicted person and on the licence terms themselves. TikTok's own avatar likeness licensing is worth reading precisely because it shows the platform building a consented path rather than treating consent as automatically sufficient elsewhere.
How do I find out if someone has made a synthetic version of me or a client?
Likeness-detection enrolment is the practical tool, and it works best for people whose likeness you legitimately control and want to monitor. Enrolling in likeness detection walks the process. It is face-oriented, which brings you back to the voice gap above: for now, monitoring for a cloned voice is meaningfully harder than monitoring for a cloned face.