Cookie Policy
Last updated: May 20, 2026
1. What is a cookie?
A cookie is a small text file stored on your device by your web browser. We also use related technologies such as local storage, session storage, and pixel identifiers in HTTP requests; for simplicity, we refer to all of these as “cookies” on this page. A few of the items in the table below (emor-theme, emor-cookie-consent, emor-cookie-visitor-id) are browser local-storage keys rather than true cookies, but we disclose them here for completeness.
2. Categories of cookies we use
2.1 Strictly necessary cookies
These cookies are required to deliver core functionality of the Service. They are exempt from consent because the Service cannot work without them. You cannot opt out of these without losing access to the dashboard.
- Authentication & session — set by Clerk to keep you signed in, manage multi-factor authentication, and prevent session hijacking. Examples:
__session,__client_uat. - CSRF and security tokens— set by our Next.js application to mitigate cross-site request forgery and other web-application attacks.
- Platform / hosting — set by Vercel for routing, edge caching, and bot protection.
- Payment processing — set by Stripe when you enter the checkout flow, used for fraud prevention and session continuity. These cookies are only set on Stripe-hosted pages and on EMOR pages that embed Stripe elements.
- Consent storage— set by EMOR to remember the cookie choice you made in the consent banner so we do not re-ask on every visit (
emor-cookie-consent) and to link your choices in our consent audit log (emor-cookie-visitor-id). Storing your preference is itself a necessary function, so these are not gated by consent.
2.2 Preference cookies
These remember a choice you made so the Service behaves the way you expect. They do not track you and are not shared with anyone.
- Theme —
emor-themestores whether you selected the light or dark dashboard theme.
2.3 Operational telemetry
These identifiers help us monitor application health and diagnose errors. They do not profile your behavior across sites or build advertising audiences.
- Error and performance monitoring — set by Sentry to associate front-end errors and performance traces with a specific session for debugging. Sampled at a small percentage of traffic. Our Sentry integration is limited to error and performance data — we do notenable Sentry’s session-replay feature. (Session replay on the marketing site is provided by Microsoft Clarity and is consent-gated; see Section 2.4.)
2.4 Analytics cookies (consent-gated)
With your consent, EMOR Voice uses two analytics tools on its public marketing pages to understand which pages and content visitors find useful. These tools do not load at all until you choose “Accept all cookies” in the consent banner described in Section 4. If you reject non-essential cookies, or ignore the banner, none of the cookies in this category are set. They never run on the signed-in dashboard, the admin console, onboarding, or any other tenant-facing surface.
- Google Analytics 4 — provided by Google for aggregate traffic measurement: page views, sessions, approximate location derived from IP address, device and browser type, and referral source. We enable IP anonymization. We do not use Google Analytics for advertising or remarketing.
- Microsoft Clarity — provided by Microsoft for product analytics, including heatmaps and session replay. Session replay records a play-back of page interactions on the marketing site (mouse movement, scrolling, clicks, and page navigation) so we can find confusing layouts and broken flows. Clarity masks text you type into form fields by default, and we do not use it to capture form-field contents. Clarity also sets the
MUIDidentifier, which Microsoft uses across its own services.
3. Cookie reference table
The table below lists the named cookies and similar identifiers in use as of May 20, 2026. Durations are approximate and set by the relevant provider; the analytics rows are only ever created if you accept.
| Cookie | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| __session, __client_uat | Clerk | Keeps you signed in, manages multi-factor authentication, and prevents session hijacking. | Strictly necessary | Session to ~1 year |
| __Host- / CSRF token | EMOR (Next.js) | Mitigates cross-site request forgery and other web-application attacks. | Strictly necessary | Session |
| Vercel platform cookies | Vercel | Request routing, edge caching, and bot protection. | Strictly necessary | Session to ~1 day |
| __stripe_mid, __stripe_sid | Stripe | Payment fraud prevention and checkout session continuity. Set only on checkout pages and pages that embed Stripe elements. | Strictly necessary | __stripe_sid ~30 min; __stripe_mid ~1 year |
| emor-cookie-consent, emor-cookie-visitor-id | EMOR | Remembers your accept/reject choice so we do not re-ask, and links your consent choices in our audit log. Storing your choice is itself necessary, so this is exempt from consent. | Strictly necessary | Until you clear browser storage |
| emor-theme | EMOR | Remembers your light/dark theme preference for the dashboard. | Preference | Until you clear browser storage |
| Sentry session identifier | Sentry | Associates a front-end error or performance trace with a session so we can diagnose it. Sampled at a small percentage of traffic. | Operational | Session to ~30 days |
| _ga, _ga_* | Google (Analytics 4) | Distinguishes visitors and sessions for aggregate marketing-site traffic measurement. Loaded only after you accept. | Analytics | Up to 2 years |
| _clck, CLID | Microsoft (Clarity) | Persists a Clarity user identifier for the marketing site so heatmaps and session replays can be attributed. Loaded only after you accept. | Analytics | ~1 year |
| _clsk | Microsoft (Clarity) | Links the page views within a single Clarity session. Loaded only after you accept. | Analytics | ~1 day |
| MUID | Microsoft (Clarity) | A Microsoft identifier that Clarity sets and that Microsoft also uses across its own services. Loaded only after you accept. | Analytics | ~1 year |
4. Your choices and managing consent
On your first visit, EMOR Voice shows a cookie banner with two equally-weighted choices:
- Accept all cookies— permits the analytics cookies described in Section 2.4.
- Reject non-essential— only the strictly- necessary and preference cookies are set. No analytics tool and no session replay loads.
Analytics tools do not load before you make a choice, and they do not load at all if you reject. Your decision is stored in your browser and recorded on our servers, with the date and the version of this policy you saw, so we can honor it and demonstrate it if asked.
You can change your decision at any time. Select Manage cookie preferences in the footer of any marketing page, or use the button near the top of this page, to reopen the banner and switch your choice. Withdrawing consent is as easy as granting it.
Separately, most browsers let you view, manage, and delete cookies through their settings. Disabling strictly-necessary cookies will break the dashboard — you will not be able to sign in or check out. To clear cookies set by EMOR Voice, sign out of your dashboard and clear cookies and site data for the emorvoice.com domain in your browser preferences.
5. Global Privacy Control and Do Not Track
Global Privacy Control (GPC). Some browsers and privacy extensions send a GPC signal that tells a website you want to opt out of tracking. EMOR Voice honors it.If your browser sends a GPC signal, the analytics tools described in Section 2.4 will not load — even if you previously chose “Accept all cookies” on this device. While the signal is present, GPC acts as an automatic withdrawal of analytics consent.
Do Not Track (DNT).Some browsers send the older “Do Not Track” signal. Because there is no industry standard for interpreting it, and because EMOR Voice runs no analytics at all unless you opt in, we do not separately act on the DNT signal. A visitor who has not accepted analytics cookies has no analytics tracking regardless of any signal. You can also withdraw a prior acceptance at any time using the “Manage cookie preferences” link described in Section 4.
6. Changes to this policy
We may update this Cookie Policy from time to time — for example, if we add, remove, or change a tracker. We will update the “Last updated” date and, where the change is material, provide a notice through the Service.
7. Contact
EMOR AI, LLC
563 NW 31st Avenue
Gainesville, FL 32609
Phone: (305) 582-0181
Email: legal@emorai.com