【Twitter API开发者账户协议必知】

中文

开发商协议
生效日期：2022年10月10日
本Twitter开发者协议（以下简称“协议”）由您（个人或实体，以下简称“您”）和Twitter（定义见下文）签订，并对您访问和使用许可材料（定义见上文）进行管理。您使用Twitter的网站、短信、API、电子邮件通知、应用程序、按钮、嵌入、广告和我们的其他覆盖服务受我们的一般服务条款和隐私政策的约束。
请仔细阅读本协议的条款和条件，包括以下引用的任何链接条款，这些条款是本许可协议的一部分。通过使用许可材料，即表示您同意已阅读并同意遵守本协议的条款和条件以及所有适用的法律法规，且不受限制或限制。如果您不同意受本协议约束，则您不得访问或以其他方式使用许可材料。本协议自您使用许可材料的第一天起生效（“生效日期”）。
如果您是代表实体的个人，您承认您有权代表该实体接受本协议。如果您未达到与TWITTER签订具有约束力的合同的法定年龄，或者根据适用法律禁止您使用或接收许可材料，则您不得使用许可材料，也不得接受本协议。
一、 Twitter API和Twitter内容
A、 定义
广播ID-为每个Periscope广播生成的唯一标识号。
开发者网站——Twitter的开发者网站位于https://developer.twitter.com
最终用户——您服务的用户。
许可材料——Twitter API、Twitter内容和Twitter标记的统称。
Periscope广播-在Twitter应用程序上公开显示的实时或点播视频流，由用户通过Twitter的Periscope Producer功能生成（如https://help.periscope.tv/customer/en/portal/articles/2600293).
服务——显示Twitter内容或以其他方式使用许可材料的服务、网站、应用程序和其他产品（包括研究）。
Tweet ID–为每个Tweet生成的唯一标识号。
推特——在Twitter应用程序上发布的帖子。
推特内容：推特、推特ID、推特终端用户档案信息、Periscope广播、广播ID以及通过推特API或通过推特授权的任何其他方式向您提供的任何其他数据和信息，以及其任何副本和衍生作品。
“推特”是指推特公司，其办公地址位于美国加利福尼亚州旧金山市市场街1355号900室，邮编94103。如果您在美国、加拿大或拉丁美洲以外的地方签订本协议或订单，则推特国际有限公司（“TIUC”）是签约实体，其注册办公地址位于爱尔兰都柏林2号费尼安街One Cumberland Place，D02 AX07。
直接消息-一个最终用户使用Twitter的直接消息功能在Twitter应用程序上向一个或多个特定的最终用户私下发送的消息。
Twitter API——Twitter应用程序编程接口（“API”）、软件开发工具包（“SDK”）和/或Twitter随API提供的相关文档、数据、代码和其他材料，可随时更新，包括但不限于通过开发者网站。
Twitter标记——Twitter向您提供的Twitter名称、商标和徽标，包括通过开发者网站。
Twitter应用程序——Twitter面向消费者的产品、服务、应用程序、网站、网页、平台和其他产品，包括但不限于通过https://twitter.com以及Twitter的移动应用程序。
B、 Twitter许可证。根据本协议和开发商政策中的条款和条件（作为以下授予的条件），Twitter特此授予您和您接受非排他性、免版税、不可转让、不可再许可、可撤销的许可，仅用于：
使用Twitter API将Twitter内容集成到您的服务中，或对Twitter明确批准的此类Twitter内容进行分析；
在本协议允许的情况下，通过您的服务向最终用户复制并显示合理数量的Twitter内容；
仅修改Twitter内容以将其格式化为在您的服务上显示；和
使用和显示Twitter标记，仅用于将Twitter的产品作为Twitter内容的来源，如本文所述。
C、 Twitter许可证您特此授予Twitter，Twitter接受非排他性、免版税、不可转让、不可再许可的可撤销许可证，以任何方式（包括网络蜘蛛和/或爬虫）访问、索引和缓存您使用嵌入推特或嵌入时间线显示Twitter内容的任何网页或应用程序。
D、 合并条款。您对许可材料的使用还受以下条款和条件的约束：
Twitter开发者政策；
API限制使用规则；
Twitter规则；
因为它与您显示任何Twitter内容有关，显示要求；
因为它与您使用和展示Twitter标志、Twitter品牌资源有关；
因为它涉及到对您的帐户采取自动操作，自动化规则；
因为它与您使用Periscope、Periscope社区指南和Periscope商标指南有关。
开发者政策、API限制使用规则、Twitter规则、显示要求、品牌资源、自动化规则、Periscope社区指南和Periscope商标指南在本文中统称为“合并开发者条款”。您同意《合并开发者条款》，该条款通过引用合并于此，并可应Twitter要求提供硬拷贝。如果联合开发商条款与本协议发生冲突，以本协议为准。《联合开发者条款》均未扩展或扩展本协议中授予的Twitter API、Twitter内容或Twitter标记的许可。
二、许可材料使用限制
A、 逆向工程和其他限制。您不会或试图（也不会允许他人）对Twitter API进行反向工程、反编译、反汇编或翻译，或以其他方式试图在任何Twitter API或其任何部分中获取源代码、商业秘密或专有技术；b） 干扰、修改、中断或禁用Twitter API的特性或功能，包括但不限于用于限制或控制功能的任何此类机制，或挫败、避免、绕过、移除、停用或以其他方式规避Twitter API的任何软件保护或监控机制；b） 向任何第三方出售、出租、租赁、再许可、分发、再分发、辛迪加、创建衍生作品、转让或以其他方式转让或提供许可材料的全部或部分使用权，本协议明确允许的除外；d） 在服务局、租赁或管理服务的基础上使用Twitter API，或允许其他个人或实体创建Twitter API的链接，或在任何其他服务器、无线或基于互联网的设备上“框架”或“镜像”Twitter API，或者以其他方式向第三方提供Twitter API的任何令牌、密钥、密码或其他登录凭证；或e）将许可材料用于任何非法、未经授权或其他不当目的，包括但不限于存储或传输侵权、诽谤或其他非法或侵权材料，存储或传输恶意代码，或存储或传输侵犯第三方隐私权的材料；（f） 利用许可材料获取或获取个人Twitter用户的非公开信息，包括但不限于用户的位置；（g） 干扰或破坏其中包含的Twitter应用程序、Twitter API或Twitter内容的完整性或性能，包括破坏任何其他人使用或享受Twitter应用程序，Twitter API或推特内容的能力，或试图获得未经授权的Twitter应用程序、Twitter API、Twitter内容或相关系统或网络的访问权；（h） 删除或更改Twitter内容上的任何专有通知或标记；或（i）通过数据代理或通过任何其他广告或货币化服务，单独使用Twitter内容或与第三方数据捆绑或衍生分析，以针对Twitter应用程序之外的广告用户，包括但不限于其他广告网络。
B、 商业使用限制。如果您的项目（位于您的Twitter开发者门户中）被指定为“非商业”，您不得将许可材料用于商业用途。商业使用限制可能不适用于正式注册的：（1）非营利组织或（2）非政府组织。“商业使用”是指许可材料的任何使用（包括对Twitter API的访问）：（i）由企业（即主要目的是通过产品或服务获得收入的实体）（或代表企业）使用，或（ii）作为货币化产品或服务的一部分使用（包括但不限于网站广告、许可费、应用内促销和赞助）。
C、 无监控或测量。尽管本协议中有任何其他规定，您只能将以下信息用于非商业的内部目的（例如，提高服务的功能）：（a）聚合Twitter应用程序用户指标，例如Twitter应用程序上的活跃用户或帐户数；（b） Twitter应用程序的响应能力；以及（c）从分析、使用或关于Twitter API的性能得出的结果、使用统计、数据或其他信息（汇总或其他）。所有此类信息均为Twitter的机密信息。

D、 费率限制。您不得试图超过或规避对Twitter API访问、调用和使用的限制（“费率限制”），或以超出合理请求量的方式使用Twitter API，构成过度或滥用，或未能遵守或不符合本协议的任何部分。如果您超过或Twitter合理地认为您试图规避费率限制、限制Twitter API使用的控制或本协议的条款和条件，那么您使用许可材料的能力可能会被暂时暂停或永久阻止。Twitter可能会监控您对Twitter API的使用情况，以改进许可材料和Twitter应用程序，并确保您遵守本协议和公司开发条款。

E、 位置数据。您不会（也不允许他人）聚合、缓存或存储Twitter内容中包含的位置数据和其他地理信息，除非与Twitter内容一起使用。您只能使用此类位置数据和地理信息来识别Twitter内容标记的位置。您不能单独使用位置数据或地理信息。

F、 Twitter标记的使用。Twitter标记可能不包含在您的注册公司名称、任何徽标或任何服务或产品名称中或作为其一部分。此外，您不得创建任何Twitter标志的衍生作品，或以创建或合理暗示不准确的认可、赞助或与Twitter关联的方式使用Twitter标志。否则，您不会以误导、混淆或欺骗服务用户的方式使用企业名称和/或徽标。Twitter标志的所有使用以及由此产生的所有商誉将符合Twitter的利益。未经Twitter事先同意，除非本协议明确授权，否则您不得使用Twitter标记。您不得删除或更改许可材料上的任何专有通知或Twitter标记。

