Privacy Policy

Behold the fruits of what the GDPR hath wrought. Does my blog really need a privacy policy? If any data is collected by this blog I don’t know what it is nor do I know how to access it. I’m sure I can find out easy enough but I really don’t think it’s a productive use of my time.

Who we are.

I am me not we https://kevinbae.com.

What personal data we collect and why we collect it.

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also 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. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you 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.

Contact forms

I don’t want you to contact me. I’m fairly non-social (I used to say anti-social but I can’t now because it makes me sound like a psychopath or something).

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 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.

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.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Analytics

There are analytics that are tracked on this blog. However, I rarely access them because I don’t sell ads and it’s kind of pointless to see where the 8 people (on a good day) came from that read anything I post.

Who we share your data with

I don’t even share it with myself.

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.

Good luck with this request because if it’s not automatically generated by WordPress I don’t really have the time to figure out who you are and how to extract your freaking data.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

The only way you can contact me is through comments to this blog or maybe by messaging me on Instagram. I’m public there. Oh, yeah, Twitter too.

Additional information

None.

How we protect your data

I don’t do anything with data. I regularly update WordPress and whatever they do to protect data is what I do. Basically, if your saying something here consider it public.

What data breach procedures we have in place

I have none. I think anyone who wants to breach this site is a waste of human flesh and probably not all that bright.

What third parties we receive data from

I don’t like to deal with second parties let alone third parties. Ergo, I don’t know and don’t care.

What automated decision making and/or profiling we do with user data

Everything here is automated except for my posts. I would be great if those could be automated too that way I’d have a more consistent and up to date blog.

Industry regulatory disclosure requirements

None. I’m an industry of one.