Legal documents

Cookie Policy

We use a minimal set of strictly-necessary cookies to operate the Service. Marketing cookies (Google Ads) and, when product analytics is enabled, PostHog analytics storage are set only after you press Accept on the consent banner — nothing marketing or analytics is stored until then, on either orgmcp.io or app.orgmcp.io. This page also lists the small amount of localStorage we rely on so the inventory is complete.

Effective
30 October 2026
Version
v3.3
Last updated
30 October 2026
Operator
Werkdata OÜ · Tallinn, Estonia
Need the signed PDF? Email legal@orgmcp.io.

Overview

A cookie is a small text file stored on your device when you visit a website. OrgMCP only uses cookies that are strictly necessary to deliver the Service you have explicitly asked for (signing in, remembering your active workspace, protecting OAuth callbacks against CSRF). Strictly-necessary cookies are exempt from the consent requirement under the EU ePrivacy Directive and the Estonian Electronic Communications Act; we still list them in full below for transparency.

Strictly necessary cookies

First-party cookies set by orgmcp.io and its app. subdomain.
NamePurposeLifetime
orgmcp_sessionSealed-session cookie issued by WorkOS AuthKit. AES-GCM encrypted with a per-environment secret. Without it you can't sign in.30 days
orgmcp_active_tenantStores the identifier of the workspace you most recently selected so you don't have to pick again on every page load.365 days
orgmcp_login_return_toRemembers the page you were heading to so we can return you there after sign-in. Set just before the login redirect.10 minutes
orgmcp_oauth_authorize_returnCarries the in-flight authorization request when you connect a third-party MCP client (e.g. Claude, ChatGPT, Cursor) and have to sign in first. Cleared once the connection completes.15 minutes

Third-party cookies on /billing

When you open the /billing page we embed Stripe's Checkout and Customer Portal via the js.stripe.com SDK. Stripe sets its own first-party cookies on the stripe.com domain to detect fraudulent activity, support the embedded flows, and complete payments. These cookies are governed by Stripe's own cookie notice (stripe.com/cookies-policy/legal); they are essential for the payment functionality and are not used by OrgMCP for analytics or marketing.

Local storage

In addition to cookies, the Service uses a small number of localStorageentries. localStorage is browser-side key/value storage that is not transmitted to our servers; it is listed here for completeness.

