Who I am
I am Mike Clargo, a private individual sharing information, observations and insights.
My website address is: https://clargo.com
What personal data I collect and why I collect it
Comments
When visitors leave comments on the site it collects 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 collect email addresses via contact forms for the purpose of sharing blog updates. People can unsubscribe from these at any time.
Cookies
If you leave a comment on this 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, I 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, the site 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 tracking your interaction with the embedded content if you have an account and are logged in to that website.
How long I retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so the site can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on this website, the site also stores 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 I hold about you, including any data you have provided to me. You can also request that I erase any personal data I hold about you. This does not include any data I am obliged to keep for administrative, legal, or security purposes.
Where I send your data
Visitor comments may be checked through an automated spam detection service. Emails provided to subscribe to the blog are submitted to mailchimp solely to provide email updates. Your data is not passed on to any other organisations and is only used for the purpose intended.
Your contact information
The only contact information I collect via this site is for the purpose of providing blog updates, and these can be unsubscribed at any time.
Additional information
How I protect your data
Your data is restricted to your email address, and is protected through Bluehost’s and Mailchimp’s security mechanisms.
What data breach procedures I have in place
If I become aware of a security breach in respect of the email addresses I hold, my procedure is to:
Inform those affected within 3 working days, identify the cause of the breach, and put in place solutions to repair the breach and prevent future breaches with 14 days.