How to Secure Your Unity Services when Project Sharing

Symptoms:

• Individuals using a shared application might generate usage data associated with the original project or organization.
• Developers testing a shared project from version control and building it with the original code can also cause usage attribution to the original Project ID and Organization ID.

Cause:

When a developer who is not part of the original organization has a project shared with them, Unity will display the following warning:

However, if the project remains linked to Unity Services during the build process, the Project ID and Organization ID might be embedded within the executable. This can result in service usage being attributed to the original account, even when the project is being used or distributed by others.

Resolution:

To prevent unintended consumption of Unity Gaming Services (UGS) resources, it's crucial to unlink the Unity Editor from the project before sharing the repository.

Unlinking the Project:

1. Editor: Navigate to Editor > Project Settings > Services.
2. Unlink: Follow the prompts to unlink the project from the associated Unity account.

Alternative Approach :

1. ProjectSettings.asset: Locate the ProjectSettings.asset file in the project's root directory.
2. Open and Edit: Open ProjectSettings.asset in a text editor like Notepad++.
3. Remove IDs:
   1. Search for "cloudProjectID" and delete the content following the colon (":").
   2. 
   3. Optionally, remove the "organizationId" in a similar manner.
4. Save: Save the changes to ProjectSettings.asset.
5. Version Control: Upload the project to the desired version control system.

More information:

docs.unity.com