I was perma-banned and I don't know why.

#1 - Oct. 17, 2013, 6:17 p.m.
Blizzard Post

So I originally contacted the support service because I lost my serial code and I needed to change my password because I forgot it. After emailing back and forth for a while, I was asked to answer some questions about my account. Things like what race, and profession is your highest level character, what guild are you in, etc. I answered the questions and was emailed back thanking me for the information and saying that they were investigating me. The next email I got was to inform me that my account was “permanently closed for violations of the User Agreement.” and that my account is “not eligible for reactivation.” I’m interpreting this to mean I have been perma-banned. Although I don’t have any idea what I have done to deserve this, and there were no reasons cited other than violations of the User Agreement. No specific clause or rule or anything about the User Agreement that I am thought to have violated.

If anyone can help me with this problem, please do!
My ticket number is 131016-002119

#3 - Oct. 17, 2013, 6:57 p.m.
Blizzard Post

I’m assuming this is in relation to Ticket 131016-002119?

The account was hacked a year ago. It was reinstated, reclaimed, reinstated, and finally closed and refunded. Obviously, someone (bad) knows your credentials and is continuing to hack your account, even when the password is changed by an agent. This makes me wonder if your e-mail account is insecure. It would be good for you to check into that now. Consider setting up a new e-mail account and updating the ticket with that new address, so that whomever has/had access does not get access again. At some point, we’ll not be able to help.

I’m asking an agent to look at this tomorrow and I made some recommendations for whomever handles this. I am sure we can help you, but please give it some time.

#5 - Oct. 18, 2013, 5:17 p.m.
Blizzard Post

Westonski — I see that an agent responded to you yesterday and that you gave information needed to resolve this. I believe this will be settled soon. Please update on the forums on Monday if you still need help.

#6 - Oct. 21, 2013, 4:59 p.m.
Blizzard Post

It appears this was addressed Friday evening, so I’m figuring all is well now.