Privacy Policy Statement

Because everyone who uses the Internet should care about his privacy when surfing websites or commenting, we created this privacy policy statement page, so users can understand what type of information the site Rotifoly collects and for what we use that data. So, here are the details if you want to check them anytime you want.

What does Rotifoly.com collect as data?

When users visit any page on the website, our system detects the region from where the visitor is coming from, for example, city or state. We use a third-party tool that’s Google Analytics, to collect the number of visits and see how users interact with the website content, like the time spent on pages.

In addition, Google Analytics collects the type of browser the visitor is using and the device type, for example, mobile, tablet, or desktop. Also, we can see the version of your web browser like Google Chrome to detect if the site can adjust the layout and the size of the page to look good and load fast. This happens when users have an old version of web browsers that do not support the latest coding technologies.

Note: we don’t know the name or any other personal information about people visiting the website unless they write their name in the comment section field or use the contact page to ask questions. Also, we don’t know what users do and all of their life activities. That’s not our goal, and it’s not in our data in any way.

Google Analytics and Cookies

Google has a service called Analytics which is simply a system that uses advanced tracking code to measure the page experience like speed, scrolling, actions taken on the site, and the number of pages viewed per unique visit. Google Analytics is a safe service that’s trusted by the biggest companies in the world, so we use it to see user interactions.

We use website cookies to save the local version of the page’s static assets like the CSS code or logo, so the next time the user visits the website, he gets a faster page loading time because the browser has already saved a cached version of the site and that’s great for all. That way, the user saves bandwidth downloading files and gets faster site speed. We save hosting resources, especially if there are lots of visits simultaneously, which may overload the server.

Everyone can accept or decline to use our site cookies directly from the web browser; refer to this guide by Google if you want to manage or reject these cookies.

How do we use the data?

When a user¬†posts a comment, we collect the email address as that’s needed to reply to the message, and also, in case the user doesn’t want to ask questions directly, they can use the contact page to send a request. Then, the site collects the regions from where that user is sending the message from and sees his IP address for security reasons. If the system detects that many users try to post comments from the same IP address many times, they’ll be blocked and marked as spam. That’s how we fight spam, like what happens with many other websites.

Also, we use the data to improve the site speed and make web pages load fast for a better user experience. Let’s say, for example, that someone visits the site from a specific region, but for some unknown reason, the page speed for that location is slower compared to other states. That’s why we may check the screen resolution and see the device type to determine if we should make changes to the site code or speed. Thus, we may use the data to improve the site content, speed, and layout and offer a better user experience.

How and where do we store the data?

As we said earlier, we don’t collect any personal details, and we store the simple data collected when users comment on an article or use the contact form, that data will be stored on secure servers in the United States of America, and we don’t share it with anyone or sell it. The servers are protected by the latest version and tools. Also, we update the system for better protection.

If you have questions about this privacy policy page, you can contact us and ask your questions.

error: