Skip to content

Cookie Policy

Last updated: (DRAFT)

DRAFT — pending attorney review

This document is a draft and may change.

This Cookie Policy explains the cookies and similar storage that QuantMap uses, why we use them, how we record your choices, and how you can change them. It is part of our Privacy Policy. Use the Cookie preferences link in the site footer, or the button in Section 5, to change your choices at any time.

1. What cookies and similar technologies are

Cookies are small text files that a website stores on your device. Similar technologies do the same job. Local storage and session storage keep data in your browser, and session storage is cleared when you close the tab. Pixels and tags are small pieces of code that report to another company when a page loads. In this policy we call all of these "cookies" or "storage" unless we need to be specific.

Cookies can be first-party, set by quantmap.app, or third-party, set by another company such as Cloudflare, Google, Meta, YouTube or Stripe. They can last for a session, until you close your browser or tab, or they can be persistent, lasting until they expire or you delete them.

The tables below come from the cookie registry, the single list that also powers Cookie preferences on this site, so the two always match.

2. The categories we use

We group cookies into five categories. Necessary storage is always on. Analytics, marketing and embedded content follow your choices (see Section 3). Functional storage is on and is not part of those choices.

Necessary

These keep the site secure and working and remember your cookie choices. They are always on. You can block them in your browser, but parts of the site may then stop working. Stripe sets its own cookies on Stripe's checkout pages, not on quantmap.app. We list them here for transparency.

Scroll sideways to see every column.

Necessary
NameProviderDurationPurpose
  • qm_consent
Cookie
QuantMapFirst party12 monthsRemembers your cookie choices.
  • __cf_bm
  • _cfuvid
  • cf_clearance
Cookie
CloudflareFirst partyUp to 12 monthsProtects the site against bots and abuse.
  • cf_chl_*
Cookie
CloudflareThird partySessionCloudflare Turnstile checks that a person, not a bot, is filling in a form.
  • __stripe_mid
  • __stripe_sid
Cookie
StripeThird partyUp to 12 monthsStripe uses these to process payments and prevent fraud.

Functional

These remember small details during your visit, such as the link you arrived from or the details you type into the walkthrough request form. Those form details are kept in your browser only until the request is sent, then removed. Campaign details from the link you arrived on (qm_utm) are kept for the browser session, and we clear them if you reject cookies in the EEA, the United Kingdom or Switzerland.

Scroll sideways to see every column.

Functional
NameProviderDurationPurpose
  • qm_utm
Session storage
QuantMapFirst partySessionKeeps the campaign details of the link you arrived from for this visit.
  • qm-walkthrough
Local storage
QuantMapFirst partyUntil clearedKeeps the details you type into the walkthrough request form (name, email, phone, your agreement to be contacted and campaign details) in your browser until the request is sent, then removes them.

Analytics

These show us how the site is used so that we can improve it. They include Google Analytics, loaded through Google Tag Manager, and our own first-party analytics. They are off until you accept them in the EEA, the United Kingdom and Switzerland, and where we cannot tell where you are (see Section 3).

Scroll sideways to see every column.

Analytics
NameProviderDurationPurpose
  • qm_vid
Cookie
QuantMapFirst party13 monthsAnonymous visitor ID that lets us recognize return visits. Set only with analytics consent.
  • qm_sid
Cookie
QuantMapFirst party30 minutesGroups your page views into one visit. Set only with analytics consent.
  • _ga
  • _ga_*
Cookie
GoogleFirst party24 monthsGoogle Analytics, loaded through Google Tag Manager, measures how visitors use the site.

Marketing

These measure our advertising and help us reach people who may be interested. They include the Meta Pixel. Meta's Conversions API, which sends events from our servers, runs only when marketing is on. Marketing is off until you accept it in the EEA, the United Kingdom and Switzerland, and where we cannot tell where you are. Everywhere else it is on unless your browser sends a Global Privacy Control signal or you opt out (see Section 3).

Scroll sideways to see every column.

Marketing
NameProviderDurationPurpose
  • _fbp
  • _fbc
