Distribute and grow
Distribute and grow

Developer essential data use policy

Updated: Feb 5, 2025
Meta automatically uses Essential Data across SDK and developer tools to make sure that Meta’s family of SDKs and developer tools work properly and to help maintain safety, security, and integrity.
Essential Data is information needed to ensure that an SDK and/or developer tool is working as expected and providing the service as outlined in Meta’s Supplemental Meta Platforms Technologies Terms of Service and Meta Platform Technologies SDK License. This includes using Essential Data to diagnose and fix any problems that developers may have in using Meta’s SDKs and tools, and employing Essential Data across Meta’s family of SDK and developer tools in order to ensure that developers can use these products together to create app experiences for Meta Quest.
Examples of the types of data that are automatically used for these purposes include:
Data required to provide our services, such as:
  • Data identifying the machine, signed user, or project identifiers to help identify usage of our tools or SDKs by a single entity.
  • Basic configuration of the system and environment where the SDK or tool is installed.
Data required for SDK operation, such as:
  • Data to ensure that our SDKs and tools function consistent with your settings.
  • Data about how often you use Meta SDKs and developer tools, to help us assess the reliability of the services, and to help document potential bugs or failures.
  • Operating system version number to ensure that the Meta SDKs are up to date.
  • Data documenting errors or crashes that occur to ensure that we fix them for normal functioning of Meta SDKs and developer tools.
  • Other data required to ensure that the Meta SDKs and developer tools function properly. For example, data on loading times for core features or services and data on failures encountered during loading or processing tasks.
Data used to understand and improve the operational security of our hardware and software, such as:
  • Data associated with potential software viruses and security intrusions.
  • Data used to respond proactively or reactively to any potential security or policy violations.
Playtesting and debugging data generated when you use a headset in “developer mode” to playtest in-development applications.
Did you find this page helpful?