Rookie HPC

Privacy Policy

When you just browse the RookieHPC website, we collect:

Personal data:

None, period.

Anonymous data:

A visit count, to know how many times each page of the RookieHPC website is viewed. These counters help us find which pages are more attractive to readers, so that we can improve less successful pages.

When you contact us via the contact form, we collect:

For us:

Your message and email address, to know why you are contacting us and to whom reply, respectively. We share these information with no one. No if, no but.

For the Google reCAPTCHA service:

According to the Google reCAPTCHA privacy policy, in section "Information we collect as you use our services": "The information we collect includes unique identifiers, browser type and settings, device type and settings, operating system, mobile network information including carrier name and phone number, and application version number. We also collect information about the interaction of your apps, browsers, and devices with our services, including IP address, crash reports, system activity, and the date, time, and referrer URL of your request". The Google reCAPTCHA service protects the RookieHPC website contact form against malicious entries by assessing whether it is filled by a human or a bot.

Security

SSL encryption

The RookieHPC website uses a secure connection as you can see in the URL bar, which has a URL beginning with "https://" or displays a little lock icon. Thus, the communications between your browser and our server are encrypted using SSL and cannot be read by third parties.

HSTS preloaded

In addition to securing your connection over HTTPS, the RookieHPC website and your browser go further and team up to make sure that every single interaction they have cannot be anything else but secure, even if a malicious entity on the network was trying to make you do otherwise. This is achieved in two steps:

  1. The server-side, us, guarantees that if we receive a request to access the unsecure HTTP version of a page, we automatically return the secure HTTPS version of that page instead.
  2. The client-side, your browser, guarantees that it will never send us a request for an unsecure HTTP version of a page at all. To achieve this, we are registered in the trusted HSTS preload list, which requires to demonstrate a list of security features, including the automatic redirection to HTTPS. Your browser regularly checks out that list and knows that websites registered in it are HTTPS-only websites. So, if your browser is asked to send us a request for an unsecure HTTP version of a page, it knows that it does not make sense and automatically sends a request for the secure HTTPS version of that page instead.

In a nutshell, we always serve the secure HTTPS version of pages and your browser always sends us requests for the secure HTTPS version of pages; we have you covered.