Back to home
Legal · Cookie Policy

Cookie Policy

Last updated · June 4, 2026

This Cookie Policy explains how EMOR Social (the “Service”), operated by EMOR AI, LLC(“EMOR,” “we,” “us,” or “our”), uses cookies and similar technologies. EMOR Social is an AI-powered social media management platform that lets you plan, generate, schedule, publish, and analyze content across social networks and manage a unified inbox. This page describes the small set of technologies the Service relies on in your browser, why we use them, and the choices you have.

The short version. EMOR Social uses only a handful of strictly necessary cookies — all set by Clerk, our authentication provider — to keep you signed in and to keep your session secure. We do not use advertising cookies, analytics cookies, or cross-site or third-party behavioral tracking cookies, and we do notsell or share personal information for advertising. A few interface preferences (such as light/dark theme and whether the sidebar is collapsed) are stored in your browser’s local storagerather than in cookies — they never leave your device and are never transmitted to us.

1. About This Policy

This Cookie Policy is a supplement to, and forms part of, our Privacy Policy. It provides additional detail about the cookies and similar browser technologies used on the EMOR Social marketing site and within the signed-in application. Where this Policy uses a term that is defined in our Privacy Policy or our Terms of Service (for example, “tenant,” “workspace,” or “subprocessor”), that term has the same meaning here.

EMOR Social is currently offered as a beta / early-access product and is provided “as is.” Features, plan inclusions, and the technologies the Service uses are still being finalized. We keep this Policy aligned with what the Service actually does today; if our use of cookies changes, we will update this page as described in Section 10.

If anything in this Policy conflicts with a more specific notice we give you at the point of collection, the more specific notice controls for the situation it describes.

2. What Cookies & Similar Technologies Are

A cookieis a small text file that a website asks your browser to store on your device. On each subsequent request to that site, the browser sends the cookie back, which lets the site recognize your session across page loads — so, for example, you stay signed in as you navigate the dashboard instead of being asked to log in on every page.

Cookies are commonly described by a few characteristics:

  • First-party vs. third-party. A first-party cookie is set by the domain you are visiting; a third-party cookie is set by a different domain (often used for cross-site advertising). EMOR Social uses no third-party advertising cookies.
  • Session vs. persistent. A session cookie is deleted when you close your browser; a persistent cookie remains until it expires or you delete it.
  • Strictly necessary vs. optional. A strictly necessarycookie is one without which a service you have requested cannot function (for example, staying logged in). Other categories — preference, analytics, and marketing cookies — are optional and, where required by law, are only set with your consent. EMOR Social currently uses only strictly necessary cookies.

Local storageis a related but distinct browser technology. Like a cookie, it stores small pieces of data on your device, but — unlike a cookie — that data is not automatically sent to a server with each request. It simply lets the application remember a preference locally. EMOR Social uses local storage for a few interface preferences, described in Section 5. The Service does not use other tracking technologies such as web beacons, tracking pixels, or fingerprinting scripts.

3. Categories We Use

Cookies are conventionally grouped into four categories. Here is exactly which categories EMOR Social does — and does not — use:

  • Strictly necessary — YES. These cookies are essential to deliver the Service you have asked for. On EMOR Social they are limited to authentication, session continuity, and security (CSRF protection), and are all set by our identity provider, Clerk. They are exempt from consent requirements because the Service cannot work without them, and they cannot be switched off through a preference control. See Section 4 for the full list.
  • Preference — NOT via cookies. We do not use preference cookies. Where we remember an interface choice (such as your theme or sidebar state), that choice is stored in your browser’s local storage instead, never transmitted to us. See Section 5.
  • Analytics / performance — NONE. EMOR Social does notcurrently use analytics or performance cookies of any kind — no Google Analytics, no Microsoft Clarity, no heatmaps, no session replay, and no product-analytics SDKs that set cookies. If we introduce analytics in the future, we will add a consent control first (see Sections 7 and 9).
  • Marketing / advertising — NONE. EMOR Social does not use advertising or marketing cookies, ad pixels, retargeting tags, or any cross-site behavioral tracking. We do not build advertising audiences and do not sell or share your information for advertising.

4. Cookies We Use

