Most crypto teams plan the campaign and the legal review as two separate things that meet at the end.
That is where launches go wrong. Not because anyone made a bad call, but because the review arrives after the creative is finished, scheduled and paid for — and the cheapest moment to change a claim is before anyone has written it.
We are not lawyers and nothing here is legal advice. What follows is how to run the working relationship between a marketing programme and the people who have to sign it off.
Get the constraints before the brief
The single highest-leverage thing you can do is a short conversation with your counsel before anyone writes a word.
You want three things out of it, in writing: which claims are off the table entirely, which need qualifying language, and which markets you are actively promoting into. That is usually a one-page answer. It will save you two full rewrite cycles.
What you should not do is ask your agency to tell you what the rules are. They do not know your structure, your entity, or how your token has been characterised. An agency that confidently tells you what you are allowed to say is telling you something it cannot possibly know.
What tends to get flagged
The pattern is consistent enough to plan around, even though the specifics differ everywhere.
- Anything touching future price, stated or implied.
- Yields presented as investment returns rather than as a protocol mechanic.
- Partnership claims stronger than the relationship. Using a well-known logo because you integrated their public API is a claim, and their legal team may read it differently than you do.
- Loose use of words like insured, backed, or approved, where the underlying relationship is weaker than the word suggests.
- Selective performance data. Showing the good period and omitting the rest reads badly even when every number is accurate.
The implication cases catch more people than the explicit ones. A countdown timer beside a price chart implies something. A comparison to another asset’s past performance implies something. Language about getting in early implies something. None of those are statements, and all of them get flagged.
Build the loop into the schedule
Review is a dependency like any other. Treat it as one.
Put disclosure requirements in creator contracts. Specific language, specific placement, and a right to review before publishing. Creators generally comply when asked clearly. The problems come from projects that never asked.
Segment by market. Build creative per market rather than one global asset with a footer disclaimer.
Keep records. What was published, where, when, by whom, and what was approved. If a question ever arrives, the file you can produce matters enormously.
Review the actual post, not just the brief. What gets agreed and what gets published diverge more often than you would expect.
Brief the people who post. Community managers answering questions in Telegram are speaking on your behalf all day. A community manager telling someone the token is going to do well has just made a claim, whether or not anyone intended it.
The awkward internal conversation
Growth and caution genuinely conflict here. The highest-converting message is usually the one closest to a claim you cannot make.
The resolution is not clever wording that gets you to the same place. It is building the campaign around things you can say — what the product does, who uses it, what problem it solves, what is verifiably true about the team and the technology. Those work. They are harder to write, which is why fewer people do them well, which is exactly why doing them well is an advantage.
What drives the review load
- Number of markets you promote in, since each is reviewed separately.
- Whether you are using creators, which multiplies both the surface and the review volume.
- Volume of published material, since review is per-asset rather than per-campaign.
- How many approval steps sit between a draft and a publish, which is the variable teams underestimate most.
The recommendation
Get a written view from counsel before the campaign is built rather than after. Then build the marketing around what is true and provable.
The projects that get into trouble are rarely the ones that made an honest mistake in a disclosure. They are the ones whose entire campaign depended on a claim they were never allowed to make.
Common questions
Who decides what a crypto campaign is allowed to say?
Your own legal team or outside counsel, and nobody else. Not your agency, not your creators, not the ad platform. This matters more than it sounds, because the answer differs by market and by how your token is characterised, and only someone looking at your specific situation can give it. What an agency can do is ask for that answer early, write inside it, and route work back for sign-off while changing it is still cheap.
When should the review start?
At the brief, not at the publish step. The expensive version of this is producing a full campaign, sending it for review, and getting it back unusable. The cheap version is a short conversation before anyone writes, where legal tells you which claims are off the table and which need qualifying. Same people, same decisions, a fraction of the cost.
What normally gets flagged in review?
Anything that touches future price, directly or by implication. Countdown timers beside charts, comparisons to another asset's history, language about getting in early. Beyond that: yields framed as investment returns, partnership claims stronger than the actual relationship, words like insured or backed used loosely, and performance data showing the good period only. Most of these are implication problems rather than statements, which is why they survive a casual read.
Who is responsible when a creator posts something wrong?
In practice the exposure tends to spread across everyone involved rather than sitting with whoever hit publish. Contracting work out does not move it. The practical consequence for campaign planning is that disclosure requirements belong in the creator contract itself, with a right to see the post before it goes live. Creators generally do what they are asked when they are asked clearly and early.
How do you run a campaign across several markets?
Segment rather than publishing one global asset. Decide which markets you actively promote in, which you geofence, and which you serve passively without promotion. Then build creative and disclosures per market. One global asset with a footer disclaimer is the pattern that causes trouble, because it promotes into markets where nobody reviewed it.
