‘Tis the season to tell people exactly what information we do and do not collect. Most sites are doing this because the European Union passed a law that requires them to do so. I’m not entirely convinced this site is obliged to do any such thing, but I do believe that making people aware of what information is gathered and used on the net is a Very Good Thing. As such, I present to you, to the very best of my knowledge, a list of information that is collected and used by Eviscerati.Org.
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.
Eviscerati.Org does not generally permit visitors, even visitors with registered accounts, to upload images. The only potential exception may be if users are permitted to submit their own portraits to customize their user accounts. In the event it is possible to 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.
Other services that might use your data
Eviscerati.Org uses some other services that may also be tracking you in some way:
You see the Patreon link over to the right? I am a creator on Patreon and use that image to link to my Patreon site. People who subscribe to my Patreon campaign can use their account to access Patreon-only account here.
If you are a Patreon subscriber using your account to access content here, we save certain functionally important Patreon information about you in this website. These include your Patreon user id, Patreon username, your first, last names and your vanity name. Additionally, the id of your campaign at Patreon and your campaign’s Patreon URL are also saved.
If you request that your data be deleted from this website, this data will also be deleted and Patreon functionality will not work. You will need to register on this website and log in to this website with Patreon again in order to re-populate this data.
I’ve had a PayPal link on the site for a very long time. Every time I take it down I get an email from someone asking me to put it back up because they’re more comfortable using that for donations than anything else. Other than the widget I put on the site, I don’t have any integration with PayPal, but I don’t know what the widget can do. If it can do anything.
…I’m sure it’s fine.
I wasn’t aware of this one until relatively recently.
I use two Google fonts, Noto Serif and PT Sans, on my website. According to their FAQ, “The Google Fonts API is designed to limit the collection, storage, and use of end-user data to what is needed to serve fonts efficiently.” Essentially (assuming I understand the explanation correctly) they’re keeping track of whether or not you’ve already made a request to download the font. The fonts are cached for a day, so if they determine you’ve already made a request for the font within the last 24 hours, they don’t bother doing it again.
They further clarify:
Use of Google Fonts is unauthenticated. No cookies are sent by website visitors to the Google Fonts API. Requests to the Google Fonts API are made to resource-specific domains, such as fonts.googleapis.com or fonts.gstatic.com, so that your requests for fonts are separate from and do not contain any credentials you send to google.com while using other Google services that are authenticated, such as Gmail.The Google Fonts FAQ
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
This site uses an anti-spam service called CleanTalk to try to separate legitimate users making comments on content and in the forums vs soulless spambots trying to advertise skin creams and bitcoin scams. Visitor comments are checked by this service.