G、 安全。您将维护Twitter API的安全性，不会向第三方提供Twitter API的任何令牌、密钥、密码或其他登录凭据。您将使用行业标准的安全措施来防止未经授权访问或使用Twitter API的任何特性和功能，包括病毒、蠕虫或任何其他有害代码或材料的访问。此外，您将通过使用行业标准的组织和技术保护措施，对Twitter内容（包括个人数据，如适用）进行保密和保护，防止未经授权的访问，并且不会像保护您存储的类似数据时那样小心。如果您知道或怀疑与许可材料相关的任何安全漏洞或潜在漏洞，您将立即通知Twitter，咨询并配合调查，协助任何必要的通知，并提供Twitter合理要求的任何信息，并将立即补救因您访问许可材料而导致的此类漏洞或潜在的漏洞

三、 更新和删除

A、 更新。您承认，Twitter可随时自行决定更新或修改许可材料（在每种情况下，均称为“更新”）。您需要实施和使用许可材料的最新版本，并对更新后所需的服务进行任何更改，费用由您自行承担。更新可能会对您的服务访问Twitter API或与Twitter API通信或显示Twitter内容的方式产生不利影响。您在更新或修改后继续访问或使用许可材料将构成对更新的约束性接受。

开发商政策

Twitter+开发者

Twitter喜欢开发者。我们对这个社区利用Twitter数据的力量创造的工具和服务感到高兴和惊讶。作为我们对这个社区承诺的一部分，我们的目标是为开发者提供开放和公平的数据访问，对Twitter上的人来说是安全的，对整个Twitter平台来说是有益的。为了进一步实现这些目标，我们制定了开发人员政策，以帮助人们了解我们的规则和对适当API和Twitter内容使用的期望。

本开发人员政策（“政策”）为与Twitter的应用程序、服务、网站、网页和内容生态系统交互的开发人员提供了规则和指南。这是您与Twitter签订的关于访问和使用Twitter API和Twitter内容的合同的一部分（作为开发者协议的一部分或与Twitter的其他书面协议）。违反政策被视为违反协议。本政策可能随时更改，恕不另行通知。本政策中使用的大写术语（未在本政策中定义）具有开发商协议或主许可协议中规定的各自含义。

使用此策略

我们制定了这项政策，以使其尽可能容易遵守。在使用Twitter API和Twitter内容时，请牢记以下政策部分的信息：

为成功做好准备-你有责任遵守所有Twitter政策。在您访问Twitter API和Twitter内容之前，务必查看并理解本政策以及我们在本文档中链接的政策。审查我们的政策所花费的时间可能会为您节省数小时的返工时间。

隐私和控制至关重要-保护和捍卫Twitter用户的隐私是我们公司的核心DNA。因此，我们禁止以任何不符合人们对隐私的合理期望的方式使用Twitter数据。通过构建Twitter API或访问Twitter内容，您可以在维护这一承诺方面发挥特殊作用，最重要的是尊重人们的隐私，并为他们提供透明度和对数据使用方式的控制。

遵循平台使用指南-获得批准访问Twitter API和Twitter内容只是第一步。如果您对如何确保计划使用Twitter平台的政策合规性有疑问，我们的平台使用指南应该是您的第一站。

我们在下面就这三个关键部分的含义提供了更多的细节。请仔细审查，以确保您对Twitter API和Twitter内容的使用符合我们的政策。

如果我们认为您违反了本政策（或任何其他Twitter政策），我们可能会暂停或永久撤销您对Twitter API和Twitter内容的访问。如果发生这种情况，请不要申请或注册其他API密钥。相反，请通过API政策支持表单与我们联系。

最后，请注意，Twitter可能会监控您对Twitter API的使用，以改进Twitter应用程序，检查任何商业用途，并确保您遵守您批准的用例和本政策。

感谢您的阅读，感谢您与我们一起建设！我们期待着看到您的创作！

为成功做好准备

通过确保您的服务从第一天开始就以正确的方式构建，您可以在使用Twitter API时避免许多潜在的陷阱。开发人员政策的这一部分包含所有开发人员在使用Twitter API或Twitter内容之前必须遵守的规则。

我们审查Twitter开发者平台的所有拟议用途，以验证政策合规性，因此您需要披露（并在适用情况下更新）您计划使用Twitter API和Twitter内容的情况，以便获得授权并保持访问。所有新开发人员必须申请开发人员帐户才能访问Twitter API。目前没有经批准的开发者帐户的开发者必须按照Twitter的指示申请一个。作为此过程的一部分，您需要向我们提供您对Twitter API和Twitter内容的预期用途的书面说明。

您的用例描述对您具有约束力，任何实质性的偏离都可能违反我们的规则并导致强制执行。您必须通知我们对您的用例进行的任何实质性修改，并在开始使用Twitter内容进行新用途之前获得批准。否则可能导致API和数据访问暂停和终止。您可以通过访问我们的API策略支持表单，选择我需要更新我的开发人员用例，或者按照Twitter的其他约定来更新您的用例。
通过构建Twitter API或访问Twitter内容，您必须遵守所有Twitter政策。其中包括本开发者政策、自动化规则、显示要求、API限制使用规则、Twitter规则、Twitter品牌资源、Periscope社区指南和Periscope商标指南，以及您与Twitter签订的与您使用Twitter API或Twitter内容有关的任何其他协议，包括但不限于开发商协议或主许可协议或订单（如适用）。您还必须遵守对这些政策的任何修改以及Twitter推出的任何新政策。您有责任监控您的服务的使用情况，并设计您的服务以防止用户违反Twitter政策。否则可能会导致暂停或终止您的API和Twitter内容访问。

您不能为单个用例或基本相似或重叠的用例注册多个应用程序。在这种情况下，“用例”是通过应用程序执行的一组一致的分析、显示或操作。请注意，向不同的人提供相同的服务或应用程序（包括工具或服务的“白标签”版本）视为单个用例。

作为这些规则的一个例外，您最多可以创建和使用3个应用程序，用于同一服务的开发、登台和生产实例。这些应用程序必须注册到单个帐户，并且应明确标识（在名称和描述中）为单个服务的开发、暂存和生产实例。您不能将开发或转移应用程序用于生产目的。

您必须将所有API密钥或其他访问凭据保密。您不得使用、也不得鼓励或帮助他人使用他人拥有的API密钥或其他访问凭据。

您与Twitter的许可协议限制您使用Twitter API和Twitter内容。除其他外，Twitter API有速率限制，有助于确保公平的数据使用，并打击平台上的垃圾邮件。您不得超过或规避本政策或您与Twitter的协议中所述的费率限制或任何其他限制或限制，这些限制或限制在开发者网站上列出，或通过Twitter传达给您。

您不得删除或更改通过Twitter API接收的Twitter内容上的任何专有通知或标记。这有助于确保人们知道Twitter内容来自何处，以及它属于谁。

出于数据完整性和平台健康原因，您不得干扰、拦截、中断或禁用Twitter API或Twitter服务的任何功能。换句话说，按照developer.twitter.com上的预期和文档使用API。有关可接受使用的更多详细信息，请参阅我们的HackerOne指南。

隐私和控制至关重要

Twitter非常重视隐私，我们希望每个使用Twitter内容和Twitter API的人都能做到这一点。任何以不符合人们对隐私的合理期望的方式使用Twitter开发者平台、Twitter API或Twitter内容的行为都可能受到执法行动的影响，包括暂停和终止API和Twitter内容访问。

您对隐私和控制的承诺必须扩展到Twitter内容的所有使用，以及您使用我们的API构建的服务的所有方面。为此，使用您服务的人必须理解并同意您如何使用他们的数据，以及您如何代表他们访问Twitter。这可以通过向人们提供明确、全面和透明的隐私政策，以及确保在代表他们采取任何行动之前，您获得使用您服务的每个人的明确和知情同意来实现。请注意，验证您的服务的人本身并不构成同意。
同意和权限

特别是，在执行以下任何操作之前，必须获得人们的明确和知情同意：

代表他们采取任何行动。这包括（但不限于）：

将内容发布到Twitter

跟踪/取消跟踪帐户

修改配置文件或帐户信息

开始外围广播

向推特添加标签或任何其他内容

重新发布通过Twitter API或其他Twitter工具以外的方式访问的内容

使用某人的Twitter内容推广产品或服务

存储非公开内容，如直接消息（DM）或任何其他私人或机密信息

共享或发布受保护的内容或任何其他私人或机密信息

如果您的服务允许人们将内容发布到Twitter，您必须在发布之前执行以下操作：

准确显示将发布的内容

向使用您服务的用户明确哪些地理信息（如果有）将添加到内容中

如果您的服务允许人们将内容发布到您的服务和Twitter，则在发布之前必须执行以下操作：

获得发布内容的权限

解释您将在何处发布内容

您必须尊重所有Twitter内容的受保护和被阻止状态。您不能将使用一个人的身份验证令牌获得的内容提供给无权查看该内容的其他人。

受保护的帐户：受保护帐户的内容仅可供所有者批准使用该帐户的用户使用。因此，如果您运行的服务访问受保护的帐户，那么您只能这样做，以便将此类内容提供给具有查看该内容权限的特定人员。

