What you agree to when you use PocketRoles and StarPocket

The short version

• These terms are the agreement for StarPocket Games' services (StarPocket Client's news and delivery, the site, support, Discord, shared bans, the StarPocket Account, the planned room list and so on).
• The source of Software such as PocketRoles is GPL-3.0. Using, studying, building, modifying and sharing it are governed only by the GPL. These terms do not reduce those freedoms.
• To use the official StarPocket Client we distribute, you need to agree to these terms and the Privacy Policy. If you do not agree, the Client closes.
• Everything is free. There are no paid features. We plan to put one optional way to help with our costs on the official site, and nowhere else (there is none yet). Supporting us changes nothing about how you are treated.
• If you are under 18, read this together with a parent or guardian and ask whether you may use it. If you are under 13, use it together with a parent or guardian.
• The author and author-selected admins and support members read requests within the stated limits. Staff who meet the purpose, viewing notice version, time and team conditions in Article 6(3) also read room restriction appeals sent through the site and write assessments, but only the author decides. Requests on the same form to erase records or report a host are read only by the author. Requests and live conversations from support chat are currently read and answered only by the author.
• We are recruiting contributors (hosts, support, translation and development; "Join us"). You must be 16 or older to apply, and if you are 16 or 17 you need a parent or guardian's consent. You apply while signed in, and the author selects and interviews applicants. Contributing is unpaid. Support members, who read support requests, must live in Japan (Article 6(4)).
• We plan to add signing in with your StarPocket Account to StarPocket Client, and StarPocket Friends (a friends list, online status, sharing your room code, icons) (planned; not in today's Client). Without signing in, the Client works exactly as before. Starting sign-in connects to our server for authentication. Friends status and related data are sent only after sign-in. People under 13 cannot use Friends (Article 8(10)).
• Support chat (planned) requires signing in with a StarPocket Account. Article search runs on the server. The AI bot answers only people aged 18+ in an eligible country who give optional consent. The bot can make mistakes. People decide the important things.
• In PocketRoles rooms everyone plays on the same terms. Do not cheat, do not ghost (pass information in from outside), do not throw a game on purpose, and do not get around a room restriction (Article 10).
• We make promises about our own decisions too: we decide only for the reasons written here, we fix our mistakes, and you can always appeal (Article 14).
• If someone does not follow the rules, they may lose access to part of the services. When that happens, we tell them the reason (which article) and a code.
• While a shared ban (decided by the author after looking at evidence) lasts, that Among Us account can't create PocketRoles rooms (planned; Play Rules, Article 9(6)). Plain Among Us from Steam can still be played.
• When we change these terms, we tell you in advance. For important changes, we ask you to press "Agree" again.

Article 1 (About these terms)

1. These terms are the agreement for using the following services provided by StarPocket Games ("we", "us") (the "Services").
   1. Websites (the PocketRoles site, the StarPocket Games site, the error-code pages)
   2. Software distribution (downloads from GitHub Releases and elsewhere; news, status notices and updates delivered to StarPocket Client)
   3. Delivery of the Aegis definitions file and the central lists in it (the shared-ban list, the erase list and the lift list)
   4. Receiving shared-ban requests and appeals
   5. Support (the support chat, the AI bot, email, Discord tickets)
   6. The StarPocket Account
   7. Communities such as the Discord server "PocketRoles 役職部屋"
   8. The planned room list and other server features
2. People who use the Services ("users") use them under these terms, the "PocketRoles Play Rules" (the "Play Rules") and the Privacy Policy.
3. People who only join a PocketRoles room are not using the Services, so they have not agreed to these terms. What the Play Rules mean for them is explained in Article 1 of the Play Rules.

Article 2 (Definitions)

In these terms, the following words mean:

1. Software: the programs we publish, such as PocketRoles, Aegis, the launcher and StarPocket Client
2. Host: a person who puts PocketRoles on their own PC and makes rooms
3. Participant: a person who joins a host's room
4. Staff: the author, admins chosen by the author (including the Aegis team), and support members chosen by the author. Support members must be at least 16 and live in Japan. Those aged 16 or 17 need a parent or guardian's consent. Members must agree to the staff pledge before helping and tell the author before moving home (Article 6(4)). The author adds admins and support members one at a time and assigns their roles and teams (how they are added: Privacy Policy Article 2(4)). Ordinary support requests are split into 9 teams (bugs, room access, help, suggestions, accounts, privacy, player reports, parents and guardians, and general support, with names such as "StarPocket Bug Team"). Support members read only requests assigned to their teams; one person may have several teams. Admins may read ordinary requests from all teams, subject to the time limit for staff other than the author in Article 6(3), but only the author may read contributor applications submitted through the "Join us" category (Article 6(4)). Room restriction appeals can be read only by the author and Room Access Team staff who meet the purpose, viewing notice version and time conditions in Article 6(3). Requests on the same form to erase records or report a host are hidden from admins and support members and read only by the author. Only the author decides whether to impose or lift restrictions. Article 6(3) and Privacy Policy Articles 2(4) and 11 explain the access limits and how requests received before staff are added are handled. Requests sent through "Ask a person" in support chat, including live conversations, are currently read and answered only by the author, and are hidden from admins and support members. Before extending access to staff, we will change these terms and the Privacy Policy and announce it in advance.
5. Central lists: the shared-ban list, the erase list and the lift list in the definitions file
6. Support chat: a chat-style help desk opened from "Ask in chat" at the bottom right of the support site (planned). You sign in with your StarPocket Account in the browser to use it (Article 8). An AI bot or article search answers first; when you send through "Ask a person", the author answers (Article 16). To contact us without signing in, use the contact page (the form and receipt-number page) or email
7. Account: the StarPocket Account in Article 8
8. Code: a short label for a kind of restriction or problem ("R-31", "S-12" and so on). The meanings are on the site's error-code list

Article 3 (Relationship with the software licence)

1. The Software is published under the GNU General Public License version 3 or any later version (GPL-3.0-or-later). The rights to run, study, modify and share the Software are governed only by the GPL.
2. These terms do not reduce any right the GPL grants. If any part of these terms could be read as reducing a GPL right, that part does not apply to GPL rights.
3. You do not need to accept the GPL to run the Software (GPL section 9). These terms are separate from the GPL: they are the agreement for the official Client we distribute and for using the Services.
   • The official StarPocket Client that we sign and distribute asks you to agree to these terms and the Privacy Policy the first time you open it. This is because the Client is an app that connects to our Services (news, the definitions file, updates, support).
   • If you do not agree, you cannot use the official Client. If you choose "Decline", the Client closes. You can uninstall it without agreeing.
   • This agreement is about using the official Client and the Services. It is not a condition of the permission (licence) to use the Software.
   • The source of PocketRoles and the Client stays GPL-3.0. Anyone, including people who do not agree, can build, modify and use it from the published source under the GPL.
4. The Aegis checks in the Software (such as the pre-launch scan, and not creating rooms during a shared ban) are there for fair rooms and users' safety.
   • Under the GPL, anyone can change or remove these checks.
   • What we can stop is only access to the Services (Article 13).
5. When you share a modified version, follow the GPL's conditions (such as publishing the source). Do not make people think a modified version is our official version (Article 9, item 3).
6. Among Us is a work of Innersloth LLC. The Software is an unofficial fan mod and has no connection with Innersloth. When you play Among Us, also follow Innersloth's Terms of Use and Mod Policy.
7. Parts made by other people, such as BepInEx, are covered by their own licences.

Article 4 (Agreeing to these terms, and showing them)

1. Please read these terms before using the Services. You are treated as agreeing to them when:
   1. on the "Terms of Use and Privacy Policy" screen of StarPocket Client, you tick "I have read and agree to the Terms of Use and the Privacy Policy" and press "Agree";
   2. in support chat (planned), after reading and confirming agreement to both documents on a screen showing links and versions of these terms and the Privacy Policy, you press "Agree and start" (we record the agreed terms, policy and screen explanation versions and the time); or on the contact page, you press "Agree and send" (this form consent is planned; today the button is only "Send", and the version of this consent is not recorded. Which promises apply to the current form will be decided after the answer to expert question 3 );
   3. when making an account, you press "Agree and create" (planned; today an account is made simply by signing in, and there is no "Agree and create");
   4. in a setting that connects to the Services, such as listing a room in the room list, you choose "Agree";
   5. when joining the Discord server, you confirm that you will follow these terms;
   6. you send a shared-ban request or an appeal by email or a Discord ticket (the place where you send it says that these terms apply);
   7. you apply through the contributor recruitment (Article 6(4)) (the application page links to these terms and the Privacy Policy).
2. You do not need to agree just to look at the site, or just to download the Software from GitHub and run it. The Privacy Policy still applies then.
3. We keep these terms on the site and in StarPocket Client so they can be read at any time. If asked, we show them right away.

Article 5 (Age, and a note for parents and guardians)

1. If you are under 18, read these terms together with a parent or guardian, ask whether you may use the Services, and agree together.
2. If you are under 13, use the Services together with a parent or guardian. People under 13 cannot use StarPocket Friends (Article 8(10); planned).
3. Discord can only be used by people aged 13 or older (older in some countries). If you cannot use Discord, use the contact form (no account needed), email, or support chat (planned). Support chat requires signing in with a StarPocket Account.
4. When consent is needed for personal information of someone under 16, we get it from a parent or guardian (Privacy Policy Article 10).
   • We plan to ask you to choose your birth year on the account page (this age field is not yet available on the live service; it is turned into an age band in your browser, and the year itself is not sent; the contact form does not ask your age). Chat does not ask again; it uses this band to decide whether to offer the bot (only 18+, not unanswered ages; Article 16(4)). Chat shows "Please use this together with your parent or guardian" to people under 18 and those who have not answered. Confirming this reminder is not a condition of chat use. For StarPocket Friends, we check with a parent or guardian when the band is under 16 (planned: before someone aged 13-15 uses it, we send a confirmation link to a guardian email address and allow use after confirmation, then delete that email address). People aged 16 or 17 using Friends only tick "I am using this together with my parent or guardian" (planned). Contributor applications are covered by paragraph 6.
5. Parents and guardians who want to check or delete their child's support requests, account or records can contact us as described in Privacy Policy Article 12.
6. You must be 16 or older to apply through the contributor recruitment (Article 6(4)). If you are 16 or 17, you need a parent or guardian's consent. The author checks that consent before approving an application.

Article 6 (Operator and contributors)

1. The Services are run by one individual developer working under the name "StarPocket Games".
   • StarPocket Games is not a company or any kind of legal entity.
   • "StarPocket Games" and "PocketRoles" are not registered trademarks.
2. The operator's name and address are given on request, as described in Privacy Policy Article 2.
3. Admins and support members chosen by the author help answer requests (Article 2(4)). Support members are not shown reply email addresses or account IDs. They see the display name of people who sent a request while signed in so that they can greet them by name. Support members do not have access to the room, user or restriction management pages. Only the author decides restrictions, shared bans, their removal and appeal outcomes. As an exception to these access limits, requests and live conversations from support chat are currently read and answered only by the author.
   • Room restriction appeals: appeals sent through the support site are read by the author and staff assigned by the author to the Room Access Team (support members and admins). Even an admin cannot read them without that team. Admins designated in the configuration file and staff on other teams cannot read them either. Staff see only items submitted for the purpose "I think the room restriction was a mistake" using a form with the new viewing notice version (1.2), which explains that staff also read them, and received at or after the latest of these four times: (1) the explicitly configured start time for staff access to appeals (no earlier than 2026-10-08 00:00, Japan time, when version 1.2 of these terms and the Privacy Policy takes effect); (2) deployment of this feature; (3) the additional access start time set for all requests and shared by all staff; and (4) the time the member was added. There is no separate access start time for each member. Lifting a temporary suspension does not change when the member was added or start a new access period. Receipt time alone cannot distinguish forms opened before deployment. Even if received after deployment, submissions using an old, missing or unknown viewing notice version are read only by the author. Other items outside the conditions, and requests on the same form to erase records or report a host, are also hidden from admins and support members and read only by the author. Staff also see nothing if the appeal access start-time setting is omitted, empty or invalid. Staff can write only an assessment (a note for the author) and a reply draft. Only the author decides whether to post a reply, change the appeal's status or lift a room restriction.
   • Teams and staff come with four safeguards: two-step verification through an authenticator app, agreement to the staff pledge, initially holding all support replies until the author approves them (the author may turn this off per member, but replies with apparent private contact details or similar content always require approval), and hiding requests received before a staff member was added from that member. Two-step verification applies to support members and admins other than the author.
   • Staff can select a template in Japanese, get the text in the user's language (Japanese, Chinese or English), and edit it to suit the request. Using a template does not change the rule that notification emails contain neither the request text nor the reply text (Article 25(1)(5)).
   • Email addresses, phone numbers, URLs, IP addresses, account numbers and friend codes written in a request are initially hidden on staff pages. A member with permission to read the request can reveal them by pressing a button, and that action is recorded. Support members are still not shown the reply email and account ID fields. For staff other than the author, admin pages carry a watermark with the viewer's staff display name and the time. Records of who viewed which request and when are kept for 1 year. Viewing many requests in a short time alerts the author and stops access. Support members have no export, bulk-copy or print view. In-game names, room codes and host names in appeal text are not hidden. We cannot completely prevent screenshots or screen recordings.
   • If information leaks, or may have leaked, we pause or remove the member at once, hold the requests that member recently viewed, use viewing records to establish the scope, and check whether notification or reporting to the affected people or Japan's Personal Information Protection Commission is required. This procedure is in place. See Privacy Policy Articles 11 and 13 for details.
4. Contributor recruitment ("Join us")
   1. We are recruiting contributors: hosts who create rooms, support members who help with support requests, and people who help with translation or development. This paragraph is the agreement with people who apply, and with people who become contributors or support members.
   2. Every role requires applicants to be 16 or older. If you are 16 or 17, get a parent or guardian's consent before you apply. The author checks that consent before approving, and records the date it was checked. Hosts must be able to create rooms with the Steam version of Among Us on Windows. Support members read the content of support requests, so only people living in Japan can apply for support. Translation and development are open to people in any country.
   3. Apply by signing in to the support site (https://support.starpocketgames.com) with email or Discord and using "Join us". Before you send it, you answer a true-or-false quiz that checks the rules. You cannot send the application until every answer is correct, but the quiz result alone never decides selection. The author reads the application, decides whether to invite you to an interview or not to go ahead, and decides after the interview whether to approve it. Only the author reads applications and selection records.
   4. We contact you through replies to your application under "Your requests". If your account has an email address, we also email you when the application is received (at most 3 receipt emails a day to the same address), and we may email you when we reply. These emails do not contain what you wrote in the application. If you choose Discord DM notifications, replies to your application are also announced by DM: only a receipt number and link, with no application, interview or reply content (Article 25(1)(5)).
   5. You choose an interview by text (in the reply box of your application) or a Discord voice call. We do not record it. We do not ask for your real name, address, school or a photo of your face. Privacy Policy 3.13 and Article 5 explain the information handled in applications and interviews and how long it is kept.
   6. After an application is not selected or is withdrawn, you cannot apply again for 30 days. An application with no decision yet is withdrawn automatically 90 days after the last activity (the application, a change of its status, or a reply from either side). After an automatic withdrawal, you also cannot apply again for 30 days. While you have an application in progress, and while you are a contributor or support member, you cannot send a new application.
   7. When an application is approved, the author sends the contributor pledge. Read all of it, and if you can keep it, reply "I agree" to your application. The author records the date you agreed and the version of the pledge. The current pledge has 16 items, and its version is 2026-10-04. The full pledge is also on the pledge page of the support site (https://support.starpocketgames.com/en/join/pledge). Contributors must not share outside anything they learn through their activities that is not yet public, or other people's information, and must keep the pledge. Support members must also agree to the staff pledge (which includes not sharing the content of support requests outside).
   8. Host, translation and development contributors are not staff. They cannot see support requests or admin pages, and the host role alone never gives access to support requests. People approved for support help with support requests as support members (Article 2(4)), following the rules in paragraph 3. They may read requests only while living in Japan and must tell the author before moving. Members recruited to help with requests in other languages must also live in Japan. People approved for support first agree to the staff pledge and complete two-step verification with an authenticator app before reading any requests (paragraph 3).
   9. Contributing is unpaid; no money is paid. If we decide on a non-cash thank-you, we will tell you. Being a contributor or support member does not change how you are treated in the Services (limits, shared bans, the order of replies and so on) (Article 14(4)).
   10. The author may remove you as a contributor or support member and end your access at any time. If you want to withdraw your application or stop being a contributor or support member, tell us at any time by replying to your application.

Article 7 (Fees)

1. The Services and the Software are free. There are no paid features, no paid membership and no paid roles. No part of them requires payment.
2. To help cover the cost of AI and APIs, the domain and electricity, we may accept optional support. There is only one place for it, and it is only on the official site (there is none yet).
3. Supporting us changes nothing at all: not how fast you get a reply, not a room restriction, not your place in a queue. It gives you no role and no feature.
4. Apart from that one place on the official site (if and when we put one there), if someone asks you for money in the name of "StarPocket Games" or "PocketRoles", it is not us. We never ask for money in a DM, inside the game, or in a Discord DM. Please tell us through support.

Article 8 (StarPocket Account)

1. You can make a StarPocket Account on the site. You do not need an account to use the Software or contact us through the contact form or email. Support chat (planned) requires account sign-in in the browser. Conversations and requests sent from chat are linked to the account. StarPocket Client, too, works exactly as before without signing in. Applying through the contributor recruitment (Article 6(4)) requires signing in. StarPocket Friends (paragraph 10; planned) will also require signing in.
2. What an account lets you do
   1. See all your support requests in one place, under "Your requests" on the support site
   2. Get an email when a reply arrives (sending it to the account's email address is planned; today it goes only to the reply-to address written on the contact page; Article 25(1)(5)). Chat requests do not receive receipt or reply notices by email. People who choose Discord DM notices receive DMs (Article 16(3))
   3. Get told when someone signs in from another device (planned)
   4. Get an email when Discord is connected to the account
   5. Sign in from StarPocket Client and use StarPocket Friends (friends list, friend cards, online status, sharing your room code, icons) (planned; paragraph 10)
   6. Get an email when a new Client signs in (planned)
   7. If you have connected Discord, also be told by Discord DM when a reply arrives (only if you choose it; you can stop at any time; Article 25(1)(5))
3. Ways to sign in (no passwords)
   1. A 6-digit code sent by email (works once; stops working after 10 minutes)
   2. A passkey (planned) (your device checks your fingerprint, face or PIN; that information stays on your device and never reaches us)
   3. Sign in with Discord (only for people old enough to use Discord)
   4. Sign-in from inside StarPocket Client (planned): either you type your email address in the Client and then the 6-digit code that arrives, or a button opens your browser, you press "Authorize" on Discord and you are brought back to the Client. Sign-in from the Client is protected by rate limits instead of the bot check (Article 18(1)(2))
4. Rules for making an account
   1. Use your own email address or your own Discord. Do not use someone else's.
   2. Your display name does not have to be your real name (today, people who sign in with Discord get their Discord display name as it is, and people who sign in by email have none; a screen to choose it yourself is planned, and you will also be able to choose it inside StarPocket Client (planned)). Names like those in Play Rules Article 6(1)(3) cannot be used. To use StarPocket Friends (paragraph 10; planned) you need a display name you chose yourself (your Discord display name is not used automatically). Your display name and icon are shown to the friends you accepted (planned).
   3. If you are under 18, make the account together with your parent or guardian. The "I am making this together with my parent or guardian" tick is planned (today's screen does not have it yet).
   4. Do not give your verification codes or passkeys to anyone. Do not give or lend your account to anyone.
   5. Give your friend card (a short code that lets someone find you in StarPocket Friends; paragraph 10; planned) only to people you really know. Do not post it in public places such as social media, streams or other people's Discord servers.
5. If you get a notice about a sign-in from a device you do not know (planned), sign that device out under "Signed-in devices" (planned). Until that list exists, tell support. Do the same if you do not recognise the sign-in. Sign-ins from StarPocket Client (planned) will be in the same list and can be signed out from there too (planned).
6. You will be able to delete your account with "Delete account" on the account page (planned). Until the button exists, ask through Article 34 (the contact page, category "Other") and we will delete it.
   • Support requests linked to the account are deleted with it.
7. Accounts with no sign-in for 2 years will be deleted automatically (planned; today nothing is deleted automatically). When this starts, people who registered an email address are told by email 30 days before, and others are told on the screen when they sign in.
8. Your account is not linked to you in the game.
   • It is not connected to your Among Us account, friend code, PUID, in-game name or PocketRoles records.
   • So a limit on your account has nothing to do with you in the game, and a room restriction in the game has nothing to do with your account.
   • If we ever build a way to link them, we will first decide on a safe method, then change these terms and the Privacy Policy and ask you to agree again.
   • If you join a friend's room (paragraph 10; planned), you see each other's in-game names. That is how Among Us works; it does not link your account to you in the game.
9. If something about an account does not follow the rules, we may stop account features within the limits of Article 13. Even then, you can still make the requests in Privacy Policy Article 12 (to see or delete your information and so on).
10. StarPocket Friends (planned; not in today's StarPocket Client. As each feature is released, we remove "(planned)" from that part and announce it)
    1. People signed in to StarPocket Client exchange friend cards (paragraph 4, item 5) and become friends only with the people they accept. There is no way to search by name.
    2. Friends see your display name, your icon, your online state (whether the Client is open and whether you are playing PocketRoles) and, when you have chosen to show it, the details of the room you are hosting (map, players, state, region) and its room code. The time you were last online is not shown.
    3. For everyone old enough to use Friends, online status starts as "shown to friends". You can switch it to "hidden" at any time in settings (while hidden, you look "offline" to friends). The room code starts as not shown; it is shown to friends only while a person who turned it on is hosting a room. You can also choose "not this time" for a single room.
    4. A friend's "Join" only copies the room code and starts Among Us. It does not put them in the room automatically. Anyone who learns the code can join the room (rooms for friends only cannot be made).
    5. Someone you block can no longer see you (they are not told).
    6. For your icon you can use one of our pictures or your own image. Your own image is given only to the friends you accepted and is never put in a public place. Photos in which a real person's face can be recognised (including your own) cannot be used (Article 9(12)). If reports of a harmful image gather in a short time, it is hidden automatically before anyone looks, and the author checks it (Article 13(1)).
    7. What you can do depends on your age band (Article 5(4)). People under 13 cannot use Friends. People aged 13-15 can use it after a parent or guardian confirms through an emailed link. They cannot upload their own image and see our preset pictures instead of friends' uploaded images. People aged 16 or 17 must tick "I am using this together with my parent or guardian". They can upload their own image, which is shown only to friends who are also 16 or 17. People aged 18 or over can upload their own image, which is shown only to friends aged 18 or over.
    8. Among Us's own friends, friend codes, PUIDs and in-game names are not used, sent or received (paragraph 8).
    9. What is sent, what is kept and when it is deleted are in Privacy Policy 3.9, 3.10, 3.12 and Article 5. What the Client sends is also in Article 12(9).

Article 9 (Things you must not do)

When using the Services, users must not:

1. write false things in shared-ban requests, appeals, or reports that a right has been infringed (Article 23), or make up or alter evidence (Aegis records, report zips, "One player's evidence" zips, screenshots and so on) and send it;
2. pretend to be someone else, including staff, the author, StarPocket Games or Innersloth;
3. share a modified version or other software as if it were our official version, or copy our official download places or documents such as these terms to make people think they are official;
4. write other people's personal information (real name, address, phone number, school, photos, friend codes, other people's /cmd id codes and so on) without their permission, or use other people's photos or personal information as an icon (Article 8(10); planned)
   • except writing your own friend code for your own appeal;
5. abuse, threaten, repeatedly contact, or use discriminatory or sexual words towards staff or other users;
6. send the same thing to the support chat or the bot again and again, send lots of unrelated content, or try to make the bot do anything other than its job (guiding people about our Services);
7. attack the servers or networks of the Services, including
   • sending large amounts of traffic, or traffic looking for weaknesses;
   • getting around the bot check or the sending limits;
   • looking for or using other people's secret support links or other people's accounts;
   • but telling only us about a weakness in the way written in SECURITY.md is not covered by this item;
8. send viruses or other harmful programs, or links meant to trick people;
9. use the Services to break the law, or to help break Innersloth's Terms of Use (such as sharing or advertising cheats);
10. advertise or sell things in the Services without our permission;
11. use someone else's account, or make an account with someone else's email address or Discord;
12. use as an icon (Article 8(10); planned) sexual, violent or discriminatory images, or a photo in which a real person's face can be recognised (including your own);
13. post a friend card (Article 8(4)(5); planned) in a public place to gather people, or buy or sell friend cards or accounts;
14. repeat friend requests or room-code sharing to harass someone, or spread another person's room code without that host's permission.

Article 10 (Playing fair)

1. PocketRoles rooms are fun because everyone plays on the same terms. When users play in a PocketRoles room (whether as a host or as a participant), they must not do the following.
   1. Using a cheat tool, or a client modified for cheating (a modified Among Us, a cheat menu, a tool that injects DLLs and so on), to do things that normal Among Us cannot do (Play Rules, Articles 2 and 3). For example, killing with a role that cannot kill, entering a vent with a role that cannot vent, moving impossibly fast, or seeing impostors and roles.
   2. Telling or receiving, from outside, things you should not know inside the game (this is called "ghosting"). For example, a dead player, someone watching a stream, or someone who can see another player's screen telling a living player, in a voice call (Discord and so on), in stream comments or in another chat, the roles, where a body is, who killed, or who went into a vent. And a living player hearing or seeing that and using it in the match. Ways of talking that the host allows in /rules (talking in a voice call only during meetings, for example) are not covered.
   3. Losing on purpose, or throwing the match. For example, teaming up with an impostor beforehand without the other players knowing when your role's way of winning does not allow it, getting yourself killed on purpose, voting the wrong way again and again on purpose, leaving in the middle of a match on purpose, or doing nothing so that the game stops (stopping it by leaving and rejoining again and again is Play Rules, Article 6(1)(5)). When a role has its own way of winning, like the Jester (who wins when exiled) or the Madmate (who helps the impostors), playing the way that role wins is not covered by this item.
   4. Using MOD or game bugs on purpose. For example, knowing that a role's ability works differently from how it should and using it again and again to win. Finding a bug and telling us about it is not covered by this item. Please tell us through support (Article 34) or in the way written in SECURITY.md.
   5. Getting around a room restriction or a shared ban. For example, someone who was removed from a room, or who can no longer join that room, joining the same room with another Among Us account. Someone under a shared ban joining, or creating, a room that uses shared bans with another account. Listing a room made with a modified version that has the shared-ban check removed on the Services (the room list and so on).
   6. Making or helping other people do the things in this article. For example, telling someone where cheat tools are, asking someone to ghost, asking someone to lose on purpose, or helping someone get around a room restriction (things inside the Services are also in Article 9, item 9).
   7. Tricking other people to get things or information from them. For example, saying "I'll give you a role", "I'll lift your ban" or "I'm staff" to make them hand over money, an Among Us account, a friend code, a password or personal information. Pretending to be staff or us (Article 9, item 2). We never ask for money or information in a room or in a DM (Article 7(4)).
   8. Hurtful words, harassment and flooding (spam). The detailed rules inside rooms are in Play Rules, Articles 5 and 6. Things inside the Services, such as support and Discord, are in Article 9, items 4 to 6. This article does not repeat them.
2. What a machine can find, and what a person decides. Aegis can find only a limited set of behaviour by machine.
   • What Aegis finds: in item 1, "moves that normal Among Us cannot do" inside the game (Play Rules, Article 2; J-21 and J-22. In registered rooms, the game-action checks are not run; Play Rules, Article 2(5)), and tools that can be used for cheating and DLLs on the host's PC (Play Rules, Article 3; codes starting with R). In item 8, words on the hurtful-word list, and flooding (Play Rules, Article 5; J-51 and J-52).
   • What Aegis does not find: all of items 2 to 7, and the harassment in item 8. Aegis cannot see inside voice calls or streams. A machine cannot tell whether someone is losing on purpose, whether they are using a bug, or whether a person on another account is the same person.
   • What machines do not find is decided by the host, who watches (Play Rules, Article 6(2)). The host can remove that person from their own room, or stop them from joining their own room. What we decide is only whether to make a shared ban after looking at the evidence (Play Rules, Article 9) and limits on a user's use of the Services (Article 13).
   • When we add more things that machines find, we change the Play Rules and tell you in advance (Play Rules, Article 12). We never use this article as a reason to look secretly inside voice calls, streams or PCs (Privacy Policy 3.11).
3. This article is a promise from users. People who only join a room have not agreed to these terms (Article 1(3)). For them, this article is a public standard that the host uses in their own room (Article 15(3)). A host can make this article a room rule with /rules.
4. When a user does anything in this article, the following happens.
   • In the room, the host removes them, or stops them from joining that room (Play Rules, Articles 6 and 8).
   • When there is evidence, the author may make a shared ban (Play Rules, Article 9).
   • For users, we may limit their use of the Services within the limits of Article 13. When we do, we tell them the reason (which item of this article), the length, the code and how to appeal (Article 13(3)).
   • We cannot ban Among Us accounts (Article 13(4)). When someone is removed from a room by a "Certain" cheat detection, an official report is sent to Innersloth if the host uses automatic reporting (Play Rules, Article 8(2)(3)). What is done with it is for Innersloth to decide.
5. This article does not reduce GPL rights (Article 3). Modifying the Software, using a modified version, and making a version with the shared-ban check removed are allowed by the GPL, and this article does not forbid them. What this article forbids is the behaviour of using them to get an advantage over other people, or to get around a room restriction or a shared ban. All we can do is limit the Services (Article 13) and make a shared ban after looking at the evidence (Play Rules, Article 9). We cannot stop anyone using the Software (GPL) or playing plain Among Us from Steam (Article 13(4)).
6. If you think someone else is doing anything in this article, tell the host of that room first. When a host sends a shared-ban request, write only what is true and do not alter the evidence (Article 9, item 1; Play Rules, Article 7(1)(3) and (5)). We do not accept a request whose only reason is "I dislike them".

Article 11 (Watching and anti-cheat (Aegis))

1. Aegis is the anti-cheat built into PocketRoles. It is a feature for keeping a host's room fair and protecting the people who join, and it is part of our unofficial MOD. It does not belong to Innersloth. This article says what Aegis does and what it does not do. The levels of detection, room restrictions, shared bans and appeals are written in the Play Rules (Articles 2 to 5 and Articles 8 to 10) (Article 15). How records are handled is written in the Privacy Policy (3.9 to 3.11, Article 9 and Article 12) (Article 24).
2. What Aegis does
   1. The scan before launching (StarPocket Client, today's launcher and the tray Aegis): before PocketRoles starts, it checks a set list of things on the host's PC. How many things are checked differs by version and by which app is used (Client, launcher or tray). Each thing checked is shown as one line on the scan screen. Only the following are checked.
      • The names and contents (hashes) of the files in the game and MOD folders: whether PocketRoles.dll has changed since it was put there, whether the BepInEx plugins folder has any plugin other than PocketRoles, whether there are DLLs used by cheats or swap-in DLLs next to Among Us.exe, and whether BepInEx is installed
      • The names and executable files of running apps: they are compared, inside this PC, with the list of tools that can be used for cheating. Where an executable file is is only asked of Windows; the memory, the windows and the screens of apps are not looked at. Only apps in the same Windows session as the host are looked at (checking executable files starts with v0.5.5)
      • Windows' protection settings (Secure Boot, TPM, test mode, the vulnerable driver blocklist and so on): only the values of Windows settings that anyone can read are read
      • The signature and version of the definitions file, the versions of Among Us and PocketRoles, the Aegis items in the MOD settings (whether detection is on), and the number of lines in the list the host writes themselves: these are only reported, and they stop nothing

        When something that does not meet Play Rules, Articles 3 and 4 (codes starting with R) is found, the Play button stops and the reason and a code are shown. Fix it and you can play right away. This is not a limit under Article 13 (Article 13(4)). When the checks happen is written in Privacy Policy 3.11.

   2. Watching inside the game
      • PocketRoles' self-check: at start-up, every 60 seconds, and when the menu is opened, it checks the names, places and signatures of the DLLs loaded into the game, whether the game's code (GameAssembly.dll in memory) has been changed, and the names of the loaded drivers. It only checks inside the game itself. If something does not match, the next lobby cannot be made (Play Rules, Article 4(1)).
      • Checks inside the room: PocketRoles on the host's PC watches what the people who joined the host's room do in the game (kills, vents, abilities, tasks, how fast they move, messages, chat flooding, hurtful words and so on; Play Rules, Articles 2 and 5) and sorts it into the 3 levels "Certain", "Repeat" and "Notice" (Play Rules, Article 8). The numbers used for these checks are published in the definitions file.
      • The tray Aegis and StarPocket Client: while the game is running, they read the MOD's game log (BepInEx\LogOutput.log) and show a Windows notification when Aegis inside the game removes someone from a room or detects something. They also check the names and executable files of running apps every 30 seconds (in StarPocket Client, while the window is visible) and, if a tool that can be used for cheating is found, tell you and write it in events.log (they stop nothing).
   3. Receiving the definitions file: we receive from GitHub the file we signed, which contains the numbers used for checks, the names of tools that can be used for cheating, the NG words, the central lists (the shared-ban list, the erase list and the lift list) and the PocketRoles version needed. It is only received; nothing about this PC is sent (GitHub receives an IP address, as with any normal connection). Only files whose signature matches are used. When they are received and how to stop it are written in Article 12 and Privacy Policy 3.9.
   4. Hosts can turn off Aegis detection and use of the shared-ban list in the settings. Do not say "Aegis protects this room" in a room where you turned them off (Play Rules, Article 7(1)(7)).
3. What Aegis does not look at
   1. It does not look at photos or documents, other apps' screens, key presses, browsers or passwords.
   2. It does not read or write the memory of other apps (including Among Us). It does not look at their module lists, windows or screens. For other games too, it only asks Windows where the executable file is and reads that file from the disk; it never puts anything into those games.
   3. It does not open personal files outside the game and MOD folders.
   4. It does not install drivers. It does not install services that stay running. It does not restart the PC and does not change Windows settings.
   5. It does not collect PC part numbers (hardware IDs). It does not use them for limits either (Article 13(4)).
   6. It puts nothing on, and checks nothing on, the PCs and phones of people who only join a room (Privacy Policy Article 9(1)). Checks inside the room are made only from the game's messages that reach the host's PC.
   7. Normal conversation is not kept in Aegis's records (Play Rules, Article 5(6)). IP addresses are not kept either.
4. Where it runs. What is not sent, and what is sent
   1. Aegis runs only inside the host's PC. No part of it runs on our servers. The records on the host's PC never reach us. We cannot look at the records on other hosts' PCs.
   2. What is never sent
      • The results of the PC scan. Even when you press "Contact support" on the "You can't play yet" screen, what is filled in first is only the code, the app version and the language. The names of what was found are not included (users write them if they want to).
      • The results of the self-check inside the game
      • The results of comparing with the shared-ban list (paragraph 6)
      • Evidence records and the room-restriction list. These reach us only when a host makes a "report zip" or a "One player's evidence" zip themselves and sends it by email (Privacy Policy 3.3). Nothing is sent automatically.
   3. What is sent (sent from the host's PC straight to the other side; it does not reach us)
      • The connection that receives the definitions file (GitHub; it is only received)
      • Official reports to Innersloth: for a person removed from a room for a "Certain" cheat found in the room, the reason and who they are are sent to Innersloth (at most once every 30 days for the same person). This is not the result of the PC scan; it is a check made inside the room. It is off at first and sent only when the host turns it on, on StarPocket Client's first screen or in the settings (from v0.5.5 on, the default is off however the mod was installed).
      • Chat translation and the Discord webhook are not Aegis features. What they send and how to stop them are written in Privacy Policy 3.9.
   4. Also checking the shared-ban list with our server is not done now. If we ever start it, nothing would be sent: the whole list would be received from our server and compared inside this PC (nothing about your account is sent; Privacy Policy 3.9). If we start it, we will ask you to press "Agree" again, as in Article 26(4). The PCs of people who have not agreed do not make this connection.
5. How long records stay
   1. Aegis keeps an evidence record on the host's PC when it removes someone from a room and when it restricts them from the room. What is in it (the name, a hash of the PUID, the code for erasing records, the time, the room, the rule, the numbers, 20 lines of that person's log and so on) is written in Privacy Policy 3.10. IP addresses and other people's chat are not included.
   2. Evidence records are kept for 90 days for everyone, whether or not they were restricted from a room. This is because appeals can arrive late. A record pointed at by a room restriction that is still running stays until 90 days after it was made or 30 days after the restriction ends, whichever is later (it stays for good when there is no end date). Only the 2 lines of the game log that back up the evidence are kept with the record.
   3. The game log, Aegis's record of events (events.log), and the report zip and "One player's evidence" zip on the desktop are deleted after 30 days.
   4. The room-restriction list stays while the restriction lasts. Only the count of breaches goes back to 0 one year after the last restriction ends.
   5. If you want your records erased, type /cmd id in a room's chat and send the code it shows to support (Play Rules, Article 11; Privacy Policy Article 12). We erase them without waiting for the 90 days. The smallest amount of information needed for a room restriction that is still running (the hash, the level and the end date), and the evidence record for that restriction, stay.
   6. We decide these defaults, but it is the host who holds the records. Hosts must not post records on social media or anywhere else (Play Rules, Article 7(1)(4)).
6. Comparing with the shared-ban list
   1. PocketRoles inside the game compares a hash of the PUID of a person who joined the room with the shared-ban list in the definitions file it received, inside the host's PC. Nothing is sent. Names and friend codes are not on the list (shared bans start with v0.5.5).
   2. PocketRoles inside the game also checks, with the same definitions file and inside the host's PC, whether the Among Us account that is signed in is on the shared-ban list (this is planned; Play Rules, Article 9(6)). It only turns the PUID and the friend code into a hash of the same form as the list and compares them; the PUID and the friend code are used only in memory and are never written down or sent. Nothing new is sent for this.
   3. The result of the check on your own account only stays in a small file on the host's PC (access-status.txt; planned). It is not sent anywhere and does not go in the report zip (Privacy Policy 3.10).
   4. Only the author can make a shared ban, and it is decided by looking at Aegis records (evidence). Not being able to create rooms while a shared ban lasts, how it is lifted, and how to appeal are written in Article 15(5) and Play Rules, Articles 9 and 10.
7. The GPL and these checks
   1. The Software is GPL. Under the GPL, anyone can change or remove the Aegis checks (Article 3). We do not stop that with technology, and we do not forbid it in these terms. Aegis is a way of telling honest users things; it is not something that cannot be removed.
   2. Using a version with the checks changed or removed is not, on its own, a reason for a limit under Article 13.
   3. However, making people think a modified version is the official version (Article 9, item 3) and not telling us it is modified when using the Services (Play Rules, Article 4(3)) are covered separately. Also, if someone with the checks removed joins another host's room, that host's Aegis and shared-ban list look at them.
   4. All we can stop is access to the Services (Article 13).
8. Mistakes happen
   1. Aegis's checks have misses and false detections (Article 20(2)(2)). The Play button can stop because of a tool that only has the same name, a visual tool such as ReShade, or test mode someone turned on themselves for development. These are not proof of cheating, and you can play right away once they are fixed (Play Rules, Article 3(5) and Article 4(4)).
   2. If you think something was found by mistake, tell us with "Contact support" on the screen. We will fix the definitions file. If you do not accept a check or a room restriction in a room, you can use the appeal in Play Rules, Article 10.
   3. Room restrictions, shared bans and appeals are decided by Aegis on the host's PC and by the author. Admins and support members help within the limits of their roles (Article 6(3)). We never let AI decide them (Article 16).

Article 12 (Updates and the definitions file)

1. The official StarPocket Client that we sign and distribute checks whether the following are newer and receives them. It receives them from GitHub (United States) and from the place BepInEx is distributed from. What the Client sends then is only what any normal download sends (the name and version number of the Client or Aegis); nothing about this PC is sent. The places it receives from get an IP address, as with any normal connection (Privacy Policy 3.9). The Client of someone signed in to a StarPocket Account also talks to our server separately (planned); that is in paragraph 9.
   1. The Aegis definitions file (a signed file containing the names of the tools Aegis looks for, the numbers used for checks, the central lists, the versions needed and so on)
   2. New versions of PocketRoles (the official releases on GitHub) and the part that runs MODs (BepInEx)
   3. News and the state of the Services (notices about maintenance and breakdowns, notice that the room-list key has been stopped (Article 13(3)), and notices about new versions of these terms and the Privacy Policy). This is planned. Today's Client does not receive these yet. When we build it, we will use only things signed with our key.
2. When it connects
   1. The definitions file is received once when the Client starts. After that, once 12 hours have passed since the last time, it is received again when the window is opened or Play is pressed. Even if you leave the Client open, it is not received more often than that.
   2. New versions of PocketRoles are checked only when the user presses "Check for updates", and during install, repair and "Update". The Client does not check by itself at start-up today.
   3. News and the state of the Services are planned to be received when the Client starts.
   4. PocketRoles inside the game also receives the same definitions file itself (when the game starts, and once a day while it is running; Privacy Policy 3.9).
3. Nothing is sent before you agree. Until you press "Agree" on the "Terms of Use and Privacy Policy" screen the first time you open it (Article 4(1)(1)), the Client does not connect to the internet. The text of the terms and the policy shown on that screen is the text kept inside the Client. If you choose "Decline", the Client closes without sending anything (Article 3(3)). The same goes for when these terms change a lot and we ask you to agree again (Article 26(4)). Starting StarPocket Account sign-in connects to our server for authentication (planned; Article 8(3)(4)). Friends status and related data (paragraph 9) are sent only after sign-in, and this traffic stops when you sign out.
4. The signature of the definitions file is checked before it is used.
   1. The definitions file carries a signature made with our key. The Client uses and saves a received file only when its signature can be checked with our public key (the key for checking signatures) that is kept inside the Client. A file whose signature does not match, and a file with no signature, are neither used nor saved. A signature made with a key we have revoked is treated as not matching either.
   2. When there is not a single file whose signature matches, the Client runs on the small list built into it. Checking signatures never stops the Client or playing.
   3. Changing the keys used to check signatures (adding an admin's key, revoking a lost key and so on) is done by releasing a new version of the Client. The keys cannot be changed from the definitions file's side.
5. We do not go back to older versions.
   1. Only a definitions file with a newer version number than the one in use is saved. A file with an older number, or with the same number but different contents, is not saved, even if the signature matches. Of the file kept inside the Client and the file received and saved, the newer one is used.
   2. PocketRoles does not install a version older than the one already installed. When the version in the official release is older than the one installed, it says "You are up to date" and does nothing (when an official release is put out again with the same version number, pressing "Update" installs the one put out again).
   3. BepInEx is installed only at the set version written in the Client, and only when the file's fingerprint (SHA-256) matches the one written in the Client. A file whose fingerprint does not match, and a version the Client does not know, are neither downloaded nor unpacked. The PocketRoles zip is received from the official release place and installed after checking that the set files are in it. Comparing the zip's fingerprint with a published list is something we plan to add.
   4. We do not put out an older version of the definitions file either. When we fix a mistake, we fix the contents, raise the version number and sign it again.
6. What changes automatically, and what starts only when the user presses something
   1. The only thing that changes automatically is the definitions file. A definitions file that has been received is used from the next scan (the scan before playing, or the next start-up). What a definitions file changes is only "lists and numbers": the names of what Aegis looks for, the numbers used for checks, the central lists and the versions needed (how far the numbers can be changed is in Play Rules, Article 12(2)). A definitions file never changes the programs of the Client, PocketRoles or the game themselves.
   2. The following start only when the user presses a button. The Client never starts them by itself.
      • Installing a new version of PocketRoles ("Update")
      • Making the MOD copy again when Among Us on Steam has been updated ("Update and play")
      • Putting back missing or changed files ("Repair")
      • Installing BepInEx (it is installed as part of install or repair)
   3. The Client itself does not yet have a way to update itself to a new version. Please download and install a new version of the Client from the official places (Article 26(7)). When we build a way for the Client to update itself, we will change this article and tell you.
   4. The Client only replaces things inside the MOD copy it made (the "Among Us PocketRoles" folder). It puts nothing in, and changes nothing in, the Steam Among Us folder.
   5. PC settings (starting the Client when the PC starts, making a shortcut and so on) are changed only when the user chooses them (Privacy Policy Article 15(2)).
7. If you do not install an update
   1. When there is a new version of PocketRoles, we tell you about it (P-23). The user decides whether to install it. You can keep playing on the version you have.
   2. However, when an old version has a big bug or a safety problem and we have released a new version that fixes it, we may write a "version needed" in the signed definitions file (this starts with PocketRoles v0.5.5). With a PocketRoles older than the version needed, you cannot create new rooms (P-22). PocketRoles inside the game tells you this and how to fix it. Joining other people's rooms, the settings, Practice and plain Among Us from Steam still work. A room and a match already open can go on. Install the new version with "Update" and you can create rooms again.
   3. When Among Us on Steam has been updated, the Play button becomes "Update and play" (P-13). Pressing it makes the MOD copy again from Steam's new files and then starts the game. Because the old copy cannot get into Among Us online, the Client does not start it until you press it.
   4. We do not stop you carrying on with an old Client. But with an old Client you may not receive new features of the Services or the news.
   5. When the definitions file or the news cannot be received (no internet, GitHub is down and so on), what was received before, or what is kept inside the Client, is used. That never stops you playing.
8. This article describes how the official Client that we sign and distribute behaves. People who build it themselves under the GPL, or modify it, decide for themselves when to update what (Article 3). The definitions file and the official releases are published on GitHub, so anyone can receive them.
9. What the Client of a person signed in to a StarPocket Account sends (planned; Article 8(10). The Client of someone not signed in does not do this)
   1. While signed in, once every 30 to 120 seconds (every 30 seconds while a room is being shown), it sends our server (through Cloudflare) the sign-in key, the current state (whether the Client is open and whether you are playing PocketRoles) and, for people who turned on showing their room code, the details and code of the room they are hosting. Playing plain Among Us from Steam is not sent.
   2. Sent when you act: changing your display name, your icon (the number of one of our pictures, or the image you chose), making and entering friend cards, accepting, declining, removing a friend, blocking, reporting, and getting a room code. Friends' icon images are received.
   3. Before uninstalling, one sign-out is sent. Signing out stops this traffic.
   4. The details, how long things are kept and how to stop it are in Privacy Policy 3.9, 3.12 and Article 5.

Article 13 (Limits on using the Services)

1. If a user does anything in Article 9 (Things you must not do) or Article 10 (Playing fair), or falls under Article 28(1) (No organised crime), or does anything in Article 28(2), or a host does any of the following, the author may limit that user's use of the Services. Admins and support members cannot impose or lift these restrictions.
   • used a cheat tool in a room (Play Rules, Article 3(1))
   • said a modified version was the official version, or did not tell us it was modified when using the Services (Play Rules, Article 4(3))
   • broke Play Rules, Article 7 (rules for hosts)

     Not meeting the conditions for the state of the host's PC (Play Rules, Article 3(2) to (4) and Article 4(1); codes starting with R) is never, on its own, a reason for a limit. The Client checks these before playing, and they also appear for people who made changes the GPL allows.

     Also, if a host's shared-ban requests (reports) are found to be wrong on appeal 3 times within 30 days (mistakes of "Certain" detections do not count), we may apply S-11 (not accepting shared-ban requests), even if they were not lies. This keeps reports reliable (Play Rules, Article 7(3) and Article 9(2)).

     Only the following limits can be used.

In StarPocket Friends (planned), when reports from other people gather in a short time, your icon is hidden, or making friend cards and showing your room code is stopped, automatically and before anyone looks. The author reviews it within 48 hours and restores it if there is no problem. This is not a limit under this article but a temporary stop until the author has looked. When it becomes a limit (S-16, S-17), we tell you as in paragraph 3.

2. The length depends on how serious it was and how many times.
   • Guide: a warning → 7 days → 30 days → no end
   • When there is immediate danger (attacks, threats, exposing personal information and so on), a long limit may be used from the start.
3. When we apply a limit, we tell the user, in whatever way we can:
   • the reason (which article and item of these terms or the Play Rules)
   • the length
   • the code
   • how to appeal

     If we have no way to tell them (for example, we have no contact), it is shown on the screen when they try to use that feature. When the room-list key is stopped (S-12), it is shown in StarPocket Client's "Service status" area, the same place as maintenance and outage notices.

4. The limits in this article apply only to the Services.
   • They do not stop anyone using the GPL Software or playing Among Us. The limits in this article never stop the Play button in StarPocket Client either.
   • A shared ban (Play Rules, Article 9; B-91) is separate from the limits in this article. While a shared ban lasts, that Among Us account will not be able to create rooms with the official PocketRoles, and the Client's Play button will turn into a grey "Restricted" button that does not start the game (both planned; neither is in today's PocketRoles or Client yet). Playing plain Among Us from Steam is not stopped (Play Rules, Article 9(6)).
   • "You can't play yet" under Play Rules, Articles 3 and 4 is a check of something found on this PC, not a limit. It goes away once fixed.
   • We cannot ban Among Us accounts.
   • We do not use limits based on PC hardware numbers (hardware IDs).
5. If you do not accept a limit, you can appeal once per limit through support.
   • Staff look at it again based on the records that remain.
   • When possible, a different staff member from the one who decided looks at it.
6. We never apply a limit only because "we think it is inappropriate" or similar.

Article 14 (Our promise to be fair)

Article 10 is users' promise to play fair. This article is the other side of it: our (staff's) promise. So that limits and shared bans are never decided by "how the author feels", we gather here the things we keep to. This article ties our own hands; it does not add new duties for users.

1. We decide only for the reasons written down. The reasons for limiting use of the Services are only those written in these terms (Article 9, Article 10, Article 13(1) and Article 28) and in the Play Rules. We never apply a limit only for a reason like "we thought it was inappropriate". When we want to add reasons or kinds of limits, we first change these terms, tell you, and ask you to press "Agree" again (Article 26(4)).
2. The state of a PC alone is never a reason for a limit. Not meeting the conditions for the state of the host's PC (Play Rules, Article 3(2) to (4) and Article 4(1); codes starting with R) is never, on its own, a reason for a limit (Article 13(1)). The Client checks these before playing, and they also appear for people who made changes the GPL allows. Fix it and you can play right away.
3. People decide, after looking at the evidence. Limits, shared bans and the results of appeals are decided from the records (evidence) that remain. We do not decide on "because someone said so" or "because we dislike them" (Play Rules, Article 9(2) and Article 10(4)). Whether the author decides alone or an admin helps, the same rules are used. Only the author decides service restrictions, shared bans, their removal and appeal outcomes. Admins and support members help within the limits of their roles (Article 6(3)). We never let AI bots decide (Article 16(2) and (5)).
4. People who did the same thing are treated the same. What a limit is and how long it lasts are decided by how serious what they did was and how many times (the guide in Article 13(2): a warning → 7 days → 30 days → no end). The following never change how someone is treated.
   • Whether they supported us (Article 7(3))
   • Whether they know the author or an admin. Whether they get on well with them or not
   • Whether they are famous. Whether their room has many people
   • Their roles on the Discord server (such as "Host")
   • Whether they appealed (we never treat someone worse because they appealed)
   • The language they use (Japanese, Chinese, English)
5. We do not start with a heavy limit. As in the guide, we start with a warning. A long limit from the start is used only when there is immediate danger (attacks, threats, exposing personal information and so on; Article 13(2)) and in the case of Article 28(3). Even then, we tell them the reason.
6. We never apply a limit silently. When we apply a limit, we always tell the user, in whatever way we can, the reason (which article and item of these terms or the Play Rules), the length, the code and how to appeal (Article 13(3)). For a shared ban, PocketRoles inside the game and StarPocket Client show the end date, the reason, how to appeal and "your code" (Play Rules, Article 9(6)). We never apply a limit secretly without telling, and we never quietly make a limit longer than the length we told you.
7. Appeals are looked at again with different eyes. You can appeal once per limit and once per shared ban (Article 13(5); Play Rules, Article 10). An appeal is looked at again from the records that remain. When possible, a staff member other than the one who decided looks at it. We write "when possible" because there are few staff today. When there are more staff, we will make it always so. For room restriction appeals sent through the support site, Room Access Team staff who meet the purpose, viewing notice version, time and team conditions in Article 6(3) also read the records and write an assessment and a reply draft; the author takes these into account when deciding. Requests on the same form to erase records or report a host are read only by the author. Posting replies, changing status and deciding to lift restrictions are not delegated to staff.
8. When we find we were wrong, we put it back.
   1. When we find a limit or a shared ban was a mistake, we lift it right away. We also tell them it has been lifted, in the place where we told them about the limit (Discord, email, that feature's screen, StarPocket Client's "Service status"). Lifting a shared ban reaches each host's PC the next time they receive the definitions file (Play Rules, Article 10(4)).
   2. A limit that was a mistake does not count towards that person's "number of times". Next time something happens, the earlier limit is treated as if it had never been, and counting starts from the beginning.
   3. We never use the record of a limit or a shared ban that was a mistake as material for treating that person worse. What we keep on our side is the log of actions that stops us making the same mistake again (Privacy Policy 3.5), and the imported records and report zips (not deleted automatically yet; Privacy Policy 3.5, item 4). We cannot delete the evidence records left on the host's PC. If that person asks, they are erased through the erase list (Play Rules, Article 11; Privacy Policy Article 12).
   4. When an automatic room restriction on a host's PC (an Aegis check) was a mistake, the author lifts it by putting it on the "lift list" (from PocketRoles v0.5.5; Play Rules, Article 8(8) and Article 10(4)). It reaches each host's PC the next time it receives the definitions file. For 30 days from listing, Aegis does not restrict that person automatically.
   5. When the cause of a mistake was in Aegis's checks, we fix the checks (in the definitions file, or in the next version of the Software). This is so that other people are not limited by the same mistake (Play Rules, Article 7(3) and Article 10(6)).
9. The same rules apply to staff. The author and the admins follow these terms and the Play Rules just like everyone else, both when they make rooms as a host and when they use the Services as a user. Being staff never means there are fewer things they must not do, or that limits are softer. When an admin does anything in Article 9 or Play Rules, Article 7, we apply the same limit as for any other user and also take away their admin role. If you think the author is not keeping the promises in this article, tell us through support (Article 34). When possible, an admin, not the author, looks at it.

Article 15 (Play Rules)

1. Behaviour in PocketRoles rooms, Aegis decisions, room restrictions, shared bans and appeals are described in the Play Rules.
2. For people who use the Services, the Play Rules are part of these terms.
3. For people who only join a room, the Play Rules are not a contract. They are a public standard that the host uses in their own room. But the shared-ban list is a list the author decided after looking at evidence, and it is used automatically unless the host turns it off. That is our decision and the host's, and it can be appealed (Play Rules, Articles 1 and 10).
4. The conditions for making a shared ban from records sent by other hosts (for a "Certain" detection whose record matches the log, one host is enough, only for the first level of up to 30 days, and at most 2 per 30 days from one and the same host; for anything else ("Repeat" detections, chat (hurtful words, flooding), harassment, or things the host decided by watching), 2 or more different hosts within 30 days, a trusted admin's report, or the author writing down the reason in the records) are in Play Rules, Article 9(2). That "2 or more different hosts" is a count of hosts, and it may go up to a larger number as more hosts join. The "at most 2 per 30 days from one and the same host" above it is a count of bans, not a count of hosts.
5. While a shared ban lasts, that Among Us account will not be able to create rooms with PocketRoles (planned; not in today's PocketRoles yet). PocketRoles in the game does the check, comparing only inside the host's PC, and sends nothing. Details are in Play Rules, Article 9(6).
   • Also checking with our server (by receiving the whole list; nothing about your account is sent) is not done now. If we start it, we will ask you to press "Agree" again, as in Article 26(4).

Article 16 (Support and the AI bot)

1. In support chat (planned), an AI bot or article search without AI answers first. The bot answers only people who tick the optional consent to send text to AI when starting (this option appears only to eligible people; paragraph 4). This optional consent starts unticked. Without ticking it, you can still use article search and Ask a person. We record the consent version and time. You can choose only at the start, and cannot add consent partway through. You can have one ongoing chat at a time; an article-search chat continues until you send through Ask a person or 24 hours have passed since it started.
   • The bot uses Claude by Anthropic PBC (United States). Article search is not AI. It sends your search text to our server and searches Help Centre articles. Your text, article-search results and bot answers remain as chat records. If you do not hand over to a person, we delete these records from the database 24 hours after chat starts. Nightly backups keep them for the backup retention period. Even while kept, they cannot be read from the author's screen. See Privacy Policy 3.1 and Article 5.
   • The bot is not a person. The screen says so too.
2. The bot is built to answer only from Help Centre articles. Even so, it can make mistakes.
   • The bot does not decide anything about your records, such as room restrictions, appeals, erasing records or limits on the Services. Staff always decide those.
3. If the bot or search does not solve your problem, send through Ask a person. Sending immediately creates a request with a receipt number. Only the author currently reads and answers it. When available, the author may have a live conversation with you (planned). If unavailable, unable to accept after a wait, the conversation goes quiet, or you or the author move it to a request, the author replies later on the receipt-number page (also available by signing in and opening Your requests; no secret link is issued). Receipt and reply notices are not emailed. People who choose Discord DM notices receive DMs, but not for each live message. Leaving the waiting room does not delete the content; it remains as a resolved request (Privacy Policy Article 5). Availability depends on the author at the time. We cannot promise an immediate reply.
   • "Attach the conversation so far" starts ticked and can be unticked. Attached text from you, article-search results and bot answers are read by the author and kept for the request retention period. If unticked, the preceding search/bot conversation records are deleted from the database on handover (nightly backups keep them for the backup retention period).
   • Ask a person in chat does not accept room restriction appeals. It directs you to the dedicated appeal form. Staff access and deletion of friend codes after 7 days for that form remain unchanged (Articles 6(3), 14; Privacy Policy 3.1 and Article 5).
   • A reply can take a few days. We cannot promise a reply by a certain time.
4. The bot is not used for the following people. Article search and Ask a person are available regardless of country or age band (these terms, including sign-in requirements, still apply). The author currently answers Ask a person.
   • People under 18 and people who have not answered the age question on the account page. Those who have not answered see a link to the account page.
   • People outside Anthropic's published list of supported countries and regions, people whose country is unknown, and people in countries or regions we additionally block. The bot is offered only in allowed countries on that list; all of Ukraine and Kosovo are excluded. Mainland China, Hong Kong and Macau are also excluded. We determine country only from Cloudflare's country signal, not the browser time zone.
   • Article search is used when monthly cost, per-chat cost, per-person daily (UTC) count or server-wide daily count limits would be reached, when AI is off or paused, or when the model price is not set. Timeouts, errors and unusable answers also return search results for that question. If this happens after sending to AI, the screen says AI is currently unavailable. Failed answers count toward the limits too.
   • AI is used for staff reply drafts (paragraph 5) only for requests where "The author may use AI to draft the reply" was ticked when sending. Even if ticked, the text of people under 16 and people using it from mainland China is not sent (Privacy Policy 3.1). Requests sent from chat are not sent for these drafts.
5. Staff may have AI (Claude by Anthropic) write drafts or translations of replies (off today; we will announce it before we start using it).
   • The text of a support request is sent to the AI only if it was ticked, and only when a staff member presses the draft button.
   • A staff member always reads and edits the draft, and a staff member sends it. The AI never sends a reply by itself.
   • The AI is never allowed to decide room restrictions, shared bans, appeals, erasing records or limits on the Services. Staff always decide those.
   • What is sent is described in Privacy Policy 3.1.
6. Which companies support messages are sent to, and how long they are kept, are in the Privacy Policy.
   • Please do not write your real name, address, phone number, school or passwords in support messages.
7. For urgent trouble such as bullying, threats or danger to life, talk to a parent or guardian, your school, the police and so on, not to us.
   • In Japan, you can also call the "24-hour Child SOS Dial" run by the Ministry of Education (MEXT). The phone number is on the Ministry's page.
   • If you are outside Japan, contact a children's helpline or the police in the country where you live.

Article 17 (What users send us)

1. Rights in support messages, reports, evidence and so on stay with the sender (or the original rights holder).
2. Users allow us to use what they send as far as needed for the following.
   • Things we may do: copy, keep, share among staff only within each member's permitted access, and translate (when DeepL is used for translation, as in Article 18(1)(7)). Only the author reads applications and selection records from the contributor recruitment (Article 6(4))
   • Purposes: responding to support requests, making decisions, improving the Software and Services, and selecting and contacting contributors (Article 6(4))
   • We do not publish what is sent to us, except the values put on the central lists (Privacy Policy Article 8).
3. Do not send things you have no right to send (other people's works, other people's personal information).

Article 18 (Outside services)

1. The Services run by borrowing services from other companies ("outside services"). The outside services we use, and what we use them for, are as follows. The company's country, the information sent, the basis for sending it abroad and the steps the company takes are written in the table in Article 6 of the Privacy Policy.
   1. GitHub (GitHub, Inc.): distributing the Software (Releases), delivering the definitions file and the central lists, publishing documents such as these terms
   2. Cloudflare (Cloudflare, Inc.): the place the official site (starpocketgames.com) and the PocketRoles site sit (Cloudflare Pages), the door for news and status notices to StarPocket Client (planned; they come from our server), the door to the home server (so that our home IP address is not shown outside), the bot check (Cloudflare Turnstile). The bot check runs every time you send a support request and every time you sign in to an account on the site. Sign-in from StarPocket Client (planned) is protected by rate limits instead of the bot check. The traffic between a signed-in Client and our server (Article 12(9); planned) also passes through Cloudflare
   3. Discord (Discord Inc., United States): the Discord server "PocketRoles 役職部屋", tickets (we use a ticket bot called Ticket Tool), notices to staff, signing in with Discord (Article 8), signing in with Discord from StarPocket Client (you press "Authorize" in your browser; planned), DMs announcing replies to support requests and Join us applications (only for people who choose them; overseas sending and handling for people under 16: Article 25(1)(5), Privacy Policy 3.1 item 7 and Article 6)
   4. Google (Google LLC): support email (Gmail)
   5. Resend (a company that sends email): sending our email, such as verification-code emails, notices that a reply has arrived, the notice when Discord is connected, the notice when a new Client signs in (planned) and the confirmation email to the parent or guardian of someone aged 13-15 (planned) (so that email is not sent straight from the home server)
   6. Anthropic (Anthropic PBC): the AI support bot (planned), and drafts and translations of staff replies (Article 16). Both are off today. When we start using them, we will tell you on a screen before we start and ask you to agree, as the Privacy Policy says
   7. DeepL (DeepL SE): translating support requests and contributor applications (the paid DeepL API Pro). Text is sent only when the author, or a staff member who can read that request, presses "Translate" (support members can translate only requests for the teams they handle). We translate only the requests of people who agreed, when sending the request, that it "may be sent to DeepL for translation" (this tick is planned). For applications, consent is given on the application page, and only the author can translate them (planned). Parts that look like contact details, such as email addresses, phone numbers, URLs and IDs, are hidden before sending. The translation is only shown on screen and is not kept on our servers. DeepL states that text received through API Pro is deleted once translated and is not used for training. This translation feature does not use the free plan. DeepL (the paid DeepL Pro) is also used to translate applications for the Steam-copy program, which is planned (the day requests open will be announced in a notice; only during the 30-day window; applicants only; Privacy Policy 3.1). Details are in Privacy Policy 3.1 item 12, 3.13 and Article 6
2. The following are sent by the Software from the host's PC straight to the other side. They do not pass through our hands. What is sent, when it is sent, and how to stop it are written in Privacy Policy 3.9.
   1. Google or DeepL (DeepL SE): chat translation (only when the host turns it on; but for a host who upgraded from v0.5.4 or earlier and never changed this setting, the config file may still say on. When the mod is reinstalled or updated with StarPocket Client (v1.1.2 or later), it becomes the answer given on the first screen. If you do not want it, turn it off with /opt translate off; Privacy Policy 3.9)
   2. Innersloth (Innersloth LLC): official Among Us reports about people removed from a room for a "Certain" cheat (only when the host turns automatic reporting on)
   3. Discord: the "people online now" number shown in StarPocket Client's community area
   4. GitHub and the place BepInEx is distributed from: receiving the definitions file, checking for and downloading updates (Article 12)
   5. Among Us' servers: the check used to choose a region (only when the host turns AutoRegion on)
3. Each outside service has its own company's terms of use and privacy policy, separate from these terms.
   • When you use the Services through an outside service, such as joining the Discord server, downloading from GitHub or signing in with Discord, please also follow that company's rules.
   • Those rules are not ones we made. We cannot change them, and we cannot promise anything on that company's behalf. What that company does to a user (stopping their account and so on) is not ours to decide either (Article 20(4)).
   • These terms are not the rules of the outside services themselves. These terms do apply to the parts of the Services that sit on top of outside services, such as the Discord server "PocketRoles 役職部屋".
4. We cannot stop an outside service going down, changing its contents or its rules, or ending.
   • When that happens, part of the Services (downloads, delivery of the definitions file, support, Discord, signing in, email notices and so on) may become unusable without notice (Article 19(1)).
   • We try to find another way as soon as we can. But we cannot promise a date (Article 20(2)).
   • Even while our home server is down, Among Us and the PocketRoles you installed can be played as usual. The game is built to work without our servers.
5. The site, Discord, support replies and the Software contain links to outside sites.
   • The places the links go to are not made by us and not run by us. We cannot check what is in them or whether they are safe. What is in them, and what happens there, is between you and whoever runs that place, and is not ours to decide. So we cannot take responsibility for it.
   • Before you send anything, buy anything or agree to anything at a link, please read that site's rules.
   • Links and downloads using the names "StarPocket Games" and "PocketRoles" anywhere other than the official site, the official GitHub and the official StarPocket Client (Article 26(7)) are not necessarily ours (Article 9, item 3). Anything asking for money is not us (Article 7(4)). If you are worried, please tell support.
6. Among Us and Innersloth
   1. Among Us is a work of Innersloth LLC. The Software is an unofficial fan mod. It is not approved or sponsored by Innersloth. There is no connection between us and Innersloth (Article 3(6)). The name and pictures of Among Us that appear in the Software and on the site belong to Innersloth (Article 22(3)).
   2. When you play Among Us, also follow Innersloth's Terms of Use and Mod Policy. These terms and the Play Rules add to those.
   3. From 30 July 2026, Innersloth's Mod Policy requires a mod that changes how Among Us behaves on the official servers to be registered when a room is created. The official PocketRoles has done this registration (lobby registration; +25) from the start (Play Rules, Article 7(1)(1)). The registration is Innersloth's rule, not one we made.
   4. Innersloth's Mod Policy requires mods to be given away free. The Software is free, and hosts do not make money from rooms either (Article 7; Play Rules, Article 7(1)(1)).
   5. The following are not ours to decide (Article 20(4)).
      • What Innersloth does to Among Us accounts (what it does with the reports in (2)(2), banning accounts and so on)
      • Innersloth's servers going down. Innersloth changing Among Us or the Mod Policy. The Software becoming unusable for a while because of that (Article 19(1) and Article 20(2)(4))
   6. When you buy Among Us on Steam and play it, the rules of Valve, who run Steam, also apply. Plain Among Us from Steam can be played even during a shared ban or a limit on the Services (Article 13(4)).
7. Parts made by other people, such as BepInEx, are covered by their own licences (Article 3(7)).

Article 19 (Changes, pauses and ending of the Services)

1. The Services are run by an individual as a hobby. They may stop without notice, for example because of:
   • power cuts, breakdowns, maintenance
   • changes in Innersloth's policies
2. We may change or end the Services. For big changes or an ending, we tell you as early as we can on the site and on Discord. Once StarPocket Client's news (planned) exists, we tell you there too.
3. Even if the Services end, the source code of Software published under the GPL can still be used under the GPL.
4. If we end the account service, we tell you at least 30 days before, and then delete account information.

Article 20 (Warranty and liability)

1. Sections 15 to 17 of the GPL (no warranty, no liability) are terms of the copyright permission (licence) for the Software. Our liability for the Services, including distributing the Software, is as in item 3 of this article (liability is not limited when we acted on purpose or with gross negligence, or for harm to anyone's life or body).
2. We try to keep the Services working correctly and safely. But we cannot promise:
   1. that they can always be used, or never stop;
   2. that Aegis decisions are always right (there are misses and false detections);
   3. that the bot's answers are always right;
   4. that we can respond right away when Innersloth changes Among Us.
3. If a user suffers damage from the Services, our liability is as follows.
   • Only where we were merely slightly negligent (ordinary carelessness), our liability is limited to the direct and ordinary part of that damage.
   • This limit does not apply where we acted on purpose or with gross negligence.
   • This limit does not apply to harm to anyone's life or body.
4. The following are not ours to decide:
   • what Innersloth does to Among Us accounts
   • what other hosts decide about their own rooms

Article 21 (Trouble between users)

1. PocketRoles rooms and the Discord server are places where people gather. So trouble between users can happen. That includes trouble between a host and someone who joined (being removed from a room, not being let into a room and so on) and arguments between the people playing. In this article, trouble with people who only join a room (participants) is treated the same way.
   • Please first talk about this kind of trouble with the people involved (the people who were there) and settle it. If the room shows /rules, please read that too.
   • When you talk with the other person, please keep to Article 9 (abuse, threats, writing personal information and so on).
2. We are not in a position to arbitrate trouble between users (to come between them and decide who is right).
   • We were not there. The records on the host's PC do not reach us (Privacy Policy Article 12(6)). Normal conversation in a room is not kept in Aegis's records (Play Rules, Article 5(6)). So we cannot check and decide whose story is right.
   • As in Article 20(4), what another host decides about their own room is not ours to decide.
3. What a host decides in their own room (removing someone, stopping them from joining that room, what /rules says, how VIPs and moderators are treated and so on) is that host's decision (Play Rules, Article 1(3) and Article 6(2)).
   • We cannot let you into a room you were kept out of by the host's decision. Only that host can lift it (Play Rules, Article 10(5)). When we can reach the host, we can pass a message on.
   • Not being able to join a host's room is not a ban of your Among Us account. You can still join other hosts' rooms.
   • A room restriction Aegis decided automatically (codes starting with J) and a shared ban (B-91) are separate from the host's decision. If you think they are a mistake, you can appeal as in Play Rules, Article 10.
4. The following are not arbitration of trouble; they are decisions we make ourselves.
   1. Whether to make a shared ban (Play Rules, Article 9), and looking again at an appeal against one. The author decides after looking at the evidence. A host's request alone is not enough. We never make a shared ban for a reason like "I dislike them" or "we had a fight" (Play Rules, Article 7(1)(5)).
   2. Limits on using the Services (Article 13), and looking again at an appeal against one.

      Both are there to keep rooms and the Services safe for everyone. They do not decide who is right in a piece of trouble.

5. Even so, please tell us when things like the following happen.
   • Harassment, threats, being targeted again and again
   • Your own personal information (real name, address, school, photos, friend code and so on) being written down or exposed
   • Someone pretending to be you
   • Anything else covered by Article 9

     Here is how to tell us.

   1. For things that happened inside the Services (the Discord server, support and so on), tell the contacts in Article 34. It helps if you say when and where it happened and what happened (as far as you know), and add screenshots. You do not need to look up and write the other person's real name or address (Article 9, item 4).
   2. For things that happened in a PocketRoles room, tell that room's host first. The host can remove that person from the room, or stop them from joining (Play Rules, Article 6). The host can also send a shared-ban request with the records attached (Play Rules, Article 9). You may tell the contacts in Article 34 as well. People who only join a room may tell us too.
   3. We never pass on the name or contact details of the person who told us to the other person (except where the law requires it and so on; Privacy Policy Article 7).
6. Even when you tell us, we cannot promise that we can always do something. The Services are run by the author alone with the admins who help, a reply can take a few days, and we cannot look into everything. This is not to pretend we did not know; it is to say honestly, from the start, what we can and cannot do.
   • What we can do: look into things that happened inside the Services and, where Article 9 applies, apply a limit within the limits of Article 13. Delete posts inside the Discord server. Make a shared ban when there is enough evidence (paragraph 4).
   • What we cannot do: look at the records on a host's PC. Undo a host's decision. Check afterwards what was said in a room. Make the other person apologise or pay for damage.
   • Even when we could not do anything, what you told us is material we use when thinking about Article 13 and shared bans.
7. When there is immediate danger (threats, stalking, danger to life and so on), please talk to the police, a parent or guardian, your school and so on, without waiting for our reply (Article 16(7)). When it becomes a legal dispute, such as asking for damages, we cannot come between you. Please talk to a lawyer or a public advice line.
8. Damage from trouble between users is a matter between the people involved in that trouble. Our liability when we were at fault is as in Article 20(3).

Article 22 (Names, logos and rights in works)

1. The names and logos "StarPocket Games" and "PocketRoles" are names and logos we use for our activity. They are not registered trademarks.
2. The logo, the mascot, the pictures on the site and the like are not covered by the Software's GPL. They are © StarPocket Games. Please do not use them on a modified version or on anything unrelated to us (Article 9, item 3). Where a file states a different licence, that licence applies.
3. The name and pictures of Among Us belong to Innersloth LLC.

Article 23 (Telling us that something breaks your rights)

1. If you think something in the Services breaks your own rights, you can tell us.
   1. The rights this covers are the following.
      • Copyright (the right of the person who made a picture, text, music, video, program and so on)
      • Trademarks (rights in the name or the mark of a product or a service)
      • Portrait rights (the right not to have your face or your figure used without your permission)
      • Privacy (the right not to have things about you that you do not want known spread without your permission)
      • Other rights protected by law (such as your good name)
   2. What this covers is things in places we run. Posts on the Discord server "PocketRoles 役職部屋", the names of rooms put on the room list and other things put on the site, and the Software, logos, mascot and site pictures we distribute (Article 22), and so on.
   3. A report can be made by the person who holds the right, or by someone that person asked. For a person under 18, a parent or guardian can make it too (Article 5). You do not need to agree to these terms or to have an account to make a report.
   4. Please ask for the following in their own ways, not under this article.
      • If you want your PocketRoles records, your value put on a central list, your support requests or your account deleted: Privacy Policy Article 12
      • If you think you were given a room restriction or a shared ban by mistake: Play Rules, Article 10
2. Send it to a contact in Article 34 (the contact form, email, a Discord ticket, or support chat, which is planned and requires signing in with a StarPocket Account). By email, please start the subject with "Rights report". People too young to use Discord should use the contact form (no account needed), email, or support chat (planned; requires signing in with a StarPocket Account) (Article 5(3)).
   • Reports are read and decided by staff, not by a bot (Article 16(2)).
3. Please write the following in your report.
   1. Which thing it is about (a link to the Discord post, or the date, time and channel. The room name. The address of the page on the site. The file name, and so on, so that we can find it)
   2. Which right you think is broken, and how
   3. Why you can say it is your right (where the original work is published, the trademark registration number, that the person shown is you, and so on)
   4. A contact where you can get our reply (an email address or a Discord account)
   5. A line saying that what you wrote is true
   • You do not have to write your real name, address or phone number, unless a legal procedure needs it.
   • If something is missing, we ask you about it.
   • Making a report while pretending to be someone else (Article 9, item 2), and sending the same report again and again (Article 9, item 6), are things you must not do.
4. When we receive a report, we do the following.
   1. We tell you it arrived, and staff check what is in it. This can take a few days. We cannot promise when it will be finished (Article 16(3)).
   2. When it is clear that a right is being broken, or when there is immediate danger (another person's personal information or a photo of a child being exposed, and so on. Article 9, item 4), we delete it or hide it right away.
   3. Otherwise, we tell the person who posted it, in whatever way we can, that there is a report and what it says, and we hear their side. We do not pass on the reporting person's name or contact. If there is no reply within 7 days of telling them, or if, after comparing both sides, we decide that a right is being broken, we delete it or hide it.
   4. "Delete or stop" means the following. Deleting a Discord post. Taking a room off the room list. Taking something off the site. Fixing our Software, logo or picture, and stopping distribution of that part until it is fixed.
   5. Once we decide, we tell both the reporting person and the person who posted it the result and the reason (Article 25).
   6. We can only delete things in places we run. We cannot delete the following. Please tell the contact for that service (Article 18), or the person who posted it.
      • Chat inside a room, and things on a host's PC
      • Discord DMs and other people's Discord servers
      • Other people's repositories on GitHub. Things belonging to people who share a modified version under the GPL (Article 3)
      • Things inside Innersloth's services
   7. For a report about the Software, we can only fix the version we distribute. Because it is published under the GPL, we cannot take back copies that other people already have.
5. A person whose content was deleted or stopped can appeal.
   1. Once per report, at a contact in Article 34. Please write why the right is yours (you made it yourself, you have permission, the person shown is you, and so on).
   2. Staff look at it again. When possible, a different staff member from the one who decided to delete it looks at it (the same as Article 13(5)).
   3. If we find it was a mistake, we put back what can be put back. A post deleted on Discord sometimes cannot be put back. That is why, except when there is immediate danger, we ask first before deleting, as in paragraph 4, item 3.
   4. When the reporting person and the person whose content was deleted say different things and we cannot decide, we ask them to settle it between themselves or through a legal procedure (Article 21). Until it is settled, we may keep that thing deleted or stopped.
   5. Our decision does not decide, as a matter of law, who holds a right.
6. Japan has the Act on Dealing with Information Distribution Platforms (its earlier name was the "Provider Liability Limitation Act". It is a law that decides how a service holding something posted by another person should handle it when it breaks someone's rights, and when the poster's information may be given out). The steps in this article (asking the person who posted it and waiting 7 days, and so on) are written to follow this law.
   • A request to be told who posted something (disclosure of sender information) is answered only when it meets the conditions and the procedure set by this law. Our server does not store IP addresses, so there is very little information we can give (Privacy Policy Article 7).
7. Reports and appeals are kept for the same period as support requests, and then deleted (Privacy Policy Article 5). What is in a report is not made public, except when we tell the person who posted it (paragraph 4, item 3) (Article 17(2)).

Article 24 (Personal information)

How personal information is handled is written in the Privacy Policy.

Article 25 (How notices reach you)

1. Notices from us to users are put in the following places. Which place is used depends on the kind of notice (paragraphs 2 and 3).
   1. The official site (where it is, is written in Article 34). A notice shows the date it was put up. Changes to these terms, the Play Rules and the Privacy Policy are also put in "Change history" on the site (Article 26(2)).
   2. Inside StarPocket Client (the news cards, and the "Service status" area that shows maintenance and outages). Client notices reach you when you open the Client (planned; Article 12(1)(3), Privacy Policy 3.9). They do not reach you while it is closed.
   3. The news channel of the Discord server "PocketRoles 役職部屋". It only reaches people who are in the server.
   4. The email address registered to an account (only for people who have an account. Paragraph 4)
   5. Chat requests receive no receipt or reply email notices. People who choose Discord DM notices receive DMs, but not for each live message. The same place as that support request (replies, appeal outcomes and so on): the receipt-number page for support chat (sign in to open it; no secret link), the email thread for email, or the Discord ticket. If you enter a reply email address on the contact page, we email it when we receive your request (planned) and when a reply arrives. These emails contain neither your name, your subject or message, nor the reply text (Privacy Policy 3.1 item 7). If you sent the request while signed in and your account has an email address, reply notifications will also go there (planned; only one email if the addresses match. Today, they go only to the address entered on the contact page). Receipt and reply notifications will use a letter layout. Reply notifications will include the handler's display name, the support desk name, the handler's icon and our own stamp illustration (planned). The opening and handler lines will use the team's name (Article 2(4); planned). If you have connected Discord and chose "Also tell me by Discord DM when there's a reply", our bot also tells you by Discord DM that a reply has arrived (only if you choose it; you can stop at any time). The DM contains only the receipt number and a link to read the reply, never the reply text. It only arrives if you are in our official Discord server and allow DMs from server members (Privacy Policy 3.1 item 7). To send DMs, we send the Discord user ID and DM text to Discord Inc. (United States). Next to the choice, we show the recipient, a Privacy Policy link and a request that people under 16 choose with a parent or guardian. If you are under 16, please choose with your parent or guardian (Article 5(4) and Privacy Policy Article 10). For applications through the contributor recruitment (Article 6(4)), we contact you through replies to your application under "Your requests". If your account has an email address, we also email you when the application is received, and we may email you when we reply. Notification emails do not contain the application or interview content. If you choose DM notifications, replies to these applications are also announced by DM: receipt number and link only, with no application, interview or reply content (Privacy Policy 3.13).
   6. The screen of that feature (PocketRoles in the game, StarPocket Client, the account page). For example, notices during a shared ban are shown on the screen in the game and in the Client (Play Rules, Article 9(6)). Notices that arrive through updates and the definitions file are in Article 12.
2. Notices that concern everyone (changes to these terms, the Play Rules and the Privacy Policy; changes to the Services, pauses and the ending of them; maintenance; the start of a new feature) are treated as told to users at the moment they are put on the official site. We also put them in the Client and on Discord, but that is to make them easier to notice. Even if the Client or Discord is late, the moment they were put on the site is what counts. Numbers of days such as "at least 14 days before the date it takes effect" (Article 26(3)) are also counted from the day they were put on the site.
3. Notices that concern only one person (limits on using the Services (Article 13), appeal results, things about an account, replies to that person's support requests) are put where they reach that person. The order is as follows.
   1. When there is a contact that person used, we reply there (paragraph 1, item 5).
   2. To people who registered an email address with an account, we send it to that email address.
   3. To people we can reach on Discord, we tell them in a Discord ticket.
   4. When none of these is possible (for example, when we do not know a contact), it is shown on the screen when they try to use that feature (Article 13(3)). When the room-list key is stopped (S-12), it is also shown in the Client's "Service status" area.

      Notices in this paragraph are treated as told when they are put in a form that reaches that person (when the email is sent, when it is written in the ticket or the chat, when it is shown on the screen). What happens when an email does not arrive is in paragraph 6.

4. For people who have an account
   1. To people who registered an email address, we may send the following to that address. A verification code for signing in (only when the user asked to sign in), a notice that a reply has arrived (excluding requests sent from chat; planned; today it goes only to the reply-to address written on the contact page; paragraph 1, item 5), a notice when Discord is connected, a notice of a sign-in from a device we do not know (planned), a notice when a new StarPocket Client signs in (planned), a notice before an account is deleted (Article 8(7); planned), notices of important changes to these terms and the Privacy Policy, and notices of limits that concern that person (paragraph 3).
   2. We do not send advertising emails. We do not write the text of a support request in an email (Privacy Policy 3.1). Whether the setting that would tell us whether an email was opened (open tracking) is switched off at our email-sending company (Resend) is being checked. The logo in our emails is embedded in the email; nothing is loaded from outside. Handler icons and stamp illustrations will be embedded in the same way (planned).
   3. If you sign in with Discord only and have no email address on your account, we cannot send notices to an account email address. We show account notices when you sign in (Article 8(7)). If you enter a reply email address on the contact page, notifications are sent there as described in paragraph 1, item 5.
   4. When a registered email address stops working, please tell a contact in Article 34. While the address does not work, important notices will not reach you.
5. Messages from users to us
   1. Please send messages to us to a contact in Article 34. They are treated as reaching us when they arrive at the contact (when the email is in our inbox, when the ticket is made, when a request is sent through Ask a person in support chat). Questions sent only to article search or the bot do not count as requests received by a person.
   2. A reply can take a few days. We cannot promise a reply by a certain time (Article 16(3)).
   3. Things sent anywhere other than the contacts in Article 34 (the author's personal social media, chat in the game, Discord DMs and so on) may not be read. Sending them there does not count as reaching us.
   4. The notice emails we send may come from an address that does not accept replies. When that is so, the email says so. Please send your reply to a contact in Article 34.
6. When an email does not arrive
   1. When we sent it correctly to the registered email address but it could not be read (it went to the spam folder, it was blocked by receiving settings, the address was wrong, the address had stopped working, and so on), it still counts as told at the moment we sent it.
   2. However, when the company that sends our email tells us that it did not arrive, it does not count as told. We tell that person again on the screen when they sign in, or on the screen of that feature. Important notices (limits, and the notice before an account is deleted) are shown on the screen too, and not left to email alone from the start.
   3. We make sure users are not put at a disadvantage because an email did not arrive. Even if a notice of a limit did not reach you, you can still appeal (Article 13(5)). The same is true when you learn about a notice later.
   4. Please check your spam settings so that our emails can reach you. The sending address is written on the official site.
7. Urgent cases
   1. In cases such as the following, we tell you right away without waiting the number of days for telling you in advance (Article 19(2) and Article 26(3)). Or we stop something first and tell you after.
      • When we have to stop the Services because of an attack, a breakdown, a change in Innersloth's policies and so on
      • When a dangerous bug (one that harms the game or other people) is found
      • When a fake using our name (a fake download, a fake support contact, or something asking for money) is found
      • When information leaks, or may have leaked (Privacy Policy Article 13)
   2. Urgent notices go first in StarPocket Client's "Service status" area and on the official site, and on Discord too. Ones about the game or a host's PC are also told through the definitions file and on the PocketRoles screen in the game (Article 12).
   3. For a dangerous bug, after a fixed version is released, we may write a "required version" in the signed definitions file, so that new rooms cannot be made with the old version (Article 12(7), item 2).
   4. After we stop something, we put the reason and when we expect it back on the official site as soon as we can. The same is true when it stopped without notice because of a power cut or a breakdown (Article 19(1)).
   5. Urgent notices may come in Japanese first, with Chinese and English later (Article 33).
8. Telling our notices apart from fakes
   1. Notices from us have the same thing on the official site or inside the official StarPocket Client. When you see "a notice from StarPocket Games" anywhere else (social media, a DM, chat in the game, someone else's site, an email), please check that the same thing is on the official site.
   2. Our notices never ask for a password (we do not use passwords at all. Article 8(3)). They never ask for money (Article 7(4)). Sign-in verification codes are only sent when the user asked to sign in. If a verification code arrives when you did not ask for one, do not use it, and tell a contact in Article 34.

Article 26 (Changes to these terms)

1. We may change these terms in either of the following cases (Japanese Civil Code Article 548-4):
   1. the change is in the general interest of users; or
   2. the change does not go against the purpose of the Services, is needed, and the new content is reasonable.
2. These terms always show a version number and the date they take effect. Each time we change them, we add to "Change history" on the site the version, the date, a summary of the change and the differences from the previous version. Older versions can be read there too.
3. When we change them, we announce the following on the site and on Discord before the date the change takes effect. Once StarPocket Client's news (planned) exists, we announce it there too. The copies of these documents inside the Client are updated when you install a new version of the Client.
   • what changes
   • the date it takes effect

     For changes that are worse for users, we announce it at least 14 days before that date.

4. For important changes like the following, we ask you to press "Agree" again in StarPocket Client, the StarPocket Account and the support chat:
   • sending more information, or to more places
   • using information for more purposes
   • adding things users must not do, or kinds of limits
   • reducing users' rights, or changing the scope of liability in a way that is worse for users
   • changing the governing law or the courts
   • when the operator of the Services changes (Article 27)

     The change takes effect as described in items 1 and 3 even without a new agreement. The official StarPocket Client cannot be used any further without agreeing to the new version (choosing "Decline" closes it; you can still uninstall it). For the other Services too, people who do not agree may not be able to use the Services related to the change. In both cases, their GPL rights to the Software do not change. However, a change that sends more information, sends it to more places or uses it for more purposes applies only to people who agreed to it. However, when the running of the Services is handed over to someone else (Article 27), Article 27 applies, because under the law information going over with a hand-over of a business does not count as "giving it to others" (Act on the Protection of Personal Information, Article 27(5), item 2). Otherwise, for people who have not agreed, we do not start the new sending or the new use.

5. Corrections that do not change the meaning, such as typos, are only added to the change history.
6. After a change takes effect, the changed terms apply.
7. The correct text of these terms is only the text in these places:
   • the official site (starpocketgames.com)
   • the official GitHub repository
   • inside the official StarPocket Client (signed by us)

     Copies elsewhere may not be correct. A modified Client may not show the terms screen, but that does not change what these terms say.

Article 27 (Handing over and transferring rights)

"Transfer" means giving your position or your belongings to someone else. This article says that users cannot transfer their position or their account, that we may hand the running of the Services over to someone else, and what happens if something happens to the author.

1. Users cannot transfer, lend or pass on their position under these terms (the rights and the promises they have under these terms) or their account to anyone else (Article 8(4), item 4). It is the same for family and friends. When another person wants to use the Services, that person should agree themselves and make their own account.
2. We may hand the running of the Services over to another person or group. For example, when the author cannot keep running them, when a team or a group is formed, or when we ask someone else to run them.
   1. What is handed over is the Services (the site, support, accounts, the central lists, the Discord server, the room list and so on) and our position under these terms, the Play Rules and the Privacy Policy. The person who takes over keeps the three documents as they are at that time. When they change them after taking over, it is as in Article 26.
   2. The Software is published under the GPL, so whether or not there is a hand-over, anyone can use, study, modify and share it as before (Article 3).
   3. We only hand over to a person or a group who promises to keep these terms and the Privacy Policy.
3. When we hand over, we tell you at least 30 days before the day of the hand-over, in the ways in Article 25.
   • What the notice says: the name of the person taking over, the day of the hand-over, what is handed over (the Services and the information), and what you can do if you do not want to keep using them (paragraph 5)
   • A hand-over is treated as an important change under Article 26(4). We ask you to press "Agree" again in the official StarPocket Client, the StarPocket Account and the support chat.
4. Users' information that we hold (support requests, accounts, report zips, "One player's evidence" zips, the ban console's records and so on) goes to the person taking over, together with the Services.
   • The person who takes over may use that information only within the purposes written in the Privacy Policy as it was before the hand-over. To add purposes or places it is sent to, they ask for your agreement again, as in Article 26(4) and Privacy Policy Article 17(3).
   • Under the law, information going over with a hand-over of a business does not count as "giving it to others", and the person's consent is not needed (Act on the Protection of Personal Information, Article 27(5), item 2, and Article 18(2)). Even so, in these terms we promise to tell you in advance (paragraph 3) and to let you leave (paragraph 5).
   • Information that has not been deleted by the day of the hand-over goes over even if you did not agree as in paragraph 3. If you do not want it to go over, please delete it before the day of the hand-over, as in paragraph 5.
5. People who do not want to use the Services after the hand-over can stop using them before the day of the hand-over.
   1. An account can be deleted with "Delete account" (Article 8(6); planned) or, until then, by asking through Article 34. A deleted account, and the support requests linked to it, do not go to the person taking over.
   2. Support requests can be deleted with "Delete this request" on the receipt-number page (planned; until then, ask through Article 34). Records on a host's PC can be asked to be erased with the /cmd id code (Privacy Policy Article 12).
   3. Even if you could not ask before the day of the hand-over, you can make the requests in Privacy Policy Article 12 (to see or delete your information and so on) to the person who took over.
   4. Stopping does not change your GPL rights to the Software (Article 3).
6. Something may happen to the author, so that the Services cannot be kept running before anyone is chosen to take over or told about it. The Services are run by one individual alone (Article 6). If the author suddenly cannot act because of illness or an accident, the notice in Article 19 may not be possible. Even then, the following does not change.
   1. You can still play. PocketRoles and StarPocket Client are built to work with what they received before (or, when they have never received anything, with what is built into the Software), even when they cannot receive news or the definitions file. We never stop play because a connection is not possible (Article 12). Among Us itself belongs to Innersloth, so nothing about us changes it.
   2. Anyone can carry on the Software. The source is published on GitHub under GPL-3.0. Anyone can make a copy (a fork), fix it and share a new version (Article 3). People who carry it on must write clearly that it is not our official version (Article 9, item 3. Article 22). The definitions file and the updates that a person who carries it on distributes reach only that person's version. They do not reach our official version.
   3. The central lists stop in the state they were last distributed in. Only the author can sign the definitions file. So no new lines can be added, no lines can be removed after an appeal, and nothing can be put on the erase list.
      • Shared bans with an end date are lifted automatically when the date comes, as before (Play Rules, Article 9(4)).
      • Shared bans with no end date stay unlifted. This is a weak point of the way things are built now. How to fix it has not been decided.
      • Hosts can stop using the shared-ban list in their own settings (Play Rules, Article 1(2)).
   4. The information we hold is as follows.
      • While the server is running, it is deleted after the periods in Privacy Policy Article 5 (except what Article 5 marks "not deleted automatically yet" or "no time limit"). Accounts can also be deleted by their owners, as before.
      • When the server stops, the information that was left at that moment stays inside the server at the author's home. The contents are encrypted and cannot be read without that server's part (the TPM) (Privacy Policy Article 11(3)).
      • Who, in place of the author, would delete the information that is left, answer support requests and tell people about it has not been decided. When it is decided, we will fix this article and tell you.
   5. The address of the official site (the domain) stops working when the cost is no longer paid, and after that someone else may take the same address. That address is then not us. The official GitHub repository stays within GitHub's rules. The Discord server follows Discord's rules.

Article 28 (Keeping out antisocial forces)

1. While using the Services, users promise the following. We promise the same.
   1. That they are not an antisocial force (an organised crime group; a member of one (including a person who left less than 5 years ago); a company or group connected with one; a person or group that unfairly demands money while calling itself a social or political movement; or any other person or group close to these)
   2. That they do not give money to, or help, an antisocial force. And that they have no other connection with antisocial forces
2. Users will not do the following to us or our staff, either themselves or through someone else.
   1. Use violence. Demand something while hinting at violence
   2. Force demands that go beyond what the law provides (for example, threatening to demand money or special treatment that no rule provides for)
   3. Get in the way of work such as handling support requests, by threatening, or by rough words or behaviour
   4. Damage our good name, or get in the way of the running of the Services, by spreading lies or by force

      Abuse and threats towards other users are in Article 9, item 5.

3. When we find that a user has broken the promise in paragraph 1, or has done anything in paragraph 2, we can stop that user from using all or part of the Services right away, without telling them in advance. We may go straight to no end date, without following the steps in Article 13(2) (a warning → 7 days → 30 days).
   • How we tell them afterwards, and how to appeal when they think it is a mistake, are as in Article 13(3) and (5).
   • What this article stops is only the Services. It does not stop anyone using the GPL Software or playing Among Us (Article 13(4)).
4. Our liability for stopping the Services under paragraph 3, when a user had broken the promise in paragraph 1 or had done anything in paragraph 2, is as in Article 20(3). The same is true when we stopped them by mistake.

Article 29 (When part of these terms becomes invalid)

1. Even if some part of these terms becomes invalid (has no effect) under the law, or a court or the like decides that it "cannot be used", the rest stays in effect. Only the invalid part is taken out, and the rest is used.
   • When a part is invalid only under the law of a particular country or region, it is taken out only between us and users living in that country or region.
2. An invalid part is not simply taken out and dropped. It is read as the meaning closest to what that part was trying to decide, as far as the law allows. For example, when the way a period or a procedure is set no longer fits a law made later, it is read as the closest way of setting it that fits that law. However, in the case of paragraph 3 (when it became invalid because it was too unfair to users), this re-reading is not done.
3. When some part of these terms becomes invalid under a law that protects users, such as the Consumer Contract Act (a law that protects consumers. Its Articles 8 to 10 make promises that are too unfair to users invalid), we do the following.
   1. That part is treated as if it had never been written. The re-reading in paragraph 2 is not done. We do not keep an invalid part in a form that is unfair to users "right up to the line the law allows".
   2. Where that part has gone, the ordinary rules of law, such as the Civil Code, apply. For example, when some part of Article 20 (Warranty and liability) becomes invalid, our liability is as the rules of law provide.
   3. The rest (paragraph 1) is also read in a way that does not put users at a disadvantage.
   4. Protections that consumers have under the law of the country where a user lives are not taken away by this article (Article 32(3)).
4. When some part of these terms goes against the Software's licence (the GPL), the GPL wins. As in Article 3(2), that part does not apply to GPL rights. Here too, the rest of these terms stays in effect.
   • The rights to run, study, modify and share the Software are not narrowed by this article, or by any other article of these terms.

Article 30 (Promises that stay after you stop)

1. After a user stops using the Services (uninstalling StarPocket Client, deleting their account, leaving the Discord server, not agreeing to a change under Article 26, and so on), the following articles of these terms still apply to the time when they were using them. They are articles written to decide things about the time after stopping.
   1. Article 17 (What users send us) … how support requests, reports and evidence sent while using the Services are handled
   2. Article 20 (Warranty and liability) … how far our liability goes for things that happened while using the Services
   3. Article 21 (Trouble between users)
   4. Article 22 (Names, logos and rights in works)
   5. Article 24 (Personal information) … how records that are still left are handled, and what users can ask for (until the records are deleted)
   6. Article 32 (Governing law and courts)
   7. Other articles that decide how these terms are read, such as Articles 29, 31 and 33, and any part that, from what it says, naturally applies after stopping too
2. It is the same as paragraph 1 when we end all or part of the Services (Article 19). GPL rights to the Software have nothing to do with this article: they stay as the GPL says, whether a user stops using the Services or the Services end (Article 3 and Article 19(3)).
3. What stays under this article are promises, not records. Users' personal information and records are deleted after the periods set by Article 24 and the Privacy Policy, even with this article (for example, the information of a deleted account is deleted right away as in Article 8(6), and when we end the account service we delete it as in Article 19(4). The periods for other records are in the table in Privacy Policy Article 5). We do not use this article as a reason to keep records longer than the set period.

Article 31 (Which document comes first)

1. We provide the following 5 documents about the Services and the Software. Each of them decides different things.
   1. GPL-3.0-or-later: the licence (the permission to use) that decides the freedom to run, study, modify and share the Software (Article 3). It is not a document we wrote, and we cannot change its text ourselves.
   2. These terms: the agreement for using the Services (Article 1).
   3. The Play Rules: how to play in PocketRoles rooms, Aegis decisions, room restrictions, the conditions for shared bans, and the rules for appeals (Article 15).
   4. The Privacy Policy: how personal information is handled (Article 24).
   5. The error-code pages: an explanation of what a code (Article 2, item 8) means and what to do when it appears. They are not promises (paragraph 5).

      The rules for Among Us itself (Innersloth's Terms of Use and Mod Policy), and the licences of parts made by other people such as BepInEx, are not our documents (Article 3(6) and (7)). This article decides the order of the 5 documents above (which one to look at first). It does not change those.

2. The GPL is the strongest document. As far as the freedom of the Software goes, when any part of these terms, the Play Rules or the Privacy Policy could be read as narrowing a GPL right, look at the GPL. That part does not apply to GPL rights (Article 3(2)). You do not need to agree to the GPL to run the Software (Article 3(3)). Agreeing to these terms is needed only to use the official StarPocket Client that we sign and distribute, and the Services (Article 3(3) and Article 4). The GPL also does not allow us to add new limits to GPL rights (GPL section 10).
3. The relationship between these terms, the Play Rules and the Privacy Policy is as follows.
   1. For people who use the Services, the Play Rules are part of these terms (Article 15). That they are not a contract for people who only join a room (Article 15) is not changed by this article either.
   2. How personal information is handled is decided by the Privacy Policy (Article 24). Where these terms or the Play Rules mention how personal information is handled, they say the same thing as the Privacy Policy in a short form. When they can be read differently, look at the Privacy Policy. Changing these terms or the Play Rules does not, by itself, add information sent, places it is sent to, or purposes it is used for (Privacy Policy Article 17(3)).
4. When documents say different things, which document to look at is decided by what the matter is about.

• When it cannot be decided what the matter is about, look at these terms. When it still cannot be decided, we try to read it in a way that does not put users at a disadvantage.
• When there are different versions of the same document, look at the version that is in effect (Article 26(6)). Where the correct text is, is written in Article 26(7) (the same is in Play Rules, Article 12(5) and Privacy Policy Article 17(5)).

5. The error-code pages are an explanation, not a promise. The promises are written in these terms, the Play Rules and the Privacy Policy.
   • When a page and these documents say different things, look at the documents. We fix the page.
   • Once the meaning of a code is decided, we do not change it. Even when article numbers change, the code stays the same and we fix the "Article" column of the page (Play Rules, Article 12(3)).
   • The site's "FAQ", the README and the short texts shown in StarPocket Client and in the game are explanations in the same way. "The short version" at the start of these terms is also a summary of the main text. When they can be read differently from the main text, look at the main text.
   • When there is a mistake in an explanation, we fix it. We try to make sure that users who acted on an explanation are not put at a disadvantage by that mistake.
6. These terms, the Play Rules and the Privacy Policy are provided in Japanese, Chinese and English. The rule for when the meanings of the language versions differ is in Article 33 (the Japanese version is the correct one).
7. The following do not rewrite these terms, the Play Rules or the Privacy Policy. These terms can only be changed by the steps in Article 26. The Play Rules only by the steps in Play Rules, Article 12, and the Privacy Policy only by the steps in Privacy Policy Article 17. A change that is not in "Change history" on the site is not a change (Article 26(2)).
   1. Things we or staff say out loud. Things said in a Discord channel or DM, in room chat, in a stream, or on social media
   2. Answers from the support bot (Article 16(2). The bot can make mistakes, and it does not decide anything about users' records)
   3. The Aegis definitions file. What the definitions file changes is only the numbers within the range written in Play Rules, Article 12(2)
   4. Documents or notices somewhere else that use our name (Article 9, items 2 and 3)

      Notices on Discord and in StarPocket Client are places where changes are announced (Article 26(3)). The change itself is the text of the new version announced there. What staff answered in a support request or an appeal is how that person's case was handled, not a change to a document. When there is a mistake in that reply, we fix it and tell them.

8. This article is not there to say "we know nothing about anything not written here". When you ask about a part of a document that is hard to understand, or about something not written in a document, we explain at the support contact (Article 34).

Article 32 (Governing law and courts)

1. These terms are read under the laws of Japan.
2. Disputes about the Services are handled by the courts that have jurisdiction under the law. These terms do not limit disputes to the courts of Japan only.
3. This article does not take away any protection that the law of the country where you live gives to consumers.

Article 33 (Languages)

1. These terms are available in Japanese, Chinese and English. The three language versions are released on the same day with the same version number.
2. If the meanings differ, the Japanese version is the correct one. We try to make sure no user is disadvantaged by a translation difference.

Article 34 (Contact)

• Contacts
  • The contact page on the site (support.starpocketgames.com). To apply through the contributor recruitment, sign in to the support site (https://support.starpocketgames.com) and use "Join us" (Article 6(4))
  • Support chat (planned; bottom right of the support site; sign in with a StarPocket Account). It does not accept room restriction appeals and directs you to the dedicated appeal form
  • Email support@starpocketgames.com (shared-ban requests and report zips from hosts: support@starpocketgames.com)
  • A ticket on the Discord server "PocketRoles 役職部屋"

Change history