Authentication and session security on EMOR Social are handled by Clerk, our identity provider. The strictly necessary cookies Clerk sets are required for the Service to function — you cannot sign in or stay signed in without them, and they cannot be disabled through a preference banner. EMOR never stores your social network or account passwords; authentication is managed by Clerk and the cookies below carry only session and validation tokens, not credentials.

The table below lists the cookies in use as of June 4, 2026. Cookie names and durations are controlled by Clerk and are approximate; the exact set present in your browser can vary with your sign-in method and account configuration.

CookieProviderPurposeCategoryDuration
__sessionClerkCarries your authenticated session so you stay signed in as you move between pages of the Service.Strictly necessarySession
__client_uatClerkRecords your authentication state (the "user authenticated at" timestamp) so the application can render the correct signed-in or signed-out view and refresh sessions reliably.Strictly necessary~1 year
__clerk_db_jwtClerkValidates your session token on each request and helps protect against cross-site request forgery (CSRF) and session-hijacking attacks.Strictly necessarySession
__clerk_* (e.g. __clerk_db_jwt_*, __refresh_*)ClerkA small family of Clerk-prefixed cookies used for session continuity, multi-factor authentication, satellite-domain handoff, and CSRF protection. The exact set depends on your account configuration and sign-in method.Strictly necessarySession to ~1 year

Clerk processes the data associated with these cookies as a service provider to EMOR, under its own privacy policy. Clerk is one of our subprocessors and is listed, together with the rest of the technologies that help power the Service, on our Subprocessors page. None of the cookies above are used to profile you across other websites or to serve advertising.

5. Interface Preferences (Local Storage)

So that the application looks and behaves the way you expect from one visit to the next, EMOR Social stores a few interface preferences in your browser’s local storage rather than in cookies. Because they live in local storage, these values are never sent to our servers, are not attached to network requests, and are not used to identify, profile, or track you across sites. They are purely cosmetic and convenience settings:

  • Theme. Whether you have chosen light or dark mode, so the app renders in your preferred theme immediately and without a flash of the wrong colors on load.
  • Layout and sidebar state. Small interface choices such as whether the navigation sidebar is expanded or collapsed, so your workspace looks the same when you return.

You can clear these preferences at any time by clearing your browser’s site data for the EMOR Social domain, or by using your browser’s developer tools to remove individual local-storage keys. Clearing them simply resets the affected setting to its default the next time you load the app; it does not delete any of your content, connected accounts, or account data, which are stored securely in your workspace and isolated from other tenants by Postgres row-level security.

6. Third-Party & Connected-Network Cookies

Within the EMOR Social application, we do notembed third-party advertising tags, social “like” buttons, or other third-party trackers that would set cookies as you browse. The only cookies set while you are using the Service are the strictly necessary Clerk cookies described in Section 4.

There is one situation in which another company’s cookies may be set, and it is initiated by you, not by EMOR:

  • Connecting a social account. When you connect an Instagram, Facebook, TikTok, YouTube, Pinterest, X (Twitter), LinkedIn, Google Business Profile, Threads, or Reddit account, the connection is brokered through our integration provider, Zernio (Late.dev), and the social network shows you its own OAuth authorization screen on its owndomain. While you are on that network’s pages, that network — and, where applicable, Zernio — may set cookies on your browser under their respective cookie and privacy policies. Those cookies are outside EMOR’s control: we do not set them, cannot read them, and cannot delete them. EMOR receives back only the access/refresh tokens and basic profile metadata needed to publish on your behalf; we never receive your social-network password.

To understand and manage cookies that a social network or our integration provider sets during connection, please review their policies. Zernio (Late.dev) and the social networks are described in our Subprocessors page, and you can manage or revoke a connected account at any time both within EMOR Social and in the security settings of the network itself.

7. What We Don’t Use

For the avoidance of doubt, and unlike many SaaS products, EMOR Social currently does not use any of the following:

  • No advertising or marketing cookies. No ad pixels, no retargeting or remarketing tags, no conversion-tracking cookies.
  • No analytics or performance cookies. No Google Analytics, no Microsoft Clarity, no heatmaps, and no session-replay tooling that sets cookies.
  • No cross-site or behavioral tracking. We do not follow you across other websites or apps and do not build behavioral profiles for advertising.
  • No selling or sharing for advertising.We do not “sell” or “share” personal information for cross-context behavioral advertising as those terms are used under California and other U.S. state privacy laws.
  • No fingerprinting. We do not use device- or browser-fingerprinting techniques to identify you.

