keepcalculator

06 Numbers and Powers

Make AI-Generated Games Private or Share Them Safely

Card No. 06·84320 · Updated · Standard formula, shown below

Making an AI-generated game private can limit who can open or edit it; sharing it safely lets selected people test or play without exposing more than necessary. The controls vary by game-creation platform, so check its visibility, link-sharing, collaboration, and publishing settings before inviting anyone.

What You’ll Need

  • Access to the account and project that contains the game.
  • The platform’s sharing or publishing controls; exact labels differ between services.
  • A clear decision about whether you want a private draft, specific testers, or a public game.
  • If you plan to share a link, a separate browser profile or private window for checking what recipients can see.

Step-by-Step

  1. Save a separate copy before changing access. Use the platform’s duplicate, copy, or version-history feature if available. Keep one copy as your working draft and make a shareable copy for testing. This gives you a way back if a publishing or permission change has unexpected effects. If the platform does not support copies, save the project’s source files or record its current settings.
  2. Remove information that should not be shared. Inspect the game, its title, description, menus, credits, and any attached files. Remove personal details, private messages, account names, or confidential material. Check that prompts, notes, and development comments are not visible to players. Do not put passwords, access tokens, private keys, or other credentials in game code or files; a game’s client-side content may be accessible to people who can play or download it.
  3. Set the project to private or restricted. Open the project’s settings or dashboard and look for labels such as Visibility, Access, Publish, or Sharing. Choose the most restrictive option that still lets you work, such as private, draft, or only me. Save the change, then return to the project list and confirm that the setting persisted. A private project may still be visible to platform staff or collaborators with access, so read the service’s explanation of its options.
  4. Distinguish project access from player access. Some platforms have separate settings for editing the project and playing a published build. Keep editing permission limited to people who need to change the game. If you want testers to play but not edit, look for a play-only, viewer, or tester role, or share a published preview instead of the editable project. Do not assume that a hidden or unlisted game is private: anyone with its link may be able to open it.
  5. Invite specific people when you need a limited audience. Add collaborators through the platform’s own invitation controls and use the lowest permission level that suits the task. Check each recipient’s account and role before sending the invitation. Avoid granting owner or administrator access for ordinary playtesting. If invitations can be forwarded or access is inherited through a team or workspace, check those settings too.
  6. Prepare a safe playtest build. Publish a preview or test build if the platform supports one, rather than exposing the working project. Remove unfinished content you do not want testers to see, and check that the build does not contain private files or credentials. If the game connects to external services, check what data it sends and whether its permissions are appropriate for a test. Use sample data rather than real personal information.
  7. Choose link settings deliberately. If you share a link, check whether it grants access to anyone who has it, whether it can be forwarded, and whether it expires. Prefer a restricted invitation when the audience must stay limited. If an unlisted link is the only option, treat it as shareable rather than secret: send it only to intended recipients and avoid posting it in public chats, profiles, or forums.
  8. Test what a recipient can see. Copy the play or project link and open it in a private browser window where you are not signed in, or ask a trusted person to check. Confirm that the intended audience can play and that people without permission cannot view or edit restricted content. A signed-in owner’s view may differ from a recipient’s view, so do not rely only on your own account.
  9. Share with a short, clear message. Tell recipients whether the link is for playing, testing, or editing, and mention any limits, such as not forwarding it. Avoid including private account details in the message. If feedback is needed, say how to report problems without asking testers to send sensitive information.
  10. Review access after the test or release. Remove collaborators who no longer need access, revoke old invitations, and disable or replace links if the platform permits it. Check the project’s visibility again after publishing or editing; some services use different settings for drafts and published builds. Keep the private working copy restricted.

Common Mistakes

  • Assuming “unlisted” means private. Unlisted usually means the project is not easy to find, not that a link requires permission.
  • Sharing the editable project instead of a playable build. This can give testers access to source material or editing controls they do not need.
  • Using a link without checking its scope. A link may grant access to anyone who receives it, even if you intended it for one person.
  • Forgetting attached files and project notes. Assets, comments, source files, and descriptions can reveal information that is absent from the game itself.
  • Leaving access in place indefinitely. Old collaborator permissions and test links can remain active after a project is finished.

Tips

  • Use separate draft, test, and public builds when the platform makes that practical.
  • Give each person only the access needed for their role; playing, commenting, and editing are different permissions.
  • Keep a simple list of who has access and when temporary access should be reviewed.
  • Check platform help for the precise meaning of private, restricted, unlisted, and public. Labels are not consistent across services.
  • Before public release, check the game and its store or project page for personal details, unwanted files, and links that expose private work.

Troubleshooting

The game is still visible after you set it to private: Confirm that you changed the published build’s visibility, not just the draft project’s. Save, refresh the page, and check from a signed-out browser. A platform may take time to update or may keep an earlier published version available; look for separate release or distribution controls.

A recipient cannot open the game: Check that you sent the play link rather than an editing or owner link, that the recipient is signed into the invited account if required, and that the invitation has not expired. Confirm that the project is published or previewable and that the recipient’s role allows access.

Someone can edit when they should only play: Remove their project-editing permission and share a play-only build or link instead. Review workspace-level access as well as project-level permissions, since a team role may grant broader access.

A shared link has spread farther than intended: Turn off link access or change the project back to restricted visibility, then revoke and replace the link if possible. Remove unintended collaborators and test the new settings from a signed-out browser. If the platform cannot revoke a link, contact its support or create a new restricted build.

You cannot find a private setting: Check the project dashboard, publish dialog, and account or workspace sharing settings. If the service offers only unlisted links, do not treat them as confidential; share only content that is appropriate for link-based access.

Frequently Asked Questions

Does “unlisted” mean only invited people can play?
No. It commonly means the game is not listed publicly, while anyone with the link may still be able to open it. Check the platform’s access description.

Can I let people play without letting them edit?
Often, yes. Share a published or preview build, or assign a viewer, tester, or play-only role if available. Test the link with a non-owner account.

Will making a project private remove copies already downloaded?
Usually not. Privacy controls generally limit future access through the platform; they cannot reliably erase files or screenshots someone already saved.

Should I share the project link or the game link?
Share the game or play link with testers who only need to play. Share an editable project link only with people who need development access.

How do I stop access after a playtest?
Remove testers or collaborators, disable or replace shared links if possible, and review both project and workspace permissions. Then verify the result from another account or a signed-out browser.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →