Partager via

XR-015: Managing Player Communication *

  • Article

Version 1.2, 4/01/2024

Titles must not transmit user data or allow communication over Xbox when the user's privacy settings do not allow it.

Titles meet this XR by retrieving data from Xbox services. If the title uses its own services, it must check the user's privacy permissions at the beginning of a session or when a new user joins the session. For user-initiated scenarios outside of sessions, titles meet this requirement by checking privacy prior to displaying the user's data and before performing the action. The following list of privacy settings is available for titles to check:

Permission name Description
CommunicateUsingText Check whether or not the user can send a message with text content to the target user.
CommunicateUsingVoice Check whether or not the user can communicate using voice with the target user.

During the gameplay session, titles which offer communication between Xbox and non-Xbox players must offer the ability to mute any non-Xbox players for the duration of the session.

More Information

Prior to allowing any activity to occur, titles must also check Xbox service for privileges, as stated in XR-045, Xbox network and Account Privileges.

Titles that support cross-network play and communication between Xbox and non Xbox players need to check communication permissions prior to allowing communication between those players. Please see XR-007: Cross-Network Play, Data Usage, and Companion App Interactions for more details and requirements for supporting cross-network play in titles.

Titles check communication settings for cross network players by using "CrossNetworkUser" which acts as a replacement for the XUID (see XDK). Based on Xbox privacy settings, these users will return a result of "allowed" only when the Xbox user's permissions are set to allow communication with all cross network players. Titles which support a cross network friends list can check communication between cross network friends by using "crossNetworkFriend" as a replacement for the XUID. Based on Xbox privacy settings, "CrossNetworkUser" will return a result of "allowed" only when the Xbox user's permissions are set to allow communication with all cross network players while "crossNetworkFriend" will return 'allowed' when the Xbox user's permissions are set to allow communication with all or cross network friends only.

Intent

Ensure that customers have appropriate and consistent control over their personal information.

015-01 User Communication

Configuration:

  • Create a set of profiles with "Others can communicate with voice, text or invites" to Everyone, Friends and Blocked.
  • For titles that support communication outside of Xbox, create a set of profiles with "You can communicate outside of Xbox with voice & text" to Allow, In-game friends and Blocked.

Note

Note: The difference between the "Allow" and "In-game friends" friends options are that "Allow" means you can talk to everyone cross network (including players you meet in random matchmaking). "In-game friends" are people you've explicitly chosen to play with by adding them to an in-game friends list.

Test Steps

  1. On Device 1, sign in to a profile that has been configured with the specific set of permissions per the Configuration.
  2. On Device 2, sign in to a profile that has no communication restrictions.
  3. On both devices, launch the title and attempt to communicate using text, voice (both via Kinect and via the headset), and video in every location supported and attempt to send multiplayer game invites.
  4. Repeat Steps 1-3 for all profiles from the Configuration step.

Expected Result

Titles must check the Xbox service for a user's permissions regarding privacy and online safety-related actions and must not transmit user data or allow communication over Xbox when the user's privacy & online safety settings do not allow it.

Pass Examples

  1. The title prevents the user from communicating via voice and text over Xbox when that specific method of communication is configured to be blocked.
  2. The title prevents the user from communicating via voice and text outside of Xbox when that specific method of communication is configured to be blocked.
  3. The title prevents the user from receiving multiplayer game invites on Xbox when that is blocked.

Fail Examples

  1. The user is able to communicate via voice and text over Xbox when that specific method of communication is configured to be blocked.
  2. The user is able to communicate via voice and text outside of Xbox when that specific method of communication is configured to be blocked.
  3. The title allows the user to receive multiplayer game invites on Xbox when that is blocked.

015-02 Muting Support

Test Steps

  1. As user A, mute user B.
  2. Have both users join an Xbox multiplayer session.
  3. Attempt to send voice communication from user B to user A.
  4. Ensure that user A is unable to receive any voice communication from user B.

Expected Result

User A must not be able to hear communication from user B.

Pass Examples

  1. Voice communication from the muted user cannot be heard by the user who initiated the mute.

Fail Examples

  1. Voice communication from the muted user can be heard by the user who initiated the mute.

015-03 Blocked Users

Test Steps

  1. As user A, block user B.
  2. Have both users join an Xbox multiplayer session.
  3. Attempt to send voice and written communication from user B to user A.
  4. Attempt to send a multiplayer game invite from user B to user A.
  5. Ensure that user A is unable to receive any communication or multiplayer game invites from user B.

Expected Result

User A must not be able to hear or see communication from user B. User A must not receive multiplayer game invites from User B.

Pass Examples

  1. Communication from the blocked user cannot be seen or heard by the user who initiated the block.
  2. Multiplayer game invitations from the blocked user are not received by the user who initiated the block.

Fail Examples

  1. Communication from the blocked user can be seen or heard by the user who initiated the block.
  2. Multiplayer game invitations from the blocked user are received by the user who initiated the block.