Does IDFV count as a "device-level ID" for the App Privacy label?

In the updated description for App Privacy, it states this under "Data Collection":

Code Block
Identifiers
User ID - Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account-level ID that can be used to identify a particular user or account
Device ID - Such as the device’s advertising identifier, or other device-level ID


I understand that if I collect IDFA, it would qualify under this category. However, if my app collects IDFV by default but not IDFA, would would my app qualify under this category?

Thanks!
Depends... You don't mention how you'll use it, so...

Quoting the docs:

Using the AppTrackingTransparency Framework
To request permission to track the user and access the device’s advertising identifier, use the AppTrackingTransparency framework. You must also include a purpose string in the system prompt that explains why you’d like to track the user. Unless you receive permission from the user to enable tracking, the device’s advertising identifier value will be all zeros and you may not track them as described above.

The ID for Vendors (IDFV), may be used for analytics across apps from the same content provider. The IDFV may not be combined with other data to track a user across apps and websites owned by other companies unless you have been granted permission to track by the user.

For more information, see:
App Tracking Transparency
Human Interface Guidelines
AdSupport Framework


As well, when the guidelines use the phrase "Such as..", it typically indicates reviewer wiggle room for on-the-fly interpretation during review.

At that point, and since a quick search here didn't show any blanket rejections based on, the only way you'll know in your example may come down to running the review gauntlet - good luck.


Does IDFV count as a "device-level ID" for the App Privacy label?
 
 
Q