Legal

Cookie Policy

MorganMatch — Last updated: 17 November 2026

This policy explains how we use cookies and similar technologies on morganmatch.ai (the "Platform"), and how you can control them. It should be read alongside our Privacy Policy.

In short: we use a small number of cookies that the Platform needs in order to work, and optional analytics that only run if you allow them. We do not use advertising or marketing cookies.

1. What cookies are

Cookies are small data files placed on your device when you visit a website. They are used to make a site work and to understand how it is used.

We also use similar technologies: your browser's local storage and session storage, which keep small pieces of information on your device in much the same way. Where we refer to "cookies" in this policy, we mean all of these.

We do not use tracking pixels or advertising tags on the Platform.

2. Who sets them

Every cookie on the Platform is a first-party cookie: it is set on our own domain. We set the strictly necessary ones ourselves. The optional analytics entries are set on our behalf by our analytics provider, PostHog, and only if you allow analytics.

No other company sets cookies through the Platform. Some features do connect your browser to another company's service, which has its own privacy and cookie policies. These are listed in section 4.

3. Cookies we use

Strictly necessary

Required for the Platform to work: keeping you signed in, protecting sign-in against attack, and remembering information you have given us part-way through a process. They cannot be switched off, and we do not need your consent to use them. None of them is used for analytics or advertising.

  • mm_session
    Set by
    MorganMatch
    Purpose
    Keeps you signed in to your candidate or client account as you move around the Platform. It holds your account details (such as your name, email address and account type), signed so that they cannot be altered.
    Duration
    30 days from your last visit. Deleted when you sign out.
  • mm_oauth_state
    Set by
    MorganMatch
    Purpose
    Protects LinkedIn sign-in: confirms that the reply from LinkedIn belongs to the sign-in you started.
    Duration
    Up to 10 minutes. Deleted as soon as you return from LinkedIn.
  • mm_oauth_audience
    Set by
    MorganMatch
    Purpose
    Remembers that you chose to sign in as a candidate while LinkedIn sign-in completes, so that we open the right account.
    Duration
    Up to 10 minutes. Deleted as soon as you return from LinkedIn.
  • mm_candidate
    Set by
    MorganMatch
    Purpose
    Recognises you when you open the private scheduling link in an email from us, so that you can respond to meeting requests from employers without signing in.
    Duration
    14 days.
  • mm_passport_entry
    Set by
    MorganMatch
    Purpose
    CompliancePassport: remembers the type of work and sector you selected, so that we show you the right sections.
    Duration
    180 days from when you last saved these answers.
  • mm_passport_answers
    Set by
    MorganMatch
    Purpose
    CompliancePassport: remembers whether you have been known by another name, so that we ask for the right documents.
    Duration
    180 days from when you last saved this answer.
  • mm_analytics_consent_v3(local storage)
    Set by
    MorganMatch
    Purpose
    Remembers whether you allowed or declined analytics, so that we do not ask you on every page.
    Duration
    Until you clear your browser's site data.

Strictly necessary: staff sign-in

Only set if you open the staff admin area. MorganMatch staff sign in to it through our technology partner, Quake, which uses its own cookies on its own website. Staff who switch on incoming-call alerts there also register a push-notification subscription and a small background script in their browser.

  • mm_quake_oauth_state
    Set by
    MorganMatch
    Purpose
    Protects staff sign-in: confirms that the reply from Quake belongs to the sign-in that was started.
    Duration
    Up to 10 minutes. Deleted as soon as sign-in returns.
  • mm_quake_oauth_next
    Set by
    MorganMatch
    Purpose
    Remembers which admin page to open once staff sign-in completes.
    Duration
    Up to 10 minutes. Deleted as soon as sign-in returns.
  • mm_quake_admin
    Set by
    MorganMatch
    Purpose
    Keeps a member of staff signed in to the admin area.
    Duration
    30 minutes from their last activity. Deleted on sign-out.

Analytics

