← All pages

Create Derivative

Definition: A near-duplicate tag of Derivative Works. With one confirmed exception (see below), the two keywords co-occur on the exact same snippets throughout this wiki — the source dataset’s keyword extractor appears to match “derivative works” and “create derivative” as two separate hits within the same sentence, not two independent clause types. Risk level: Identical to Derivative Works — see that page for the risk discussion. This page exists only to preserve the dataset’s original keyword granularity, not to document a distinct clause.

Platforms Using This Clause

Common Wording

For most platforms, see Derivative Works — every snippet tagged create derivative is byte-identical to a snippet also tagged derivative works on the same platform page and date, except for the snippet below.

Limits on using our intellectual property If you use content covered by intellectual property rights that we have and make available in our Products… we retain all rights to that content (but not yours)… You must obtain our written permission (or permission under an open source license) to modify, translate, create derivative works of, decompile, or reverse engineer our products or their components, or otherwise attempt to extract source code from us, unless an exception is provided for under applicable law. — Facebook, Terms of Service, 2022-07-26 (the exact same text persists through 2023-05-12; the create derivative/derivative works tag divergence specifically is confirmed only for 2022-07-26 through 2023-02-01 — from 2023-03-07 onward this snippet is tagged with both keywords, ending the divergence) — restricts users from creating derivative works of Meta-owned IP/products, the reverse direction from the Content-license clause this keyword usually co-tags.

Notes & Trends

Confirmed for Twitter’s Developer Agreement and Terms of Service, and Facebook’s “Other” page (verified programmatically: every create derivative-tagged snippet on every date in those pages is also tagged derivative works on that same date). First confirmed divergence: Facebook’s Terms of Service breaks this pattern on 47 dates (2022-07-26 through 2023-02-01) — a snippet tagged create derivative (“Limits on using our intellectual property”: “You must obtain our written permission… to modify, translate, create derivative works of, decompile, or reverse engineer our products…”) is not also tagged derivative works on those dates, even though it literally contains the phrase “create derivative works of.” This is a distinct clause from the main Content-license paragraph documented on Derivative Works — it restricts users from creating derivative works of Meta’s own IP/products (the reverse direction from Meta’s grant over user Content), not a duplicate tag of the same sentence. Worth treating create derivative as tracking genuinely independent language going forward, at least for Facebook’s Terms of Service. Facebook’s Terms of Service divergence does not recur on Instagram’s Terms of Service — verified programmatically across all 128 dates in that file, every create derivative-tagged snippet is also tagged derivative works on the same date, with no exception. Instagram’s ToS appears not to separately tag an equivalent “Limits on using our intellectual property” clause the way Facebook’s does. LinkedIn’s Terms of Service is a clean co-occurrence case (no divergence from derivative works), but notable for being the only platform page where this keyword’s snippet genuinely disappears from the document over time rather than persisting under different wording — see Derivative Works for the confirmed-via-raw-cross-check restructuring finding. Moltbook’s Terms of Service adds a second, independent occurrence of this exact phrase within the same document: separate from the Data-license grant, the “Limitations of Use” section also bans users (and their AI Agents) from “modify[ing], copy[ing], prepar[ing] derivative works of, decompil[ing], or reverse engineer[ing] any materials or software” on the site — the restriction direction, confirming this platform shows both directions for the clause type in one document. Pinterest’s Terms of Service is a clean co-occurrence case, but the most significant for this keyword cluster overall: it confirms the platform-grants-user-to-user-rights pattern documented under Derivative Works was present in this wiki’s dataset well before TikTok’s later, more widely-noted 2025-06-25 rewrite. Quora’s Terms of Service adds a third confirmed user-to-user occurrence (same baseline date as Pinterest’s) and is also the first platform in this wiki to show both the platform-claims-it-for-itself/users direction and the restriction direction for this exact keyword in one document — its “Restricted Uses” clause separately bans third parties from using AI/ML “to create derivative works of Our Content and Materials.” Snapchat’s Terms of Service is a fourth clean co-occurrence case and a fourth confirmed user-to-user grant at the same 2022-07-11 baseline date. Spotify’s Terms of Service is a fifth clean co-occurrence case, granted to Spotify alone rather than extended to other users. Threads’ Terms of Service is a sixth clean co-occurrence case, distinctive for explicitly extending the license to sharing onto independent fediverse Third Party Servers. Tumblr’s Terms of Service is a seventh clean co-occurrence case, notable for showing both directions of the underlying clause in one document via two mirrored reblogging licenses. Twitch’s Terms of Service is an eighth clean co-occurrence case, distinctive for a confirmed 2025-04-10 strengthening that adds a user-to-user version of the license alongside the original platform-only grant. WeChat’s Terms of Service is a ninth clean co-occurrence case, the restriction direction protecting WeChat Software itself. WhatsApp’s Terms of Service is a clean co-occurrence case for its Content-license grant, but its separate restriction clause uses prepare derivative alongside derivative works instead of create derivative — a second platform (after Moltbook’s “Limitations of Use”) showing this exact variant pairing, distinct from the Facebook-specific divergence noted above.