Privacy Policy

Photo by Christina Branco on Unsplash

1 Introduction

At this blog (https://ricardoromanj.com), your privacy is important to me. This privacy policy contains the type of information that this blog collects and how it is used. Hence forth, the document uses the terms blog, the author and we interchangibly.

If you have any questions, please reach out to me at privacy@ricardoroman.net.

This privacy policy is only valid for visitors of this blog with regards of the data they share with us. It does not apply to external links.

2 Consent

By remaining on this blog and viewing posts, you consent to this privacy policy and its terms.

3 Data

3.1 What information we collect

This blog collects and stores any information you enter on our website or provide us in any other way. In addition, we collect the Internet Protocol (IP) address used to connect your computer to the Internet; computer and connection information. The blog uses software tools to measure and collect session information, including page response times, length of visits to certain pages, page interaction information, and methods used to browse away from the page. The blog does not collect personally identifiable information (such as name, email, password, communications); payment details (including credit card information), comments, feedback, product reviews, recommendations, and personal profile.

To use this blog you are not required to provide any personal information or any data that could personally identify you or any user.

Please be aware, if you contact the author directly, we may receive additional information about you. This may include your name, email address, the contents of the message and/or attachments you may send us, and any other information you may choose to provide.

3.2 About log files

This blog is hosted through Firebase Hosting. Firebase, as other hosting providers, use log files. These files log visitors when they visit websites. All hosting companies do this and a part of hosting services’ analytics. The information collected by log files may include Internet Protocol (IP) addresses, browser type, Internet Service Provider (ISP), date and time stamp, referring/exit pages, and possibly the number of clicks. These are not linked to any information that is personally identifiable. For further details, please refer to Firebase’s Privacy Policy.

3.3 Why we collect this information

The author collects Non-personal Information for the following purposes:

1. Provide, operate and maintain the website
2. Improve and expand the content
3. Understand how readers use the website
4. Curate our content so that we provide only the best for our readers
5. Develop new features and functionalities
6. Improve the reader’s reading experience from this blog

3.4 How we collect this data

3.4.1 Cookies

This blog uses cookies to collect the data.

1. We use cookies from Google Analytics to collect non-personal, aggregated, statistical information about session information, including page response times, length of visits to certain pages, page interaction information, and methods used to browse away from the page. Please find Google Analytics’ Privacy Policy here.
2. We use a cookie to know when a user consents to the use of cookies and stop displaying the cookie banner at the footer of the page.

You can choose to disable cookies through your individual browser options. To know more detailed information about cookie management with specific web browsers, view your browser’s page and documentation.

3.5 Where the data is stored

Depending on the type of data, it can be stored on different services.

• At the time of publication of this Privacy Policy, Firebase Hosting stores its data in the United States. Please refer to Firebase’s Privacy Policy. Please note that this blog does not control this and may change without notice.
• At the time of publication of this Privacy Polciy, Google Analytics operates servers all over the world, so the location of the data may vary depending on where you visit this site from. Please see Google’s Privacy Policy. Please be aware that this blog does not control this and may change without notice.

4 Third party privacy policies

This privacy policy does not apply to third parties. Thus, I advise you to consult the respective Privacy Policies of these third-parties for more detailed information. It may include their practices and instructions about how to opt-out of certain options. You may find a comprehensive list of these Privacy Policies and their links here:

• This blog is hosted by Firebase. Find their privacy policy here.
• Google Analytics provides metrics and measurements to understand how websites are used. Find their privacy policy here.

5 GDPR and CCPA

Under GDPR and CCPA, visitors are entitled to request copies of thier data and / or have their data deleted. As of the publication date of this policy, the data this blog collects cannot identify any individual person. For this reason, it is not possible to locate a single visitor’s data for retrieval or deletion. For such requests, please consult Google’s Privacy Policy.

6 Children’s privacy

Another one of my priorities is children’s privacy. I encourage parents to observe, participate in, monitor and guide their children’s activity online. This blog does not knowingly collect Personal Identifiable information from children under 13 years of age. If you think that your child provided this kind of information on this blog, we strongly encourage you to contact me immediately and I will do my best efforts to promptly remove such information from my records. At the moment, the only way of providing personal information is through direct contact and not through this site.

7 Updates to this privacy policy

The author reserves the right to modify this privacy policy at any time, so please review it frequently. Changes and clarifications will take effect immediately upon their posting on the website.