In short: Merget's sites use cookies and browser storage to keep you signed in, to remember how you left a page, to remember your privacy choice, and for analytics with session recording. On the website at merget.ai, analytics and session recording start when a page loads. On the dashboard, analytics start when a page loads, whether or not you are signed in, and session recording starts only after you sign in; when you sign in, the dashboard's analytics from before become part of your account's record. The website shows a notice on your first visit, and you can opt out of its analytics at any time under Privacy choices, at the foot of every page. There are no advertising cookies. This notice lists each site's cookies and the browser storage it uses, by name or by the prefix a family of keys shares. The Privacy Statement at https://merget.ai/legal/privacy-statement says what the data is used for.
1. What this notice covers
A cookie is a small record a site asks your browser to keep and send back. Browser storage (local storage and session storage) is similar, except that your browser never sends it anywhere on its own; the page reads it. "Session" below means the record goes when you close the tab (session storage) or when the cookie's own lifetime ends. "Strictly necessary" means the site cannot do what you asked without it, such as keeping you signed in.
This notice covers merget.ai, auth.merget.ai, sema.merget.ai and demo.merget.ai, the Cal.com booking window that merget.ai opens, and the Stripe pages the dashboard sends you to. The HTTP API and the MCP server at sema.merget.ai use bearer tokens, not cookies.
2. Cookies and storage by site
Website
merget.ai measures how visitors find and use it, with PostHog as its analytics service. Analytics and session recording start when a page loads. A recording shows the page as you saw it and what you did on it; everything you type into a field is hidden before the recording leaves your browser, and the booking window is not recorded. The analytics script loads from merget.ai's own address, and its requests pass through merget.ai's server, which removes your cookies from them before they reach PostHog. The website loads no tag manager and no advertising script.
The first-visit notice links this policy and the Privacy Statement. Scrolling or waiting five seconds hides it for this tab session without saving a choice. OK dismisses it. Configure opens separate switches for usage analytics and session recording. Turn off both and select Save choices to opt out in this browser. The page clears analytics cookies and storage. The server deletes mg_vid and sets no new ID while both categories are off. Privacy choices, at the foot of every page, lets you change these settings and shows your analytics ID so that you can ask for its data to be deleted. If your browser sends a Global Privacy Control signal, the panel confirms that Merget honored it.
| Name | Kind | Purpose | Lifetime |
|---|---|---|---|
mg_vid | Cookie, first party, HttpOnly, Secure; written only by merget.ai's server | The website's analytics ID (anonymous until it is linked to an account or a booking): a random value that tells one browser's visits apart from another's. The page asks merget.ai's server for it once per tab and hands it to the analytics when they hold no ID of their own, so the ID lasts even in browsers that clear what scripts store after 7 days. No script can read or change it, and the server does not set it while you have opted out. | 1 year, renewed on each visit; deleted when you opt out |
mg_privacy | Cookie, first party, Secure; written only by merget.ai's server, read by the page | Saves ack for both categories, analytics or replay for one, and out for neither. While it says out, merget.ai's server sets no analytics ID and the page loads no analytics. | 1 year, renewed on each visit; set again if it is gone while mg.privacy still holds your answer |
mg.privacy | Local storage, preference | A copy of your answer to the notice and when you gave it, so the page can act on it at once, and so it can record your answer in mg_privacy again if that cookie is gone. | Until you clear your browser's storage; Safari removes it after 7 days without a visit, and the page writes it again from mg_privacy |
mg.noticeDismissed | Session storage, preference | Remembers that the notice closed after five seconds or a scroll. | The tab session |
ph_phc_*_posthog, ph_phc_*_posthog_cpm | Cookie, first party, Secure; written by the analytics script, on merget.ai only | The analytics service's state for this browser: its copy of the analytics ID and a device ID, the current session and whether it is recorded, whether the visits are linked to a profile, the address and site you first arrived from, and a click ID built from the fbclid that Meta's apps, such as Facebook and Instagram, add to links, if the link that brought you carried one (_cpm records which of that state the cookie carries). | Up to 1 year, renewed while you visit; Safari keeps cookies written by scripts for at most 7 days |
ph_* | Local and session storage, analytics | The rest of the analytics service's state: the properties sent with every event, such as the site or campaign you first arrived from, which session and tab the events belong to, and the part of a session recording not yet sent, kept in the tab between pages. | Local storage until you clear it (Safari removes it after 7 days without a visit); session storage, the tab |
__ph_opt_in_out_phc_* | Local storage, analytics control | Written by the analytics script when you opt out: it tells the script to capture nothing in this browser. | Until you clear your browser's storage; Safari removes it after 7 days without a visit |
mg.ctx | Session storage, analytics | What merget.ai's server answered when the tab first asked: the analytics ID, the country and the network you connect from, and whether the browser holds a dashboard session. Later pages in the tab read it instead of asking again. | The tab |
mg.internal | Local storage, analytics | Set only in the browsers of Merget's team, by opening a page with ?mg_internal=1; marks their visits as internal so that reports leave them out. ?mg_internal=0 removes it. | Until removed, or until you clear your browser's storage; Safari removes it after 7 days without a visit |
merget-signed-in | Cookie, first party, HttpOnly, Secure; set by the dashboard on merget.ai and its subdomains | A hint that this browser holds a Merget dashboard session. merget.ai's server checks only whether it is present, and the website's analytics record that with the visit. It is never a credential: nothing signs you in with it. | 30 days, renewed while you use the dashboard; removed when you sign out |
scroll:* | Session storage, preference | For each page you open (scroll: and the page's path), how far down it you had scrolled, so a reload, or going back or forward to it, returns you to the same place. Kept in this tab only. | The tab |
| Cal.com's cookies and storage | Third-party cookies and browser storage, set by Cal.com (app.cal.com) inside the booking window | Book a call opens a booking window that is Cal.com's page, loaded only when you open it. Cal.com sets the cookies and storage its booking page uses: a bot-protection cookie, an ID that holds the time you pick while you finish booking, and display settings such as the theme. Cal.com runs booking windows on many other websites. Its privacy policy at https://cal.com/privacy covers what it sets. Merget does not set or read them. | Set by Cal.com; the bot-protection cookie lasts 30 minutes |
What the website's analytics record is described in the Privacy Statement under Website. When usage analytics is on, the website passes its ID to Cal.com in the booking window's web address, so that Merget can link a call you book to your visits. Following Sign up or Log in with usage analytics on adds the same ID to the dashboard's address after a #, a part of the address your browser does not send to any server; the dashboard keeps it in sema.telemetry.handoff until it has linked your website visits to your account, unless the ID is already linked to another account, and from then on later visits from this browser, whoever makes them, are linked to it too. Turning off usage analytics stops both handoffs. Following Sign up or Log in with it off makes the dashboard drop an ID the website handed to that tab earlier. A dashboard tab that received the ID before you opted out can still link it if you finish signing in there without following Sign up or Log in again. Likewise, a booking window opened before you opted out already carries the ID, and a call you book in it is still linked to your visits; reload the page before you book to open one without it.
Sign-in
auth.merget.ai is the Merget account page: sign-in, sign-up, two-factor setup and agent consent. It sets no cookie of Merget's own. Everything it keeps lives in your browser's storage, where only the page can read it.
| Name | Kind | Purpose | Lifetime |
|---|---|---|---|
mc.forge.session, mc.forge.refresh | Local storage, strictly necessary | Your session with the account page and the token that renews it, so a reload does not sign you out. | Until you sign out or the session ends |
mc.forge.* (among them emaillink, emailwait, emailproven, emailverified, passwordreset, verifywait, factors-changed, resetorigin, signedout, storage-probe) | Local or session storage, strictly necessary | Where you are in an email link sign-in, a password reset or an email verification, so the tab that started it can finish it; whether you signed out here; and whether this browser's storage works at all. | The flow, or the tab |
merget.auth.* (among them step, redirect-pending, handoff-spent, signed-in-here, first-factor-intent, email-sent, new-account, stepup, profile-draft, recovery-pending, recovery-used, recovery-replaced, signup-recovery-*, survey-skipped, build-reloaded, skew-probe, skew-notice) | Local or session storage, strictly necessary | The state of a sign-in in progress: which step you are on, where to return to, which sign-in method you started with, a profile you have started but not saved, whether you saved or replaced your recovery codes, whether the optional survey was skipped, and whether a clock-skew notice was shown. | The flow, or the tab |
| Identity Platform storage | Browser storage (IndexedDB), strictly necessary, set by Google's sign-in library | The sign-in state Google Identity Platform keeps for the password, Google and GitHub sign-in methods. | Until you sign out |
| Google reCAPTCHA | Google's own cookies and storage | Tells sign-in attempts from people apart from automated ones. The badge on the page links Google's privacy policy and terms. | Set by Google |
Each browser remembers when you last confirmed your second factor; the account page asks again every 30 days, per browser.
Dashboard
sema.merget.ai is the Merget dashboard. It sets two cookies, one that keeps you signed in and one that tells the website you are, keeps its preferences and its analytics identifiers in local and session storage, and, while you sign in from the website, keeps the website's analytics ID in session storage.
| Name | Kind | Purpose | Lifetime |
|---|---|---|---|
__Host-Http-merget-refresh | Cookie, first party, HttpOnly, Secure, strictly necessary | Holds the refresh token that renews your session, so you stay signed in across tabs, reloads and browser restarts. Only the dashboard's own server reads it; no script can. | Until the token expires, at most 30 days; cleared at sign-out |
merget-signed-in | Cookie, first party, HttpOnly, Secure, on merget.ai and its subdomains | Tells merget.ai that this browser holds a dashboard session; the website's analytics record whether it is present. A hint only, never a credential: nothing signs you in with it. | 30 days, renewed each time the dashboard loads your account; removed at sign-out |
sema.forge.* (session, signing_out, signed_out, probe, auto_starts), sema.pkce, sema.pending_link, sema.pending_setup, sema.github.setup_started, sema.billing.checkout_started, sema.preload_reload_at | Local or session storage, strictly necessary | Your signed-in state in this browser, a sign-in or sign-out in progress, a GitHub link or install you started and have not finished, and a checkout you opened. | The flow, or until you sign out |
sema.last_org, sema.rail, sema.kbd_tips, sema.theme, sema.graph.colorBy, sema.graph.treePaneWidth, sema.graph.lastRepo.*, sema.queue.orderPaneWidth, sema.queue.land.dismissed | Local storage, preferences | The organization you opened last, whether the sidebar stays expanded, keyboard tips, the theme, pane widths, how the graph is colored, the repository you opened last in each organization's graph, and notices you dismissed. Stored in this browser only. | Until you clear your browser's storage |
sema.snap.* | Session storage, functional | A copy of what the home, merge queue, runs and analytics pages last showed you, so that a reload paints them at once while they load again. A copy more than an hour old is not shown. | The tab; cleared when you sign out |
ph_* (PostHog) | Local and session storage, analytics | The analytics service's state for this browser: its identifiers for the browser, the session and the tab; the address of the first page you opened here and the site that sent you to it; once you sign in, your account's id, email address, name, username and products, and the organization you are working in, with your role in it, its name and its seat counts; the part of a session recording not yet sent, kept in the tab between page loads; and the support window's state (ph_conv_*: the conversation, the ticket you opened and whether the window is open). If local storage is unavailable, all of it lasts only while the page is open; the dashboard never lets the service fall back to a cookie. | Local storage until you clear it; signing out removes your account's and organization's details and the support window's state, and keeps the browser's identifier. Session storage, the tab |
sema.telemetry.probe, sema.telemetry.reset | Local storage, analytics | Whether the analytics can keep their identifiers in local storage (probe, removed as soon as it is written), and a sign-out the analytics have not yet seen, so that their next start forgets your account (reset). | A moment (probe); until the analytics next start (reset) |
sema.telemetry.handoff | Session storage, analytics | The website's analytics ID, carried over when you follow Sign up or Log in on merget.ai, so that once you sign in the dashboard can link your website visits to your account. The dashboard removes it from the page's address as soon as it reads it. | Until the visits are linked, the tab closes, or you follow Sign up or Log in after opting out |
What the analytics record, and how session recordings are masked before they leave your browser, is described in the Privacy Statement under Analytics and support. Recording starts only after you sign in, and never on the pages that complete a sign-in or a GitHub installation. The service receives no cookie from Merget and never your sign-in token.
Demo
demo.merget.ai is a playground with simulated data. It records no analytics and no session recordings. Who may open it is controlled by Cloudflare Access, which sets its own cookies under Cloudflare's policy.
| Name | Kind | Purpose | Lifetime |
|---|---|---|---|
sema_demo | Cookie, first party, HttpOnly, strictly necessary | Identifies your demo session, so the demo keeps the world you are looking at. | 1 hour |
merget-demo-refresh | Cookie, first party, HttpOnly, strictly necessary | Keeps the demo's simulated sign-in going, as the dashboard's refresh cookie does. | At most 30 days; cleared when the demo world resets |
merget.demo.journey | Session storage | Which guided scenario you are in and which steps you completed. | The tab |
Stripe Checkout and billing portal
Upgrading a plan, paying for extra credits and managing billing happen on pages Stripe hosts, on Stripe's domains. Stripe sets its own cookies there, for fraud prevention and to run the page, under Stripe's cookie policy at https://stripe.com/legal/cookies-policy. Merget sets no cookie on those pages and never sees your card details.
3. Your controls
- Opt out on the website. Open Configure in the notice or Privacy choices in the footer. Switch off Usage analytics and Session recording, then select Save choices. This deletes
mg_vidand the analytics cookie and storage; whilemg_privacysaysout, merget.ai's server sets no analytics ID. To turn the analytics back on, change your choice under Privacy choices. The choice is kept in themg_privacycookie for a year from your last visit and in this browser's storage (mg.privacy); while either still holds it, the page records it again in the other, so deleting the cookies alone does not undo it, except in Safari after 7 days without a visit, when Safari has already erased the storage. To forget it, delete merget.ai's cookies and site data together. - Global Privacy Control. Merget treats the signal as a request to opt out of the sale or sharing of personal information and of targeted advertising. Merget does neither on any of its sites, so the signal has nothing to switch off: the website's analytics, which PostHog processes for Merget as its service provider, continue, and each event records that your browser sent the signal. To stop them, turn both categories off under Privacy choices. A script that sells or shares personal information, or serves targeted advertising, will not run where the signal is present if Merget ever adds one.
- Do Not Track. Merget's sites do not respond to Do Not Track signals; the website's analytics run the same with or without one. Use Privacy choices to turn them off.
- Browser settings. You can block or delete cookies and storage in your browser. Deleting merget.ai's cookies ends the analytics ID that browser held, usually from the next page you open: unless you have opted out, that page gets a new ID from merget.ai's server and removes the old one from the analytics' storage. A tab that was already open, or a page that cannot reach the server within half a second, keeps using the old ID from this browser's storage until a later page gets the new one; to end it at once, close merget.ai's tabs and delete its cookies and site data together. Deleting the cookies alone does not forget an opt-out while
mg.privacystill holds it (in Safari, not after 7 days without a visit); deleting the cookies and site data together does: the notice appears again and the analytics start as on a first visit, so opt out again afterwards. Blocking the dashboard's refresh cookie or storage signs you out when the page closes; blocking the demo's cookie resets the demo on every visit. - Analytics data. The dashboard's analytics identifiers live in your browser's local storage, and for the tab in session storage, and go when you clear them. To have the analytics, session recordings and support reports held about you deleted from the analytics service, and from Merget's training datasets, write to support@merget.ai; deleting your account does not remove them from the analytics service on its own. Without an account, copy the analytics ID shown under Privacy choices on merget.ai and send it with your request, as the Privacy Statement describes under Deletion.
- Advertising. There are no advertising cookies on any Merget site.
4. Changes, prior versions and contact
Changes
We may change this notice when a site's cookies or storage change. We post each new version here with its effective date. For a material change, such as adding advertising cookies or a new analytics service, we also email account holders at least 30 days before it takes effect. A change that only adds a strictly necessary key or renames one takes effect when published.
Prior versions
This version replaces the version effective November 15, 2026.
Contact
Merget, Inc.
418 Broadway, Unit 7259, Albany, NY 12207
support@merget.ai