> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/itservices/user-interface/insight-tech-user-interface/accounts/regulatory-data.md).
# Responsible Gaming
The **Responsible Gaming** tab within the Accounts page provides operators with real-time insight into player wellbeing and betting risk, helping identify problematic betting behaviours and initiate timely interventions. Powered by Sportradar's BettorSense solution, this section supports compliance with local regulations and reinforces responsible gaming practices across all integrated operators.
### What it shows
This tab displays an overview of the bookmaker’s risk exposure related to responsible gaming, including:
* The overall **distribution of accounts** by Responsible Gaming (RG) Score category, from "No Risk" to "Very High Risk"
* An **executive summary** highlighting key takeaways, such as the share of accounts with critical scores and changes in high-risk segment size
* A **time series chart** showing use of self-exclusion and other RG tools
* A **ranked list of accounts** currently in High or Very High RG Risk segments, including:
* Current RG Score
* Weekly and monthly score changes
* Profit/Loss and stake in the last 30 days
* Last score update timestamp
All data shown is calculated and refreshed daily based on the latest player-level behaviours, betting history, and model evaluations.
### Use cases
This page is designed primarily for RG officers, compliance teams, and responsible gaming delegates within the operator organisation. Key use cases include:
* Quickly identifying Very High Risk players requiring immediate outreach or intervention
* Monitoring the effectiveness of RG tools and campaigns over time
* Triaging self-exclusion trends and comparing them to historic volumes
* Verifying player-level RG Score changes and aligning them with transaction history
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sportradar.com/itservices/user-interface/insight-tech-user-interface/accounts/regulatory-data.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
