Cookie Policy – RakeRadar.com
This Cookie Policy (the “Policy”) explains what cookies and similar technologies are, for what purposes they are used on the RakeRadar.com website (the “Website”, “we”, “us”), and how you can manage them.
Important: The Website may use cookies and similar technologies for technical purposes, security (including Cloudflare), analytics, click measurement (including clicks on affiliate links) and enforcing jurisdictional restrictions (e.g. blocking traffic from specific jurisdictions based on IP geolocation).
1. What are cookies and similar technologies?
Cookies are small text files stored on your device (computer, smartphone, tablet) while browsing websites. They help the Website recognize your browser, remember settings and ensure proper operation.
In addition to cookies, we may also use similar technologies, such as local storage, pixels (pixel tags), session identifiers or technical signals, which serve similar functions (e.g. measurement, security, diagnostics).
2. Why do we use cookies?
On the Website, cookies may be used for the following purposes:
- Technical (essential) – so that the Website works correctly, loads pages, and maintains the session and basic settings.
- Security – protection against abuse, bots and attacks, stability and performance (including Cloudflare mechanisms).
- Analytics and statistics – understanding how users use the Website, what they read and where the UX needs improvement.
- Click measurement – recording clicks on outbound links, including affiliate links, to measure content effectiveness and settle partnerships.
- Enforcing jurisdictional restrictions – supporting access blocks and filters (e.g. geoip block for restricted jurisdictions), in combination with IP geolocation.
- Preferences – remembering selected settings, if the Website provides such features.
3. What types of cookies may we use?
The Website may contain the following categories of cookies:
3.1 Necessary (technical) cookies
They are necessary for the proper functioning of the Website. Without them, the site may malfunction or not work at all. These cookies usually do not require consent in many jurisdictions because they are “strictly necessary”.
3.2 Security and performance cookies (including Cloudflare)
They may be used to protect against abuse, filter traffic, prevent attacks and improve performance. The Website may use Cloudflare services, which may use their own cookies/identifiers for security purposes.
3.3 Analytics cookies
They are used to create statistics and analyses of Website usage (e.g. popular subpages, time on site, navigation paths). We want to develop the Website based on real user behaviour, not guesswork.
3.4 Measurement cookies (clicks, affiliation)
They may be used to record clicks on outbound links and affiliate links. The purpose is to analyse content effectiveness and properly settle affiliate partnerships. Clicks may be measured both on the Website side and on the partners’ side (Operators/affiliate networks) after navigating to their site.
3.5 Functional cookies
If the Service provides features that require remembering preferences (e.g., display settings), functional cookies may be used.
4. Third-party cookies (Operators, affiliate networks)
The Service may contain links to external websites (Operators) and affiliate links. After clicking and navigating to an external website, cookies may be stored by a third party (the Operator or an affiliate network) for the purpose of:
- attributing the click and any potential conversion (e.g., registration),
- ensuring the Operator’s website functions,
- analytics and security on the Operator’s side.
We do not control third-party cookies. In such cases, the privacy and cookie policies of the relevant third party apply.
5. IP geolocation, cookies, and jurisdictional restrictions
We may use IP geolocation mechanisms (e.g., GeoDB databases and/or infrastructure provider tools) to determine the user’s approximate country. In combination with technical mechanisms (e.g., firewall rules, access blocks), this may result in restricting access to the Service for selected jurisdictions.
In this context, cookies may support the operation of filters (e.g., remembering a decision about a notice or restriction). If you believe that a block has affected you by mistake, you can contact us: [email protected].
6. How long are cookies stored?
Cookies may be:
- session – deleted after closing the browser,
- persistent – stored for a specified period or until removed by the user.
The storage period depends on the type of cookies, their function, and the configuration of the Service and third-party services.
7. How to manage cookies?
You have several options for controlling cookies:
7.1 Browser Settings
You can change your browser settings to block cookies, delete them, or receive a warning before they are saved. Instructions can be found in your browser’s documentation.
7.2 Deleting Cookies
You can delete cookies at any time from your browser. Please note that deleting cookies may cause some settings or features of the Service to stop working properly.
7.3 Consent Banner (CMP), if available
If the Service displays a cookie consent banner (CMP), you can give or withdraw consent for specific categories of cookies (e.g., analytical). The consent mechanism may vary depending on jurisdiction and implementation.
Note: blocking technical and security cookies may hinder the use of the Service or cause it to malfunction.
8. Do Not Track and Similar Signals
Some browsers offer “Do Not Track” signals. These standards are not uniform, so the Service may not respond to these signals consistently across all environments. If we implement consent management mechanisms, they will be the primary way to choose cookie preferences.
9. Changes to the Cookie Policy
We may update the Cookie Policy in case of technological, legal, or organizational changes. The new version is effective from the moment of publication on the Service.
Last updated: 2025-12-25
10. Contact
If you have any questions about cookies or privacy, please contact us:
Email: [email protected]