发布

完成数据使用情况检查 (DUC)

更新时间: 2025年10月10日

如果应用使用受开发者数据使用政策（表 1）约束的开放平台 SDK 功能，则必须完成数据使用情况检查 (DUC)。DUC 流程会要求您团队的管理员确认您的 API 访问情况符合开发者数据使用政策 (DDUP)，从而帮助保护用户的数据和隐私。不使用这些平台 SDK 功能的应用无需完成 DUC。

如果您想在应用中使用平台功能，请使用开发者面板中的 DUC 工具：

选择您需要的功能

记录您想要访问每项功能的原因，以及每项功能如何增强用户体验

记录您计划如何使用从每项功能中收集到的用户数据

让 Meta 审核您的隐私政策以确保合规

确认您理解并遵守 DDUP

Meta 应用审核团队会审核您的 DUC，确保您的应用符合我们所有的要求。如果您的 DUC 通过审核，您的应用将有权访问您请求的用户数据。如果审核未通过，Meta 应用审核团队将提供反馈，以便您能更正或改进保护用户数据和隐私的方式。然后，您可以再次尝试通过 DUC 审核。

观看视频

提交 DUC 时需要帮助？观看此处有关提交数据使用情况检查⁠的短视频课程。

Data Use Checkup (DUC) differs from Data Protection Assessment (DPA)

数据使用情况检查是指开发者如何请求访问他们操作应用所需的功能，以及证明他们遵守开发者数据使用政策。数据保护评估会评估开发者是否遵守 Meta 的政策，包括数据禁用、数据删除、与第三方共享数据和数据安全。

何时提交 DUC

只要应用没有其他 DUC 正在审核中，您团队的管理员就可以为此应用提交 DUC。如果您的 DUC 目前正在审核中，您必须等到该 DUC 获得批准或被拒，才能提交更多更改。

在应用开发初始阶段，请完成并提交 DUC，以获得您请求的平台功能的临时访问权限。您的应用会被授予自动访问这些功能的权限，直到您准备好将应用提交审核。

如果您想请求新平台功能的 API 访问权限，或您想更改已获得访问权限的功能的使用方式，请修改并重新提交 DUC，准确说明更改或补充情况。

将应用提交审核前，请修改并重新提交 DUC，确保其准确、充分地解释了您的应用将如何使用平台功能的 API 访问权限。请注意，当您将应用提交审核后，任何平台功能的临时访问权限将被撤销。直到您的 DUC 通过审核后，应用才能重新获得这些功能的访问权限。如需了解更多信息，请参阅等待 DUC 审核时如何开发应用。

At yearly intervals, resubmit your DUC to recertify your app’s continued compliance with Meta policies. If an app isn’t recertified yearly, it is removed from the Meta Horizon Store or Link PC-VR Store and loses access to platform features.

Note: Yearly DUC recertification is an additional submission outside of requests to update or change your current approved features. For example, if your approved application adds the In-App Purchases feature and it has been less than one year since your last certification, this is considered a new DUC submission to add this new platform feature.

Table 1. Platform features that require a DUC

Apps with...	Need a DUC for these Platform features...
Achievements	User ID, User Profile, Deep Linking
Add-ons	User ID, User Profile, In-App Purchase
Avatars	User ID, User Profile, Avatars
Blocked Users	Matchmaking
Challenges	User ID, User Profile, Challenges
Cloud storage	User ID, User Profile
Content sharing and live-streaming	User ID, User Profile
Custom items	User ID, User Profile
Destinations, rich presence, app deep linking	User ID, User Profile, Deep Linking
Displaying followers to invite	User ID, User Profile, Followers, Invites
Events	User ID, User Profile, Deep Linking
In-App content	User ID, User Profile
Leaderboards (followers)	User ID, User Profile, Followers
Leaderboards (global)	User ID, User Profile
Matchmaking	User ID, User Profile, Followers, Blocked Users, Invites
Multiplayer with Photon or Playfab	User ID, User Profile, Followers, Invites
Parties and party chat	User ID, User Profile, Parties
Peer-to-peer networking	User ID, User Profile
Rooms	User ID, User Profile, Invites, Followers
Subscriptions	Subscriptions
User age group	User ID, User Age Group
Users who invite others	User ID, User Profile, Invites, Deep Linking
Viewing usernames	User ID, User Profile
Voice Chat (VoIP)	User ID, User Profile

