The short version: apexgscore.com does not place any cookies on your device, does not run any third-party analytics, and does not embed advertising or social-media tracking. The pages render as static documents served from a content delivery network. There is no consent banner because there is nothing to consent to.

The longer version follows.

§ 01 What Cookies and Trackers Are

A cookie is a small text file placed on your device by a website. Trackers more broadly include any technology that allows a website or third party to identify, profile, or follow you across pages or sessions — including pixel tags, web beacons, fingerprinting scripts, and third-party SDKs. Most commercial websites use one or both, often dozens of them per page, to support advertising, analytics, A/B testing, and behavioral profiling.

§ 02 What This Website Uses

This website is built as a set of static HTML, CSS, JavaScript, SVG, and font files served through Cloudflare's content delivery network. As of the effective date of this notice, the site:

  • does not set any first-party cookies;
  • does not set any third-party cookies;
  • does not include any third-party analytics tag (no Google Analytics, no Plausible, no Fathom, no Mixpanel, no Adobe Analytics, no Microsoft Clarity, no Heap, no PostHog, no Hotjar, no Matomo, no equivalent product);
  • does not include any advertising or retargeting pixel (no Meta Pixel, no LinkedIn Insight Tag, no Google Ads tag, no TikTok Pixel, no equivalent);
  • does not embed any social-media login, share, or follow widget that tracks visitors;
  • does not use device fingerprinting, session replay, or behavioral-profiling SDKs;
  • does not sync identifiers across sites or devices;
  • does not use local storage, session storage, or IndexedDB to identify or profile visitors.

The browser may briefly cache static assets (images, fonts, CSS) so that pages load faster on repeat visits. This caching is transparent, controlled by your browser, and does not involve any identifier issued by Apex.

§ 03 What Our Hosting Provider Does

Our content delivery network and origin host (Cloudflare, Inc.) operates the global edge infrastructure that serves the website. As an unavoidable part of providing this service, Cloudflare's edge nodes process basic technical metadata for each request — IP address, user-agent string, the URL requested, response status, and timestamp — for purposes such as denial-of-service mitigation, bot management, and operational monitoring. This processing is governed by Cloudflare's own privacy and security practices.

Cloudflare may, in some circumstances and only for security purposes, set its own first-party cookies (such as __cf_bm for bot management). Apex does not configure, control, or read these cookies. Their behavior is described in Cloudflare's cookie policy.

§ 05 Why We Run the Site This Way

Apex serves an institutional audience. Many of the readers we expect to visit this site — pension fund staff, asset-management research teams, sovereign-wealth fund analysts, regulators, academics, and members of the press — have legitimate reasons to read about governance topics without being profiled, retargeted, or added to a downstream marketing dataset. Operating the site without trackers is the simplest way to honor that expectation. It also dramatically reduces the surface area of our compliance obligations under privacy laws of various jurisdictions.

If, in future, we add any feature that requires a cookie or tracker (for example, a logged-in subscriber portal), we will update this notice and, where required by applicable law, present a clear opt-in mechanism before any non-essential cookie is set.

§ 06 Browser Settings

You retain full control of your browser's cookie and tracking settings, regardless of any specific site's behavior. Major browsers (Chrome, Safari, Firefox, Edge, Brave, Arc) all allow you to view, block, or delete cookies; to enable strict tracking protection; and to send Do-Not-Track or Global Privacy Control signals. Because this site does not set cookies, those signals have no effect here, but they remain useful for the rest of the web.