Cookie policy

Necessary cookies support the service you request. Optional analytics and advertising tools load only after you explicitly accept their purpose. Rejecting optional cookies leaves the website and account features available. Scrolling, continuing to browse, and closing the settings window do not grant consent.

Use Cookie settings in the website footer or on this cookie policy page to accept, reject, or change optional purposes. Both acceptance and refusal last 180 days in this browser. We ask again when that period ends or the configured providers or policy change. A new device or cleared cookies may require a new choice. No optional provider is authorized just because you previously accepted a different provider.

Withdrawal stops future use of the optional tags, clears their known first-party cookies and browser storage, and reloads the page to unload their code. We cannot remove third-party cookies on another domain or erase information a provider already received. Use browser controls and the privacy rights described in our privacy policy for those cases.

The session cookie (reach-bookcom-session) keeps your session and sign-in state. Its configured inactivity lifetime is 120 minutes. XSRF-TOKEN protects requests against forgery and follows the session lifetime. Provider authentication flows may also require temporary security state.

reachbook_consent remembers a consent receipt with a random identifier for 180 days. It is encrypted and inaccessible to page scripts. reachbook_tracking_block records a temporary refusal while a choice is being saved, including when saving fails; it expires after 180 days or clears after a verified save. The reachbook:consent-change browser-storage key tells other tabs to refresh their choice and remains until browser storage is cleared.

The appearance cookie lasts 365 days and sidebar_state lasts 7 days. They remember display and navigation preferences. The appearance preference and recent-workspace items also use local browser storage, which remains until cleared. You can clear these in your browser or change the corresponding setting. Blocking necessary storage can prevent sign-in, saved choices, and other requested features from working.

Live chat storage is created only if you open the chat yourself using Chat with us or Contact support. Crisp Chat then stores a session identifier and your message history in this browser, under crisp-client keys in local browser storage and its own cookies, so the conversation survives a page change while you wait for an answer. Nothing from Crisp loads before that request. Signing out unbinds this browser from a member conversation, and you can clear the remaining entries in your browser.

Necessary storage is used under the exemption for storage required to provide a service you explicitly request, including section 25(2) TDDDG where applicable. Live chat storage relies on that same exemption, because it exists only once you ask for the chat. Our privacy policy explains the separate GDPR bases for processing associated personal data.

Google Analytics (analytics): _ga, _ga_*. Up to 180 days with this integration.

Microsoft Clarity (analytics): _clck, _clsk. Visitor identifier: one year; session identifier: 1 day.

Analytics measures visits to our public website and use of its pages. Advertising measures campaign results and supports personalized advertising audiences. Optional providers can receive browser and device information, IP addresses, page visits, campaign or click identifiers, and cookie identifiers. The relevant providers are named above and in Cookie settings.

Our integrations run only on the public marketing pages for signed-out visitors. They do not load in mailboxes, workspaces, account settings, authentication, or legal pages. We do not send mailbox messages, prospect records, account identifiers, form contents, or hashed email addresses to these tags. Automated form collection and matching must remain disabled in vendor configuration.

Optional storage and related processing rely on your consent under section 25(1) TDDDG and Article 6(1)(a) GDPR where applicable. Providers may process information outside the EEA, including in the United States. The privacy policy explains international transfers and how to request information about applicable safeguards. Vendor-side retention may differ from cookie lifetimes; consult the linked provider notices.

We retain a consent receipt containing a random identifier, the purposes selected, the displayed provider and purpose information, policy version, and choice and expiry times. It contains no account identifier, IP address, or browser fingerprint. We use it to remember and demonstrate the choice and schedule deletion one year after it was recorded.

You can contact [email protected] about cookies or your privacy rights. The privacy policy explains access, deletion, objection, and complaints to a supervisory authority. Necessary session storage is independent of consent to optional tracking.