Who we are
Company Name: REALiX, s.r.o.
General Manager/Owner: Martin Malík
Company Seat: B. Nemcovej 2291/28, 90101 Malacky, Slovakia
Company registered in: Business Register of the District Court Bratislava I, Section: Sro, Insert No.: 168207/B, IČO: 55 326 811
VAT ID: SK2121954659
What personal data we collect and why we collect it
Our company and our software (HWiNFO) doesn’t collect any personally identifiable information. The only exception is the HWiNFO Forum, where common user-provided data is gathered from registered users for login identification. HWiNFO does not transmit any information via network; a network connection to our servers is used only to retrieve latest version information. No information is transmitted to our or any other servers.
This website uses cookies
We use cookies to personalize content and ads, to provide social media features and to analyze our traffic. We also share information about your use of our site with our social media, advertising and analytics partners who may combine it with other information that you’ve provided to them or that they’ve collected from your use of their services. You consent to our cookies if you continue to use our website.
Cookies are small text files that can be used by websites to make a user’s experience more efficient.
The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.
What Are Cookies? What is a Cookie?
Cookies are small files which are stored on a user’s computer. They are designed to hold a modest amount of data specific to a particular client and website, and can be accessed either by the web server or the client computer. This allows the server to deliver a page tailored to a particular user, or the page itself can contain some script which is aware of the data in the cookie and so is able to carry information from one visit to the website (or related site) to the next.
Are Cookies Enabled in my Browser?
To check whether your browser is configured to allow cookies, visit the Cookie checker. This page will attempt to create a cookie and report on whether or not it succeeded.
For information on how to enable or disable cookies, see ‘Enabling cookies’.
For information on how to delete and clear cookies, see ‘Deleting cookies’.
Can I see/view the cookies I have on my computer?
Most browsers have a configuration screen which allows the user to see what cookies have been stored on the computer, and optionally to delete them. For more information, see the viewing cookies page.
Note that it is not possible for a webpage to view cookies set by other sites, as this would represent a privacy and security problem.
What’s in a Cookie?
Each cookie is effectively a small lookup table containing pairs of (key, data) values – for example (firstname, John) (lastname, Smith). Once the cookie has been read by the code on the server or client computer, the data can be retrieved and used to customize the web page appropriately.
When are Cookies Created?
Writing data to a cookie is usually done when a new webpage is loaded – for example after a ‘submit’ button is pressed the data handling page would be responsible for storing the values in a cookie. If the user has elected to disable cookies then the write operation will fail, and subsequent sites which rely on the cookie will either have to take a default action, or prompt the user to re-enter the information that would have been stored in the cookie.
Why are Cookies Used?
Cookies are a convenient way to carry information from one session on a website to another, or between sessions on related websites, without having to burden a server machine with massive amounts of data storage. Storing the data on the server without using cookies would also be problematic because it would be difficult to retrieve a particular user’s information without requiring a login on each visit to the website.
If there is a large amount of information to store, then a cookie can simply be used as a means to identify a given user so that further related information can be looked up on a server-side database. For example the first time a user visits a site they may choose a username which is stored in the cookie, and then provide data such as password, name, address, preferred font size, page layout, etc. – this information would all be stored on the database using the username as a key. Subsequently when the site is revisited the server will read the cookie to find the username, and then retrieve all the user’s information from the database without it having to be re-entered.
How Long Does a Cookie Last?
The time of expiry of a cookie can be set when the cookie is created. By default the cookie is destroyed when the current browser window is closed, but it can be made to persist for an arbitrary length of time after that.
Who Can Access Cookies?
When a cookie is created it is possible to control its visibility by setting its ‘root domain’. It will then be accessible to any URL belonging to that root. For example the root could be set to “whatarecookies.com” and the cookie would then be available to sites in “www.whatarecookies.com” or “xyz.whatarecookies.com” or “whatarecookies.com”. This might be used to allow related pages to ‘communicate’ with each other. It is not possible to set the root domain to ‘top level’ domains such as ‘.com’ or ‘.co.uk’ since this would allow widespread access to the cookie.
By default cookies are visible to all paths in their domains, but at the time of creation they can be restricted to a given subpath – for example “www.whatarecookies.com/images”.
How Secure are Cookies?
There is a lot of concern about privacy and security on the internet. Cookies do not in themselves present a threat to privacy, since they can only be used to store information that the user has volunteered or that the web server already has. Whilst it is possible that this information could be made available to specific third party websites, this is no worse than storing it in a central database. If you are concerned that the information you provide to a webserver will not be treated as confidential then you should question whether you actually need to provide that information at all.
What are Tracking Cookies?
Some commercial websites include embedded advertising material which is served from a third-party site, and it is possible for such adverts to store a cookie for that third-party site, containing information fed to it from the containing site – such information might include the name of the site, particular products being viewed, pages visited, etc. When the user later visits another site containing a similar embedded advert from the same third-party site, the advertiser will be able to read the cookie and use it to determine some information about the user’s browsing history. This enables publishers to serve adverts targeted at a user’s interests, so in theory having a greater chance of being relevant to the user. However, many people see such ‘tracking cookies’ as an invasion of privacy since they allow an advertiser to build up profiles of users without their consent or knowledge.
What cookies are used?
This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.
Your consent applies to the following domains: hwinfo.com
Necessary (5)
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
__cfduid | hwinfo.com | Used by the content network, Cloudflare, to identify trusted web traffic. | 1 year | HTTP Cookie |
euconsent-v2 | hwinfo.com | Consent String of the IAB CMP Framework (TCF) v2. | 13 months | HTTP Cookie |
FCCDCF | hwinfo.com | Funding Choices | 13 months | HTTP Cookie |
FCNEC | hwinfo.com | Funding Choices | 365 days | HTTP Cookie |
_GRECAPTCHA | www.google.com | Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis. | 6 months | Third-party |
Performance/Statistics (4)
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
_ga | hwinfo.com | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 2 years | HTTP Cookie |
_gat | hwinfo.com | Used by Google Analytics to throttle request rate | Session | HTTP Cookie |
_gid | hwinfo.com | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | Session | HTTP Cookie |
collect | google-analytics.com | Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels. | Session | Pixel Tracker |
Targeting/Marketing (4)
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
IDE | doubleclick.net | Used by Google DoubleClick to register and report the website user’s actions after viewing or clicking one of the advertiser’s ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. | 1 year | HTTP Cookie |
DSID | doubleclick.net | This cookie is set to note your specific user identity. It contains a hashed/encrypted unique ID. | 1 hour | HTTP Cookie |
__gads | hwinfo.com | This cookie is associated with the DoubleClick for Publishers service from Google. Its purpose is to do with the showing of adverts on the site. | 1 year | HTTP Cookie |
addtl_consent | hwinfo.com | A list of consented Google Ad Tech Providers that are not registered with IAB. | 1 month | HTTP Cookie |
Forum (4)
The following cookies are used by the HWiNFO forum only (based on XenForo) and most of them are applied only for users logged-in.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
xf_csrf | hwinfo.com | User Unique Token | Session | HTML Local Storage |
xf_push_notice_dismiss | hwinfo.com | User Choice for Push service | 1 year | HTML Local Storage |
xf_session | hwinfo.com | Session ID | Session | HTTP Cookie |
xf_user | hwinfo.com | User ID | 1 year | HTTP Cookie |