Responsible play, written as a self-assessment card

The responsible-play route is a self-assessment card. It does not run a clinical screening, does not diagnose a condition and does not provide treatment. The route restates the standard tools list, points to the in-app responsible-play panel, and links to state help-line 1800-XXX-XXXX as a placeholder shape.

The route exists because the responsible-play posture is one of the most important readings on the editorial reference. Visitors who land on myteam11app.com before deciding to enter through the verified first-party path need to know what tools are available inside the operator product and what help-line references exist at the state level.

The route does not invent phone numbers. State help-line references use the placeholder shape 1800-XXX-XXXX; the in-app responsible-play panel exposes the current list. Visitors who need a specific help-line number should rely on the in-app panel, not on a third-party reading.

The standard responsible-play tools list is exposed inside the in-app responsible-play panel. The list below restates the five tools; the in-app panel is the authoritative reading of the current limits and the standing windows.

• Deposit limit. Caps the amount the visitor can fund the wallet with over a standing window. The visitor can set a daily, weekly or monthly cap. Changes are typically processed instantly.
• Loss limit. Caps the amount the visitor can lose over a standing window. The visitor can set a daily, weekly or monthly cap. Changes are typically processed instantly.
• Session limit. Caps the duration of a single session. The visitor can set a session cap; the in-app product enforces the cap by signing the visitor out at the standing window.
• Time-out. Suspends the account for a standing window. The visitor can pick a time-out from a list of standing windows. The request is typically processed instantly.
• Self-exclusion. Closes the account for a longer standing window. The visitor can pick a self-exclusion window from a list of standing windows. The request is typically processed within 24 hours.

Each tool can be set or changed inside the in-app responsible-play panel. The visitor is in charge of the choice; the editorial reference does not make the choice for the visitor.

Self-assessment is a personal exercise. The five questions below are a starting point, not a clinical screening. Visitors who answer yes to several of these questions should consider opening the in-app responsible-play panel and setting a tool.

1. Am I playing to escape stress or boredom? Playing to escape stress or boredom is a warning sign. The visitor should consider a time-out.
2. Am I chasing losses? Chasing losses is a warning sign. The visitor should consider a loss limit.
3. Am I spending more than I can afford? Spending more than the visitor can afford is a warning sign. The visitor should consider a deposit limit.
4. Am I playing longer than I planned? Playing longer than planned is a warning sign. The visitor should consider a session limit.
5. Have I tried to stop and failed? Trying to stop and failing is a warning sign. The visitor should consider a self-exclusion and a state help-line call.

The five questions are not exhaustive. The visitor who needs a specific clinical reading should consult a qualified professional in their jurisdiction.

The route references state help-line 1800-XXX-XXXX as a placeholder shape. The placeholder exists because state help-line numbers are operator-controlled fields that change between releases and across jurisdictions. The visitor should not rely on a specific number from a third-party surface; the in-app responsible-play panel exposes the current list.

The visitor who needs a specific help-line number should rely on the in-app panel, the relevant state government website, or a qualified professional in their jurisdiction. The editorial reference does not invent phone numbers because a fabricated number is worse than no number at all.

If a visitor cannot find a help-line number through the in-app panel, the visitor should open the in-app help and use the responsible-play escalation channel. The escalation channel records the case and continues into the operator's responsible-play team.

This route does not run a clinical screening. It does not diagnose a condition. It does not provide treatment. It does not expose a specific state help-line number. It does not run the in-app responsible-play panel. It does not process self-exclusion requests.

If a visitor lands on this route expecting any of those surfaces, the route forwards them to the correct entry: clinical screening to a qualified professional, treatment to a qualified professional, help-line numbers to the in-app responsible-play panel, and self-exclusion requests to the in-app panel.

The boundaries exist because the editorial reference is not a clinic and is not the operator. myteam11app.com is an editorial product reference; the route restates the framework the operator references, in measured language, without inventing facts.

The editorial reference carries three routes that overlap with the responsible-play reading. The first is /is-legal/, which restates the regulatory framework the operator references. The second is /delete-account/, which describes the account-deletion path. The third is /privacy/, which restates the data-handling envelope.

Self-exclusion is not the same as account deletion. Self-exclusion closes the account for a standing window and the visitor can return after the window expires. Account deletion is permanent; the visitor's data is removed within the standing window of the deletion request.

The visitor who needs to delete the account should read /delete-account/ before opening the in-app account-deletion request. The standing reading is dated 17 August 2026.