The following additional rules apply for any use of the Twitter services or features listed below:
You must present people with easy to find options to log into and out of Twitter, for example via the OAuth protocol. The Sign in with Twitter option must be displayed at least as prominently as any other sign-up or sign-in feature on your service. You must also provide people without a Twitter account the opportunity to create one via Twitter.
Once someone on your service authenticates via Sign in with Twitter you must clearly display their Twitter identity. Twitter identity includes the person’s current Twitter @handle, avatar, and Twitter logo. Any display of someone’s Twitter followers on your service must clearly show that the relationship is associated with Twitter.
To ensure a quality experience you must develop your Card to render across all platforms where Cards are displayed. Additional rules that you must follow when using Cards include:
You must mark your Tweet as ‘true’ for sensitive media if you plan to display such media within a Card
You must use HTTPS for hosting all assets within your Card. Your Card should never generate active mixed content browser warnings
Audio and video content should include stop or pause controls, and default to ‘sound off’ for videos that automatically play content
You may not exceed or circumvent Twitter’s limitations placed on any Cards, including the Card’s intended use. Additional restrictions on Cards use include:
You may not place third-party sponsored content within Cards without Twitter’s approval
You may not attach monetary incentives (including virtual currency) within your Card or on Twitter from your Card
You may not include content or actions within your Card that are misleading or not contextually relevant, such as URLs and media.
You may only attach an App Card to a Tweet when someone is explicitly promoting or referring to the app in the Tweet
You must contact us about your Twitter API access if you expect your service to exceed 10 million daily broadcasts. You may be subject to additional terms if you exceed this threshold. Additional restrictions on Periscope developer use include:
You must provide a reasonable user-agent, as described in the Periscope Producer technical documentation, for your service when accessing the Periscope API
You must honor requests from people to log out of their Periscope account on your service
- You may not provide tools in your service to allow people to circumvent technological protection measures