Whenever I try to see profile EU / US I get redirected to Battle.net
Its been like this for days. Is this intended?
1 Like
Yes.
1 Like
It’s not just the EU armoury site that’s disabled.
On the US forums, there’s a stickied post in General Discussion.
As we don’t have an EU Community Manager, we don’t get a sticky…
As a workaround, if you visit www.d3planner.com you can use its import facility to view the gear / build on your heroes. If you want other people to view your hero, you can use the Save option to generate a link specific to your hero, and link that to people.
2 Likes
Could it be due to RGPD legal requirements not to show personal information?
There’s zero personal information on the armoury site. Only the person logged in sees their account name at the top right, not other people viewing your profile.
1 Like
Maybe it’s to do with the new forum format?
Another thing is that on the old forum page there was a direct link to the Diablo III front page.
The new forums went live around four months ago.
The armoury site’s been down for around six weeks.
So, it’s unlikely.
1 Like
Hey @Meteorblade, personal information is not exactly obvious sometime. As soon as your battle tag is unique and uniquely associated with you as an individual, the fact that there are information about your battle tag becomes records of your person.
So if using some battle.net sites publicly (not being myself logged in therefore not belonging to the community), I can retrace the hours played, the fact that you played an insane amount of hours, this could maybe be taken as personal information records which falls into the GDPR (RGPD in French).
I am saying this because they also recently asked devs (such as myself) using the D3 Community API to declare the way they would use the data grabbed from the API about people’s profiles. This is clearly because of personal information handling.
And since the API and the battle net profiles are very linked (I reckon their technical architecture implies that the battle net profile pages available on the web are driven by the API). They ask devs to comply with new personal information sharing policies and might need to deal with the same issue on the public pages.
I am guessing that you will need to be authenticated to view the profiles pages in the future.