The OnlyFans tag-a-collaborator box is not a model release

Two creators shoot a collab. Both have verified OnlyFans accounts. The clip goes up, one tags the other, the platform pings the tagged account, both tick the box, the video publishes. When creators talk about their first collabs, that is usually the entire paper trail that comes up — the tick-box and nothing else. The tick-box has the shape of a release — a named, verified second person consenting to something — so the folder where a signed model release should live stays empty.

That's the gap this post is about. The platform's collaborator flow and your own model release are two different documents doing two different jobs, and the dangerous part is how similar they feel in the moment. One of them protects the platform. The other one protects you. You want both, and most collabs running today only have one.

I'm not a lawyer, and nothing here is legal advice. I'm about a year into self-producing, and my authority on paperwork comes from years of writing and reviewing contracts in a different industry, plus actually sitting down and reading platform terms the way a producer has to. Get a lawyer in your jurisdiction for anything that matters. This is the explanation I'd give a collaborator across the table before we shoot.

What the platform release flow actually does

When you tag a collaborator and they accept, the platform is solving the platform's problem. It needs to know that every person appearing in content on its servers is a verified adult who consented to being there. The tag-and-accept flow ties the second face in your video to a verified account, with an ID check behind it, and records that the verified person said yes to this content existing on the platform.

That's genuinely useful. It's an age-verification and consent checkpoint, it's timestamped, and it's enforced — the platform won't publish the content until the tagged person accepts. As a compliance gate for content hosted on that platform, it does its job.

But read the direction of the protection. The flow exists so the platform can demonstrate, to regulators and payment processors and its own lawyers, that it isn't hosting content featuring unverified or non-consenting people. The records it generates live in the platform's systems, structured around the platform's obligations. You are a beneficiary of that process in roughly the way a passenger benefits from an airline's maintenance log. It's good that it exists. It was not written for you.

I won't quote terms-of-service language at you, because platform terms change and any section number I cite today could be stale by the time you read this. Go read the current terms yourself — the creator agreement, the acceptable-use policy, the co-author or collaborator language — as a producer rather than as a user clicking through. The pattern I'm describing is visible in plain sight once you read it that way.

What the tick-box doesn't do for you

Here's the list of jobs your own model release does that the platform flow doesn't. Again — I'm not a lawyer, and a lawyer is exactly who you want if any one of these has already gone wrong for you. But the gaps themselves are structural, not subtle.

It doesn't grant you a license that survives the platform. The collaborator flow authorizes content on the platform. Your account gets banned, you leave for a competitor, the platform changes its rules or stops operating in your country — and the consent record you were leaning on lives inside a system you no longer have access to, covering a context that no longer exists. A signed release is yours. It sits in your records and travels with the footage wherever the footage legitimately goes.

It doesn't cover anywhere else. The tick-box says yes to this content on this platform. It says nothing about your own website, your clip-store accounts, another subscription platform, a promo cut on social, or a trailer on a tube site. Every one of those is a separate use, and the platform flow grants you none of them.

It doesn't establish your 2257 file. If you're producing content in the US, the federal record-keeping requirements are your obligation as a producer — your records, your custodian statement, your copies of ID and signed documents, organized the way the regulation describes. "The platform verified them" is not a records file you maintain; it's a records file someone else maintains, which you can't produce on inspection. I wrote up the producer-side mechanics in my 2257 requirements post — the short version is that the obligation doesn't transfer just because a platform also checked ID for its own reasons.

It can't be customized. A real release between two creators carries the deal points that actually matter: what each of you can and can't do with the footage, which platforms are in scope, whether faces can appear in free promo, what acts or angles are excluded, what happens if one of you wants the content taken down later, whether the grant survives a falling-out. The tick-box is a tick-box. It has no field for "not on the free page," no field for "takedown on request after two years," no field for anything. If the deal between you has any shape at all beyond "this clip may exist here," the platform flow cannot hold it.

Where the scope mismatch actually bites

The failure mode isn't abstract. It's the most normal thing in creator economics: using the same footage in more than one place.

Say you shoot a collab, publish it on OnlyFans through the tag-and-accept flow, and it does well. Six months later you put the same clip on your own site as part of a bundle. The only paper that exists is the platform tick-box — which covered the platform. Your co-performer never agreed, in any document you hold, to that footage being sold on a domain you control. If the two of you are still friendly, nothing happens. If you've fallen out, or they've left the industry and want their catalogue gone, you're now distributing content of another person with no release that covers the use. That's not a hypothetical fight you'd enjoy having, and "we both ticked the box" is a weak place to argue from. I'm not a lawyer; I can't tell you how that dispute ends in your jurisdiction. I can tell you the version of you holding a signed release never has to find out.

Same story with cross-posting to a second platform. The second platform will run its own verification flow — which solves the second platform's problem and still leaves yours unsolved. You can tick boxes on five platforms and hold zero documents of your own at the end of it.

And the asymmetry cuts both ways. If your collaborator posts the footage somewhere you never agreed to, the platform tick-box you accepted doesn't carry your limits either — it couldn't, because it never asked what your limits were. A mutual release protects both people in the scene. That's why it's worth the extra ten minutes even between friends, and why content-trade shoots deserve real paper too — I covered that side of it in the content-trade agreement post.

The stack: platform flow, your release, your records

So the answer isn't "skip the platform flow and use a real release instead." You don't get to skip it — the platform requires it to publish. And you shouldn't want to skip it; an independent, ID-backed verification of your collaborator is a useful second layer. The answer is a stack, and every collab gets all three layers:

1. The platform's collaborator flow, because it's required and because the platform's verification is a real check you didn't have to run yourself.
2. Your own signed model release, covering the uses you actually intend — named platforms, your own site, promo cuts — with the exclusions and takedown terms the two of you actually agreed to. This is the document that's still yours when the platform isn't.
3. Your 2257 records, built and stored the way the regulation describes, with the release and the ID copies in the file before the content is published anywhere.

None of this is expensive or slow. The free model release generator I built produces a signed-and-dated PDF in a few minutes, and it exists precisely because "the paperwork is annoying" is the reason most collabs run on a tick-box alone. Ten minutes before the shoot. That's the whole cost.

The back catalogue: paper it now, not never

Which leaves the uncomfortable part. If you've been collaborating for a while, you probably have content already published where the platform flow is the only thing that exists. No release, no 2257 file entry beyond your own. The temptation is to leave it alone — it's published, nothing bad happened, opening the conversation feels awkward.

Paper it anyway. A release signed after the fact isn't as clean as one signed before publication — I'm not a lawyer, and how much retroactive paper helps in a real dispute is exactly the kind of question one is for — but a signed document dated today beats an empty folder on every future day. The conversation is easier than it sounds: "I'm getting my records in order, here's a one-page release covering what we already published, want to flag anything before you sign?" A collaborator who balks at that is telling you something useful about the next shoot. Work backwards from the content that's earning or that you're most likely to redistribute, and chip away at the list.

The tick-box was never the release. It was the platform doing its own homework while you watched. Do yours — on the next shoot, and on the back catalogue, in that order.

— Sly