DragonPrime - LoGD Resource Community
Welcome Guest
  • Good morning, Guest.
    Please log in, or register.
  • May 24, 2018, 08:26:02 AM
Home Forums News Downloads Login Register Advanced Search
* * *
DragonPrime Menu
Resource Pages

Pages: 1 2 [3]   Go Down
Author Topic: GDPR Privacy in the EU (and those who accept EU players) - Issues with Lotgd  (Read 3007 times)
0 Members and 1 Guest are viewing this topic.
Offline Offline

Posts: 427

View Profile
« Reply #30 on: February 04, 2018, 05:30:55 PM »

I think I attached it in this thread "charrestore".
But I fixed minor things, mostly a search bug which did not show any chars saved if you leave the email address.

The very same actually, just minor modifications.

It works on my site well, I already restored a few.
And I like it  better w/o user email - you don't have to dally around "I can't tell you what email that char was made", because you simply don't know anymore Cheesy

So should I now use this one you just attached...or the one I was using?  The first one you posted?
Captain of the Guard
Offline Offline

Posts: 212

View Profile WWW
« Reply #31 on: March 26, 2018, 09:42:31 AM »

The last one Tongue

I'll make hopefully the last stuff on easter.

I updated my lotgd install to 16.04 with php7 + myslq 5.7.
Not a lot of fun though.

I had double-encoded utf8 strings in my db -_- now it's all fixed.
Captain of the Guard
Offline Offline

Posts: 212

View Profile WWW
« Reply #32 on: May 20, 2018, 09:38:25 AM »

Well, busy on the last couple of days.

I used the "creationaddon" to show my privacy policy statements, but it has one drawback: it *only* confirms them on creation(hence the name), and it has no way to do so afterwards. I had to expand that function, and also add a date as to when the privacy was accepted.
If somebody needs it, I will attach it.

here is the last version of the gdpr extension (=manages only the data export for the user and the 100% safe deletion and no restoral - if you push the mysql functions in you have to execute after you pushed the data in, but that can be set automatically if you need to).

Due to the fact that it's not install-and-done, but needs mysql adaptions, I apologize.
The mysql stuff has to be done in the db, which is something not being able to easily put into a module (no synctable for functions).

EDIT: Just as a summary, you need(!) a privacy statement accessible like an imprint on any page, it has to declare a lot of things. That's mandatory. Mine: https://shinobilegends.com/gdpr/SL%20Data%20Privacy%20Agreement%20and%20Transparency%20Report.pdf
« Last Edit: May 20, 2018, 09:48:23 AM by Nightborn » Logged
Pages: 1 2 [3]   Go Up
Jump to:  

DragonPrime Notices
Play LoGD on Dragonprime

Support Us
No funds raised yet this year
Your help is greatly appreciated!
Recent Topics
DragonPrime LoGD
Who's Online
17 Guests, 0 Users
Home Forums News Downloads Login Register Advanced Search