Who we are
boilerplate: “Our website address is: https://www.violet-mica.com.”
What personal data we collect and why we collect it
boilerplate: “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.”
boilerplate: “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.”
Currently (2018-05-21) there are no contact forms. If you would like to contact me, see the “Your contact information” section below (#contact-info).
boilerplate: “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.”
boilerplate: “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.”
boilerplate: “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.”
boilerplate: “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
boilerplate: “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.”
Who we share your data with
I don’t share your data. Remember that any comments you leave on this site are publicly visible.
How long we retain your data
boilerplate: “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.”
boilerplate: “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
boilerplate: “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
boilerplate: “Visitor comments may be checked through an automated spam detection service.” (as of 2018-05-21, they are not, but I may, if I begin to receive too many comments.)
Your contact information
If you want to send me an encrypted message, get my PGP key from my About page.
How we protect your data
Comments you leave are publicly visible to anyone who can visit the site (i.e. nearly anyone who has access to the internet). This website is not intended to hold private information, by its nature as a public blog. I use automatic https forwarding (if you try to visit my site at http, you will automatically be forwarded to https), which uses SSL, which means communications between this site and your computer are encrypted (although, remember that any information you leave or access on this site is public) (also note that if you initially try to visit my site with http instead of https, the url you enter after http:// is probably visible to eavesdroppers). I use a public certificate from Let’s Encrypt. My password is at least 15 random characters and also uses salt. There is no “admin” user or a default password on this site, despite attackers occasionally attempting to login as “admin”. My login credentials are protected against brute force attacks, which occasionally triggers due to attempted attacks.
What data breach procedures we have in place
Because the information on this website is public, the only private information is my password (which is not stored in plaintext on this site anyways) and un-published posts/pages (drafts). In the event of a breach, I will change my password, database password, and if affected, a new certificate.
What third parties we receive data from
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements