Acceptable use
Written to be read. Where a sentence here is uncomfortable, that is because the thing it describes is, and hiding it in longer words would not change it.
What this is
The public statement of the same rules that already run against every broadcast before its search is allowed to start. Nothing here is a policy we intend to apply; it is a description of code that is running.
Never allowed
These are refused automatically, before the search runs. Nothing is charged, because nothing happened.
- Phishing and scams — anything built to get a payment or a credential out of somebody under a false pretence.
- Illegal solicitation.
- Hate speech — attacks on people for what they are.
- Sexual content.
- Financial fraud patterns — guaranteed returns, recruitment pyramids, and the rest of the family, in any category, not only investment.
Allowed, but not to everybody yet
investment needs a sending history before an account may post in it at all. Payment does not substitute. This is the one category where the risk is the claim rather than the reach, so a reach limit is not the right instrument.
Content flagged but not blocked may send while a person reviews it. If the review goes against it afterwards, the consequences below apply to that broadcast retroactively.
Conduct
- Do not work around moderation, tier limits or rate limits, including by opening a second account to escape a restriction on the first.
- Do not try to identify a subscriber, or reach them anywhere other than the channel they agreed to.
- Do not put false information in a verification request.
- Do not scrape or harvest beyond what the product hands you directly.
- Do not advertise a business in the dating category. It exists for people describing themselves, and a matchmaking service posting there is using a channel built on the assumption that a person is on the other end.
What happens
- A blocked broadcast simply does not run. No charge, no strike — though trying repeatedly is itself conduct, and reads as such.
- Bounces above 5% or complaints above 0.3% on a run demote the account a tier, automatically, which lowers how many people one broadcast may reach.
- Bounces above 20% on a single run suspend the account there and then, whatever its history. A list that bad is not bad luck.
- A confirmed violation of the two sections above can end the account. It does not take your unused balance with it — see the refunds page.
Those are the real numbers the code checks, not illustrative ones. Getting back a tier is the same mechanism in reverse: 3 clean runs to leave the lowest tier, and 20 over at least 30 days to reach the highest.
Reporting
Every delivered message carries a way to report it, and every public alert in Explore does too. A report on a public alert removes it from Explore immediately, before anybody reviews it — the review decides whether it goes back, not whether it comes down.
Reports on delivered broadcasts reach the same moderation queue that reviews flagged content before it sends.
Changes
These rules are the ones in the code. When the code changes, this page changes in the same commit, and active accounts are told before a material change takes effect.