I'm working my way thru GDPR and my various blogs and websites. In the process, I'm having to learn more about how these free sites (Wordpress.com and Google) work.
One of the first things I did today was to search my email for GDPR and search again for action required. This was so that I could opt in to the various email lists to which I subscribe. At this point, I don't think I've received emails from all of my lists. Thus, I will be repeating this step in the days to come.
The second task on my "GDPR TO DO" list was to create a page for my privacy policy on my blogspot.com blogs (Heartland Genealogy: Developing Skills and Nemaha Tales) and then to actually write a policy. For the most part, I copied my privacy policy from my Wordpress blog and modified it for the Google aspects of a blogspot.com blog versus a Wordpress.com blog. I ran into a 'stumbling block' in that my new page wasn't showing on my blog -- even though I had published it. To get the page to be viewable, I had to modify my layout. I elected to add a 'Pages' widget below the header. Thru the widget, I was able to put a check mark by the Privacy page to create a link to it on the blog.
My next task was to continue working on my Google site, Heartland Genealogy. Previously, I had played around with converting my classic site to a 'new' Google site. However, I hadn't actually published the new site. I elected to go ahead and convert my site to the new site in hopes that the 'new' Google sites will incorporate whatever tools Google provides for GDPR. I also felt like the new site was more mobile friendly than the 'classic' site. However, I miss the ability to 'manage' the site!
I copied the text for my privacy page from my blog and pasted it into a new privacy page. I had to edit the cookie info since the site notice is currently missing.
I want to thank The Legal Genealogist for all of her posts on GDPR. Her blogpost, "The GDPR, You and Me" has been most helpful in getting thru these tasks!
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.