配信

データの使用状況の確認(DUC)を実施する

更新日時: 2025/10/10

データの使用状況の確認(DUC)は、開発者データ使用ポリシーの対象となるPlatform SDK機能を使うすべてのアプリに課される要件です(表1)。DUCプロセスでは、APIアクセスが開発者データ使用ポリシー(DDUP)に準拠していることをチームの管理者が宣言することが必要になり、これによりユーザーのデータとプライバシーを保護するのに役立ちます。対象のPlatform SDK機能を使用しないアプリの場合、DUCは必要ありません。

アプリの中でプラットフォーム機能を使う場合は、開発者ダッシュボードのDUCツールを使って、次のことをしてください。

必要な機能を選択する

各機能にアクセスする理由、そうすることによってユーザーのエクスペリエンスがどのように向上するのかをドキュメントにまとめる

各機能から収集されるユーザーデータをどのように使用する予定かについてドキュメントにまとめる

プライバシーポリシーのコンプライアンスについてMetaによる審査を受ける

DDUPについて理解した上で従っていると宣言する

MetaアプリレビューチームがDUCを審査し、アプリがMetaのすべての要件に確実に準拠するようにします。DUCが合格すると、リクエストしたユーザーデータにアプリからアクセスできるようになります。不合格の場合、Metaアプリレビューチームからフィードバックが提供されます。それに基づいて、ユーザーのデータやプライバシーを保護する方法を修正したり改善したりすることができます。その後、再度DUCの審査を受けて合格を目指してください。

動画の視聴

DUCの申請時にサポートが必要な場合は、このデータの使用状況の確認の提出⁠に関する短い動画コースをご覧ください。

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

データの使用状況の確認は、どのように開発者が、アプリの運用に必要な機能へのアクセスを要求し、開発者データ使用ポリシーへの全般的な順守を保証しているか示すものです。データ保護評価は、禁止されているデータの使用、データの削除、サードパーティとのデータの共有、データセキュリティに関して、開発者がMetaのポリシーを遵守しているかどうかを評価します。

DUCを申請するタイミング

チームの管理者は、そのアプリの別のDUCの審査が行われている最中ではない限り、DUCを申請できます。DUCが現在審査中の場合、そのDUCが承認または却下されるまでは、変更事項を追加提出することができません。

最初のアプリ開発時に、DUCを完了して提出し、要求するプラットフォーム機能への暫定的なアクセスを取得します。アプリは、レビュー申請する準備が整うまでは、機能への自動アクセスを許可されます。

新しいプラットフォーム機能へのAPIアクセスを希望する場合や、すでにアクセスしている機能の使用状況を変更する場合は必ず、その変更または追加を正確に説明するためにDUCを修正し、再提出してください。

アプリを申請して審査を受ける前に、アプリによるプラットフォーム機能へのAPIアクセスの使用方法を正確かつ完全に説明するために、DUCを修正して提出します。アプリレビューの申請後、プラットフォーム機能への暫定的なアクセスは取り消され、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.