Cookie Policy

01What this page covers

This page lists the cookies and similar technologies that adoptiv.com and the Adoptiv application load today. It is a list of what is really there, not a list of what a cookie policy usually says.

Similar technologies means anything that stores or reads data in your browser for the same purposes: local storage, session storage, and the session replay used by our analytics and error monitoring. Those are covered here too, in their own section, because calling them something other than cookies does not make them less your business.

Cookies are grouped below into four categories: essential, analytics, support and marketing. Each table gives the cookie name, who sets it, what it is for, and how long it lasts. Where a name contains a placeholder in angle brackets, the real cookie has an account or project identifier in that position.

02Essential cookies

These keep you signed in and keep sign-in secure. They are all set by Adoptiv as first-party cookies on adoptiv.com. They carry no advertising or analytics data. You cannot turn them off and still use the product, because they are the mechanism by which the product knows who you are.

03Analytics cookies

These tell us which pages people read, which links they follow, and where they give up. Google Analytics 4 property G-563K6W8H86 is the primary measurement. PostHog adds product analytics and session replay.

PostHog traffic is routed through adoptiv.com/ingest, a first-party reverse proxy, so its cookie is a first-party cookie on adoptiv.com rather than a third-party one. The reason is practical: a large share of business browsers block requests to posthog.com outright.

PostHog session replay records pages viewed, clicks, scrolling and mouse movement. Every form input is masked in your browser before anything is sent, so what you type into a name, email, phone or message field never leaves your device. Replay is pseudonymous: it is tied to the identifier in the cookie above, not to your name.

04Support cookies

Intercom runs the messenger in the bottom corner of the site and inside the application. It loads for every visitor, before you click it. We have made that choice deliberately and we would rather say so here than bury it: the messenger is how you reach a person, and a support channel that only appears after you have agreed to be measured is not a support channel.

If you start a chat we ask for your name and email so we can reply. If you are signed in, the messenger identifies you from your Adoptiv session, so a chat starts without a form.

Calendly runs the demo booking window. Its script is not loaded on page load. It loads the first time you hover, focus or click a booking button, and not before.

05Marketing cookies

These measure whether an advertisement led to a demo request. Adoptiv runs Google Ads account AW-18162896463. We do not sell any of this data and we do not run advertising inside the product.

06Things that are not cookies

Three technologies store data in your browser without using a cookie. They belong on this page.

• mv2-consent, in local storage. Your answer to the consent banner, with the time you gave it. This is the record of your choice, so clearing it puts the banner back.
• mv2-internal, in local storage. Set only when someone at Adoptiv visits with ?internal=1 in the address, so that our own visits can be filtered out of the numbers. Nothing sets it for you.
• Sentry session replay, in session storage. Our error monitoring loads on every page. It captures a replay of the moments around an error so a crash can be reproduced. All text is masked and all media is blocked, so the replay is a wireframe of the layout rather than a picture of your content. It records roughly one session in ten, plus every session in which an error occurs.

One more thing worth stating, because it is a request to a third party even though it sets no cookie: the site's typefaces load from Google Fonts. That request tells Google the address of the browser making it.

07Where these tags load, and where they do not

The Google tag checks the hostname before it does anything. It runs on adoptiv.com and www.adoptiv.com only. It does not run on staging, on development hosts, on a customer's workspace subdomain, or on any mirror of the site that someone else has put up. Nothing about your use of your own workspace is measured in Google Analytics or Google Ads.

One more distinction worth stating, because it is unusual. The marketing pages you are reading now set no cookies of their own and load no third-party tag at all: no analytics, no advertising, no chat widget, no session replay. Nothing in your browser records that you were here. The tables above describe the signed-in application, and the marketing tags described under analytics and marketing run on adoptiv.com. If that changes, this page changes with it and the date at the top moves.

08What you can refuse, and what it costs you

Plainly, category by category.

• Essential: you cannot refuse these and sign in. They are not a tracking mechanism, they are the sign-in mechanism. If you block them in your browser, sign-in will fail.
• Analytics: you can refuse these, and it costs you nothing. You lose no feature. We lose the picture of which pages are working.
• Marketing: you can refuse these, and it costs you nothing. Advertisements you see elsewhere become less relevant to what you looked at here, and we lose the ability to tell which campaign produced a demo request.
• Support: refusing means no messenger. Intercom's cookies are set when the page loads, not when you open the chat, so declining analytics does not stop them. If you do not want them, block them in your browser or use a private window, and write to support@adoptiv.com instead. You lose in-page chat and nothing else.

Where you are matters. In the EEA, the United Kingdom and Switzerland, analytics and advertising storage start denied and stay denied until you choose otherwise in the banner. Everywhere else they start granted and you can decline at any time. PostHog follows the same rule: in those regions it does not start at all until you accept.

09How to change your choice later

Your answer to the banner is kept in your browser's local storage under mv2-consent, not in a cookie, so a cookie-clearing tool alone may not reach it.

An acceptance lasts 12 months. A decline hides the banner for 24 hours and then we ask again, because a decline is an answer about today and not a permanent instruction we can rely on.

• To be asked again now: clear site data for adoptiv.com in your browser, which removes mv2-consent. The banner returns on the next page load and you can choose differently.
• To refuse everything permanently: block third-party cookies, or block adoptiv.com cookies, in your browser settings. This will also stop you signing in.
• To opt out of Google Analytics across every site that uses it: install Google's Analytics opt-out browser add-on.
• To delete a chat history: write to privacy@adoptiv.com and say which conversation.
• To ask what we hold about you and have it deleted: privacy@adoptiv.com. The privacy policy at /legal/privacy sets out the rest of your rights.

10Changes and contact

When we add or remove a tag, this page changes on the same day and the date at the top moves. If the change adds a new category of tracking, the banner will ask you again rather than assume your earlier answer covers it.

Questions about anything on this page go to privacy@adoptiv.com. Adoptiv Inc, 2810 N Church St STE 88783, Wilmington, DE 19802, United States.