Cookie Policy
Effective September 10, 2026 · Version 2026-09-10
This policy explains what Mirror | Mirror stores in your browser, why, and how long it stays there. It covers cookies and the two related browser storage mechanisms — local storage and session storage — because they raise the same question even though only one of them is technically a cookie.
Strictly necessary
| Name | Type | Purpose | How long |
|---|---|---|---|
| __meeting_session__ | Cookie | Carries your meeting credential. It is what lets you reload the page mid-meeting without being thrown out, it is the only credential the session-renewal endpoint accepts, and it is what lets you share a slide deck or a document in a meeting you joined without an account. HttpOnly, Secure and SameSite=Lax, so it cannot be read by scripts and is not sent with cross-site requests. | Just over 8 hours, matching the life of the meeting credential inside it. |
| Clerk session cookies | Cookie | Set by Clerk, our authentication provider, to keep you signed in. Set on our domain and on clerk.mirrormirror.live. | Governed by Clerk; typically until you sign out or the session expires. |
Your preferences
| Name | Type | Purpose | How long |
|---|---|---|---|
| mm:device:mic, mm:device:camera | Local storage | The microphone and camera you last chose, so you do not have to re-pick them every meeting. Stored per browser, not per meeting. | Until you clear your browser's site data. |
| mm:audio:hifi | Local storage | Whether you turned on high-fidelity audio — a property of your headphones, not of any one meeting. | Until you clear your browser's site data. |
| mm:mute:audio, mm:mute:video | Local storage | Whether you last muted your microphone or camera, so that rejoining a meeting does not silently switch them back on. Changing an audio setting mid-meeting reconnects you, which is the case this exists for. Stored per browser, not per meeting. | Until you clear your browser's site data. |
| mm.toolbar.density, mm.carousel.visible, mm.panel.open, mm.panel.width | Local storage | Interface preferences: how compact the toolbar is, whether the participant carousel is shown, and whether the side panel is open and how wide you made it. | Until you clear your browser's site data. |
| mm:exactSelection | Local storage | Remembers your choice about how participants are selected for display. | Until you clear your browser's site data. |
| mm.modes.v1 | Local storage | Display modes you have saved for presenting — the name you gave each one and the on-screen adjustments it applies. These stay on this device and are never sent to us or to anyone else in a meeting. | Until you delete the mode or clear your browser's site data. |
While a meeting is open
| Name | Type | Purpose | How long |
|---|---|---|---|
| mm:invite2:<meeting> | Session storage | The shareable invite link for the meeting you are in, so it can be copied without re-fetching it. | Until you close the tab. |
| mm:source:<meeting> | Session storage | Which document is currently on screen, so a reload puts you back where you were. | Until you close the tab. |
| mm:scroll:<document> | Session storage | Your scroll position in a shared document, so your own reload restores it. Your position is yours; it does not move anyone else's view. | Until you close the tab. |
| mm:teleprompter:<meeting> | Session storage | Teleprompter state for the meeting you are presenting in. | Until you close the tab. |
Third parties
These services may store something in your browser of their own. We do not control their names or lifetimes, so we describe what they are for rather than listing keys we cannot promise are current.
- Clerk
- Authentication. Keeps you signed in and protects the sign-up form against automated abuse.
- Cloudflare
- Bot protection on our sign-up and sign-in forms, reached through Clerk. It runs adaptively, so it may not appear on every visit.
- Stripe
- Payments and fraud prevention. Card details are entered on Stripe's own hosted checkout page, not on ours, and never pass through our systems.
- Sentry
- Error reporting, so we find out when something breaks. Configured to not store IP addresses and to scrub sensitive data.
- Attaching a Google Doc to a presentation. Google's file picker and sign-in scripts load only when a presenter opens the Share document menu, and only on the meeting page — if you never open that menu, nothing from Google is loaded.
What we do not do
We do not use cookies or browser storage for advertising. We do not use them to build a profile of you, and we do not sell or share what is stored.
We do not run third-party analytics or tracking pixels. The only third parties that can store anything in your browser through Mirror | Mirror are the five listed above, and each is there to make a specific part of the product work.
We do not use cookies or browser storage to keep the audio, video or screen-sharing content of a meeting; that content is processed only for the duration of the meeting and discarded when it ends. If you choose to record a meeting, your own browser holds that recording while it is being made and saves the file to your computer — it is never sent to us.
Your choices
You can clear anything on this page at any time through your browser's settings — usually under a heading like “Cookies and site data”. Clearing it costs you only your remembered preferences; nothing is lost that cannot be set again.
You can also block cookies entirely, but the strictly necessary ones are what keep you signed in and keep you in a meeting across a page reload. Blocking those will stop the product working.
Preferences and per-meeting state never leave your device. Clearing them is a purely local act — there is nothing on our side to delete.
Changes to this policy
If we add or remove anything stored in your browser, we update this page in the same change that alters the code, and move the effective date above.