Community Guidelines — Bet Playground

Last updated: May 6, 2026

Bet Playground is a simulated sports betting app built around a single idea: that people who already gamble — or are tempted to — should have a risk-free place to scratch the itch. Our long-term goal is to help users gamble less in the real world, not more anywhere. These guidelines cover the social and shared parts of the App (usernames, team names, group bets, leaderboards, friends, support tickets) so that the community supports that goal rather than working against it.

By using the App you agree to follow these guidelines, in addition to our Privacy Policy and Terms of Service.


What we expect from you

What is not allowed

The following behaviours violate these guidelines and may result in a warning, suspension, or permanent ban depending on severity. The list isn't exhaustive — we'll act on anything that genuinely undermines the community even if we haven't explicitly named it here.

Identity and account abuse

Display strings (usernames, team names, group names, proposal titles)

All of these are passed through an automated profanity filter. The following are not allowed even when the filter doesn't catch them:

Real-money gambling crossover

Leaderboard, FBL, and group-bet integrity

Harassment and abuse

Platform abuse

Off-platform conduct

We generally don't police what users do off the platform, but if you use Bet Playground identifiers (your username, FBL team name, group name) to harass another Bet Playground user elsewhere — on social media, messaging apps, or in person — we will treat that the same as on-platform harassment.

Responsible-gambling controls — please use them

Even though there's no real money in the App, the patterns of gambling are real, and rehearsing those patterns can normalise them. The App ships with controls designed to help you stay in charge of your own behaviour:

Find them in Profile → Responsible Gambling. Setting them is a sign of strength, not weakness. We will never make it harder to tighten a limit.

If you are gambling for real money outside the App and finding it hard to stop, please contact one of these free, confidential services:

Security research

If you believe you've found a security vulnerability in the App, the website, or the backend, please report it via support and mark the ticket category "Security". Do not publicly disclose the vulnerability, do not access another user's data, and do not run automated tooling against the production backend. We aim to respond to security reports within 72 hours.

Enforcement

We use a graduated response based on severity, intent, and history.

SeverityTypical action
First-time minor (e.g. profane username caught after registration)Display string changed; user notified via support reply
Repeat or moderate (multi-accounting, leaderboard cheesing)Temporary suspension (7–30 days); offending content removed
Severe (harassment, threats, real-money-conversion scams, ban evasion)Permanent ban; data retained per the Privacy Policy retention rules

Bans are applied at the account level via our admin tooling and recorded in our append-only audit log. Banned accounts cannot log in. If you believe a ban was issued in error, you can appeal by emailing complaints@betplayground.co.uk with your account email.

We reserve the right to remove content, restrict access, or terminate accounts at our discretion when behaviour materially undermines the community or the harm-reduction mission of the product.

Reporting another user

If you see behaviour that violates these guidelines:

  1. Open the in-app Help & Support screen.
  2. File a ticket with category Report a user (or the closest equivalent).
  3. Include the offending username and a brief description.

We review reports within 48 hours. Reporters are not identified to the reported user.

Changes to these guidelines

We may revise these guidelines as the community grows or new behaviours emerge. Material changes will be flagged in the App's "What's New" screen on update. Continued use of the App after changes constitutes acceptance of the revised guidelines.

Contact