Submitting a DUC

A DUC may only be submitted by someone with an admin role on your team.

On the Developer Dashboard, go to the app’s card and then select Data Use Checkup.

Based on the needs of your app, select Add next to each platform feature your app needs to access.

For each feature you add:

From the Usage list, select all the ways in which your app uses the requested feature.

In the Description box, describe how your app uses the feature. Be as specific as possible. Select Choose files on your device to upload any screenshots that demonstrate this usage. For example, you can test your features using test users to demonstrate the usage. Remember:

User data must be used to run, support, and maintain a feature of your app to provide the experience requested by the user from whom the user data was collected.

User data can only be used to conduct analytics if the data has been aggregated, and/or anonymized.

User data can be shared only when you have the express written consent of the user.

Select the checkbox to certify your use of any data from the specific feature will comply with relevant policies.

Select Add to Request.

After adding all features your app needs, go to the bottom of the page to submit the request.

If this is the app’s first DUC, select Submit Requests (n).

If modifying an existing DUC, select Submit Recertification.

The content of your privacy policy is reviewed as part of your DUC submission. If you need to update your privacy policy URL, click the App Submission link to go to the app submissions page and update the URL.

Select the checkbox to certify that you are overall complying with Developer Data Use Policy.

Select Submit for Review.

How to develop apps while waiting for DUC approvals

Your app’s access to some or all Platform APIs is restricted while waiting for DUC approval. This might restrict your ability to develop and test other API functions. For example:

While your app is undergoing Store review, you lose the app’s provisional access to all platform APIs. You regain access to them only after your DUC is approved.

After an app is approved for Meta Horizon Store or Link PC-VR Store, you can only access the platform features that were listed in the app’s DUC. To gain API access to more platform features, you must recertify DUC and wait for approvals.

DUC approvals take time. If you are waiting for DUC approval, the only way to continue app development and testing is to use test user accounts. Test user accounts are exempt from DUC requirements. When you use test users to make API calls to platform features, the features return valid data even if your app has not been approved for those features.

Using test user accounts returns the real data associated with the test users. For example: test users have their own user IDs, their own avatars, and their own followers lists. For more information, see Test Users.

Duty to report data use incidents

If your app experiences a data incident that compromises the security of user data or systems that process user data, or if you received or processed user data in violation of our policies and terms, you must report it to Meta by way of the Incident Reporting Form⁠.

DUC feature reference

Following is a list of platform features that require user data. Each section describes the allowed usage of those features and user data, and links to more information. If your app does not use any of the platform features in this list, you do not need to complete the Data Use Checkup process.

Avatars

Grants an app access to Meta and Meta Avatars, a persistent identity across the Meta Quest ecosystem. With avatars, users can bring their own visual identities into your app. You must integrate the Meta or Meta Avatars SDK in order to enable this feature.

Allowed use:

Display the user’s avatar within your app.

Learn more:

Meta Avatars - Unity

Meta Avatars - Unreal

Meta Avatars - Native

Challenges

Grants an app access to challenges data.

Allowed Use:

Access user-created challenges in your app.

Learn more:

Challenges - Unity

Challenges - Unreal

Challenges - Native

Blocked users

Grants an app the ability to integrate blocking.

Allowed uses:

Allow users to block in your app.

Identify user blocks to honor them in your app.

Learn more:

Blocking - Unity

Blocking - Unreal

Blocking - Native

Deep linking

Grants an app access to view a user’s desired destination within an app.

Allowed use:

Allows the developer to enable deep linking in two separate applications: One single-player app and one multiplayer app. This enables the user to join a multiplayer session from a single player app.

Learn more:

Deep Linking - Unity

Deep Linking - Unreal

Deep Linking - Native

In-App purchase

Grants an app the ability to do in-app purchases.

Allowed use:

Provide in-app purchases to the user.

Learn more:

Add-Ons - Downloadable Content and In-App Purchases

Invites

Grants an app the ability to facilitate multiplayer scenarios.

Allowed uses:

Help users find their followers to join together in social VR experiences.

Learn more:

Rooms and Room Invites - Unity

Rooms and Room Invites - Unreal

Rooms and Room Invites - Native

Followers

Grants an app access to the current user’s followers who are also entitled to your app. Access to a user’s followers list is required to enable some other platform features.