被阻止的帐户：Twitter上的用户可以出于任何原因阻止对其帐户的访问。不允许混合从令牌（或任何其他基于API的操作）获得的信息以绕过此选项。

由于直接消息（DM）本质上是非公开的，因此提供DM功能的服务必须采取额外措施来保护个人隐私。您不能向未经授权查看DM内容的人提供DM内容。如果您的服务提供DM功能，您还必须：

如果您为DM发送读回执事件，请通知其他人。您可以通过直接在服务中提供通知，或通过显示会话中其他参与者的已读回执来完成此操作。

在将媒体配置为在DM中发送为“共享”（即可在多个DM中重复使用）之前，请获得同意。如果您确实允许DM中的媒体被“共享”，您必须提供一个明确的通知，即任何人都可以使用媒体的URL访问此内容。

内容合规性

如果您离线存储Twitter内容，则必须使其与Twitter上该内容的当前状态保持最新。具体来说，如果在Twitter上删除或修改了任何内容，则必须删除或修改这些内容。这必须尽快完成，或在收到Twitter或适用Twitter帐户所有者的请求后24小时内完成，或根据您与Twitter的协议或适用法律的其他要求完成。除非法律另有禁止，否则必须在Twitter明确书面许可的情况下进行。

修改的内容可以采取各种形式。这包括（但不限于）：

已成为私有或获得保护状态的内容

已从平台暂停的内容

已从中删除地理标记的内容

已从Twitter上保留或删除的内容

非Twitter匹配

我们限制您可以将Twitter上的人与从Twitter获取或存储的信息进行匹配的情况。非Twitter匹配涉及将Twitter内容（包括Twitter@handle或用户ID）与个人、家庭、设备、浏览器或其他非Twitter标识符相关联。只有在您在建立协会之前获得该人的明确同意，或如下文所述，您才可以这样做。

如果您没有一个人的明示、选择同意将其Twitter身份链接到非Twitter标识符，我们要求您绘制的任何连接仅基于某人合理期望用于该目的的信息。此外，如果没有某人的明确选择同意，您只能尝试根据以下内容将您的某人记录与Twitter身份进行匹配：

此人直接向您提供的信息。请注意，与您之前没有关系的个人的记录，包括从第三方获得的个人数据，不符合此标准；和/或

公共数据。本文中的“公共数据”指：

您从公共的、普遍可用的资源（如专业协会成员目录）中获得的有关某人的信息

witter上公开的个人信息，包括：

推特

个人资料信息，包括账户简介和公开位置

显示名称和@句柄

您的隐私政策

在允许用户下载、安装或注册您的服务之前，您必须向他们显示您的服务的隐私政策。它必须至少披露以下信息：

您从使用您服务的人那里收集的信息

您如何使用和共享这些信息（包括与Twitter）

人们如何与您联系，询问和请求他们的信息

您的隐私政策必须符合所有适用法律，并且对人们的保护程度不亚于Twitter的隐私政策以及我们其他服务和公司附属公司的隐私政策。如果您无法遵守您和/或Twitter的隐私政策，您必须停止访问Twitter API和使用所有Twitter内容。

使用地理数据

由于这些信息的敏感性质，地理数据的使用受到了额外的限制。如果您的服务将位置信息添加到推特或Periscope广播中，您必须向人们披露：

添加位置信息时

是否将位置信息添加为地理标记或注释数据

无论您的位置信息是作为地点列出的，还是作为地理坐标列出的

如果你的应用程序允许人们在推特上发布他们的位置，你必须完全遵守推特的地理指南。

禁止单独使用位置数据或地理信息。您不得（也不得允许他人）存储、聚合或缓存Twitter内容中包含的位置数据和其他地理信息，但作为推特或Periscope广播的一部分除外。例如，您可能无法将位置数据或地理信息从推特中分离出来，以显示个人在一段时间内的位置。允许使用热图和相关工具显示聚集的地理活动（例如：使用标签的城市人数）。

Twitter密码

您不能存储Twitter密码，也不能要求用户直接向您提供Twitter密码、帐户凭据或开发人员应用程序信息（包括用户密钥）。我们建议使用登录Twitter作为身份验证工具，将您的服务和Twitter上的人联系起来。

平台使用指南

您是否认真审查了Twitter的政策并以正确的方式设置了API访问？您的服务是否遵循Twitter的隐私和控制准则？如果你能回答这两个问题，那么你就可以开始使用Twitter API和Twitter内容了。Twitter的平台使用指南提供了所需的帮助，以确保您在服务的整个生命周期中从第1天开始使用Twitter内容是合规的。我们建议定期审查这些规则，以确保您的集成以安全且有益于Twitter和整个Twitter平台的方式运行。

垃圾邮件、机器人和自动化

禁止使用Twitter API和开发人员产品制造垃圾邮件，或从事任何形式的平台操纵。您应该审查有关平台操纵和垃圾邮件的Twitter规则，并确保您的服务不会，也不会让人们违反我们的政策。

执行写入操作（包括发布推特、跟踪帐户或发送直接消息）的服务必须遵循自动化规则。特别是，您应该：

在向人们发送自动回复或直接消息之前，始终获得明确同意

立即尊重拒绝与您联系的请求

切勿执行批量、攻击性或垃圾邮件操作，包括批量跟踪

切勿在多个帐户中发布相同或基本相似的内容

如果您使用的是基于API的bot帐户，则必须明确指出该帐户是什么以及谁负责。你不应该误导或混淆人们你的帐户是否是机器人。一个好的方法是在个人简介中加入一个声明，说明该帐户是机器人。

Twitter性能基准测试

您不能使用Twitter API来衡量Twitter的可用性、性能、功能或使用情况，以用于基准测试、竞争或商业目的。例如，您不应使用Twitter API：

计算Twitter聚合指标，例如每月活跃（MA）或每日活跃（DA）的总数

计算聚合Periscope度量，例如广播视图总数

计算推特推特总计指标，例如每天发布的推特总数或账户参与次数

衡量或分析Twitter的响应能力

测量或分析Twitter上的垃圾邮件或安全性，以下情况除外
测量或分析Twitter上的垃圾邮件或安全性，以下情况除外

我们支持有助于改善Twitter会话健康的研究。您可以使用Twitter API和Twitter内容来衡量和分析垃圾邮件、滥用或其他与平台相关的主题，以用于非商业研究目的。未经Twitter明确书面许可，您不得使用Twitter API或Twitter内容开发、创建或提供商业服务，以测量、分析或试图识别违反Twitter政策的行为或内容。

如果您对您的用例是否符合此目的的非商业研究有疑问，请通过API策略支持表单提交请求。

公开展示推特

您必须保持您公开显示的或向使用您服务的人显示的所有Twitter内容的完整性。如果您不使用Twitter for Websites来显示内容，则必须使用Twitter API来检索可供显示的最新版本。如果显示的内容不再通过Twitter API提供，则您必须尽快将其从您的服务中删除，或在收到Twitter或适用Twitter帐户所有者的删除请求后24小时内删除，或根据适用法律的其他要求删除。

如果您在脱机状态下显示Twitter内容，则必须遵守特定规则。如果您脱机显示Tweets，请遵循广播中使用Tweets的指南。如果您脱机显示Periscope广播，请遵循使用Periscope Broadcasts的指南。

如果您嵌入或显示推特，如果您的网站每日访问量超过1000万，您必须联系我们了解您的Twitter API访问情况。Twitter保留要求附加条款作为您使用Twitter API的条件的权利。网站开发者使用Twitter的其他限制包括：

嵌入式推文和/或嵌入式时间表

您必须向人们提供充分的法律通知，充分披露Twitter收集和使用您网站上浏览活动的数据，包括基于兴趣的广告和个性化。您还必须获得人们的合法充分同意，才能进行此类收集和使用

您必须提供法律上充分的说明，说明人们如何选择退出Twitter的基于兴趣的广告和个性化，如下所述

Twitter网站小部件

您必须确保向用户提供有关在其设备上存储和访问cookie或Twitter cookie使用中描述的其他信息的清晰全面的信息，并获得其同意，如果法律要求提供此类信息并获得此类同意

针对13岁以下儿童的服务

针对13岁以下儿童的服务必须选择不在任何嵌入的推特和/或嵌入的时间表中定制Twitter，方法是将选择退出参数设置为“true”，如下所述

内容重新分发

获取Twitter内容的最佳位置是直接从Twitter。因此，我们限制将Twitter内容重新分发给第三方。如果您向第三方提供推特内容，包括可下载的数据集或通过API，您只能分发推特ID、直接消息ID和/或用户ID（下文所述除外）。我们还授予学术研究人员出于非商业研究目的共享推特ID和用户ID的特殊权限。

总的来说，除非您获得Twitter的书面许可，否则在任何30天内，您不得向任何实体（包括与单个实体相关的多个个人）分发超过1500000个推特ID。此外，如果通过非自动化方式（例如，下载电子表格或PDF），所有开发人员可以每天向使用您服务的每个人提供多达50000个公共推特对象和/或用户对象。

如果学术研究人员代表学术机构且仅出于非商业研究目的，则允许他们分发无限数量的推特ID和/或用户ID。例如，您可以共享无限数量的Tweet ID，以便对您的研究进行同行评审或验证。如果您对您的用例是否符合此类别有疑问，请通过API策略支持表单提交请求。

