Legal
1.1 What This Addendum Covers. This Org-Managed Players Addendum (the "Addendum") supplements the CK Spatial Fabric API Terms of Service (the "Terms") between Crowded Kingdom Studios, Inc. ("CK") and the Customer whose Organization uses Managed Players. Capitalized terms this Addendum does not define have the meanings the Terms give them. Where this Addendum conflicts with the Terms on a matter concerning Managed Players, this Addendum governs; on every other matter, the Terms govern.
1.2 Managed Players. A "Managed Player" is a Crowded Kingdoms account that your Organization creates and signs in for one of your end users, under an identifier you assign, instead of an account the end user creates and signs in to with CK. A Managed Player has no Crowded Kingdoms password, email address, or sign-in of its own, uses only the Apps of the Organization that created it, and has no wallet.
1.3 Acceptance. An administrator of your Organization accepts this Addendum on the Organization's behalf in Crowdy Studio. By accepting, that administrator represents and warrants that they have the authority to bind the Organization and the Customer that owns it to this Addendum. Your Organization cannot create Managed Players or sign them in until the current version of this Addendum has been accepted for it.
1.4 Availability. CK makes Managed Players available to an Organization at its discretion and may set limits on them, including how many an Organization may have. CK may modify, suspend, or withdraw the feature for an Organization or generally.
1.5 Revisions. CK may revise this Addendum by posting a new version, and Section 1.4 of the Terms applies to a revision. Where CK designates a revision as one your Organization must accept, your Organization cannot create Managed Players or sign them in after the revision takes effect until an administrator accepts it; a Managed Player already signed in keeps its current sign-in until that sign-in expires.
2.1 Your End Users. Managed Players are your end users under Section 3.8 of the Terms. You provide the terms and the privacy notice under which they use Your Applications. CK does not ask Managed Players to accept CK's Player Terms of Service or Player Privacy Policy, and those documents do not govern their use of Your Applications.
2.2 Identity. You are responsible for identifying and authenticating each person you sign in as a Managed Player, for the identifiers and display names you assign, and for ensuring that each Managed Player is used only by the person you assigned it to.
2.3 Age and Country. Section 6.11 of the Terms applies to Managed Players. Each time you sign a Managed Player in, you tell CK the person's age in years and the country they are in, and CK relies on what you tell it. CK applies Section 6.11 of the Terms to what you assert: it refuses to sign in a Managed Player who is under 13, or under the minimum age CK sets for their country, or who is in a country where CK does not offer the Service to players. CK does not ask Managed Players for their age or country itself. You are responsible for the accuracy of every age and country you assert. You represent and warrant that you obtain each one from the person through an age screen you run before you sign them in, that you will not assert an age or a country you know or have reason to believe is wrong, and that you will not create a Managed Player for anyone you know or have reason to believe is under 13.
2.4 Conduct. You are responsible for your Managed Players' compliance with Section 5 of the Terms as if their use of the Service were yours, and for promptly disabling or deleting a Managed Player who does not comply. CK may suspend or delete a Managed Player, or suspend your Organization's use of Managed Players, under Section 3.5 of the Terms.
2.5 Players Under 18. For a Managed Player whose asserted age is under 18, CK applies its defaults itself: the player's voice and video are off in both directions until a parent or guardian consents through the consent service CK uses, and afterwards reach, and come from, only the player's contacts; and the player's direct messages start off. Your Applications must not be designed or operated to get around these defaults, and an App that admits players under 18 must keep replay logging on (Section 6.4a of the Terms).
2.6 What Stays Yours. CK's checks and defaults under Sections 2.3 and 2.5 do not reduce your other responsibilities. You remain responsible for your age screen; for the terms and privacy notice your Managed Players use Your Applications under, which must tell them what the Service records about them, including the Input Log Section 6.4a of the Terms describes, and that reports about them can be kept and passed on as Section 5.4 describes; for moderating Your Applications, including acting on the reports your players make; and for every other obligation your relationship with your players carries because of their age, including any notice, consent, advertising or design obligation beyond what CK's defaults do.
3.1 Managed Player Credentials. Your Organization signs Managed Players in with org tokens, or with assertions signed by keys whose public halves you register with CK (together, "Managed Player Credentials"). Managed Player Credentials are API keys for the purposes of Section 3.2 of the Terms. Keep them on servers you control; never place one in a client application, a web page, or anything else you distribute to end users.
3.2 Attribution. Every sign-in made with your Managed Player Credentials, and all use of the Service by a Managed Player signed in that way, is attributed to your Organization and billed under Section 4 of this Addendum, whether or not you authorized it.
3.3 Compromise. If you know or suspect that a Managed Player Credential has been exposed or misused, you must revoke it at once, in Crowdy Studio or through the API, and notify CK under Section 3.4 of the Terms.
4.1 Your Organization Pays. Managed Players have no wallet. Everything a Managed Player consumes on the Service is metered to your Organization under Section 4 of the Terms at the Rate Card's rates, including the storage of the projects and libraries they create and, in an App where you let them build and run Mods, the compute of their Mods and their use of the AI tools in Crowdy Studio. These are Fees of your Organization. They are not player compute billed to an end user under Sections 3.8 and 16.3 of the Terms.
4.2 No Purchases. A Managed Player cannot hold a balance with CK, buy anything from CK, or receive payments through the Service. Anything you sell to your Managed Players is between you and them.
4.3 Mods. Whether Managed Players may build and run Mods in an App is your decision, made for each App in Crowdy Studio. Section 16 of the Terms applies to their Mods as it does to any Mod in your App.
5.1 Processing Role. Personal data about Managed Players, including the identifiers and display names you assign and what they transmit through the Service, is Customer Data. Section 6 of the Terms applies to it, and CK processes it as your processor or service provider as Sections 6.10 and 6.12 of the Terms describe.
5.2 Identifiers. Do not use an email address, a government identifier, or a payment card or bank account number as a Managed Player's identifier or display name.
5.3 Requests and Deletion. You are responsible for responding to your Managed Players' requests about their personal data. You can rename, disable, end the sessions of, or delete a Managed Player at any time. Deleting a Managed Player ends its sessions, removes the identifier and display name you assigned from its account record, and, shortly afterwards, erases its content in your Apps: its projects, libraries and Mods, its actors, avatars and saved state, its access to your Apps, and its memberships in teams and channels. A team or channel it created that others belong to remains, without an owner. Deleting a Managed Player does not erase its edits to your Apps' worlds, which remain under the account's identifier without the identifier or display name you assigned; its Input Log records, which are deleted at the end of their retention period under Sections 6.2 and 6.4a of the Terms; or usage, billing and audit records. Section 6 of the Terms continues to apply to what remains. While a legal hold covers your Organization or a Managed Player, including the hold CK places on a player who is the subject of an open safety report, CK will not delete the Managed Players it covers; you can still disable them, which ends their access and keeps their data.
5.4 Safety Reports. When a safety report is filed in one of your Apps by or about a Managed Player, CK keeps its own copy of what the report needs: the Input Log records of the players involved from shortly before the reported moment until the report was filed, their account records, including the identifiers and display names you assigned, and what your Apps' servers on the Service hold about them. CK uses that copy, and its personnel read it, only to handle the report, to protect children, and to meet CK's legal obligations, including reporting apparent child sexual exploitation to the National Center for Missing & Exploited Children. CK keeps it until the report is resolved or, where CK has made such a report, for one year after it did, or longer where the law or a legal hold requires. CK does this to meet its own obligations, not as your processor, and deleting a Managed Player does not remove the copy while CK keeps it.
6.1 Suspension. CK may stop your Organization's Managed Players from signing in, or suspend the feature for your Organization, where Section 3.5 of the Terms permits a suspension or where a Managed Player Credential appears to be compromised.
6.2 Termination. This Addendum ends when the Terms end for your Organization or when CK withdraws the feature for it. When it ends, your Managed Players can no longer sign in, and Section 12 of the Terms governs Customer Data, including the personal data of your Managed Players.
7.1 Indemnity. Your indemnity under Section 11 of the Terms applies to every claim, demand, proceeding, penalty, fine, and loss arising from or relating to your Managed Players, including claims brought by a Managed Player, by anyone signed in with your Managed Player Credentials, or by any regulatory or governmental authority, and including any claim arising from an age or country you asserted, from your age screen, from the terms and privacy notice you provide, from the moderation of Your Applications, or from any other obligation Section 2.6 of this Addendum leaves with you. It does not apply to the extent a claim arises from CK's failure to apply the checks in Section 2.3, or the defaults in Section 2.5, to what you asserted.
© 2026 Crowded Kingdom Studios, Inc. All rights reserved.