Optional, and off unless you allow it. If you do, we use PostHog to see how the Platform is used so that we can improve it: the pages you visit, the features you use, errors you run into, and recordings of your screen that hide all text and images. We also record pay benchmark searches that we had no figure for (the job title typed, the region and the contract type), so that we know where to add data. If you are signed in, PostHog links all of this to your account, with your name, email address and whether you are a candidate or a client. With each event PostHog also receives standard technical details, such as your IP address, your browser, device type, language and time zone, the address of the page you were on and of the page where your visit started, and the website you came from. If you later withdraw your permission, PostHog deletes its cookie and local storage entry from your device straight away, and its session storage entries when you close the tab. In the names below, [ID] stands for our PostHog project ID.

  • ph_[ID]_posthog
    Set by
    PostHog, on our behalf
    Purpose
    Gives your browser a random ID so that visits from the same browser can be counted together. While you are signed in, it holds your account ID instead. It also holds a visit ID, and the page address and referring website from when analytics first loaded. It does not contain your name or email address.
    Duration
    1 year.
  • ph_[ID]_posthog(local storage)
    Set by
    PostHog, on our behalf
    Purpose
    Holds the same details as the cookie, with the time the random ID was created.
    Duration
    Until you withdraw your permission or clear your browser's site data.
  • ph_[ID]_posthogph_[ID]_session_registered_propertiesph_[ID]_window_idph_[ID]_primary_window_exists(session storage)
    Set by
    PostHog, on our behalf
    Purpose
    Lets PostHog tell one browser tab from another during a visit.
    Duration
    Until you close the tab.
  • __ph_opt_in_out_[ID](local storage)
    Set by
    PostHog, on our behalf
    Purpose
    Set when you withdraw your permission, so that PostHog stays switched off. If you allow analytics again, it records that instead.
    Duration
    Until you clear your browser's site data.

We do not use advertising, marketing or social media cookies, and we do not use cookies to remember display preferences. What you save on the Platform, such as your profile, role briefs and saved searches, is kept in your account on our systems, not in cookies.

4. Other services your browser connects to

A few features connect your browser directly to a service run by another company. None of them sets cookies on the Platform, but the provider receives technical details such as your IP address, and handles them under its own privacy policy.

  • Address search (Google). Location fields use Google Maps Platform's address search. When you open a form that has one, your browser loads it from Google, and Google receives your IP address and what you type into that field. See the Google Privacy Policy.
  • LinkedIn sign-in. If you choose to sign in with LinkedIn, you do so on LinkedIn's website, which uses its own cookies. See the LinkedIn Cookie Policy.
  • Video meetings (Zoom). Introduction meetings are held on Zoom. Opening a meeting link takes you to Zoom, which uses its own cookies. See the Zoom Cookie Policy.
  • Voice calls (Twilio). If you choose to talk to Morgan, our AI assistant, by voice, the call is carried by Twilio and uses your microphone only with your permission. See the Twilio Privacy Notice.

5. Your choices

The first time you visit the Platform, a banner asks whether you will allow analytics. Nothing optional is stored on your device unless you choose Allow.

You can change your mind at any time using the settings below. If you withdraw your permission, we stop collecting analytics from your browser straight away and delete the analytics entries from your device, as described in section 3. This does not affect analytics collected before you withdrew it.

These settings cover analytics in your browser. Our servers also keep records of key steps in your account, such as signing up, and of errors, without using cookies. Our Privacy Policy explains them.

Your choice is saved in the browser you are using, so it applies to that browser only. We will ask again on another browser or device, or if you clear your browser's site data.

You can also block or delete cookies through your browser settings. If you block strictly necessary cookies you will not be able to sign in, and other parts of the Platform may not work. Guidance is available from your browser provider.

6. How long cookies last

Each cookie we set has a fixed lifetime, shown in the tables above, and your browser deletes it automatically when that time is up. Some are removed sooner, when you sign out or finish signing in. Entries in local storage have no expiry date and stay until they are cleared. Entries in session storage are removed when you close the tab.

7. Changes to this policy

We will update this policy as our use of cookies and similar technologies changes. The date at the top shows when it was last revised.

8. Contact

Email: privacy@morganmatch.ai
Address: Morgan Match Ltd, 3rd Floor, Standon House, 21 Mansell Street, London, E1 8AA