提供给第三方的任何Twitter内容均受本政策约束，这些第三方在接收此类下载之前必须同意Twitter服务条款、隐私政策、开发者协议和开发者政策。您不得允许任何实体规避本政策、开发商协议或与Twitter的任何其他协议中包含的对Twitter内容分发的任何其他限制或限制。

潜望镜生产商
如果您希望您的服务每天播放量超过1000万次，您必须联系我们了解您的Twitter API访问情况。如果超过此阈值，您可能会受到其他条款的约束。Periscope开发者使用的其他限制包括：
访问Periscope API时，您必须按照Periscope Producer技术文档中的描述，为您的服务提供合理的用户代理
您必须尊重人们的请求，以便在您的服务中注销他们的Periscope帐户
您不得在服务中提供工具，让人们规避技术保护措施

英文

Developer Agreement
Effective: October 10, 2022

This Twitter Developer Agreement (“Agreement”) is made between you (either an individual or an entity, referred to herein as “you”) and Twitter (as defined below) and governs your access to and use of the Licensed Material (as defined below).Your use of Twitter’s websites, SMS, APIs, email notifications, applications, buttons, embeds, ads, and our other covered services is governed by our general Terms of Service and Privacy Policy.

PLEASE READ THE TERMS AND CONDITIONS OF THIS AGREEMENT CAREFULLY, INCLUDING ANY LINKED TERMS REFERENCED BELOW, WHICH ARE PART OF THIS LICENSE AGREEMENT. BY USING THE LICENSED MATERIAL, YOU ARE AGREEING THAT YOU HAVE READ, AND THAT YOU AGREE TO COMPLY WITH AND TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT AND ALL APPLICABLE LAWS AND REGULATIONS IN THEIR ENTIRETY WITHOUT LIMITATION OR QUALIFICATION. IF YOU DO NOT AGREE TO BE BOUND BY THIS AGREEMENT, THEN YOU MAY NOT ACCESS OR OTHERWISE USE THE LICENSED MATERIAL. THIS AGREEMENT IS EFFECTIVE AS OF THE FIRST DATE THAT YOU USE THE LICENSED MATERIAL (“EFFECTIVE DATE”).

IF YOU ARE AN INDIVIDUAL REPRESENTING AN ENTITY, YOU ACKNOWLEDGE THAT YOU HAVE THE APPROPRIATE AUTHORITY TO ACCEPT THIS AGREEMENT ON BEHALF OF SUCH ENTITY. YOU MAY NOT USE THE LICENSED MATERIAL AND MAY NOT ACCEPT THIS AGREEMENT IF YOU ARE NOT OF LEGAL AGE TO FORM A BINDING CONTRACT WITH TWITTER, OR YOU ARE BARRED FROM USING OR RECEIVING THE LICENSED MATERIAL UNDER APPLICABLE LAW.

I. Twitter API and Twitter Content
A. Definitions
Broadcast ID - A unique identification number generated for each Periscope Broadcast.

Developer Site ‒ Twitter’s developer site located at https://developer.twitter.com

End Users ‒ Users of your Services.

Licensed Material ‒ A collective term for the Twitter API, Twitter Content and Twitter Marks.

Periscope Broadcast - A live or on-demand video stream that is publicly displayed on Twitter Applications and is generated by a user via Twitter’s Periscope Producer feature (as set forth at https://help.periscope.tv/customer/en/portal/articles/2600293).

Services ‒ Your services, websites, applications and other offerings (including research) that display Twitter Content or otherwise use the Licensed Material.

Tweet ID ‒ A unique identification number generated for each Tweet.

Tweet ‒ a posting made on Twitter Applications.

Twitter Content ‒ Tweets, Tweet IDs, Twitter end user profile information, Periscope Broadcasts, Broadcast IDs and any other data and information made available to you through the Twitter API or by any other means authorized by Twitter, and any copies and derivative works thereof.

“Twitter” means Twitter, Inc., with an office located at 1355 Market Street, Suite 900, San Francisco, CA, 94103, USA. If you enter into this Agreement or an Order outside of the United States, Canada or Latin America, Twitter International Unilimited Company with its registered offices at One Cumberland Place, Fenian Street, Dublin 2, D02 AX07, Ireland (“TIUC”) is the contracting entity.

Direct Message - A message that is privately sent on Twitter Applications by one end user to one or more specific end user(s) using Twitter’s Direct Message function.

Twitter API ‒ The Twitter Application Programming Interface (“API”), Software Development Kit (“SDK”) and/or the related documentation, data, code, and other materials provided by Twitter with the API, as updated from time to time, including without limitation through the Developer Site.

Twitter Marks ‒ The Twitter name, trademarks, and logos that Twitter makes available to you, including via the Developer Site.

Twitter Applications ‒ Twitter’s consumer facing products, services, applications, websites, web pages, platforms, and other offerings, including without limitation, those offered via https://twitter.com and Twitter’s mobile applications.

B. License from Twitter. Subject to the terms and conditions in this Agreement and the Developer Policy (as a condition to the grant below), Twitter hereby grants you and you accept a non-exclusive, royalty free, non-transferable, non-sublicensable, revocable license solely to:

Use the Twitter API to integrate Twitter Content into your Services or conduct analysis of such Twitter Content, as explicitly approved by Twitter;

Copy a reasonable amount of and display the Twitter Content on and through your Services to End Users, as permitted by this Agreement;

Modify Twitter Content only to format it for display on your Services; and

Use and display Twitter Marks, solely to attribute Twitter’s offerings as the source of the Twitter Content, as set forth herein.

C. License to Twitter You hereby grant Twitter and Twitter accepts a non-exclusive, royalty free, non-transferable, non-sublicensable revocable license to access, index, and cache by any means, including web spiders and/or crawlers, any webpage or applications on which you display Twitter Content using embedded Tweets or embedded timelines.

D. Incorporated Terms. Your use of the Licensed Material is further subject to and governed by the following terms and conditions:

the Twitter Developer Policy;

the API Restricted Use Rules;

the Twitter Rules;

as it relates to your display of any of the Twitter Content, the Display Requirements;

as it relates to your use and display of the Twitter Marks, the Twitter Brand Resources;

as it relates to taking automated actions on your account, the Automation Rules;

as it relates to your use of Periscope, the Periscope Community Guidelines, and the Periscope Trademark Guidelines.

The Developer Policy, API Restricted Use Rules, Twitter Rules, Display Requirements, Brand Resources, Automation Rules, Periscope Community Guidelines, and Periscope Trademark Guidelines are collectively referred to herein as the “Incorporated Developer Terms”. You agree to the Incorporated Developer Terms, which are hereby incorporated by reference and are available in hardcopy upon request to Twitter. In the event of a conflict between the Incorporated Developer Terms and this Agreement, this Agreement shall control. None of the Incorporated Developer Terms expand or extend the license to the Twitter API, Twitter Content or Twitter Marks granted in this Agreement.

II. Restrictions on Use of Licensed Materials
A. Reverse Engineering and other Restrictions. You will not or attempt to (and will not allow others to) a) reverse engineer, decompile, disassemble or translate the Twitter API, or otherwise attempt to derive source code, trade secrets or know-how in or underlying any Twitter API or any portion thereof; b) interfere with, modify, disrupt or disable features or functionality of the Twitter API, including without limitation any such mechanism used to restrict or control the functionality, or defeat, avoid, bypass, remove, deactivate or otherwise circumvent any software protection or monitoring mechanisms of the Twitter API; b) sell, rent, lease, sublicense, distribute, redistribute, syndicate, create derivative works of, assign or otherwise transfer or provide access to, in whole or in part, the Licensed Material to any third party except as expressly permitted herein; d) provide use of the Twitter API on a service bureau, rental or managed services basis or permit other individuals or entities to create links to the Twitter API or “frame” or “mirror” the Twitter API on any other server, or wireless or Internet-based device, or otherwise make available to a third party, any token, key, password or other login credentials to the Twitter API; or e) use the Licensed Material for any illegal, unauthorized or other improper purposes, including without limitation to store or transmit infringing, libelous, or otherwise unlawful or tortious material, to store or transmit malicious code, or to store or transmit material in violation of third-party privacy rights; (f) utilize the Licensed Material to derive or obtain non-public information of individual Twitter users, including without limitation a user’s location; (g) interfere with or disrupt the integrity or performance of the Twitter Applications, Twitter API or Twitter Content contained therein, including by disrupting the ability of any other person to use or enjoy the Twitter Applications, Twitter API or Twitter Content, or attempt to gain unauthorized access to the Twitter Applications, Twitter API, Twitter Content or related systems or networks; (h) remove or alter any proprietary notices or marks on the Twitter Content; or (i) use Twitter Content, by itself or bundled with third party data, or derivative analysis therefrom, to target users with advertising outside of the Twitter Applications, including without limitation on other advertising networks, via data brokers, or through any other advertising or monetization services.

B. Commercial Use Restrictions. If your Project (located in your Twitter developer portal) is designated as ‘non-commercial’ you shall not make Commercial Use of the Licensed Materials. Commercial Use restrictions may not apply to those officially registered: (1) non-profits or (2) NGOs. “Commercial Use” means any use of the Licensed Materials (which includes access to the Twitter API): (i) by (or on behalf of) a business (i.e. entity whose primary purpose is to earn revenue through a product or service) or (ii) as part of a product or service that is monetized (including but not limited to website advertising, licensing fees, in-app promotions, and sponsorships).

