Thanks for the email and happy to try to clear things up.

1. The TOS go into affect today and section *4. Updates* states that
everyone has 30 days to comply with any changes to the ToS. If you

2. The TOS **does not** restrict the content coming from a user, whether
posted through an app on the user's behalf or by the user themself on To be even clearer, services that pay customers to post clearly
disclosed paid tweets are not affected by the changes to the TOS.

Let me know if that clears things up.

Best, Ryan

On Mon, May 24, 2010 at 10:51 AM, Adam Fortuna <>wrote:

> Hey Ryan (and everyone else), few questions about the fine details of
> this I'd love to get clarification on.
> First and foremost - when do the new TOS go into effect? I see they're
> already up on the API TOS page (
> ), but would like clarification. We're suddenly in violation now, so
> want to see what kind of timeline we have to comply.  Are you'll going
> to start enforcing this immediately, or do you'll have a set date to
> comply with the new TOS by.
> One of the points in the post, the killer line obviously, is "we will
> not allow any third party to inject paid tweets into a timeline on any
> service that leverages the Twitter API".
> Based on that it seems it's still within the rules if a Twitter User
> posts an ad themselves to Twitter manually, rather than a 3rd party
> doing it? Can you verify if that's a violation or not?
> From the blog post it would seem that is acceptable, but the one line
> from the new TOS might negate it: "Tweets may be used in
> advertisements, not as advertisements.".
> Does this mean that even a tweet posted manually to a users timeline
> cannot be an advertisement? In other words, no commerce, whether it's
> direct relationship between a Tweeter and an Advertiser, or through an
> intermediary (SponsoredTweets,, etc) is a violation -- whether
> the 3rd party posts it themselves of the Twitter User does the actual
> posting?
> Thanks, hope to get clarification soon,
> Adam Fortuna
> SponsoredTweets

Reply via email to