This document was last modified on November 4, 2018.
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.
Any information entered may be stored in our database. We do not share this information with anyone. It’s typically deleted after a short period of time (less than 6 months).
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.
Toaster Squad doesn’t collect any analytics. That said we use a few plugins for our site that might. The following are all our current plugins: WP Fastest Cache, Wordfence, Jetpack, All in One SEO, and Woocommerce.
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.
Who we share your data with
Since we use WordPress for some sites, they could potentially collect data. YouTube videos are also embedded in a number of posts. Twitch is also linked to occasionally. Here are their privacy policies: WordPress, YouTube, Twitch.
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.
*Check additional information below.
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 (and all) personal data we hold about you.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Our contact information
Our website is open source. If you’re worried about your privacy for any reason feel free to check out all the code of our site here.
User accounts that are over 2 years old, and have shown no activity will receive an email asking if they would like to keep their account. After 3 years of no activity, we send a final warning email. If there is no further activity after 6 months we delete the account, and all information connected to the account.
How we protect your data
All data is sent through a secure SSL connection and hosted on a protected (encrypted) server.
What data breach procedures we have in place
In case of a breach all affected parties will be notified and the method used will be rectified.