Browser-side localStorage entries.
KeyPurposeLifetime
orgmcp_cookie_notice_dismissedRecords that you closed the cookie banner so we don't show it on every page load. We deliberately use localStorage rather than a cookie so dismissing the banner does not itself write a tracking artefact.Until you clear browser storage
orgmcp_help_widget_openRemembers whether the in-app help widget is expanded or collapsed.Until you clear browser storage
orgmcp_ads_consent_v1Records your choice on the marketing-site consent banner (accepted or rejected) so we don't ask again. We deliberately use localStorage rather than a cookie so remembering your decision does not itself write a tracking artefact.Until you clear browser storage
orgmcp_ads_activation_v1:<workspace id>Set only after you accepted ads consent, once the app has reported the “OrgMCP Activation” conversion (your workspace's first source finished indexing or its first MCP tool call ran), so it is never reported twice from this browser.Until you clear browser storage

Google Ads tag & consent

Both the marketing site (orgmcp.io) and the application (app.orgmcp.io) load the Google Ads tag (AW-18467814155) so we can measure which advertising campaigns bring people to OrgMCP and attribute workspace signups and activations. We run it under Google Consent Mode v2: before the tag loads, all advertising and analytics storage signals (ad_storage, ad_user_data, ad_personalization, analytics_storage) are defaulted to denied. No advertising cookie is set, and no conversion is reported, until you press Accept on the consent banner; pressing Reject keeps everything denied. One decision covers both hosts — accepting on the marketing site carries over to the app via the orgmcp_ads_consent cookie below, so you are never asked twice. We do not load any Google Display, Partners, or other remarketing-network scripts. Product analytics, when enabled, is PostHog on EU cloud only — see the next section. We do not load Hotjar, Segment, or a session-replay SDK.

Consent-gated first-party cookies (set only after you press Accept, or, for the signup signal, only when a new workspace is created).
NamePurposeLifetime
orgmcp_ads_consentRecords your Accept/Reject choice on the consent banner and shares it across orgmcp.io and app.orgmcp.io (scoped to the orgmcp.io parent domain) so you are asked only once. Stores just granted or denied — no identifier.6 months
orgmcp_signup_conversionA short-lived, one-shot signal set by the server only when you create a new workspace, so the app can report the “OrgMCP Signup” conversion exactly once. Read and cleared on the next page load; never set on a login or a repeat visit. If you have not accepted ads consent, no conversion is reported.5 minutes

Product analytics (PostHog)

When this deployment is built with a PostHog project key, both orgmcp.io and app.orgmcp.io load PostHog's analytics SDK from PostHog Cloud EU (https://eu.i.posthog.com, Frankfurt). The SDK is not initialised, and no analytics event is sent, until you press Accept. Until that moment PostHog is not loaded; the integration is configured so that any pre-consent state uses in-memory persistence only and writes no cookie. Pressing Reject keeps analytics off.

After you accept, we capture page views, page leaves, and autocaptured interactions (clicks). Element text and attributes are masked so a visible email address is not copied onto an event. Signed-in use is tied to your user id and the active workspace id only — we do not send your email address, name, or workspace name. Campaign labels already stored in the first-party omcp_attr cookie (UTM parameters, referrer host, landing path) are attached as event properties. OAuth code and similar secrets are stripped from page URLs before they are sent. Session replay is off.

Staging and local development do not load PostHog. If the project key is unset, the SDK is left out entirely.

PostHog storage, written only after you press Accept.
NamePurposeLifetime
ph_<project>_posthogFirst-party PostHog cookie (and matching localStorage) holding an anonymous or user-id distinct id and the session id, scoped to orgmcp.io so the marketing site and the app share one analytics identity. Set only after Accept.Up to 1 year
__ph_opt_in_out_<project>PostHog's own record of the opt-in, stored in localStorage (not a cookie). It mirrors the choice you already made on our banner.Until you clear browser storage

How to disable cookies

Strictly-necessary cookies are required to sign in and use the Service. You can refuse marketing and analytics cookies with Reject on the banner and keep using OrgMCP. You can also browse the marketing site and the documentation with cookies disabled entirely; sign-in will not work without the session cookie.

Changes to this policy

We update this Cookie Policy whenever the underlying cookie or localStorage inventory changes. Material changes are also announced via the cookie banner.

Contact

Questions: privacy@orgmcp.io.

Changelog

  • v3.3 — 30 October 2026 — Documented consent-gated PostHog product analytics on orgmcp.io and app.orgmcp.io (EU cloud). The SDK loads only after Accept, identifies signed-in use by user id and workspace id, and does not send email addresses. Added the ph_<project>_posthog cookie, set only after Accept.
  • v3.2 — 27 October 2026 — Added the consent-gated “OrgMCP Activation” Google Ads conversion on app.orgmcp.io and the orgmcp_ads_activation_v1:<workspace id> localStorage key that keeps it to one report per workspace.
  • v3.1 — 22 September 2026 — Extended the Google Ads tag (AW-18467814155) and Consent Mode v2 to the application host app.orgmcp.io so a workspace signup can be attributed, still gated on your consent. Added the orgmcp_ads_consent cookie (shares one consent decision across the marketing site and app) and the short-lived, one-shot orgmcp_signup_conversion signal cookie (fires the signup conversion once, only on new workspace creation and only with consent).
  • v3.0 — 22 September 2026 — Documented the Google Ads tag (AW-18467814155) on the marketing apex, loaded under Google Consent Mode v2 with all advertising/analytics signals defaulted to denied until you accept. Added the orgmcp_ads_consent_v1 localStorage key that records your banner choice.
  • v2.0 — 12 May 2026 — Added a localStorage inventory (the previous statement that the marketing site set “no cookies at all” was misleading once the cookie banner shipped). Documented Stripe's Checkout cookies on /billing. Referenced the Estonian Electronic Communications Act alongside the EU ePrivacy Directive. Linked to the canonical Privacy Policy from the contact block.
  • v1.0 — 1 April 2026 — Initial publication.