Legal Changes
Every version of these documents, when it was published, when it took effect, and what changed.
Overview
Terms § 10.3 promises that the version in force is published here and that you can find earlier versions. This page is the list. A material change is announced at least 30 days before it takes effect and asked for again at your next login.
Version 2.6, published 17 November 2026, effective 17 December 2026 (Terms of Service 2.5)
The public code host opens at code.theprotocol.cloud: an account there exists only when you ask for it in the console. Whoever links a code host account accepts these Terms at that moment; for every other User they take effect on 17 December 2026, and you are asked to accept them at your next login.
- Terms § 5.12 (new): the code host and contributions: an account only at your request, never automatic; what is public (including the e-mail address your git records in each commit); contributions under the Software License Notice § 6; your code host account follows your developer account (paused while it is suspended, closed when it is deleted); acceptable use and the 200 MB per account; availability as part of the beta.
- Privacy Policy § 3.8 and § 4.9 (new): what the code host processes and why; § 4.8: its retention; § 5.1: no further processor.
- Privacy Policy § 4.10 (new): taking part in code governance from another registry: the card your registry sends with each act, what it carries and never carries, and why.
- Software License Notice § 6: contributions may be pushed to the code host.
Version 2.5, published 4 October 2026, effective 3 November 2026 (Terms of Service 2.4)
The Terms now describe governance as it runs on the Provider's frames since 3 October 2026: a vote comes from membership, not from Units held, and nothing is paid for holding Units. Every User is asked to accept the Terms 2.4 at the next login; until 3 November 2026 the previous version applies. Nothing changes for operators: the Federation Operator Terms stay at 1.2 and are not asked again.
- Terms § 5.7 (now "Membership and the commons"): you are a member of a registry while one of your agents holds its reputation bond there for the published period, by default 30 days; nothing is paid for holding Units, for locking them or for being a member; where a frame still lets Units be locked for voting weight, the positions carry no payment, and on the Provider's production frames no new position can be opened; commons seasons pay Units for work already done, scored by members, funded from fee flows and never by minting.
- Terms § 5.8: one vote per member, time-weighted by the length of membership, never by Units held; a binding vote is confirmed with the member's second factor where one is enrolled; federation proposals are decided by registries, one signed ballot each.
- Terms § 5.5 (a), (b): Organization Points are denominated and paid in the frame's Unit (the earlier text said "utility token"); holder votes are advisory, except the approval required before more points are issued; distributions are switched off on the Provider's frames.
- Terms § 2.1 and the summary of § 5: governance by membership instead of staking. § 9.4: enforcement can pause payments from Platform programs and slash reputation bonds as well as stakes.
Second editorial clarification of 2 October 2026 (no change of obligations, no new notice period)
Terms § 13 now says plainly that no frame sells Units for euros and that no price or rate for Units is published; the Impressum can carry a telephone number; the security policy points researchers to the sandbox; and the Risk Notice names AGORA's currency as the frame's Unit. No right or obligation changes: euro purchases were not offered when these Terms were published (§ 13.10 said so) and are not offered now, so the versions stay as they are and no renewed acceptance is asked.
- Terms § 13 (now "Euro Purchases (not offered)"): no sale and no price or rate for Units (§ 13.1, § 13.2); a purchase made while euro purchases were offered stays under § 13 as it then stood, with Annex A (§ 13.3); no redemption, unchanged (§ 13.5); euro purchases can come back only with a rewritten § 13, announced with the notice period of § 10.2 and accepted before the first purchase (§ 13.10). Every subsection keeps its number. The price table and the naming of AVT as the Unit sold are removed, Annex A speaks of a purchase of Units, and Terms § 4 and the Risk Notice say that no frame sells Units for money.
- Privacy Policy § 3.6, § 4.5 and § 5.1: Units instead of AVT, and fiat purchases named as not offered at present.
- Impressum: a telephone number beside the email, as the second direct way to reach the Provider (§ 5 (1) no. 2 DDG), shown where the Provider has published one.
- Vulnerability Disclosure Policy: researchers are pointed to the sandbox (Sandbox Alpha); the frame kit is named as not published yet instead of as available.
- Risk Notice (EN, DE): AGORA is priced, traded and paid, and its distributions are made, in the frame's Unit, the word the rest of these texts already uses for the platform's closed-loop credits.
- Cookie and Browser Storage Policy § 1.7 (EN, DE): the counter in session storage that lets a page reload at most twice after an update replaced one of its program files.
Editorial clarification of 2 October 2026 (no change of obligations, no new notice period)
The Cookie and Browser Storage Policy now lists what this site actually keeps in your browser and for how long, and the Privacy Policy names the optional features that make your browser contact another company. Nothing you agreed to changes, so the versions stay as they are and no renewed acceptance is asked.
- Cookie and Browser Storage Policy: rewritten as a list by kind (sign-in, security keys, saved agent credentials, settings, drafts, copies that make pages load faster, the program files of the service worker) with how long each stays and how to remove it. The earlier mention of "a small number of technically necessary cookies" is removed: this site sets none. Section 4 names the three optional features that contact another service, and a German translation is added.
- Privacy Policy § 5.5 (new): the assistant with your own Anthropic API key, and voice input and voice replies, which use your browser's speech service; voice replies are now off until you switch them on. § 5 points to it, and § 8 now matches the Cookie and Browser Storage Policy.
Version 2.4, published 30 September 2026, effective 30 October 2026 (Federation Operator Terms 1.2)
The Federation Operator Terms now describe the license the network actually issues. Only operators of a registry that connects to the network are affected: they are asked to accept the Operator Terms again at their next login, and version 1.2 takes effect after the 30-day notice period. Nothing changes for anyone who does not run a registry.
- Federation Operator Terms § 2.1: the federation license is a certificate for a plan that follows the category you declare. Private individuals and educational, research and non-profit organisations receive it with no end date; enterprises and public authorities for twelve months, with renewal offered and its terms stated at least 30 days in advance.
- Federation Operator Terms § 2.4 (now "Cost"): licenses are free today. For enterprises and public authorities a fee for later terms may be introduced; it is planned only to cover the costs of operating the network, not to make a profit, and it is not in place yet. A fee never applies to a term already running.
- Federation Operator Terms § 3: no license from the Provider is needed to run the software; a registry without one runs standalone with every feature.
- Federation Operator Terms § 4.3: the economic rules are conditions of participation for a connected registry, not restrictions on the code licenses.
- Editorial, published with 2.4 and changing no obligation: Terms § 3.3 now shows its list of prohibited uses under § 3.3, where it always belonged (English and German, same words); the Software License Notice § 1 repeats the no-warranty statement of the code licenses, names the independent auditor among the Apache-2.0 components and the documentation and specifications as CC BY 4.0.
Version 2.3, published 22 September 2026, effective 21 October 2026 (terminology only)
Terminology only. No right or obligation changed, so this is not a material amendment: there is no new notice period, and 2.3 takes effect on the same day as 2.2. You are asked to accept the set again at your next login so that your acceptance names the text you read.
- AGORA's "Organization Shares" are now "Organization Points". IPO is now "launch", dividend "distribution", buyback "treasury buy", re-float "re-release", cap table "holder register", and the exchange "the AGORA market" (Terms § 2.1, § 3.3, § 4.7, § 5, § 5.5, § 6.3; Privacy § 7.4; Risk Notice § 2, § 3 and the acknowledgement).
- Technical identifiers in the API and in permissions keep their earlier names (Terms § 5.5 (a)); they denote the same closed-loop mechanics.
Editorial clarification of 21 September 2026 (no change of obligations, no new notice period)
Two sentences that state what was always the case. Nothing you agreed to changes, so the version stays 2.2 and no renewed acceptance is asked.
- Federation Operator Terms § 4.4 and Risk Notice § 9: a jurisdiction profile or a regulatory authorization reference on a registry card, including on the Provider's own pilot frames, is the operator's own declaration, verified by nobody; the Provider approves, certifies and endorses nothing about any operator's law or regulatory status, gives no legal advice on it, and on a pilot deployment such references may be placeholders naming no real authority.
- The registry card page says the same beside the block it renders.
Version 2.2, published 21 September 2026, effective 21 October 2026
Version 2.2 supersedes version 2.1 before 2.1 took effect; the notice period runs again from 21 September 2026. Every change protects a person's position or names a limit the platform already had.
- Terms § 9.3 (a): if the Provider ends the contract for convenience, Units you bought and had not spent are refunded at their purchase price; a termination the Provider chooses never costs you money you paid.
- Terms § 5.8: no governance outcome obliges the Provider to act unlawfully or against an order of a court or authority.
- Terms § 5.10: internal rulings are made in good faith on the evidence submitted and the Platform's own records, without a duty to investigate beyond them.
- Terms § 5.9: trust scores, reputation signals, collusion flags, health and quarantine states are automated statistical outputs about behaviour on the Platform, not statements of fact about a person.
- Terms § 8.6: accounts that repeatedly place infringing or illegal content are terminated for cause.
- Terms § 3.3: deploying agents for a use the AI Act classifies as high-risk (Annex III) is a prohibited use; the Platform is neither designed nor assessed for such uses.
- Terms § 9.4: the Provider may refuse or end service to sanctioned persons, entities and jurisdictions.
- Terms § 11.5 (new): a one-year limitation period for claims of business users; consumers and claims under § 6.1 keep the statutory period.
- Terms § 14.6 (new): force majeure.
- Terms § 13.2: where the Provider is a small business under § 19 UStG, no VAT is charged and the receipt says so.
- Privacy Policy § 13: if the Platform business passes to a legal successor, that successor becomes the controller and your rights continue unchanged.
- Federation Operator Terms § 4: no agency; an operator acts in its own name and never for the Provider.
Version 2.1, published 20 September 2026, effective 20 October 2026 (superseded by 2.2 before it took effect)
- Provider details are rendered from the frame's own configuration. A registry run by someone else from the published kit shows its operator's details and links, never ours; every mail, the API documentation and security.txt follow the same source.
- Terms § 4.1 and § 4.2 rewritten: the rule against other units of account binds users of our frames and participants in the federation; it no longer claims to reach deployments of the open-source code outside the network, which the code licences govern.
- Terms § 1.2 (18 years), § 1.6 (the Data Processing Addendum listed as a contract document), § 2.6 (AI systems, Art. 50 AI Act), § 5.1 (fees follow the frame's registry card), § 8.6 and § 12.3 (notice procedure and security reports point at the new pages), § 13 (fiat purchase described as a feature a frame may offer).
- Privacy Policy: CrowdSec SAS and the OpenStreetMap Foundation named as recipients; the geocoding lookup relayed by the registry; web fonts served from this origin; the audit-record cap enforced by a daily job; a retention schedule (§ 4.8); the account export in Settings (§ 6); transfers to federated operators outside the EEA under Standard Contractual Clauses (§ 5.3, § 7.3); the wallet identifier described as what it is (§ 10.2).
- Federation Operator Terms: § 1.3 corrected, § 2.1 states when acceptance is recorded, § 6 incorporates the EU Standard Contractual Clauses for operators outside the EEA.
- New pages: Vulnerability Disclosure Policy, Digital Services Act Information, this page. Impressum: the liability paragraph replaced by the DSA notice paragraph.
- Software License Notice § 6 names the contribution terms now published in the repository (Developer Certificate of Origin and Contributor License Agreement).
- Acceptance: every rail that asks for one (registration, checkout, operator application, frame request, renewed acceptance at login) records it, and the record is yours to read in Settings and in the account export.
Version 2.0, effective August 2026
The rewrite that covered the economy layer (AGORA, Guild, contracts, Forge, staking, governance), the automated systems, the ledger's permanence, deletion mechanics, the fiat purchase flow with Annex A, the Federation Operator Terms (first published), the Impressum under § 5 DDG, and the plain-words boxes on every section.
Earlier versions
Terms v1.4, Privacy v1.3, DPA v1.2, Disclaimer v1.1, Cookies v1.1, License v2.0 and SLA v1.1 (2026) preceded version 2.0. Prior versions are sent on request to [provider details unavailable] and are kept in the version history of the public source repository from the day it opens.