Responsible Gaming - Self-Exclusion requests

Responsible Gaming - Self-Exclusion requests

If you feel you need a break from the game, please contact us by submitting a ticket to Player Support or contacting support@clubwptgold.com. Players should use the term "Self-Exclusion" in the subject line of the ticket or email. 

A member of our support team will process this request as a priority. 

Self-Exclusion requests are permanent and cannot be reversed. Players will only be eligible to redeem Sweeps Coins that are considered redeemable and have met the play through requirements.
    • Related Articles

    • Account Verification - What is Source of Wealth (SOW)?

      As we take a risk based approach to AML/TF policies, it may be necessary to request Source of Wealth documentation. This information assists us in determining a player's source of funds, which is sometimes necessary to prevent money laundering and ...
    • Closing your account

      Are you looking to just take a break? You can exclude yourself for a set period of time by contacting us at support@clubwptgold.com with "Self-Exclude" in the subject line, and then in the body of the email please advise us as to how long of a break ...
    • Alternative Method of Entry FAQ

      For full rules and instructions please reference our Terms of Service which can be found here. General Questions Q: What is the Alternative Method of Entry for Sweeps Coins? A: The AMOE is a way for you to receive free Sweeps Coins by mailing in a ...
    • Location Issues

      We understand how frustrating technical issues can be, especially when you're eager to enjoy our new Multi-Tabling feature. Our team is here to guide you through resolving this geolocation challenge. Why Is This Happening? This issue is likely due to ...
    • Location Issues

      We understand how frustrating technical issues can be, especially when you're eager to enjoy our new Multi-Tabling feature. Our team is here to guide you through resolving this geolocation challenge. Why Is This Happening? This issue is likely due to ...