C. No Monitoring or Measuring. Despite any other provision herein, you may only use the following information for non-commercial, internal purposes (e.g., to improve the functionality of the Services): (a) aggregate Twitter Applications user metrics, such as number of active users or accounts on Twitter Applications; (b) the responsiveness of Twitter Applications; and © results, usage statistics, data or other information (in the aggregate or otherwise) derived from analyzing, using, or regarding the performance of the Twitter API. All such information is Twitter’s Confidential Information.

D. Rate Limits. You will not attempt to exceed or circumvent limitations on access, calls and use of the Twitter API (“Rate Limits”), or otherwise use the Twitter API in a manner that exceeds reasonable request volume, constitutes excessive or abusive usage, or otherwise fails to comply or is inconsistent with any part of this Agreement. If you exceed or Twitter reasonably believes that you have attempted to circumvent Rate Limits, controls to limit use of the Twitter APIs or the terms and conditions of this Agreement, then your ability to use the Licensed Materials may be temporarily suspended or permanently blocked. Twitter may monitor your use of the Twitter API to improve the Licensed Materials and Twitter Applications and to ensure your compliance with this Agreement and Incorporated Developer Terms.

E. Location Data. You will not (and you will not allow others to) aggregate, cache, or store location data and other geographic information contained in the Twitter Content, except in conjunction with the Twitter Content to which it is attached. You may only use such location data and geographic information to identify the location tagged by the Twitter Content. You may not use location data or geographic information on a standalone basis.

F. Use of Twitter Marks. The Twitter Marks may not be included in or as part of your registered corporate name, any of your logos, or any of your service or product names. Moreover, you may not create any derivative works of the Twitter Marks or use the Twitter Marks in a manner that creates or reasonably implies an inaccurate sense of endorsement, sponsorship, or association with Twitter. You will not otherwise use business names and/or logos in a manner that can mislead, confuse, or deceive users of your Services. All use of the Twitter Marks and all goodwill arising out of such use, will inure to Twitter’s benefit. You shall not use the Twitter Marks except as expressly authorized herein without Twitter’s prior consent. You will not remove or alter any proprietary notices or Twitter Marks on the Licensed Material.

G. Security. You will maintain the security of the Twitter API and will not make available to a third party, any token, key, password or other login credentials to the Twitter API. You will use industry standard security measures to prevent unauthorized access or use of any of the features and functionality of the Twitter API, including access by viruses, worms, or any other harmful code or material. Additionally, you will keep Twitter Content (including, where applicable, personal data) confidential and secure from unauthorized access by using industry-standard organizational and technical safeguards for such data, and with no less care than it uses in connection with securing similar data you store. You will immediately notify Twitter consult and cooperate with investigations, assist with any required notices, and provide any information reasonably requested by Twitter if you know of or suspects any breach of security or potential vulnerability related to the Licensed Material and will promptly remedy such breach or potential vulnerability resulting from Your access to the Licensed Material

III. Updates and Removals
A. Updates. You acknowledge that Twitter may update or modify the Licensed Materials from time to time, and at its sole discretion (in each instance, an “Update”). You are required to implement and use the most current version of the Licensed Materials and to make any changes to your Services that are required as a result of such Update, at your sole cost and expense. Updates may adversely affect the manner in which your Services access or communicate with the Twitter API or display Twitter Content. Your continued access or use of the Licensed Materials following an update or modification will constitute binding acceptance of the Update.

B. Removals. If Twitter Content is deleted, gains protected status, or is otherwise suspended, withheld, modified, or removed from the Twitter Applications (including removal of location information), you will make all reasonable efforts to delete or modify such Twitter Content (as applicable) as soon as possible, and in any case within 24 hours after a written request to do so by Twitter or by a Twitter user with regard to their Twitter Content, unless prohibited by applicable law or regulation and with the express written permission of Twitter.

IV. Ownership and Feedback
A. Ownership. The Licensed Material is licensed, not sold, and Twitter retains and reserves all rights not expressly granted in this Agreement. You expressly acknowledge that Twitter, its licensors and its end users retain all worldwide right, title and interest in and to the Licensed Material, including all rights in patents, trademarks, trade names, copyrights, trade secrets, know-how, data (including all applications therefor), and all proprietary rights under the laws of the United States, any other jurisdiction or any treaty (“IP Rights”). You agree not to do anything inconsistent with such ownership, including without limitation, challenging Twitter’s ownership of the Twitter Marks, challenging the validity of the licenses granted herein, or otherwise copying or exploiting the Twitter Marks during or after the termination of this Agreement, except as specifically authorized herein. If you acquire any rights in the Twitter Marks or any confusingly similar marks, by operation of law or otherwise, you will, at no expense to Twitter, immediately assign such rights to Twitter.

B. Feedback. You may provide Twitter with comments concerning the Licensed Material, Twitter Applications or your evaluation and use thereof (collectively, “Feedback”). You hereby grant Twitter all rights, title and ownership of such Feedback (including all intellectual property rights therein), and Twitter may use the Feedback for any and all commercial and non-commercial purposes with no obligation of any kind to you.

V. Termination. Twitter may immediately terminate or suspend this Agreement, any rights granted herein, and/or your license to the Licensed Materials, at its sole discretion at any time, for any reason by providing notice to you. You may terminate this Agreement at any time by ceasing your access to the Twitter API and use of all Twitter Content. Upon termination of this Agreement, (a) all licenses granted herein immediately expire and you must cease use of all Licensed Materials; and (b) you shall permanently delete all Licensed Material and Twitter Marks in all forms and types of media, and copies thereof, in your possession. The parties to this Agreement will not be liable to each other for any damages resulting solely from termination of this Agreement as permitted under this Agreement. Sections II (Restrictions on Use of Licensed Materials), IV (Ownership and Feedback), V (Termination), VI (Confidentiality), VII (Compliance Audit), VIII (Warranty Disclaimer), IX (Indemnification), X (Limitation of Liability) and XII (Miscellaneous) of this Agreement will survive the termination of this Agreement.

VI. Confidentiality. You may be given access to certain non-public information, software, and specifications relating to the Licensed Material (“Confidential Information”), which is confidential and proprietary to Twitter. You may use this Confidential Information only as necessary in exercising your rights granted in this Agreement. You may not disclose any of this Confidential Information to any third party without Twitter’s prior written consent. You agree that you will protect this Confidential Information from unauthorized use, access, or disclosure in the same manner that you would use to protect your own confidential and proprietary information of a similar nature and in no event with less than a reasonable degree of care.

VII. Compliance Audit. Twitter, or a third party agent subject to obligations of confidentiality, shall be entitled to inspect and audit any records or activity related to your access to the Licensed Material for the purpose of verifying compliance with this Agreement. Twitter may exercise its audit right at any time upon notice. You will provide your full cooperation and assistance with such audit and provide access to all Licensed Material in your possession or control, applicable agreements and records. Without limiting the generality of the foregoing, as part of the audit, Twitter may request, and you agree to provide, a written report, signed by an authorized representative, listing your then-current deployment of the Licensed Material and Twitter Content. The rights and requirements of this section will survive for one (1) year following the termination of this Agreement.

VIII. Warranty Disclaimer. THE LICENSED MATERIAL IS PROVIDED TO YOU “AS IS”, “WHERE IS”, WITH ALL FAULTS AND EACH PARTY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR A PARTICULAR PURPOSE, AND ANY WARRANTIES OR CONDITIONS ARISING OUT OF THIS AGREEMENT, COURSE OF DEALING OR USAGE OF TRADE. TWITTER DOES NOT WARRANT THAT THE LICENSED MATERIAL OR ANY OTHER TWITTER PRODUCT OR SERVICE PROVIDED HEREUNDER WILL MEET ANY OF YOUR REQUIREMENTS OR THAT USE OF SUCH LICENSED MATERIAL OR OTHER PRODUCTS OR SERVICES WILL BE ERROR-FREE, UNINTERRUPTED, VIRUS-FREE OR SECURE. THIS DISCLAIMER OF WARRANTY MAY NOT BE VALID IN SOME JURISDICTIONS AND YOU MAY HAVE WARRANTY RIGHTS UNDER LAW WHICH MAY NOT BE WAIVED OR DISCLAIMED. ANY SUCH WARRANTY EXTENDS ONLY FOR THIRTY (30) DAYS FROM THE EFFECTIVE DATE OF THIS AGREEMENT (UNLESS SUCH LAW PROVIDES OTHERWISE).

IX. Indemnification. You shall defend Twitter against any and all actions, demands, claims and suits (including without limitation product liability claims), and indemnify and hold Twitter harmless from any and all liabilities, damages and costs (including without limitation reasonable attorneys’ fees) to the extent arising out of: (i) your use of the Licensed Material in any manner that is inconsistent with this Agreement; or (ii) the performance, promotion, sale or distribution of your Services. In the event Twitter seeks indemnification or defense from you under this provision, Twitter will promptly notify you in writing of the claim(s) brought against Twitter for which it seeks indemnification or defense. Twitter reserves the right, at its option and sole discretion, to assume full control of the defense of claims with legal counsel of its choice. You may not enter into any third party agreement, which would, in any manner whatsoever, affect the rights of Twitter, constitute an admission of fault by Twitter or bind Twitter in any manner, without the prior written consent of Twitter. In the event Twitter assumes control of the defense of such claim, Twitter shall not settle any such claim requiring payment from you without your prior written approval.

