What is recorded
When measurement is enabled, each click on an outbound link (official product pages, any clearly marked partner link, and cited sources, documentation or original videos) and on a small set of key on-site buttons is stored as one row in a first-party click log. A row holds the time (UTC); the link type; our page path and article; the link position and label; the product or source and its full destination address; the hostname of the site that referred your visit (never the full referring URL); any utm_source, utm_medium, utm_campaign, utm_term and utm_content tags, each cut to 100 characters; yes/no flags for whether a Google, Microsoft or Meta ad-click identifier was present, never its value; the page where your visit started; a coarse device type and browser family; country and state or region from our host’s location headers; a bot flag; and a random visit identifier. We do not store your IP address, full user agent, cookies, email address or any ad-click identifier value. The user agent is read briefly to derive the device type, browser family and bot flag, then discarded. Daily totals per platform, product, article and link placement are also kept; the filtered total is not a count of unique people.
Visit information in your browser
To connect a click with how the visit began, the site keeps a small record in your browser’s sessionStorage for the current tab: the random visit identifier, landing page path, referring site hostname, campaign tags and the ad-click presence flags. It is not a cookie. It is cleared when you close the tab, replaced on a new UTC day, and sent to us only with a tracked link or button click. With JavaScript off, nothing is kept in your browser and a click row records only the page you clicked from.
Purpose
The click log measures which pages and links send readers to which providers and sources, and how visits arrive, for example from search, AI assistants, social sites or email. It is not used to identify you by name, build profiles across visits or sell data. Reports are request counts, not proof of a signup, trade, conversion or commission.
Scenario inputs and sharing
Calculator and worksheet inputs are processed in the browser. Copying a scenario link places bounded numbers and product labels in a URL, which you may choose to send to others. A loaded URL can reach normal hosting logs; do not share inputs you consider private. Referral reports classify a small allowlist of page/product pairs into research journeys, not individual readers or wealth categories.
Choices and retention
When your browser sends Global Privacy Control or Do Not Track, no visit record is kept in your browser, Google Analytics does not load and key-button clicks are not sent. A click on an outbound link is still recorded on our server and counted in the daily totals, but with no visit information: no visit identifier, no campaign (utm) tags, no ad-click flags, no referring site and no landing page. That row holds only the time, the link and its destination, our page you clicked from (when your browser reports it), the coarse device type and browser family, country and region, and the bot flag. The link always works. HEAD and prefetch requests are not counted. Our own measurement sets no cookies and uses no fingerprinting; Google Analytics and YouTube players have separate practices described below. Click-log rows are kept until we delete them; there is currently no automatic deletion period. Daily aggregate rows older than 90 days are deleted on reporting writes and reads.
Google Analytics
When Google Analytics 4 is enabled, Google receives page views and the same click events (product or source, destination site, our page, link position, link type and visit channel), together with what your browser normally sends, such as your IP address and device and browser details, and Google Analytics cookies are set on this site. We configure it with advertising storage denied and with Google signals and advertising personalisation turned off. It is not loaded when your browser sends Global Privacy Control or Do Not Track. Google processes this data under its own policies.
YouTube videos
Official demonstrations are embedded directly from YouTube using its privacy-enhanced (youtube-nocookie.com) player, so the player loads with the page. When it loads, Google/YouTube may receive your IP address and device information, and may process player storage, advertisements and viewing activity under its own policies. Privacy-enhanced mode is not tracking-free, and loading the player cannot be undone after the fact. Videos never autoplay, and no external thumbnails load. You can skip the player and use the sourced text guide instead. When aggregate measurement is enabled, video ID, UTC day and bounded page-load/start/completion event counts are stored separately from outbound referrals for up to 90 days. These are request counts, not unique viewers or merchant conversions. GPC and DNT opt out of this first-party measurement; playing a video does not override those choices.
External services
Official links take you to separately operated websites. Hosting providers can independently process infrastructure logs; this application’s minimal database does not describe or control every vendor log. We do not collect wallet keys, provider login details or personal trading histories.
Measurement limits
A count of link requests does not identify a person, prove an account conversion or establish revenue. Do not put sensitive personal or financial information in search or tracking parameters.
Content reviewed 2026-10-26
Explore the complete editorial library → · Research methods →