Privacy Policy

Who we are

Go to the page who we are to know more.

What personal data we collect and why

See below the data we collect and why we collect them.

Comments and Contact Form

When visitors leave comments on the site, we collect the data shown in the comment form, in addition to the IP address and data from the visitor’s browser, to assist in the detection of spam. All comments are stored in our databases. The person’s name, site disclosure and comment appear respectively in the post in which the comment was left. The contact information of the comments, such as e-mails, is used only for contact by the author of the blog. No email is passed on to third-party companies. The same goes for contacts made by the contact form of the blog. In this case, the message appears only in the email inbox of the blog author. No information from the contact page is disclosed on the site. We reserve the right to delete emails with offences to the author of the blog or other readers who commented on specific posts. Spam and comments with advertising-only character also run the risk of not being released. A string anonymized created from your email (also called a hash) can be sent to Gravatar to verify that you use the service. Gravatar’s privacy Policy is available here: https://automattic.com/privacy/. After your comment is approved, the photo of your profile is publicly visible with your comment.

Media

If you send images to the site, avoid sending those that contain embedded location data (EXIF GPS). Visitors can download these images from the site and extract their location data.

Cookies

By leaving a comment on the site, you can choose to save your name, email and site in the cookies. This is aimed at your comfort, so you don’t have to fill in your data again when you make another comment. These cookies last a year. If you have an account and access this site, a temporary cookie is created to determine whether your browser accepts cookies. It does not contain any personal data and will be dropped when you close your browser. When you access your account on the site, we also create multiple cookies to save your account data and your screen display choices. Login cookies are kept for two days and screen options cookies for a year. If you select “Remember Me,” Your access will be kept for two weeks. If you disconnect from your account, the login cookies will be removed. If you edit or publish an article, an additional cookie is saved in your browser. This cookie does not include any personal data and simply indicates the post ID pertaining to the article you just edited. It expires after one day.

Embedded media from other sites

Articles on this site may include embedded content such as videos, images, articles, etc. Embedded content from other sites behave in exactly the same way as if the visitor was visiting the other site. These sites can collect data about you, use cookies, incorporate additional third-party tracking, and monitor your interaction with this embedded content, including your interaction with embedded content if you have an account and are connected to the site.

Newsletter and RSS Feed

When registering to receive the newsletter of the blog, we are sent the contact email to have this automatically receive in your Inbox the emails of the updates of the blog first hand. No email from the newsletter register is passed on to third parties. Only are used by the blog for that end character. It is worth remembering that only receives the newsletter who confirms the receipt by filling the code against Spam in the dialog box that appears after the registration. RSS Feed readers have their privacy guaranteed. Neither the author of the blog has access to information of who are the RSS subscribers of the blog.

Financial data

We have our backpacking travel consultancy to two incorporated into the blog, which can exchange financial data with our consumers. That will be at the discretion of the consumer. The information received varies according to the service contracted with us. If you hire some service with backpacking to two, everything will be done to minimize this exchange of data, as a generation of billets so that the consumer can make the payment itself. We may have access to the form of payment made, but not to the details of it. Already in the case of lodging reservations through the Booking.com, we have no access to your personal and financial data. Some anonymous information shared with us, is: date you made the reservation, reserved accommodation and device used to make the reservation (cell phone, tablet or computer).

Analysis

On this site, we use Google Analytics to analyze data access to the site. Their privacy policy can be found here. For the purposes of statistics, anonymous accesses are collected by the JetPack plug-in.

With whom we share your data

While we do not share your personal data with anyone else, other people may have access to your personal information as your name and email through comments made on our blog. Comments Plug-ins, the backpacking team to two or any other plug-in where they need to add their information may be in the hands of third parties. Obviously, when this data is accessed the only goal is to complete some process by which it was collected. In general, statistics on the demographics of our readers can be shared with our partners through our media kit, such as gender, age, location and time of stay on our blog. All this information is shared anonymously. Google collects your access trends in order to be used in AdSense. This type of data is collected directly by them. This is not done by anyone involved in backpacking to two.

How long do we keep your data

If you leave a comment, the comment and its metadata are preserved indefinitely. We do this so that it is possible to automatically recognize and approve any subsequent comments rather than retain it for moderation. For users who register on our site (if any), we also keep the personal information they provide in your user profile. All users can view, edit, or delete your personal information at any time (only you cannot change your username). Site administrators can also view and edit this information.

What are your rights to your data

If you have an account on this site or if you have left comments, you can request an exported file of the personal data that we keep on you, including any data that you have provided to us. You can also request that we remove any personal data that we keep on you. This does not include any data that we are required to maintain for administrative, legal or security purposes.

Where we send your data

Visitor reviews can be marked by an automatic spam detection service.

How we protect your data

We hire security packages at Hostgator, where we host our blog. We change our passwords frequently, thus minimizing possible attempts at malicious access. Our domain is also safe (https://), adding more security to anyone who adds their data to our blog. Your data is very important, so we have a few steps to contribute to this protection, such as two-step verification for all accounts with Administrator privilege and encrypted navigation throughout the site.

What are our data violation procedures

In case of data breach, all users registered on the site will be prompted immediately and prompted to update their passwords.

of which third parties we receive data

We haven’t received any third-party data.

European Union general Data Protection Regulation

For more information, please access this site. Our blog is hosted in Brazil. Even without sharing data with third parties, we will follow the guidelines of RGPD whenever necessary.

Plugin: Smush

Note: Smush does not interact with end users on your website. The only input option Smush has is to a newsletter subscription for site Admins only. If you would like to notify your users of this in your privacy policy, you can use the information below. Smush sends images to the WPMU DEV servers to optimize them for web use. This includes the transfer of EXIF data. The EXIF data will either be stripped or returned as it is. It is not stored on the WPMU DEV servers. Smush uses a third-party email service (DRIP) to send informational emails to the site administrator. The administrator’s email address is sent to Drip and a cookie is set by the service. Only administrator information is collected by Drip.