If this ever changes — for example, if we add privacy-respecting analytics — we will update this Policy and put a consent control in place before any non-essential cookie is set, as described in Sections 9 and 10.

8. Managing Cookies

You are always in control of cookies through your browser. Most browsers let you view the cookies stored, delete some or all of them, and block cookies from being set in the future. Where to find these controls varies by browser; consult the help pages for Chrome, Firefox, Safari, or Microsoft Edge.

Important consequence. Because the only cookies EMOR Social sets are strictly necessaryfor authentication and session security, the signed-in parts of the Service cannot function if you block or delete them. If you disable these cookies, you will not be able to sign in or remain signed in, and the dashboard will not work. There is no separate “reject” toggle for them precisely because the Service you requested depends on them. You can, of course, still browse the public marketing pages.

To remove the cookies set by EMOR Social, sign out and then clear cookies and site data for the EMOR Social domain in your browser settings. To remove the interface preferences described in Section 5, clear your browser’s site data for the same domain.

9. Regional Notes (EU/UK ePrivacy, GPC/DNT)

9.1 EU/UK ePrivacy and the GDPR

Under the EU ePrivacy Directive, the UK’s Privacy and Electronic Communications Regulations (PECR), and the GDPR/UK GDPR, prior consent is required before non-essentialcookies may be stored on or read from a user’s device. Cookies that are strictly necessaryto provide a service the user has explicitly requested — such as keeping an authenticated user signed in — are exempt from this consent requirement.

Because EMOR Social uses only strictly necessary cookies and sets no analytics, preference, or marketing cookies, no cookie consent banner is legally required, and we do not display one. The legal basis for the strictly necessary cookies is our legitimate interest in, and the necessity of, delivering a secure, functioning Service that you have asked to use.

If we ever introduce non-essential cookies(for example, optional analytics), we will, before setting any such cookie, implement a compliant consent mechanism that lets EU/UK and other applicable visitors give or withhold consent, make rejecting as easy as accepting, and record that choice — and we will update this Policy accordingly.

9.2 Global Privacy Control (GPC) and Do Not Track (DNT)

Global Privacy Control (GPC).Some browsers and privacy extensions send a GPC signal indicating that you wish to opt out of the “sale” or “sharing” of your personal information and of certain tracking. EMOR Social does not sell or share personal information for advertising and runs no advertising or analytics cookies, so there is no such activity for a GPC signal to stop. We nonetheless respect the intent behind GPC: if we later introduce any non-essential or analytics technologies, a present GPC signal will be treated as an opt-out of them. How we handle GPC and other opt-out preference signals more broadly is described in our Privacy Policy.

Do Not Track (DNT).Some browsers can send a legacy “Do Not Track” signal. Because there is no common industry standard for interpreting DNT, and because EMOR Social performs no cross-site tracking and runs no analytics cookies in the first place, there is nothing for the Service to disable in response to a DNT signal. A visitor is not tracked regardless of whether DNT is set.

10. Changes to This Policy

We may update this Cookie Policy from time to time — for example, to reflect changes in the technologies we use, in our service providers, or in applicable law. When we make changes, we will revise the “Last updated” date at the top of this page. If a change is material — in particular, if we begin using any non-essential cookie — we will provide more prominent notice (such as a notice within the Service or a consent control) before the change takes effect, where required by law. Your continued use of the Service after an update takes effect means you acknowledge the revised Policy. We encourage you to review this page periodically; it is always available from the footer of our marketing site.

11. Contact

If you have questions about this Cookie Policy or about how EMOR Social uses cookies and similar technologies, please contact us:

EMOR AI, LLC
563 NW 31st Avenue
Gainesville, FL 32609
Phone: (305) 582-0181
Legal: legal@emorai.com
Support: support@emorai.com

EMOR Social is one of several products operated by EMOR AI, LLC. For more about how we handle your information generally, see our Privacy Policy, the technologies that help power the Service on our Subprocessors page, and the terms governing your use of the Service in our Terms of Service.