The Unity Editor collects anonymous data. Unity uses this information to make informed decisions on how to improve features in the Editor. the features of the Editor. Unity collects the analyticsAbbreviation of Unity Analytics See in Glossary using Google Analytics. The Unity Editor makes calls to a Uniform Resource Identifier (URI). The Uniform Resource Name (URN) part of the URI contains details that describe what Editor features or events users use.
Examples of analytics
The following are examples of some of the analytics that Unity collects:
Menu item use: If some menu items are used rarely or not at all, Unity could simplify the menus by moving or hiding those items.
Build times: By collecting data about how long builds take to compile, Unity can focus on optimizing the correct code.
Lightmap baking: The length of time it takes for lightmapsA pre-rendered texture that contains the effects of light sources on static objects in the scene. Lightmaps are overlaid on top of scene geometry to create the effect of lighting. More info See in Glossary to bake indicates how much effort Unity should spend on optimizing this area.
Disabling Editor Analytics
If you don’t want to send anonymous data to Unity then you can disable Editor Analytics. There are two ways to do this, which depend on the type of license you use:
If you use a Unity Pro license, go to Edit (MacOS: Unity) > Preferences > General and select Disable Editor Analytics (Pro only).