Cookie policy

Draft of 13 November 2026

This policy explains the cookies and similar storage (such as local storage in your browser) that ROOKON uses on its website and in the app. Optional cookies are only set after you say yes. The privacy policy explains how we handle the data.

Necessary on the website

Your cookie choice is stored in your browser’s local storage (key rookon.consent) so we don’t ask again on every page. Nothing else is needed for the website to work.

Necessary when you are signed in

• Sign-in: first-party, HTTP-only cookies named rookon.session_token and related rookon.* cookies keep you signed in, complete two-factor sign-in, and remember a device you mark as trusted. They are removed when you sign out or expire.
• Phone review screen: the cookie rookon_review_target remembers the workspace and project you last reviewed (their ids only).
• Preferences in local storage: your sound setting, whether Rooky has already welcomed you, whether this browser’s notifications are set up, and the light or dark theme of status pages. These stay on your device and are not used for tracking.

Analytics (optional)

With your consent, Google Tag Manager loads Google Analytics 4 to measure page views and demo interactions on our website. Google Consent Mode v2 signals are set to “denied” until you choose, and nothing optional loads before that.

Marketing (optional)

With your consent, Google Ads conversion tracking measures which campaigns lead to sign-ups, and the campaign parameters of your visit are kept for the browser session (key rookon.attribution).

Partner referrals

With marketing consent, a partner link stores the partner code and click time for 30 days (cookie rookon_ref) so the partner is credited if you sign up later. Without consent nothing is stored; the code stays visible in the link and on the sign-up form instead. A code you type into the sign-up form is kept for one hour (cookie rookon_ref_code) so it still applies if you continue with Google or Microsoft.

On websites that use ROOKON

ROOKON’s script on our customers’ websites sets no cookies and uses no device storage for analytics. Only if a customer turns on experiments, and the visitor has given consent on that website, does it store a random test id in the cookie rk_ab. Each customer decides this on their own website and explains it in their own cookie policy.

Changing your choice

Use “Cookie settings” in the footer at any time. Withdrawing consent stops optional tracking from that point on. You can also delete cookies and local storage in your browser settings; you will then be signed out.