X. Limitation of Liability. IN NO EVENT WILL TWITTER BE LIABLE TO YOU OR ANY END USERS FOR ANY INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY, PUNITIVE OR CONSEQUENTIAL DAMAGES OR ANY LOSS OF OR DAMAGE TO USE, DATA, BUSINESS, GOODWILL OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT. IN ANY CASE, TWITTER’S AGGREGATE LIABILITY FOR ANY AND ALL CLAIMS UNDER THIS AGREEMENT WILL NOT EXCEED $50.00 USD. THE FOREGOING LIMITATIONS, EXCLUSIONS AND DISCLAIMERS SHALL APPLY REGARDLESS OF WHETHER SUCH LIABILITY ARISES FROM ANY CLAIM BASED UPON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, AND WHETHER OR NOT TWITTER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. INSOFAR AS APPLICABLE LAW PROHIBITS ANY LIMITATION ON LIABILITY HEREIN, THE PARTIES AGREE THAT SUCH LIMITATION WILL BE AUTOMATICALLY MODIFIED, BUT ONLY TO THE EXTENT SO AS TO MAKE THE LIMITATION COMPLIANT WITH APPLICABLE LAW. THE PARTIES AGREE THAT THE LIMITATIONS ON LIABILITIES SET FORTH HEREIN ARE AGREED ALLOCATIONS OF RISK AND SUCH LIMITATIONS WILL APPLY NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY.

XI. Agreement Updates. Twitter may update or modify this Agreement or any of the Incorporated Developer Terms from time to time at its sole discretion by posting the changes on this site or by otherwise notifying you (such notice may be via email). You acknowledge that these updates and modifications may adversely affect how your Service accesses or communicates with the Twitter API. If any change is unacceptable to you, your only recourse is to cease all use of the Licensed Material. Your continued access or use of the Licensed Material will constitute binding acceptance of such updates and modifications.

XII. Miscellaneous.
A. Assignment. You may not assign any of the rights or obligations granted hereunder, in whole or in part, whether voluntarily or by operation of law, contract, merger (whether you are the surviving or disappearing entity), stock or asset sale, consolidation, dissolution, through government action or otherwise, except with the prior written consent of Twitter, Inc. Twitter, Inc. is authorized to sign modifications and consents on behalf of Twitter International Unlimited Company, an Irish company responsible for the information of Twitter users who live outside the United States. Any attempted assignment in violation of this paragraph is null and void, and Twitter may terminate this Agreement.

B. User Protection. Unless explicitly approved otherwise by Twitter in writing, you may not use, or knowingly display, distribute, or otherwise make Twitter Content, or information derived from Twitter Content, available to any entity for the purpose of: (a) conducting or providing surveillance or gathering intelligence, including but not limited to investigating or tracking Twitter users or Twitter Content; (b) conducting or providing analysis or research for any unlawful or discriminatory purpose, or in a manner that would be inconsistent with Twitter users’ reasonable expectations of privacy; © monitoring sensitive events (including but not limited to protests, rallies, or community organizing meetings); or (d) targeting, segmenting, or profiling individuals based on sensitive personal information, including their health (e.g., pregnancy), negative financial status or condition, political affiliation or beliefs, racial or ethnic origin, religious or philosophical affiliation or beliefs, sex life or sexual orientation, trade union membership, Twitter Content relating to any alleged or actual commission of a crime, or any other sensitive categories of personal information prohibited by law.

C. Government Use. If you will display, distribute, or otherwise make available any Twitter Content to End Users that are, or that act on behalf of, any government-related entity (each a “Government End User”), You will identify all such Government End Users when submitting that use case for review to Twitter and will thereafter notify Twitter in writing of any new Government End Users, and any new use cases with existing Government End Users, prior to the Services displaying, distributing, or otherwise making available any Twitter Content to a Government End User or for any new use case, and Twitter will have the right at anytime to prohibit you from making Twitter Content available to any new Government End User. In no event shall your use, or knowingly display, distribute, or otherwise make Twitter Content, or information derived from Twitter Content, available to any Government End User whose primary function or mission includes conducting surveillance or gathering intelligence. If law enforcement personnel request information about Twitter or its users for the purposes of an ongoing investigation, You may refer them to Twitter’s Guidelines for Law Enforcement located at https://t.co/le. The Twitter API and Twitter Content are “commercial items” as that term is defined at 48 C.F.R. 2.101, consisting of “commercial computer software” and “commercial computer software documentation” as such terms are used in 48 C.F.R. 12.212. Any use, modification, derivative, reproduction, release, performance, display, disclosure or distribution of the Twitter API or Twitter Content by any government entity is prohibited, except as expressly permitted by the terms of this Agreement. Additionally, any use by U.S. government entities must be in accordance with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4. If you use the Twitter API or Twitter Content in your official capacity as an employee or representative of a U.S., state or local government entity and you are legally unable to accept the indemnity, jurisdiction, venue or other clauses herein, then those clauses do not apply to such entity, but only to the extent as required by applicable law. Contractor/manufacturer is Twitter, Inc. 1355 Market Street, Suite 900, San Francisco, California 94103.

D. Compliance with Laws; Export and Import. Each party will comply with all applicable foreign, federal, state, and local laws, rules and regulations, including without limitation, all applicable laws relating to bribery and/or corruption. The Licensed Material is subject to U.S. export laws and may be subject to import and use laws of the country where it is delivered or used. You agree to abide by these laws. Under these laws, the Licensed Material may not be sold, leased, downloaded, moved, exported, re-exported, or transferred across borders without a license, or approval from the relevant government authority, to any country or to any foreign national restricted by these laws, including countries embargoed by the U.S. Government (currently Cuba, Iran, North Korea, Northern Sudan and Syria); or to any restricted or denied end-user including, but not limited to, any person or entity prohibited by the U.S. Office of Foreign Assets Control; or for any restricted end-use. You will maintain all rights and licenses that are required with respect to your Services.

E. Data Protection Addendum. The parties agree that in addition to this Agreement, the Twitter Controller-to-Controller Data Protection Addendum located at https://gdpr.twitter.com/en/controller-to-controller-transfers.html shall apply with respect to the processing of Twitter Content and is hereby incorporated by reference.

F. Governing Law; Dispute Resolution. This Agreement will be governed by and construed in accordance with the laws of the State of California, without regard to or application of conflicts of law rules or principles. Any dispute, claim or controversy arising out of or relating to this Agreement or the breach, termination, enforcement, interpretation or validity thereof, including the determination of the scope or applicability of this Agreement to arbitrate, shall be determined by arbitration in San Francisco, CA before a single arbitrator. The arbitration shall be administered by JAMS pursuant to its Comprehensive Arbitration Rules and Procedures. Judgment on the Award may be entered in any court having jurisdiction. You and Twitter hereby expressly waive trial by jury. As an alternative, you may bring your claim in your local “small claims” court, if permitted by that small claims court’s rules. You may bring claims only on your own behalf, and unless Twitter agrees, the arbitrator may not consolidate more than one person’s claims. Despite the foregoing, you agree that money damages would be an inadequate remedy for Twitter in the event of a breach or threatened breach of a provision of this Agreement protecting Twitter’s intellectual property or Confidential Information, and that in the event of such a breach or threat, Twitter, in addition to any other remedies to which it is entitled, is entitled to such preliminary or injunctive relief (including an order prohibiting Company from taking actions in breach of such provisions), without the need for posting bond, and specific performance as may be appropriate. The parties agree that neither the United Nations Convention on Contracts for the International Sale of Goods, nor the Uniform Computer Information Transaction Act (UCITA) shall apply to this Agreement, regardless of the states in which the parties do business or are incorporated. No waiver by Twitter of any covenant or right under this Agreement will be effective unless memorialized in a writing duly authorized by Twitter.

G. Severability. If any part of this Agreement is determined to be invalid or unenforceable by a court of competent jurisdiction, that provision will be enforced to the maximum extent permissible and the remaining provisions of this Agreement will remain in full force and effect.

H. Entire Agreement. This Agreement constitutes the entire agreement among the parties with respect to the subject matter and supersedes and merges all prior proposals, understandings and contemporaneous communications. Any modification to this Agreement must be in a writing signed by both you and Twitter, Inc. This Agreement does not create or imply any partnership, agency or joint venture.

Developer Policy

Twitter + Developers
Twitter loves developers. We’re delighted and amazed by the tools and services this community creates by harnessing the power of Twitter data. As part of our commitment to this community, we aim to provide data access that is open and fair for developers, safe for people on Twitter, and beneficial for the Twitter platform as a whole. To further these goals we’ve crafted the Developer Policy as a guide to help people understand our rules and expectations about appropriate API and Twitter Content usage.

