The Obligatory GDPR Page.
Who am I?
I’m just this Floridian turned Oregonian who writes a personal blog when the need hits.
The web address here? http://lick.blue/ (SSL coming when I find a host that’ll let me use Let’s Encrypt.)
What info do I collect here, and why?
When folks leave a comment (or several), we collect the data shown in the comments form, along with the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it.
If you upload images to the website, then you as the user should avoid uploading images with embedded location data (EXIF GPS) included.
Visitors to the website can download and extract any location data from images on the website, and the site owner does not have the responsibility to go remove your EXIF data for you.
Several image editors exist to remove this type of data prior to uploading.
Contact forms and Cookies
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will attempt to set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day. Haha, no. This is my blog. You don’t get to publish articles here.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.).
Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
The author and site owner recommends the use of browser add-ons, such as Privacy Badger if this offends you, as it happens everywhere, not just on tiny blogs.
The author and site owner use WordPress’ Jetpack Site Stats. This provides very limited information to the site owner, particularly what’s being read, and that’s about that.
Who we share your data with
/dev/null after I’ve taken a peek. That’s it. Off to the great bucket of bits in the sky.bin.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
An email to me (authorname plus-sign blog at-sign domain dot tld), if you absolutely must.
How we protect your data
Your comments and preferred name are publicly posted (unless moderated for spam). This is public, because you have deemed it so. Nothing to protect.
There. Here’s your GDPR prattle. Your princess is now in another castle.