Who we are
Our website address is: https://www.fatalencounters.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.
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.
We tried to use Google Analytics, but couldn’t figure it out. We’ve recently tried Monster Insights and JetPack, but we’re not having much luck with them, either. Any or all of them may work at some point. They may even work now, but we don’t know how to access them.
Who we share your data with
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. So, if you’re interested in the name and email address you provided on our subscription popup, please send name, credit card number, and secret PIN on back of your card with the email address and name you provided when you filled out the little subscription popup.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Your contact information
Please feel free to contact the site host, D. Brian Burghart at firstname.lastname@example.org
To be honest, Fatal Encounters doesn’t look at any of your personal data. All the above is from WordPress partners.
How we protect your data
Other than having a secure website and not sharing data, we don’t have any way of protecting data you share publicly on the internet.
What data breach procedures we have in place
Everything is publicly available on this website. We don’t store any credit card or personal information on the site. From one point of view, everything here is breached.
What third parties we receive data from
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements
I don’t even know what this means.