Cookie Policy
Effective 2026-04-22 · Last updated 2026-04-22 · Version 1.0
This policy explains the cookies (and equivalent browser-storage mechanisms) that Rogger uses. We keep the list short on purpose.
1. What Rogger does NOT do
- We do not use advertising cookies.
- We do not use cross-site tracking cookies.
- We do not integrate Google Analytics, Meta Pixel, TikTok Pixel, LinkedIn Insight Tag, or any other third-party analytics or advertising SDK on rogger.io.
- We do not sell or share cookie data with data brokers or advertisers.
2. What Rogger does use
All cookies set by Rogger directly fall into the "strictly necessary" category under the ePrivacy Directive and equivalent regulatory guidance, meaning they do not require opt-in consent because they are essential to the operation of the site:
| Name | Purpose | Type | Duration |
|---|---|---|---|
| ist_session | Authenticates your session after you sign in. Without this cookie, you cannot stay logged in. | Strictly necessary | 30 days (rolling) |
| __cf_bm | Cloudflare bot-management — distinguishes real users from automated traffic. Set by Cloudflare at the edge. | Strictly necessary (security) | 30 minutes |
| cf_clearance | Cloudflare challenge verification for suspicious traffic. Set only if you successfully complete a challenge. | Strictly necessary (security) | 30 minutes |
3. How to manage cookies
You can block all cookies in your browser settings. If you do, you will not be able to sign in to Rogger — the session cookie is how we remember you. Public pages (rogger.io, /security, /privacy, etc.) will still work without cookies because they do not require authentication.
4. Third-party cookies on customer-embedded widgets
The Rogger review widget, when a business customer embeds it on their own website, does not set any cookies. The widget fetches reviews over a public API endpoint and renders them client-side.
5. Changes
If we ever add a non-essential cookie, we will update this page and present a consent banner to users in the EU, UK, and other regions where opt-in consent is required, before that cookie is set.
6. Contact
Questions: [email protected].