Cookie Architecture & Telemetry Policy
At Assembly Minds, we engineer our platforms for speed, security, and privacy. This document outlines our transparent approach to state preservation, session management, and the minimal telemetry mechanisms required to deliver our enterprise-grade digital experiences.
01. Purpose of Cookies & Telemetry
In modern web architecture, state preservation across stateless HTTP requests is a fundamental necessity. We utilize minimal cookies and local storage tokens exclusively to maintain session integrity, execute Cross-Site Request Forgery (CSRF) token handling, monitor structural latency, and deliver interface responsiveness. We deploy zero intrusive telemetry—our engineering principles dictate that user data is solely utilized to maintain platform functionality, not for behavioral aggregation.
02. Strictly Necessary Security & Session Cookies
Certain cookies are designated as strictly necessary. These tokens facilitate CSRF protection, session state integrity, secure authentication handshakes, and local storage caching for immediate interface responsiveness. Because these tokens are structurally tied to security and service integrity, they cannot be disabled without critically breaking the Assembly Minds web experience.
| Token Key | Function | Duration |
|---|---|---|
| __Host-csrf_token | Cryptographic token preventing Cross-Site Request Forgery (CSRF) attacks on POST/PUT requests. | Session |
| am_session_id | Maintains the authenticated state and encrypted handshake during active platform usage. | Session (Strict) |
| am_telemetry_opt | Stores explicit consent preferences regarding non-essential operational metrics. | 12 Months |
03. Performance & Scheduling Cookies
To facilitate seamless discovery and project initiation, we integrate enterprise calendaring solutions such as Cal.com for appointment scheduling widgets. Interacting with these widgets may set localized cookies essential for managing booking state, timezone calculations, and calendar availability syncing.
Additionally, we passively collect anonymous client-side crash telemetry and Web Vitals metrics (LCP, FID, CLS) to continuously monitor the structural health of our global edges. This data is strictly non-identifiable and aggregates network throughput statistics without linking to individual user identities or personal profiling vectors.
04. Zero Ad-Network Tracking or Data Brokering
Our operational model fundamentally rejects the data brokerage economy. Assembly Minds explicitly does not deploy third-party advertising tracking pixels (including Meta Pixel, Google Ads Remarketing tags, or TikTok tracking scripts). We do not aggregate behavioral profiles for external monetization, nor do we sell telemetry data to third-party data brokers.
Furthermore, our systems are engineered to natively respect the Global Privacy Control (GPC) and Do Not Track (DNT) header signals emitted by privacy-conscious browsers, ensuring complete compliance with advanced privacy directives at the protocol level.
05. How to Manage and Revoke Cookies via Browser Settings
You retain absolute control over cookie execution through your browser's security architecture. Should you choose to implement strict blocking, be aware that strictly necessary security tokens will be rejected, which will functionally degrade or completely block access to secure zones and third-party integrations such as the appointment scheduling widgets.
- Google Chrome: Navigate to Settings > Privacy and security > Cookies and other site data.
- Apple Safari: Navigate to Preferences > Privacy > Block all cookies.
- Mozilla Firefox: Navigate to Options > Privacy & Security > Enhanced Tracking Protection.
- Microsoft Edge: Navigate to Settings > Cookies and site permissions > Manage and delete cookies and site data.