It explains what "cookies" are and how this site uses cookies and other tracking technologies in order to improve this site and to deliver the best and more personalized service. Our Cookies Policy applies to all users of this Web.

Cookies are small files placed on your computer by a Web page when you visit it. They can be used to store all sorts of useful information to make your next visit easier and more convenient, i.e. to remember user preferences and recommend content. Some people are uncomfortable not knowing what information is in a cookie. Accepting cookies through your Web browser is your personal choice. You can set your browser to disable cookies. However, if you choose not to accept cookies, we may not be able to provide you with as good of an experience as one that is specifically fixed onto your needs by utilizing the cookie.

The Web uses cookies to draft statistical reports and/or analysis on the use of the various pages on our site (how many people visit each page and information of this nature). We may use the services of third parties to collect and use anonymous information about your visits to and interactions with our Web through the use of technologies such as cookies to personalize advertisements for goods and services.

Below there is a more detailed analysis of the cookies used in the Web:

  • X-XSRF-Token Cookie ( Strictly Necessary Cookies ): The Web is making sure to take all measurements to protect your access to the application from cross-site request forgery (CSRF) attacks. Cross-site request forgeries are a type of malicious exploit whereby unauthorized commands are performed on behalf of an authenticated user. The Web automatically generates a CSRF "token" for each active user session managed by the application. This token is used to verify that the authenticated user is the one actually making the requests to the application. The Web stores the current CSRF token in an XSRF-TOKEN cookie that is included with each response generated by the application.
  • Session Cookie ( Strictly Necessary Cookies ): The Web uses the session cookie to identify a session instance of a user.
  • Remeber Me Token Cookie ( Functionality Cookies ): The Web uses a remember me token cookie to store the remember me token generated when you select (click) the remember me checkbox when logging in to the application. This cookie is used to automatically log in the user to the application the next time you visit the application from the same browser and considering the cookie has not expired.
In addition, part of our interface is using google fonts, therefore our Company remotely calls Google's API service for providing the required fonts. Google Fonts: (Dirived from google fonts FAQ)

The Google Fonts API is designed to limit the collection, storage, and use of end-user data to what is needed to serve fonts efficiently.

Use of Google Fonts is unauthenticated. No cookies are sent by website visitors to the Google Fonts API. Requests to the Google Fonts API are made to resource-specific domains, such as or, so that your requests for fonts are separate from and do not contain any credentials you send to while using other Google services that are authenticated, such as Gmail.

In order to serve fonts quickly and efficiently with the fewest requests, responses are cached by the browser to minimize round-trips to our servers.

Requests for CSS assets are cached for one (1) day. This allows us to update a stylesheet to point to a new version of a font file when it’s updated, and ensures that all websites using fonts hosted by the Google Fonts API will be using the most updated version of each font within 24 hours of each release.

The font files themselves are cached for one year, which cumulatively has the effect of making the entire web faster: When millions of websites all link to the same fonts, they are cached after visiting the first website and appear instantly on all other subsequently visited sites. Our Company sometimes updates font files to reduce their file size, increase coverage of languages, and improve the quality of their design. The result is that website visitors send very few requests to Google: We only see 1 CSS request per font family, per day, per browser.

Google Fonts logs records of the CSS and the font file requests, and access to this data is kept secure. Aggregate usage numbers track how popular font families are, and are published on our analytics page. The Company uses data from Google’s web crawler to detect which websites use Google fonts. This data is published and accessible in the Google Fonts BigQuery database. To learn more about the information Google collects and how it is used and secured, see Google's Privacy Policy.