Like many other Web sites, campingandhikingideas.com makes use of log files. As a result, information inside the log files is used. This includes internet protocol ( IP ) addresses, type of browser, and Internet Service Provider ( ISP ). It also has a date/time stamp, referring/exit pages, and number of clicks. This information is used to analyze trends, administer the site, track user’s movement around the site, and gather demographic information. IP addresses and other such information are not linked to any information that is personally identifiable.
Cookies and Web Beacons
DoubleClick DART Cookie
campingandhikingideas.com has no access to cookies that third-party advertisers use. They also have no control over cookies that third-party advertisers use.
Third-party Privacy Policies
If you are not a subscriber, you can opt out of all communication with campingandhikingideas.com simply be leaving this page.
If you wish to disable cookies, you may do so through your individual browser options. You can find more detailed information about cookie management with specific web browsers at the browsers’ respective websites
Camping and Hiking Ideas is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to amazon.com. They are also participants in the SiteGround Affiliates Program, for the same reason. Google AdSense is also an affiliate, for the same reason.
Who we are
In this section you should note your site URL (https://www.campingandhikingideas.com), as well as the name of the company(none–just a blog), organization(none–just a motley crew of fellow campers with similar interests, not even a club), or individual(me!–Rowena Maxine “Max” Lundquist) behind it, and some accurate contact information(which is on the contact page, which you can access by clicking here).
The amount of information you may be required to show will vary depending on your local or national business regulations. You may, for example, be required to display a physical address, a registered address, or your company registration number(none of which is necessary because this isn’t a company–it’s just a blog. And not a very big one).
Goin’ with the Suggested text: Our website address is: https://www.campingandhikingideas.com.
What personal data we collect and why we collect it
In this section you should note what personal data you collect from users and site visitors. This may include personal data, such as name, email address, personal account preferences; transactional data, such as purchase information; and technical data, such as information about cookies. (As far as I know I don’t collect any data–but I’m going to check to make sure.)
You should also note any collection and retention of sensitive personal data, such as data concerning health.(Nope. How are you, by the way? jk)
In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.(Don’t collect it, don’t have a reason, not my business).
By default WordPress does not collect any personal data about visitors, and only collects the data shown on the User Profile screen from registered users. However some of your plugins may collect personal data. You should add the relevant information below.(Hmmm…may have to check Mailchimp.)
In this subsection you should note what information is captured through comments. We have noted the data which WordPress collects by default.(Word Press is so helpful here).
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.(This is the text they suggested, and I’m going with it!)
In this subsection you should note what information may be disclosed by users who can upload media files. All uploaded files are usually publicly accessible.(Since users can’t upload media files to my humble little blog this is a non-issue as well.)
Suggested text: 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.(But I’m keeping the suggested text in, just in case of future stuff. Hey, you never know.)
By default, WordPress does not include a contact form. If you use a contact form plugin, use this subsection to note what personal data is captured when someone submits a contact form, and how long you keep it. For example, you may note that you keep contact form submissions for a certain period for customer service purposes, but you do not use the information submitted through them for marketing purposes. (The contact form I use is for the use of anyone interested in subscribing to campingandhikingideas. We use the information (which is your name and email address only) to send monthly newsletters to each subscriber. No other use is made of the name and email address by me. I do not, nor will I ever, use the information for marketing purposes.)
In this subsection you should list the cookies your web site uses, including those set by your plugins, social media, and analytics. We have provided the cookies which WordPress installs by default. (Okey-dokey, I am again going with the suggested text:)
Suggested text: 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. (Thanks Word Press!)
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. (No accounts on this website so we’re good here.)
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.(Nor does anyone log in, other than me. But I’m keeping this in, you know, just in case. For the future. DRAMATIC MUSIC.)
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.(Are you talking to me?)
Embedded content from other websites
Suggested text: 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. (Staying with this suggested text, because it’s just what I wanted to say. If I had known how to say it.)
By default WordPress does not collect any analytics data. However, many web hosting accounts collect some anonymous analytics data. You may also have installed a WordPress plugin that provides analytics services. In that case, add information from that plugin here. (See paragraph above.)
Who we share your data with
By default WordPress does not share any personal data with anyone.
How long we retain your data
In this section you should explain how long you retain personal data collected or processed by the web site. While it is your responsibility to come up with the schedule of how long you keep each dataset for and why you keep it, that information does need to be listed here. For example, you may want to say that you keep contact form entries for six months, analytics records for a year, and customer purchase records for ten years.(Goin’ with the suggested text below. Oh, yeah.)
Suggested text: 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.(This I’m in with.)
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.(I’m keeping this in. For The Future. DRAMATIC MUSIC)
What rights you have over your data
In this section you should explain what rights your users have over their data and how they can invoke those rights.
Keeping the suggested text: 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.(I am down with that.)
Where we send your data
In this section you should list all transfers of your site data outside the European Union and describe the means by which that data is safeguarded to European data protection standards. This could include your web hosting, cloud storage, or other third party services.
European data protection law requires data about European residents which is transferred outside the European Union to be safeguarded to the same standards as if the data was in Europe. So in addition to listing where data goes, you should describe how you ensure that these standards are met either by yourself or by your third party providers, whether that is through an agreement such as Privacy Shield, model clauses in your contracts, or binding corporate rules.
Suggested text: Visitor comments may be checked through an automated spam detection service.(Keeping this suggested text. That’s about all that happens with the data, as far as I know.)
Your contact information
In this section you should provide a contact method for privacy-specific concerns. If you are required to have a Data Protection Officer, list their name and full contact details here as well.(Data Protection Officer! What am I, the camping and hiking police? Unless there actually are camping and hiking police. In which case I apologize for my irreverence.)
(It occurs to me that someone, some day, may have privacy-specific concerns. Just put something in the subject box regarding said concern–‘Privacy concern’ might be a good suggestion–and send it to email@example.com . I might be treating this with a touch of flippancy, but I always take my emails from you guys seriously. Not kidding.)
How we protect your data
In this section you should explain what measures you have taken to protect your users’ data. This could include technical measures such as encryption; security measures such as two factor authentication; and measures such as staff training in data protection. If you have carried out a Privacy Impact Assessment, you can mention it here too. (Since the data is only the users’ names and email addresses, and since they are only for subscription purposes at Mailchimp, your data is about as protected as it can get or needs to be.)
What data breach procedures we have in place
In this section you should explain what procedures you have in place to deal with data breaches, either potential or real, such as internal reporting systems, contact mechanisms, or bug bounties. (Panic, followed by frantic emails.)
What third parties we receive data from
What automated decision making and/or profiling we do with user data
If your web site provides a service which includes automated decision making – for example, allowing customers to apply for credit, or aggregating their data into an advertising profile – you must note that this is taking place, and include information about how that information is used, what decisions are made with that aggregated data, and what rights users have over decisions made without human intervention. (Nope.)
Industry regulatory disclosure requirements
If you are a member of a regulated industry, or if you are subject to additional privacy laws, you may be required to disclose that information here. (And, finally, Nope.)
So there you have it, folks. Hope it has been a little more readable for you than it was for me.