Where player accounts are supported, the system maintains and backs up for each account the player ID and name, player data including the verification method, the date of agreement to the terms and privacy policy, account details and balance, the attendant text field, previous accounts and deactivation reasons, registration date and method (remote or on-site), last login, exclusion and limitation information (request time, description and reason, type, start and end dates) and financial transaction information (type, time, unique ID, amount, balance before and after, fees, handling user or device, status, method, deposit authorisation number and location).
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.