become GDRP compliant - wordpress plugin

[bill]

.

all sites need to be GDRP compliant

check out this wordpress plugin:

https://wpgdprfix.in/ <--------------

[vblogger]

Perfect solution, thanks bill

[Nakedtruth]

How important is this to be compliant with, being honest here, but my blogs are not that big or in the spotlight.

[bill]

How important is this to be compliant with, being honest here, but my blogs are not that big or in the spotlight.

do your blogs now, or will they ever in the future, accept traffic from europe?

here are articles from Forbes and other sites:


https://www.technologyemploymentlaw.com ... o-prepare/


https://www.forbes.com/sites/forbestech ... -business/


https://www.forbes.com/sites/forbestech ... 82ff9b52c8


https://www.compliancejunction.com/gdpr ... companies/

[HeidiHoe]

God I hate high pressure sales pitches! They usually have the opposite effect on me. Makes me NOT want to buy. There's a new privacy function in the latest WP update that was just released. I haven't dug into it yet but perhaps it takes care of everything this plugin does?

[bill]

disclaimer -- i am cot a lawyer nor do i play one on tv

but if you do not have a membership site and if tou are not selling anything on your site and if you are not collecting any nanes or emails, then standard disclaimers may be ok if you only have affiliate banners and juicy ads or etc

[HeidiHoe]

disclaimer -- i am cot a lawyer nor do i play one on tv

but if you do not have a membership site and if tou are not selling anything on your site and if you are not collecting any nanes or emails, then standard disclaimers may be ok if you only have affiliate banners and juicy ads or etc

Yeah, but you should probably still link a privacy policy stating your practices. All my sites except for one fall in that category. You might what to review external services that you use for stats, communication, etc. For example, if you're using webalizer it'll collect IPs. Also, if you have a blog that allows account creation, posting comments, etc you're most likely collecting personal info. Some plugins and external services will give you the option not to collect IPs which are considered to be personal data under the GDRP. Also a good idea to have a contact link or info on your privacy policy regardless of what site you have if it's commercial. I hate to be anal, but I guess it's in my nature

I just moved all my sites in the last few days and now my legal docs linked in the footers aren't pulling in. I keep 'em all in one folder and use includes for easy maintenance. Under my new setup looks like I need to resort to frames across domains. Been procrastinating but that's on my plate today I guess. That and reviewing all the legalese and updating privacy policy....

[bill]

I just moved all my sites in the last few days and now my legal docs linked in the footers aren't pulling in. I keep 'em all in one folder and use includes for easy maintenance.

are you saying that if you have
www.WebsiteA.com
www.WebsiteB.com
www.WebsiteC.com

you have a common Privacy Policy for all sites on 1 page, saying something like

---------------------------------------------------------------------------------------
this Privacy Policy and Terms of Service applies to the following websites
www.WebsiteA.com
www.WebsiteB.com
www.WebsitesC.com

the rest of the privacy policy webpage continues
blah blah blah blah blah privacy pollicy description blah blah bloah

==================================================================




and then you link each site to that Privacy notice, that says it applies to that site, but none of the sites list their terms on their site, but link to a common site's terms ?

or does each website need to have its own privacy policy and terms and conditions pages located with its own domain, and not designated and shared with other websites owned by a person?

[HeidiHoe]

I don't specify the sites name. I just call it site. I have one policy that applies to all. I do that with privacy, tos, 2257, dmca. I keep the docs in one folder and use php includes to include the docs in the sites. One site required a different 2257 so I have a separate one for it in same folder that I'll include instead. Content producers are listed in a separate file inside same folder and php included in 2257 file. Anything site specific such as contact link for specific site can be added in the page below the include. I can still use my setup but will need to use frames to place the whole mess on the individual sites. One page to link in a frame using parameters to call specific docs and styles should do the trick.
I try to avoid duplication and disorganization thus reducing work load and potential errors. Hope this makes sense, it's really quite simple. If you're using wordpress there's several plugins out there that'll let you do php code in content and widgets.

[bill]

Thank You

you are extremely smart

[HeidiHoe]

Thank You

you are extremely smart

Just good at avoiding unnecessary work

[HeidiHoe]

Holy crap... just got done with my privacy policy. I think all my sites are compliant now, if not then fuck it! I damn near set my brain on fire. This damn GDRP is one ate up MoFo!

[bill]

The data subject’s right of access which means 1) the right to know whether data concerning him or her are being processed and 2) if so, access it with loads of additional stipulations (GDPR Article 15).

The data subject’s right to rectification. When personal data are inaccurate, then controllers need to correct them indeed (GDPR Article 16).

The previously mentioned right to erasure or right to be forgotten with additional stipulations, among others if personal data has been made public (GDPR Article 17).

The data subject right to restriction of processing. Simply said, the right of the consumer or whatever you call the natural person under the scope of the GDPR, to limit the processing of his/her personal data with, once more, several rules and exceptions of course (GDPR Article 18).

The right to be informed. Here we stretch it a bit. In general, the GDPR asks controllers and so on to inform data subjects on several matters. Providing clear and correct information is a key duty in many regards. Simply said, the GDPR wants consumers to know because if you don’t know you can’t decide, right? However, here we rather mean GDPR Article 19 which, again simply put, means that personal data that have undergone an action as a consequence of one of the other, just mentioned data subject rights, the controller must inform recipients who got these data, where feasible. And then the data subject also has a right, even if not strictly called a right, to ask “who are all these recipients who got to see my data”. So, right or not? It explains why we said 7.5 but it really is a right. More about information duties further below.

The right to data portability. This is again one of those data subject rights that are in the infographic and which we covered more in depth previously. With the right to data portability we’re in GDPR Article 20, so, keeping in mind that data subject rights are covered in Articles 5 until 22 that means two more to go.

GDPR Article 21 is all about the data subject’s right to object. That does indeed mean what it says: data subjects can say they don’t want the personal data processing to be done or going on. This might seem a bit overlapping with other data subject rights but it isn’t. Of course in practice the data subject can, again within specific conditions, exercise the right to object and the right to be forgotten. Especially direct marketers and people who do profiling should pay a lot of attention to the right to object as it’s a lot about them and certainly profiling with automated means (though not solely).

The data subject right not not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her. This is pretty much a copy and paste of GDPR Article 22, Paragraph 1, which ends the ‘official’ list of data subject rights.

[HeidiHoe]

Okay...

The biggest impact as I see it is that we need to be able to provide website users with a copy of their personal data we have on file and we need to have the ability to erase said data. The latest WP release and some plugin updates have that ability built in placing it right at your fingertips. Including request confirmation emails

If a user reaches out with a request it doesn't matter who they contact at the organization. If they contact joe blow at xyz.com who cleans the toilets then xyz.com must comply. We can not charge for requests unless they are excessively repetitious and we must scrub their personal data unless it conflicts with laws.

What makes it such a pain in the ass to write the policy is that it has to be so detailed and in non-legalese. I use pretty much the same external services on all sites, some have more than others. I included them all (I think... hope so). I don't have any automated approval systems in place so I don't have to worry about that. I just wrote one standard policy leaving out the specific site info. Then I included the policy on all my sites (in the fashion I mentioned earlier) placing the specific site info above it on the page and called it done.

Here is what it looks like on a few different sites:
https://fuckingcamz.com/privacy/
https://carnalsex.com/privacy/
https://sexysexxx.com/privacy/

[bill]

Very nice - thank you for sharing your hard work and efforts