Cookie
MetaFirst party3 monthsMeta Pixel measures ad results and helps us reach people who may be interested.

Embedded content

These let us play videos and show other content from other sites, such as YouTube. We do not load YouTube until you click play on a video. The video then loads from youtube-nocookie.com, Google's privacy-enhanced mode. Clicking play allows embedded content for this site, and you can withdraw that under Cookie preferences. These other sites may set their own cookies.

Scroll sideways to see every column.

Embedded content
NameProviderDurationPurpose
  • VISITOR_INFO1_LIVE
  • YSC
  • VISITOR_PRIVACY_METADATA
Cookie
YouTubeThird party6 monthsSet by YouTube when you play an embedded video.

3. Your choices depend on where you are

We infer your region from your IP address and apply one of two sets of rules.

  • EEA, United Kingdom and Switzerland, and where we cannot tell where you are (for example when you use a privacy network such as Tor). Analytics, marketing and embedded content are off until you choose. The banner gives Accept all and Reject all equal weight, and closing it without choosing does not turn anything on.
  • Everywhere else. Analytics is on and marketing is on, and a banner tells you so. Embedded content stays off until you click play on a video or allow it in Cookie preferences. You can opt out at any time with the Do Not Sell or Share link or under Cookie preferences, and closing the banner keeps these defaults.

Global Privacy Control. If your browser sends a Global Privacy Control (GPC) signal, we keep marketing off in every region. GPC overrides an earlier choice to accept marketing, and the marketing setting then shows as locked in Cookie preferences, with an explanation. GPC applies to the browser that sends it.

4. How we record your choices

When you make a choice, or when we apply the default for your region, we store it in a first-party cookie called qm_consent. It lasts 12 months and holds no name, email address or other direct identifier. It records:

  • a consent reference ID, a unique code that is new for every decision. You can see it in Cookie preferences and quote it if you contact us;
  • the version of the cookie registry your choice was made under;
  • the type of region we applied: opt-in (the EEA, the United Kingdom, Switzerland, and where we cannot tell where you are) or notice (everywhere else);
  • your choices for analytics, marketing and embedded content, and whether you have opted out of sale or sharing;
  • whether your browser sent a Global Privacy Control signal; and
  • how and when you made the choice, such as Accept all, Reject all, saved preferences, the Do Not Sell or Share page, GPC, or playing a video.

When you reject or withdraw consent, we turn off the related tools, clear our own identity cookies (qm_vid and qm_sid) and tell the Meta Pixel to revoke consent. Cookies that other companies set may stay in your browser until they expire or you delete them.

We also keep a record of each choice on our servers as evidence that we respected it. It holds the consent reference ID, your choices and when and how you made them, the region type and country, whether GPC was detected, the versions of the cookie registry and banner wording, the page you were on, your session and visitor IDs where you have them, your browser details, and a hashed version of your IP address. We keep these records for five years (see Section 10 of the Privacy Policy).

5. How to change your choices

You can open Cookie preferences at any time to switch analytics, marketing and embedded content on or off, see your consent reference ID and when you last updated your choices, and read the same list of cookies as on this page.

Other ways to change your choices:

  • use the Cookie preferences link in the site footer;
  • opt out of sale and sharing on the Do Not Sell or Share page, which works without JavaScript;
  • send a Global Privacy Control signal from your browser or an extension; or
  • block or delete cookies in your browser settings. Blocking necessary cookies may stop parts of the site from working, and a browser setting does not change the choices we have recorded.

6. Vendors and their policies

Some cookies are set by companies other than us. Their own policies explain how they use the data they collect.

7. Changes to the registry and to this policy

The registry is our single list of the cookies and storage the Service uses. When we add, remove or change an item or a tool, the registry gets a new version number. That version is stored in your qm_consent cookie and in our consent records, and a new version asks you to make your choices again. We may also update this policy. The "Last updated" date at the top of this page shows when it last changed.

Cookie list version: 2026-11-03.1

8. Contact us

Adaptos Research LLC is responsible for this policy. For questions about cookies, email support@quantmap.app. For everything else about your personal data, see our Privacy Policy.