Apple is introducing a privacy policy for including privacy manifest files in new and updated applications targeted for iOS, iPadOS, macOS, tvOS, and visionOS platforms on the App Store.
The privacy manifest file (PrivacyInfo.xcprivacy
) lists the types of data your Unity applications, or any third-party SDKs, packages, and plug-insA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary collect, and the reasons for using certain Required Reason API categories.
Important: If the use of the Required Reasons APIs by you or third-party SDKs isn’t declared in the privacy manifest, your application might be rejected by the App Store. The applications targeted for macOS platforms do not require to declare the use of the Required Reasons APIs. For macOS applications, the privacy manifest requirement only applies if you plan to publish your application on the App Store. For more information, visit Apple’s documentation on Required Reasons APIs.
You must review your native code, C# code, and data collection and tracking practices to understand if Apple’s privacy manifest policy applies to you. Follow these guidelines to decide if you need to include a privacy manifest file in your product:
If your application includes multiple third-party SDKs, packages, and plug-ins, then these third-party components (if applicable) must provision their own privacy manifest files separately. Note: It’s your responsibility however, to make sure that the owners of these third-party components include privacy manifest files. Unity isn’t responsible for any third-party privacy manifest, and their data collection and tracking practices.
If your application includes Unity framework implementations of the C# .Net framework APIs that call certain APIs listed in the Apple’s Required Reasons API categories, then you must assess your product for the API usage. For assessing what constitutes as part of data collection and tracking practices, refer to Apple’s documentation on privacy manifest files. Note: It’s your responsibility to assess your use of each of these APIs and declare the applicable reasons for using them.
Depending on whether you’re using Unity to develop an application or providing your SDKs, packages, and plug-ins to use with Unity applications, the requirement for providing a privacy manifest file might differ.
Note: The above guidelines are provided for your convenience. It’s important that you review Apple’s documentation on privacy manifest files before creating a privacy manifest for your project.
If you’re developing an application using Unity, consider the following steps:
If you meet one or both of the conditions from step 1, create a privacy manifest file in Xcode and save it in the Assets/Plugins folder of your project.
In the privacy manifest file, declare the approved reasons for using the Required Reason APIs or C# .Net framework APIs, as applicable.
Important: If you don’t declare the reasons for the use of APIs, your application might be rejected by the App Store. The applications targeted for macOS platforms do not require to declare the use of the Required Reasons APIs.
Verify if your native application code collects any type of data categorized by Apple and declare those data types in the privacy manifest file as applicable. Any third-party SDKs, packages, and plug-ins used in your application must include their own separate manifest files to declare data collection and the use of any Required Reasons APIs with approved reasons.
Notes:
It’s your responsibility to check the accuracy of the privacy manifest within the Unity framework and if any third-party components included in your Unity project require any declarations in you privacy manifest. It’s recommended that you search these third-party components for any references to a privacy manifest declaration.
If you’re a plug-in, package, or SDK owner, and you provide a service or package to be included within a Unity project as a .framework, follow these steps:
If your product isn’t used as a .framework within a Unity project, then consider delivering it as a .framework. If you’re unable to do so, then follow these steps:
The following table provides a list of C# .Net APIs that call the Required Reasons API category named File timestamp API. If your application, SDK, package, or plug-in code calls any of the APIs from this list, declare the reasons for their use in your privacy manifest file following the guidelines specified in Apple’s documentation on Required Reasons API.
Note: The following list is verified only for Unity versions 2021.3 LTS and later.
Unity Engine calls the Required Reasons APIs from the following categories and declares these categories with the listed reasons for their use.
Category | Reason | Description |
---|---|---|
File timestamp APIs | 0A2A.1 | Used by C# timestamp APIs |
File timestamp APIs | C617.1 | Used to check files |
User defaults APIs | CA92.1 | Used for PlayerPrefs API |
System boot time APIs | 35F9.1 | Used to calculate time between various events |
Disk space APIs | E174.1 | Used to check disk space for AssetBundles |
Note: Starting with Unity Editor versions 2021.3.35f1, 2022.3.18f1, and 2023.2.7f1, Unity Engine automatically includes these reasons in the privacy manifest file. If you’re using an older Unity Editor version, you must always declare these reasons in the privacy manifest file of your project.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.