This Developer Policy (“Policy”) provides rules and guidelines for developers who interact with Twitter’s ecosystem of applications, services, website, web pages and content. It is part of your contract with Twitter governing access to and use of the Twitter API and Twitter Content (either as part of the Developer Agreement or other written agreement with Twitter). Policy violations are considered violations of your agreement. This Policy may be changed from time to time without notice. Capitalized terms used in this Policy, which are not defined in this Policy, will have the respective meanings ascribed to them in the Developer Agreement or the Master License Agreement.

Using this policy
We’ve structured this policy to make it as easy to follow as possible. Please keep information from the following policy sections top of mind as you use the Twitter API and Twitter Content:

Set Yourself Up for Success - You are responsible for complying with all Twitter policies. It’s important that you review and understand this Policy, as well as the policies we link to in this document, before you access the Twitter API and Twitter Content. The time spent reviewing our policies may save you hours of rework down the road.
Privacy and Control are Essential - Protecting and defending the privacy of people on Twitter is built into the core DNA of our company. As such, we prohibit the use of Twitter data in any way that would be inconsistent with people’s reasonable expectations of privacy. By building on the Twitter API or accessing Twitter Content, you have a special role to play in safeguarding this commitment, most importantly by respecting people’s privacy and providing them with transparency and control over how their data is used.
Follow the Platform Usage Guidelines - Getting approved to access the Twitter API and Twitter Content is just the first step. Our Platform Usage Guidelines should be your first stop anytime you have questions about how to ensure policy compliance for your planned use of the Twitter platform.
We’ve provided a lot more detail on what each of these three key sections mean below. Please review them carefully to ensure that your usage of the Twitter API and Twitter Content is consistent with our policies.

If we believe you are in violation of this Policy (or any other Twitter policy), we may suspend or permanently revoke your access to the Twitter API and Twitter Content. If this happens to you, do not apply for or register additional API keys. Instead, contact us via the API Policy Support form.

Finally, please note that Twitter may monitor your use of the Twitter API to improve the Twitter Applications, to examine any commercial use, and to ensure your compliance with your approved use case and this Policy.

Thanks for reading, and thank you for building with us! We look forward to seeing what you create!

Set yourself up for success
You can avoid many potential pitfalls while using the Twitter API by ensuring that your service has been built the right way from day 1. This section of the Developer Policy contains rules that all developers must follow before using the Twitter API or Twitter Content.

We review all proposed uses of the Twitter developer platform to verify policy compliance — so you’re required to disclose (and update, as applicable) your planned use of the Twitter API and Twitter Content in order to be granted and to maintain access. All new developers must apply for a developer account to access the Twitter API. Current developers without an approved developer account must apply for one as directed to do so by Twitter. As part of this process, you’ll need to provide us with a written description of your intended uses of the Twitter API and Twitter Content.

Your use case description is binding on you, and any substantive deviation from it may constitute a violation of our rules and result in enforcement action. You must notify us of any substantive modification to your use case and receive approval before you may begin using Twitter Content for that new purpose. Failure to do so may result in suspension and termination of your API and data access. You can update your use case by visiting our API Policy Support form, selecting I need to update my developer use case, or as otherwise agreed by Twitter.

By building on the Twitter API or accessing Twitter Content, you must comply with ALL Twitter policies. These include this Developer Policy, the Automation Rules, the Display Requirements, the API Restricted Uses Rules, the Twitter Rules, the Twitter Brand Resources, the Periscope Community Guidelines, and the Periscope Trademark Guidelines, as well as any other agreements you enter into with Twitter relating to your use of the Twitter API or Twitter Content, including but not limited to the Developer Agreement or a Master Licensing Agreement or Order (as applicable). You must also comply with any modifications to these policies and any new policies launched by Twitter. It is your responsibility to monitor the use of your service and to design your service to prevent violations of Twitter policy by people who use it. Failure to do so may result in suspension or termination of your API and Twitter Content access.

You may not register multiple applications for a single use case or substantially similar or overlapping use cases. In this context, a “use case” is a consistent set of analyses, displays, or actions performed via an application. Please note that providing the same service or application to different people (including “white label” versions of a tool or service) counts as a single use case.

As a single exception to these rules, you may create and use a maximum of 3 applications for development, staging, and production instances of the same service. These apps must be registered to a single account, and should be clearly identified (in the name and description) as dev, staging, and prod instances of a single service. You may not use development or staging applications for production purposes.
You must keep all API keys or other access credentials private. You may not use, and may not encourage or facilitate others to use, API keys or other access credentials owned by others.

Your license agreement with Twitter limits your use of the Twitter API and Twitter Content. Among other things, the Twitter API has rate limits which help to ensure fair data usage and to combat spam on the platform. You may not exceed or circumvent rate limits, or any other limitations or restrictions described in this Policy or your agreement with Twitter, listed on the Developer Site, or communicated to you by Twitter.

You may not remove or alter any proprietary notices or marks on Twitter Content received via the Twitter API. This helps to make sure that people know where Twitter Content is coming from, and who it belongs to.

For data integrity and platform health reasons, you may not interfere with, intercept, disrupt, or disable any features of the Twitter API or the Twitter service. In other words, use the APIs as intended and documented on developer.twitter.com. Refer to our HackerOne guidelines for more details about acceptable use.

Privacy and control are essential
Twitter takes privacy seriously, and we expect everyone using Twitter Content and the Twitter API to do the same. Any use of the Twitter developer platform, Twitter API, or Twitter Content in a manner that is inconsistent with peoples’ reasonable expectations of privacy may be subject to enforcement action, which can include suspension and termination of API and Twitter Content access.

Your commitment to privacy and control must extend to all uses of Twitter Content and all aspects of the service that you build using our API. To that end, the people using your service must understand and consent to how you use their data, and how you access Twitter on their behalf. This can be accomplished through providing people with a clear, comprehensive, and transparent privacy policy, as well as ensuring that you get express and informed consent from each person using your service before taking any action on their behalf. Please note that a person authenticating into your service does not by itself constitute consent.

Consent & permissions
In particular, you must get express and informed consent from people before doing any of the following:

Taking any actions on their behalf. This includes (but is not limited to):

Posting content to Twitter

Following/unfollowing accounts

Modifying profile or account information

Starting a Periscope Broadcast

Adding hashtags or any other content to Tweets

Republishing content accessed by means other than via the Twitter API or other Twitter tools

Using someone’s Twitter Content to promote a product or service

Storing non-public content such as Direct Messages (DMs), or any other private or confidential information

Sharing or publishing protected content, or any other private or confidential information

If your service allows people to post content to Twitter you must do the following before publishing:

Show exactly what will be published

Make it clear to people using your service what geo information (if any) will be added to the content

If your service allows people to post content to both your service and Twitter, you must do the following before publishing:

Obtain permission to post the content

Explain where you will post the content

You must respect the protected and blocked status of all Twitter Content. You may not serve content obtained using one person’s authentication token to a different person who is not authorized to view that content.

Protected accounts: A protected account’s content is only available to people who have been approved by the owner to follow that account. So, if you run a service that accesses protected accounts, you may only do so to serve such content to the specific people with permission to view that content.

Blocked accounts: People on Twitter are able to block access to their accounts for any reason they choose. Commingling information obtained from tokens (or any other API-based action) to bypass this choice is not permitted.

As Direct Messages (DMs) are non-public in nature, services that provide DM features must take extra steps to safeguard personal privacy. You may not serve DM content to people who are not authorized to view that content. If your service provides DM functionality you must also:

Notify people if you send read receipt events for DMs. You can do this by providing a notice directly in your service, or by displaying read receipts from other participants in a conversation.
Get consent before configuring media to be sent in a DM as “shared” (i.e. reusable across multiple DMs). If you do allow media in a DM to be “shared,” you must provide a clear notice that this content will be accessible to anyone with the media’s URL.

Content compliance
If you store Twitter Content offline, you must keep it up to date with the current state of that content on Twitter. Specifically, you must delete or modify any content you have if it is deleted or modified on Twitter. This must be done as soon as reasonably possible, or within 24 hours after receiving a request to do so by Twitter or the applicable Twitter account owner, or as otherwise required by your agreement with Twitter or applicable law. This must be done unless otherwise prohibited by law, and only then with the express written permission of Twitter.

Modified content can take various forms. This includes (but is not limited to):

Content that has been made private or gained protected status
Content that has been suspended from the platform

Content that has had geotags removed from it

Content that has been withheld or removed from Twitter

Off-Twitter matching
We limit the circumstances under which you may match a person on Twitter to information obtained or stored off-Twitter. Off-Twitter matching involves associating Twitter Content, including a Twitter @handle or user ID, with a person, household, device, browser, or other off-Twitter identifier. You may only do this if you have express opt-in consent from the person before making the association, or as described below.

In situations in which you don’t have a person’s express, opt-in consent to link their Twitter identity to an off-Twitter identifier, we require that any connection you draw be based only on information that someone would reasonably expect to be used for that purpose. In addition, absent a person’s express opt-in consent you may only attempt to match your records about someone to a Twitter identity based on:

Information provided directly to you by the person. Note that records about individuals with whom you have no prior relationship, including data about individuals obtained from third parties, do not meet this standard; and/or

Public data. “Public data” in this context refers to:

Information about a person that you obtained from a public, generally-available resource (such as a directory of members of a professional association)

Information on Twitter about a person that is publicly available, including:

Tweets

Profile information, including an account bio and publicly-stated location

