Roles & Agreements
Beyond Terms & Privacy, which covers using Nexa's products, there are three separate written agreements for the three roles people actually take on around Nexa Studio: partners, moderators, and team members. This page explains why each one exists and what it actually covers — not the full legal text, just the shape of it.
Why these exist at all
Each agreement exists to make expectations clear before someone takes on a role that comes with real access or responsibility — a partnered server, a moderator role, or a team position. None of them are meant to turn an honest mistake into a legal problem. All three include the same core promise: Nexa Studio doesn't use lawsuits, legal threats, or law enforcement to resolve normal disputes under these agreements. The only exception in all three is the same narrow one — something that's independently illegal on its own, like fraud or a real threat to someone's safety. Everything else gets handled through the agreement itself: a conversation, a warning, or removing the role or partnership.
A username is enough
None of these agreements require a real legal name anywhere — a Discord username is explicitly enough to sign each one.
Discord Partnership Agreement
For servers that want to officially partner with Nexa Studio. It's not employment, ownership, or a permanent business relationship — it's a community partnership where both sides support each other.
What a partner gets: permission to identify as an approved Nexa Studio partner, permission to promote Nexa Studio, the option to use approved Nexa Studio products, partnership support, and the option to collaborate on future projects. There's no cost or purchase required to become a partner.
What's expected in return: keeping the partnership honest, not misusing Nexa Studio's name or branding, not claiming Nexa Studio's work as the partner's own, and reporting security issues instead of exploiting them.
Paid projects: if Nexa Studio and a partner work together on something that actually makes money, the default split (unless agreed otherwise in writing) is 5% to Nexa Studio, 95% to the partner — and only for that specific project, not the partner's general server income.
Ending it: either side can end the partnership. Ending it doesn't mean anyone committed a crime — it means the partnership and its benefits stop.
Moderator Agreement
Required reading and signing before anyone is given a moderator role in the Nexa Studio Discord server — you can't get the role without signing first.
Account security matters here specifically: if a moderator's account is hacked or stolen, the role is removed or suspended and isn't restored automatically — the moderator has to verify their identity with the Mod Manager before getting it back. This is exactly why Account Security & 2FA matters more for staff than for a regular member.
What gets a moderator role revoked: going inactive without letting the team know, sharing mod-only or private information (which also comes with a one-week timeout), recruiting people into unrelated servers by DMing them as a Nexa Studio moderator, or otherwise breaking the agreement.
Team Agreement
For anyone joining the Nexa Studio team — development, design, audio/voice, game dev, scripting, or otherwise. Also required reading and signing before joining; no signature, no team role.
There's a real experience requirement. Applicants need relevant experience in the category they're applying for, and an application without it is automatically declined — not personal, just a bar for reliable output.
Activity is expected on an agreed schedule — daily, weekly, whatever's actually agreed to — and falling out of that schedule without notice can mean losing the role and any private access that came with it.
Ownership: work created for Nexa Studio as part of a team role belongs to Nexa Studio, unless a different arrangement is agreed to in writing before the work starts. Joining the team doesn't hand over ownership of Nexa Studio's existing products, code, or branding.
The common thread
All three agreements share the same backbone: clear expectations, a no-legal-action default for normal disputes, confidentiality around private information, and revocation (of a role, partnership, or access) as the real consequence rather than anything more severe. If you're signing one of these, the specific document itself is the actual source of truth — this page is just here to explain why they exist and roughly what's in them.