2. Cookie categories we use#
The table below summarises the categories of cookies and similar technologies we use, their purpose, and typical lifespan. Exact names may vary as the platform evolves.
| Category | Purpose | Type | Typical duration |
|---|
| Essential — authentication | Keep you signed in to the dashboard | First-party (cookies / local storage) | Until sign-out or session expiry |
| Essential — security | Abuse protection, bot checks on forms and demos, and session integrity | First / third-party | Session |
| Essential — abuse prevention | A browser/device identifier used at sign-up and on public demos to enforce free-credit and demo limits | First-party (local storage) and derived signals | Persistent until cleared |
| Functional — preferences | Theme preference, cookie-consent choice, anonymous identifier for blog likes, and the API key you enter in the developer playground | First-party (local storage) | Persistent until cleared |
| Analytics | Aggregated page performance and feature adoption | First / third-party | Up to 13 months |
| Session replay | Recording page interactions, with inputs masked, to diagnose usability problems | Third-party | Up to 13 months |
| Payment / checkout | Set by the payment gateway during checkout | Third-party | Session |
| Edge security / CDN | Abuse protection and performance at the edge | Third-party | Session to 1 year |
Essential cookies
Required for the platform to function. These cannot be disabled without breaking core features.
- Authentication — Session tokens to keep you signed in to console.callmissed.com
- Security — Abuse protection, bot-protection checks on sign-up, demo, and booking forms, and session integrity
- Abuse prevention — A browser/device identifier used to detect repeat sign-ups for free credits and to apply daily limits on public voice demos
- Load balancing — Routing requests to healthy servers
Functional storage
- Theme preference — Light/dark mode (stored in local storage)
- Cookie-consent choice — Remembering whether you accepted or declined analytics
- Blog likes — An anonymous identifier so a like is counted once
- Developer playground — The API key you enter is kept in your browser's local storage and is not sent anywhere except to our API with your requests
The embeddable website chat widget does not set cookies.
Analytics
We use privacy-conscious product analytics to understand page performance and feature adoption. Analytics data is aggregated and not sold. On our main website and dashboard, analytics cookies and events are placed only after you accept them in the cookie banner. On our documentation, status page, and developer playground, basic page analytics runs without a banner.
Session replay
Session replay records how pages are used — clicks, scrolls, and page changes — so we can find and fix usability problems. Form inputs and fields we mark as sensitive (such as API keys and webhook secrets) are masked, and replay is disabled on authorisation screens. A session-replay tool, which may set its own cookies, loads on our main website, dashboard, and developer playground without a separate consent prompt. An additional replay capability also records the network requests a page makes (addresses, timing, and content), with passwords, tokens, and API keys removed in your browser before upload. On the main website and dashboard it is enabled only after you accept analytics in the cookie banner; on our documentation, status page, and developer playground it runs without a banner. You can block session replay with your browser's tracking protection or a content blocker without affecting how the Service works.
Marketing cookies
We do not use third-party advertising cookies on our core product. If we introduce marketing cookies in the future, we will update this policy and obtain consent where required by law.
