Data ownership and responsibilities
Learn about your responsibilities for managing your users' data
읽는 시간 2분최근 업데이트: 21일 전
The Developer Data framework is based on a simple principle: it’s your data. Unity collects and processes Developer Data solely on your behalf—and only within the scope you’ve configured.
That means you are responsible for using the framework correctly, for collecting valid consent from your end users, and for complying with all applicable privacy regulations. Unity supports you in these responsibilities by providing a streamlined set of controls and tools that are designed to be as set-and-forget as possible without minimizing their importance.
Because you own the data, you are responsible for:
- Correctly setting collection and usage preferences
- Implementing valid user consent and/or opt-out mechanisms (if needed)
- Complying with laws and regulations relevant to your region and audience
Developer Data collection begins whenever diagnostic data collection is enabled in the Unity Editor. From that point on, Unity will collect and use Developer Data based on what is essential for the products and services you use and in accordance with your settings in the Dashboard. This ensures Unity acts as conservatively as possible while providing a functional customer experience.
Going further, Unity wants you to be able to benefit from your Developer Data wherever you find it useful. This includes products and services where Unity is obligated to act as a Data Controller. Such situations may require more formal and explicit data transfers and deserve an additional layer of consideration. The Developer Data framework makes this easy by adding another layer of specific controls designed to help you make smart and relevant decisions based on your own priorities and needs.
For example, if you were to choose to allow Unity Ads User Acquisition to access your Developer Data to improve campaign performance or for Unity Ads Monetization to increase player LTV, you may ask yourself if you are collecting sufficient consent from your end users. The framework is designed to help you make these types of decisions intentionally and in context.
When you use the Unity Dashboard to configure your Developer Data settings, you’ll notice certain settings may trigger extra confirmations and/or require you to take additional explicit actions. This happens contextually whenever a change from Unity as a data processor to Unity as a data controller is required—and even in cases where such a scenario might apply. When you use the Developer Data framework, there shouldn’t be surprises.
The Developer Data framework is designed to give you confidence that your data follows your instructions wherever and however you choose to use it.