Third-party advertising is currently off.
The site publishes the account-issued publisher authorization in ads.txt and an ownership meta tag. Those static strings help establish site and seller ownership; they do not load a vendor, set a cookie, create an advertising identifier, or prove that Google has approved the site.
No substitute ad network is silently enabled while AdSense review is pending. A future vendor requires its own contract, policy, privacy, security, consent, and placement review. First-party product information may appear without a third-party advertising request and is labeled as coming from Discovery.
The private application does not carry ad code.
The account, chart workspace, uploaded material, generated reports, decision journal, billing, checkout, pricing, and legal routes run in the React application. That application does not import the Research Notes ad loader and its normal content-security policy does not permit AdSense. Signing in does not activate an advertisement.
The only prepared placement is on the exact static path /research-notes/chart-evidence-checklist/. Navigation between that document and the product uses a full page load, so third-party code cannot persist through a client-side route change into an account screen. The editorial document does not initialize Clerk, read an account identity, request entitlements, accept uploads, or access report and journal storage.
- Private product routes
- No AdSense loader, placement, slot, or ad-tech CSP permission.
- Editorial allowlist
- One exact, substantive public article; every other path fails closed.
- Placement count
- At most one normal-flow placement per document load; no refresh timer.
- Current fallback
- A first-party Discovery information card, visibly distinct from editorial content.
Google may receive advertising request data.
Only after all activation gates pass, the isolated article may request Google’s AdSense script and one manually configured ad unit. Google and its advertising partners may then receive ordinary request information such as IP address, browser and device details, page URL and context, consent signals, ad interactions, and advertising or storage identifiers. Depending on consent, location, Google settings, and the approved configuration, Google may use data to deliver, limit, protect, measure, or personalize advertising.
If advertising is activated, third-party vendors, including Google, may use cookies to serve ads based on a visitor’s prior visits to this website or other websites. Google’s use of advertising cookies enables Google and its partners to serve ads based on visits to this site and/or other sites on the Internet.
Visitors may opt out of personalized advertising through Google Ads Settings. If the reviewed account configuration permits other third-party vendors or ad networks, Discovery will identify them and link their policies and available opt-outs here before activation; visitors may also opt out of some third-party vendors’ personalized-ad cookies through AboutAds. Opting out of personalization does not necessarily stop contextual or limited ads, ordinary network transmission, or processing needed for security and invalid-traffic prevention.
Explore AI will not intentionally send an uploaded chart, report text, journal entry, account email, billing record, private ticker, or authenticated workspace event to AdSense. The editorial article contains no such data. Google’s own processing is governed by its published advertising and privacy terms; visitors should review those terms through the consent interface before choosing.
No consent signal, no loader.
Activation requires a Google-certified consent-management platform where Google requires one, applicable U.S. state privacy messaging and opt-outs, and a reviewed integration that emits a versioned consent result. A local button or browser-storage flag is not represented as certified consent. Global Privacy Control overrides an affirmative signal and keeps the placement off.
The ad loader waits for all of the following at the same time: the exact allowlisted path, the explicit release kill switch, the expected publisher ID, certified-CMP readiness, the current consent version, affirmative certified consent, no active GPC signal, and a real account-issued slot. Missing or malformed state shows the first-party fallback instead.
If consent is withdrawn after vendor code has loaded, the page removes the active placement and does not request another one. Already executed JavaScript cannot literally be removed from browser memory, so a full reload is required to create a new vendor-free document. The loader has no automatic refresh, retry loop, route listener, or background timer.
One reserved area, separated from actions.
The sponsor area is placed between completed article sections, in normal document flow, after substantial original content. Space is reserved at desktop and mobile widths to reduce layout shift. The area is labeled above the creative and remains separated from navigation, privacy controls, product actions, charts, forms, and links that a visitor could mistake for part of an advertisement.
Discovery does not ask visitors to click an ad, promise a benefit for interaction, disguise an ad as evidence, place a creative over content, or allow paid placement to change a research result. The implementation requests no more than one unit in a document load and does not refresh it. A loader or local request-queue failure restores the labeled first-party message without retrying. Creative no-fill behavior remains a required canary check before activation; the current release never makes the request.
Contact Explore AI Inc.
For questions about this editorial surface, advertising, privacy, or a future consent choice, email [email protected] with “Discovery Advertising Privacy” in the subject. The broader Discovery Privacy Notice and Cookie & Advertising Notice govern the product alongside this more specific explanation.