Private-Room Safety Checklist for Hosts

A before, during, and after checklist for hosts of Game Junction private rooms: code sharing, admission, voice, names, reporting, and closing the room.

Our general safety article explains the principles behind private rooms. This page turns them into a checklist you can follow every time you host. It is organised into three stages: before the session, during it, and after it. Each item is short on purpose, because a checklist you actually use beats a long policy you only intend to read.

Game Junction rooms are invitation-only by design: there are no public lobbies and no matchmaking with strangers. Your habits as host are what make that design work in practice. If you only remember one thing, remember this: the room code is the key, so share it deliberately and close the room when you are finished.

Before the session

Decide who is invited and make a short list. Knowing exactly who you expect makes it obvious when an unexpected name appears. If children are playing, tell their parents or guardians which game and which time, and share the room code with them rather than posting it in a bigger group.

Choose the game and check that it supports online rooms. Decide in advance whether optional voice features will be used. For mixed-age sessions with children, a good default is voice off and an existing video call on, where you can see everyone's face. Turn voice on only when you have discussed it with the adults in the group.

Create the room shortly before the start time rather than hours ahead. A room that sits open for a long time with a code in circulation is easier to misuse than one that opens at the moment everyone arrives. Enable host admission if the game offers it and younger players are expected.

Prepare the message you will send. State the game name, the code, the start time, and a reminder not to forward the code to others. A clear message reduces the chance that the code is shared more widely than you intended.

Sharing the code

Send the code only through private channels you already trust: a family group, a direct message, or by saying it on a call. Avoid public stories, open communities, and large groups with members you do not know. Do not take a screenshot of the lobby that includes the code and post it online, because the code is visible in the picture.

If you are unsure who may see a message, assume more people than you expect. Group chats are forwarded, screenshots are shared, and members can leave and rejoin. When in doubt, create a fresh code for the next game.

During the session

Check the player list before pressing start and again whenever someone joins. Match every name against your invitation list. If you see a name you do not recognise, ask in your private chat who it is. If nobody can confirm, remove the player if the game allows, or close the room and create a new one with a different code. There is no need to investigate while the game is paused for everyone else; a new room takes seconds.

Encourage simple display names. First names or family nicknames are enough. Remind everyone not to type phone numbers, addresses, school names, or passwords anywhere in the game. If a child is about to type something personal, a calm reminder is better than a lecture.

Keep an eye on voice if it is enabled. As host you can usually control whether voice is on for the room. If the conversation becomes uncomfortable, mute or turn off voice for everybody and continue with the game alone. Make it clear that this is a normal host decision and not a punishment.

Use in-app reporting where available if someone behaves badly. Take note of any Support ID shown on screen, leave the room, and contact support. Do not engage with a stranger or try to negotiate; leaving is the safest and most effective response.

Supporting children

Sit nearby or stay on a video call whenever young children play. Tell them they can leave a room at any time and that nobody will be upset with them. Agree on a family sentence, such as I want to stop, which signals that a game should end immediately.

Explain that real people are on the other side of the screen, even though the game feels like a toy. Kindness rules apply in rooms just as at home: no teasing about losses, no mocking of names, no pressure to continue when someone is upset. Hosts model this by praising effort and gracefully handling defeats.

After the session

Close the room. That one action means the code can no longer be used, even if someone saved it. If you plan to play again, create a new room next time instead of reusing the old code. Treat codes as disposable.

Ask players how it went. A short question such as did everything feel okay gives children and shy adults a chance to mention anything that bothered them. If someone raises a concern, listen first and write down the details, including the game, the time, and the display name involved.

If something needs to be reported, email support with the game name, whether you were on web or Android, the time, and any Support ID. For privacy or legal grievances, use the Grievance Officer address on our Contact page. Clear details help us respond quickly and fairly.

The one-minute version

Invite only people you know. Share the code privately. Check the player list. Keep names simple. Decide on voice before you start. Leave and report if something feels wrong. Close the room when you finish. Print those seven lines and stick them near your screen, and you will cover nearly everything that matters for a safe, relaxed game night.

Related guides

Play on Game Junction