LolaJack Responsible Gaming: Breaks, Self-Exclusion, and Account Control
The most important distinction on this page is between ordinary account closure and a protective restriction. A break or self-exclusion is meant to limit access, while a normal closure request follows a different account path and does not replace a protective action.
The second key point is that the first route for a break or self-exclusion is support. A safer-play control can also appear in the account area shown as Profile, but the practical starting point is still the support route when access needs to be limited.
These tools are meant for control, not for routine account management. If the goal is to stop access rather than solve a payment, login, or bonus issue, this page is the correct starting point.
What Responsible Gaming Means at LolaJack
Responsible gaming here means using tools that limit access when gambling activity should pause or stop. The practical focus is account control, not promotion, and the system separates protective actions from ordinary support or closure requests.
This is why the page stays narrow by design. It is not meant to solve login, payout, or offer problems first, but to help the user act when continued access itself has become the concern.
Breaks and Self-Exclusion
A break and self-exclusion both begin through support, but they serve the same core purpose: stopping or restricting account access when gambling should not continue. The useful first move is to treat them as protective restrictions, not as ordinary account settings.
The account may also show a safer-play control inside the Profile area. That helps with orientation inside the account, but it does not change the core rule that support is the main route when a restriction has to begin.
- Decide whether the goal is a temporary stop or a stronger restriction.
- Use the support route to start the request.
- Check the account area for the safer-play control in Profile if it is available.
- Do not treat the request as a normal closure or a routine help message.
How This Differs From Account Closure
A protective restriction is not the same as closing an account in the ordinary way. A normal closure request should only be made when there is no balance and no pending withdrawal left on the account, while a break or self-exclusion is about restricting access itself.
This difference matters because users often combine two separate goals in one request. If the real need is to stop gambling access, a break or self-exclusion is the stronger and more accurate path than a standard closure request.
Underage Restrictions and Consequences
Underage registration is prohibited. This is a hard rule, not a flexible account preference, and it applies before any normal use of the account begins.
The consequence is also clearly stated. Winnings from underage players can be cancelled, which makes age eligibility one of the strictest account conditions on the site.
- Underage registration is not allowed.
- Underage play is treated as a rule breach, not as a recoverable account mistake.
- Winnings can be cancelled when the player is underage.
Where to Get Help
The first internal route is support, because breaks and self-exclusion requests begin there. When assistance is needed beyond the account itself, the page also names outside-help options that are meant for broader gambling-related support.
Those outside-help options include GamCare, Gamblers Anonymous, and Gambling Therapy. For direct account-side help, contact the support service so the request is handled through the correct channel.
What to Check Before Sending the Request
The message should match the real purpose of the action. If the goal is a break or self-exclusion, the request should say that clearly instead of mixing the issue with bonus, payment, or payout questions that belong somewhere else.
- State clearly whether the goal is a break or self-exclusion.
- Do not frame the request as a general payment or bonus complaint.
- Use the account route meant for protective restrictions, not routine closure language.
- Keep the request focused on access control.
What Happens During Restriction
The practical effect of a break or self-exclusion is reduced or stopped account access. That is the whole point of the tool, so the user should expect restriction, not ordinary account continuity with only minor adjustments.
This is also why the action should be chosen carefully and clearly. Once the request is made as a protective restriction, it should be treated as an account-control measure rather than a routine support step.
What This Page Does Not Cover
This page does not replace account verification, payout troubleshooting, or normal support for technical problems. If the issue is really about documents, delayed payouts, or sign-in rather than gambling control, the account should be checked through the related page first.
If access needs to be limited, stay on this path. If the problem is not protective but technical or transactional, continue through the relevant account page after account access is restored if needed.
FAQ
How does a break start?
A break starts through support. The account may also show a safer-play control in Profile, but the confirmed main route is still the support path.
Is self-exclusion different from ordinary account closure?
Yes. Self-exclusion is a protective restriction meant to stop or limit access, while an ordinary closure request follows a different account path and should only be made when there is no balance and no pending withdrawal.
Where can safer-play controls appear in the account?
A safer-play control can appear in the account area shown as Profile. That helps with orientation, but the support route remains the main starting point for a restriction request.
What happens if a player is underage?
Underage registration is prohibited, and winnings from underage players can be cancelled. This is one of the strictest account rules on the site.
Where can outside help be found?
The named outside-help options on the page are GamCare, Gamblers Anonymous, and Gambling Therapy. They sit alongside the internal support route, not instead of it.
Should a break request be mixed with payout or bonus issues?
No. A break or self-exclusion request should stay focused on access control. Bonus, payout, and technical account issues belong to their own support or account paths.