Cookie Policy
Last updated: 2026-01-21
Contact: [email protected]
Categories
We group cookies into strictly necessary, functional, analytics, and preference categories. Strictly necessary cookies enable security features, load balancing, and session continuity. Functional cookies remember UI choices such as sidebar collapse state. Analytics cookies help us understand aggregate navigation patterns. Preference cookies store documentation settings like code sample language when you opt in. Representative rows include: ch_session (necessary, session, authentication continuity), ch_prefs (preferences, 12 months, UI density), ch_doc_lang (functional, 6 months, documentation language), ch_anon_id (analytics, 13 months, rotating identifier). Durations are targets and may adjust with product releases; enterprise administrators may request a JSON export of the active inventory.
Consent
Where required, we obtain consent before setting non-essential cookies. You may withdraw consent at any time through the cookie preferences link or by clearing cookies in your browser. Withdrawing consent does not affect the lawfulness of processing based on consent before withdrawal. Some features may degrade if necessary cookies are blocked; we surface notices when that occurs.
Preferences
You can manage cookies through our preferences center linked in the footer and in the consent toast. Browser vendors publish instructions for blocking or deleting cookies. Note that blocking all cookies may prevent single sign-on flows from completing. Documentation mirrors may set isolated cookies scoped to sandbox domains; those domains are listed in our technical appendix for administrators.
Contact
For questions about cookies, email [email protected] with the subject line “Cookie inquiry”. Include approximate timestamps and URLs to help us investigate. If you believe a cookie was set in error, we will review telemetry configuration and update this policy if we identify a systemic issue.
Third Parties
When support or analytics vendors set cookies, they act under our agreements and documented purposes. We review vendor cookie inventories during procurement. If a vendor introduces a new cookie category, we update subprocessors documentation and, where necessary, refresh consent prompts. You should review vendor policies when using embedded content from their domains.