Who we are
Our website address is: http://www.accidentalwizardry.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 (added by Carolyn: AND YOUR IMMORTAL SOUL!!!! actually I’m experimenting with Amazon’s DNS logging capabilities but I might get bored)
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. (Also added by Carolyn: WHY DO WE NEED GRAVATAR?!?!?! TO DO LIST: Figure out if we can ditch Gravatar. )
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. (Carolyn here again: Check the instructions on your smartphones to see how to disable embedded location data. AND WHY ARE YOU UPLOADING PICTURES TO OUR SITE ANYWAY????)
Visitors to the website can download and extract any location data from images on the website.
(From Carolyn: Um nope. We don’t have any of those yet. But hey, we might. And OMFG am I glad people are starting to get serious about privacy settings.)
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies.
(Carolyn: Nope. We don’t want it.)
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.
(OMG are we doing that? Don’t do that. Another thing for the task list….)
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.
(Carolyn’s task list now has–To avoid XSS attacks on our beloved customers, if any, get rid of embedded content.)
Who we share your data with
(GOD. Just. No.)
How long we retain your data
(WE don’t, but you can be sure as hell that every Facebook and Twitter cookie you still have because you forgot to clear your @*%&* CACHE before you got here is going to collect every byte of it.)
If you leave a comment, the comment and its metadata are retained indefinitely. (So don’t.) 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. Nope.), we also store the personal information they provide in their user profile. (So don’t.) 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. (AND YOUR SOUL.)
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.
(WHAT A PAIN. SERIOUSLY. DON’T LEAVE ANYTHING ON THIS SITE)
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
(From Carolyn–Should we start a mailing list? Hmmm. Until then, no.)
How we protect your data
(BY NOT COLLECTING IT IN THE FIRST PLACE)
What data breach procedures we have in place
(None. Carolyn is experimenting with every feature that AWS makes available, and will bound to screw up something. Caveat Visitor. )
What third parties we receive data from
(nah. Too much trouble.)
What automated decision making and/or profiling we do with user data
(If you see any of this going on please let us know so we can stomp it out.)
Industry regulatory disclosure requirements
(We regulate any staff member who fails to be industrious with the application of a cattle prod.)