CompanionCookie policy
Last updated: 7 October 2026
This page lists every cookie Companion sets, and the third parties our pages talk to. We have kept it short because there is not much to report.
This website
Our own pages set no cookies. There is no analytics tag, no advertising pixel and no tracking of any kind on these pages.
The typefaces, images and styles are all served from this site itself, so reading a page does not disclose your visit to a font service or any other third party.
There is one exception, and it is the booking calendar. The “Book a meeting”
section of the home page shows a calendar provided by Cal.com, loaded from app.cal.com
inside a frame. It is only requested when you scroll near that section or follow a link to it;
until then the page asks nothing of Cal.com. Once it loads, Cal.com receives your IP address
and may set cookies of its own inside that frame: at the time of writing a security cookie
from its network provider, Cloudflare (__cf_bm, about 30 minutes), and whatever
its booking page needs to work. We do not set those cookies and cannot read them. If you make
a booking, Cal.com passes us the details you enter; our privacy policy
covers what we do with them, and Cal.com’s own policy covers what it does.
If you would rather not load it, blocking app.cal.com in your browser leaves the section showing plain links to the same meetings, and you can always arrange a call by emailing info@msgcompanion.com instead.
The Companion product
Once you sign in to a workspace, the application uses the following.
| Cookie | Purpose | Type | Expires |
|---|---|---|---|
sb-…-auth-token | Keeps you signed in and identifies your session. Set by Supabase, our authentication provider. | Strictly necessary | On sign-out, or when the session lapses |
mw.demo.role | Remembers which role you are previewing the product as, in demonstration workspaces only. | Strictly necessary | 30 days |
ph_…_posthog | Product analytics, so we can see which features are used. Only set where analytics is enabled. | Analytics | 12 months |
Strictly necessary cookies do not require consent: the product cannot keep you signed in without them. Where analytics cookies are used, we ask first, and declining them does not change how the product works.
Our error-monitoring tool records diagnostic information when something breaks. It does not set cookies and does not capture the contents of your conversations.
The chat widget on a business’s website
A business using Companion can add our chat widget to its own website. The widget sets no
cookies. It keeps one entry in your browser’s local storage, named
mc_widget: followed by the business’s widget key. It holds a reference to your
chat session and whether you have closed the widget’s greeting, so a conversation survives
a page reload; the details you type are held by the business, not in your browser. It is
strictly necessary for the chat to work, is only written once you start a chat or close the
greeting, and stops being used after 24 hours without activity. The business whose site you are on is responsible for telling you
about it.
Our iPhone app
The app does not use cookies. It keeps your signed-in session in the app’s own storage on your iPhone until you sign out.
Managing cookies
Every major browser lets you see the cookies a site has set and delete them, usually under privacy or site settings. Blocking the strictly necessary cookies above will stop you signing in to the product; the marketing site will be unaffected, because our own pages set none.
Changes
If we add or remove a cookie, we will update this page and change the date at the top.
Contact us
Questions about this page go to support@msgcompanion.com. More detail on how we handle personal data is in our privacy policy.