Display name and @handle

Your privacy policy
You must display your service’s privacy policy to people before they are permitted to download, install, or sign up to your service. It must disclose at least the following information:

The information that you collect from people who use your service

How you use and share that information (including with Twitter)

How people can contact you with inquiries and requests regarding their information

Your privacy policy must be consistent with all applicable laws, and be no less protective of people than Twitter’s Privacy Policy and the privacy policy of our other services and corporate affiliates. You must cease your access to the Twitter API and the use of all Twitter Content if you are unable to comply with your and/or Twitter’s Privacy Policy.

Using geo-data
Use of geo data comes with additional restrictions due to the sensitive nature of this information. If your service adds location information to Tweets or Periscope Broadcasts, you must disclose to people:

When you add location information

Whether you add location information as a geotag or annotations data

Whether your location information is listed as a place, or as geographic coordinates

If your application allows people to Tweet with their location you must comply with Twitter’s geo guidelines in full.

Any use of location data or geographic information on a standalone basis is prohibited. You may not (and may not permit others to) store, aggregate, or cache location data and other geographic information contained in Twitter Content, except as part of a Tweet or Periscope Broadcast. For example, you may not separate location data or geographic information out from Tweets to show where individuals have been over time. Heat maps and related tools that show aggregated geo activity (e.g.: the number of people in a city using a hashtag) are permitted.

Twitter passwords
You may not store Twitter passwords, or request that people provide their Twitter password, account credentials, or developer application information (including consumer key) to you directly. We suggest the use of Sign-in with Twitter as the authentication tool to link your service and people on Twitter.

Platform usage guidelines
Have you taken care to review Twitter’s policies and set up your API access the right way? Does your service follow Twitter’s privacy and control guidelines? If you can answer yes to these two questions, then you are ready to start using the Twitter API and Twitter Content. Twitter’s Platform Usage Guidelines provide the assistance needed to ensure that your use of Twitter Content is compliant from day 1 throughout the lifecycle of your service. We suggest reviewing these rules on a regular basis to make sure that your integration is operating in a way that is safe and beneficial to people on Twitter and the Twitter platform as a whole.

Spam, bots, and automation
The use of the Twitter API and developer products to create spam, or engage in any form of platform manipulation, is prohibited. You should review the Twitter Rules on platform manipulation and spam, and ensure that your service does not, and does not enable people to, violate our policies.

Services that perform write actions, including posting Tweets, following accounts, or sending Direct Messages, must follow the Automation Rules. In particular, you should:

Always get explicit consent before sending people automated replies or Direct Messages

Immediately respect requests to opt-out of being contacted by you

Never perform bulk, aggressive, or spammy actions, including bulk following

Never post identical or substantially similar content across multiple accounts

If you’re operating an API-based bot account you must clearly indicate what the account is and who is responsible for it. You should never mislead or confuse people about whether your account is or is not a bot. A good way to do this is by including a statement that the account is a bot in the profile bio.

Twitter performance benchmarking
You may not use the Twitter API to measure the availability, performance, functionality, or usage of Twitter for benchmarking, competitive, or commercial purposes. For example, you should never use the Twitter API to:

Calculate aggregate Twitter metrics, such as the total number of Monthly Actives (MAs) or Daily Actives (DAs)

Calculate aggregate Periscope metrics, such as total number of broadcast views

Calculate aggregate Twitter Tweet metrics, such as the total number of Tweets posted per day, or the number of account engagements

Measure or analyze the responsiveness of Twitter

Measure or analyze spam or security on Twitter, except as permitted below

We support research that helps improve conversational health on Twitter. You may use the Twitter API and Twitter Content to measure and analyze topics like spam, abuse, or other platform health-related topics for non-commercial research purposes. You may not develop, create, or offer commercial services using the Twitter API or Twitter Content that measure, analyze, or attempt to identify behaviors or content which violate Twitter policies without express written permission from Twitter.

If you have questions about whether your use case qualifies as non-commercial research for this purpose please submit a request via the API Policy Support form.

Public display of Tweets
You must maintain the integrity of all Twitter Content that you display publicly or to people who use your service. If you don’t use Twitter for Websites to display content, then you must use the Twitter API to retrieve the most current version available for display. If displayed content ceases to be available through the Twitter API, then you must remove it from your service as soon as reasonably possible, or within 24 hours after the receipt of a removal request from Twitter, or the applicable Twitter account owner, or as otherwise required by applicable law.

There are specific rules you must follow if you display Twitter Content offline. Follow the guidelines for using Tweets in broadcast if you display Tweets offline. Follow the guidelines for using Periscope Broadcasts if you display Periscope Broadcasts offline.

If you embed or display Tweets, you must contact us about your Twitter API access if your site exceeds 10 million daily impressions. Twitter reserves the right to require additional terms as a condition to your use of the Twitter API. Additional restrictions on Twitter for Websites developer use include:

Embedded Tweets and/or embedded timelines

You must provide people with legally sufficient notice that fully discloses Twitter’s collection and use of data about browsing activities on your website, including for interest-based advertising and personalization. You must also obtain legally sufficient consent from people for such collection and use
You must provide legally sufficient instructions on how people can opt out of Twitter’s interest-based advertising and personalization as described here

Twitter for Websites widgets

You must ensure that people are provided with clear and comprehensive information about, and consent to, the storing and accessing of cookies or other information on their devices as described in Twitter’s cookie use, where providing such information and obtaining such consent is required by law

Services targeted to children under 13

Services targeted to children under 13 must opt out of tailoring Twitter in any embedded Tweet and/or embedded timelines by setting the opt-out parameter to be ‘true’ as described here

Content redistribution
The best place to get Twitter Content is directly from Twitter. Consequently, we restrict the redistribution of Twitter Content to third parties. If you provide Twitter Content to third parties, including downloadable datasets or via an API, you may only distribute Tweet IDs, Direct Message IDs, and/or User IDs (except as described below). We also grant special permissions to academic researchers sharing Tweet IDs and User IDs for non-commercial research purposes.

In total, you may not distribute more than 1,500,000 Tweet IDs to any entity (inclusive of multiple individuals associated with a single entity) within any 30 day period unless you have received written permission from Twitter. In addition, all developers may provide up to 50,000 public Tweets Objects and/or User Objects to each person who uses your service on a daily basis if this is done via non-automated means (e.g., download of spreadsheets or PDFs).

Academic researchers are permitted to distribute an unlimited number of Tweet IDs and/or User IDs if they are doing so on behalf of an academic institution and for the sole purpose of non-commercial research. For example, you are permitted to share an unlimited number of Tweet IDs for the purpose of enabling peer review or validation of your research. If you have questions about whether your use case qualifies under this category please submit a request via the API Policy Support form.

Any Twitter Content provided to third parties remains subject to this Policy, and those third parties must agree to the Twitter Terms of Service, Privacy Policy, Developer Agreement, and Developer Policy before receiving such downloads. You may not enable any entity to circumvent any other limitations or restrictions on the distribution of Twitter Content as contained in this Policy, the Developer Agreement, or any other agreement with Twitter.

Pay to Engage
Your service shouldn’t compensate people to take actions on Twitter, as that results in inauthentic engagement that degrades the health of the platform. As you use the Twitter API you may not sell or receive monetary or virtual compensation for any Twitter or Periscope actions. This includes, but is not limited to, Tweets, follows, unfollows, retweets, likes, comments, and replies.

Service authenticity
You must clearly identify your service so that people can understand its source and purpose. Don’t use names, logos, or URLs that mask your service’s identity and features, or that falsely imply an affiliation with Twitter or third parties. Note that creating applications for the purpose of selling names, or to prevent others from using names, is prohibited.

You may not use any URL (including shortened URLs) for your service that directs people to:

A site that is unrelated to your service

A spam or malware site

A site that encourages people to violate Twitter policy

Twitter name, logo, and likeness
You may only use and display the Twitter name and logo to identify Twitter as the source of Twitter Content. You should never use the Twitter name and logo, the Twitter Official Partner Program badge, or any other similar marks or names in a manner that creates a false sense of endorsement, sponsorship, or association with Twitter. The Twitter Brand Resources contain detailed information to help you use the Twitter brand in the right way.

You may only use the Twitter Verified Account badge and any other enhanced account categorization as it is reported to you by Twitter through the API. This helps people know that the content your service displays is equivalent to that shown on Twitter.

Advertising on Twitter
There are restrictions regarding how and where you are allowed to advertise around Twitter Content. To start, your advertisements can’t resemble or reasonably be confused by people as a Tweet or Periscope Broadcast. Other rules on advertising include:

There must be a clear separation between Twitter Content and your advertisements. You may not place any advertisements within the Twitter timeline or on or within Periscope Broadcasts on your service other than Twitter Ads or advertisements made available through the official Twitter Kit integration with MoPub.

Twitter reserves the right to serve advertising via the Twitter API. If you decide to serve Twitter Ads once we start delivering them via the API, we will share a portion of advertising revenue with you in accordance with the relevant terms and conditions.

You may not use Twitter Content, or information obtained from the Twitter API to target people with advertising outside of the Twitter platform.

The following additional rules apply for any use of the Twitter services or features listed below:

Twitter Login
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.

Twitter Cards

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

Periscope Producer

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