Found in 16 of 343 platforms tracked (5% adoption) · 31 provisions
The approval mechanism establishes Cohere's authority to gate access based on use case review, while the documented harm assessment requirement creates a procedural obligation for developers to evalu…
This clause extends Google's usage policy compliance requirements beyond direct API users to their downstream users, establishing a contractual obligation for API users to maintain control and monito…
The clause establishes Google's operational authority to enforce the Acceptable Use Policy through service suspension as a remedial measure, with a defined notice-and-cure period before suspension ta…
The clause creates a conditional authorization structure: real-time asset and person tracking is permitted under the service only when preceded by documented consent acquisition. This establishes a c…
This provision defines the scope of acceptable application development on the Google Maps platform by establishing that derivative or competing mapping services are not permitted uses. It operational…
This clause establishes Meta's operational authority to remove users from the platform without triggering notice, cure, or explanation requirements. The provision defines the platform's enforcement m…
This provision establishes Meta's unilateral authority to interpret compliance, conduct audits of data usage, and modify service access without specifying advance notice requirements or procedural co…
The audit right establishes Meta's operational authority to inspect developer applications and systems for policy compliance. This mechanism enables Meta to monitor adherence to platform requirements…
This provision operationalizes Meta's legal obligations under federal children's privacy law by distributing compliance responsibility to third-party developers who build on Meta's platforms. The cla…
The clause establishes that default model behavior is not fixed but subject to operator-level customization, creating a tiered control architecture where baseline outputs can be adjusted through oper…
The provision establishes the operational scope of data collection infrastructure that Paramount+ and its partners maintain. It specifies the technical mechanisms (cookies, SDKs, pixel tags) and the …
This provision defines the operational scope of the Public API Network as a public catalog and allocates the responsibility for content review to the publishing user rather than to Postman. The claus…
This clause creates a multi-party contractual structure where RapidAPI's liability and obligations do not extend to third-party API providers. The provision establishes that API provider terms operat…
This provision establishes the operational framework under which personal information flows to third parties beyond Shopify's direct control. The clause creates a contractual requirement that app dev…
This provision establishes a contractual obligation chain in which API developers function as intermediary enforcers of the policy terms. It allocates to developers the operational responsibility for…
Device fingerprinting enables persistent user identification and tracking across sessions without relying solely on cookies or login credentials. The operational significance is that this mechanism a…
This disclosure establishes the operational architecture of the service and clarifies that backend routing occurs regardless of API key usage, which affects data flow and processing procedures within…
This clause defines the ownership structure of the platform and reserves intellectual property control to Google. It establishes the baseline under which all user rights to access and use the platfor…
This clause establishes a contractual obligation for customers to propagate Google's substantive terms downstream to their own end users, creating a chain of contractual compliance and ensuring that …
This restriction establishes the permissible scope of integration for developers using Google's mapping services. It ensures Google Maps Platform content and functionality remain contained within Goo…
The clause establishes operational constraints on how customers may handle Content retrieved through the platform, distinguishing between prohibited storage practices and a narrowly-defined exception…
The prohibition creates a contractual constraint on how customers may store and deploy map data, requiring adherence to specified use cases rather than permitting unlimited local storage or reproduct…
This clause establishes a contractual limitation on the scope of permitted use of the platform, requiring customers to differentiate their applications from Google's own product portfolio. The provis…
This audit right enables Meta to monitor developer conduct across its platform ecosystem and enforce compliance with established policies. The provision supports Meta's ability to maintain platform i…
This provision allocates responsibility for data governance by clarifying the scope of Plaid's privacy obligations. It establishes that Plaid does not control or govern how third-party developers han…
This provision clarifies the scope of the Additional Terms by distinguishing between the executable code (governed by these terms) and the underlying source code (governed by separate open source lic…
The disclosure establishes transparency regarding the licensing framework governing Chrome's source code components and specifies where users and third parties can access license terms and source cod…
The attribution requirement establishes a mandatory disclosure mechanism that links Maps API implementations to Google as the service provider. This obligation ensures consistent brand attribution ac…
This clause establishes Meta's operational authority to incorporate user-generated feedback into platform development, product improvement, and related business purposes without royalty obligations o…
The Developer Terms of Use establish a distinct contractual layer for API access and third-party application development, which may include additional restrictions on data use, rate limits, and intel…
This clause defines the boundary of intellectual property control between the parties and establishes the scope of Twilio's processing rights over customer-generated data. The provision operationaliz…
Create a free account and watch the platforms that matter to you. We'll email you the moment something changes.
A developer / api restrictions clause is a provision in a platform's terms of service or privacy policy governing developer / api restrictions-related rights, obligations, or restrictions.
ConductAtlas tracks 16 platforms with developer / api restrictions clauses - roughly 5% of platforms in the archive. 16 are classified as high severity.
Severity reflects the magnitude of rights waived, availability of opt-out, breadth of users affected, financial or legal exposure created, and the degree of discretion retained by the platform.