Who we are
Our website address is: https://galencharlton.com/blog. This blog is administered by Galen Charlton, who can be emailed at gmcharlt AT gmail DOT com.
What personal data we collect and why we collect it
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.
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.
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.
In particular, this blog includes a sidebar embedding my Twitter feed, and some posts includes tweets written either by myself or by other people.
This site uses a local instance of Piwik for website analytics under the control of Galen Charlton.
Who we share your data with
Posts and comments made to this blog are syndicated via RSS. Posts are also automatically shared to Twitter.
Other than the inherent publication of any comments you make if you choose to include personal data in your comments, or profile, personal data will never be intentionally shared with third parties.
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
To request an export of your personal data or to request that your personal data be removed, please contact Galen Charlton at gmcharlt AT gmail DOT com. Requests will be handled promptly when received, but please be aware that this is a personal blog and I cannot guarantee instantaneous response. I also reserve the right to delete all personal data associated with a requester if a request to erase subsets of it gets too fiddly to manage.
In the event of a server or WordPress compromise that comes to my attention and which has, or possibly has, resulted in the disclosure of personal data, the breach will be will announced via a post here. In addition, to the extent that email addresses are provided by commenters, notification of a breach will be emailed to them.