The short version
We use Google Analytics 4 to understand which public pages readers use and which broad topics and markets deserve more attention. Analytics runs automatically for visits that Cloudflare classifies as coming from the United States outside California, unless the browser has disabled it. California visits, visits outside the United States, and visits whose region cannot be determined require permission first. We do not use this integration to create advertising profiles.
Your analytics preference
Checking the analytics preference saved in this browser.
A choice you make here is stored only in this browser. Global Privacy Control and Do Not Track signals keep analytics disabled, including for US visits.
What the analytics setup measures
When analytics is active, the site records page views and standard technical context such as referrer, browser and device category, approximate geography, and engagement information. We also record selections of articles, markets, service desks, areas, and cited source links. Site searches record the search term and result count so we can identify missing coverage; terms that resemble an email address, phone number, or URL are replaced with a redacted marker before the event is sent.
Google Analytics may set first-party cookies whose names begin with _ga. These help distinguish visits and sessions. We do not enable Google Signals, ad personalization, ad-user data, or advertising storage in the site code.
How the regional decision works
Cloudflare already processes an IP address to deliver each request and supplies the site with a country and first-level region result at its network edge. A narrowly routed function converts those results into either “automatic” or “consent required.” It does not return the country, region, or raw IP address to the page, does not write the result to storage, and sends a non-cacheable response. California, an unknown location, or an unavailable result is treated as consent required.
Automatic US measurement outside California is evaluated for each page visit and is not recorded as though the reader explicitly consented. A VPN, relay, or corporate network can affect the regional decision.
What we do not intentionally collect
Do not submit personal, confidential, account, medical, legal, payment, or property-access information through site search. The publication does not intentionally send names, email addresses, phone numbers, exact private addresses, article-source notes, or contact-form text as analytics event parameters. The current newsletter field is disabled and does not transmit an email address. Article drafts, research packets, client files, prospect files, contact-message contents, and other private editorial material are never part of the public analytics integration.
US and California privacy choices
California visits require permission before analytics loads. For other US visits, analytics runs automatically unless the reader has opted out. We do not use this analytics configuration for targeted advertising, cross-context behavioral advertising, Google Signals, ad personalization, or advertising user data. A browser Global Privacy Control signal is treated as an instruction to disable analytics everywhere, including for an otherwise automatic US visit. We apply the same behavior to Do Not Track. Readers can also disable analytics at any time from the controls on this page.
Your choice
For a consent-required visit, the Google tag does not load and this integration sends no measurement until the reader chooses “Allow analytics.” Choosing “Disable analytics” overrides automatic US measurement, prevents the tag from loading on later pages, and removes accessible first-party Google Analytics cookies for this site. A reader can change a saved choice above.
Service provider and retention
Google processes analytics information for this measurement property. Google may apply its own security, retention, and data-processing practices. Publication administrators should limit access to the analytics property, retain only the period needed for editorial planning, and avoid linking this property to advertising products unless this policy is reviewed and updated first.
Questions
Send privacy or analytics questions to [email protected]. Corrections to published reporting follow the separate Corrections Policy.