"Rollbit will not be held liable for any loss or damages which occured as a result of circumventing our self-exclusion program"
Pretty obvious that's exactly what happened here...
I don't really know what OP expects of us bringing this issue here.
Somewhere between testing how sympathetic Bitcointalk regulars are and expressing genuine distress due to a very specific type of mental disorder (no offense if that's the case OP... we all have problems).
So please tell me what "circumventing" I made. Did I create a new account? Did I change my device and network? Did I provide someone else data to KYC? NO<
I even contacted them before getting in my main account. Then they blocked the withdraw (how convenient).
I'm glad you asked about this, as it's probably the second cause of your issue here. This is what I know from other issue with other casino and I am not sure if Rollbit also applies this mechanism, but I think it's safe to assume they are.
Usually, under normal circumstances, self-exclusion will prevent the problematic gambler from playing on the platform again by "blacklisting" the credentials --be it your IP or your ID. But when someone have another account, where one got self-excluded and the other is not, they're kinda crash the self-exclusion system, because the automated system read that the IP --and other parameter they utilize-- should and should not be on the blacklist at the same time.
This should explain your queries on the post above the one I quoted; yes, their system is automated, and you happen to accidentally bypassed that security measure by having two accounts. This is possibly what they refer as circumventing the self-exclusion. Because like previously said, in order for self-exclusion to kick in, it needs participation of both parties. When you did not mention the other account, you're kinda half-heartedly self-exclude yourself, and you circumvented the exclusion you put yourself in by still trying to access with that account.