What this site records.
We use first-party interaction data to understand which claims, show positioning, and commercial ideas people genuinely respond to.
Anonymous experiment analytics
The site can record page views, button/link clicks, claim-card views after a short visibility threshold, the position where a claim appeared, claim detail views, Watch This Claim opens, scroll milestones, active-time checkpoints, section views, Quick Pick pair exposures and choices, share attempts/successes, form-field engagement by field name, referring source, campaign tags, browser language, approximate device type, viewport size, and which homepage version was shown.
We use random first-party visitor and session IDs so multiple actions can be understood as part of the same visit. We also store first-touch campaign attribution so a later signup can still be connected to the source that originally brought the visitor to the site.
Information you choose to submit
If you provide an email to watch a claim, submit a claim idea, answer the optional question about why a claim interests you, or request sponsorship information, that submitted information is stored in separate first-party data files. Sponsor enquiries can also include the partnership type, realistic pilot budget range, timing, and an optional claim of interest.
What we intentionally do not collect
We do not intentionally record passwords, raw keystrokes, the text you type before submitting it, mouse-movement recordings, third-party advertising identifiers, or a device fingerprint. The analytics event endpoint does not intentionally store your IP address.
Why content order can change
Claims are randomized by browsing session so one idea does not win simply because it is always displayed first. Quick Pick also randomizes which claim appears on the left or right. We do not show public popularity numbers while the experiment is running because seeing other people’s choices could influence yours.
Homepage experiment
Visitors may see one of two homepage messages: one emphasizing the show itself and one emphasizing participation in choosing what gets tested. The private dashboard compares downstream behaviour such as claim exploration and email commitment.
Storage and retention
Experiment data is stored on the site’s own server in protected files. Before broad public recruitment, the site operator should define and follow an appropriate retention period for the jurisdictions being targeted.
This operational notice explains how the test build works. It is not legal advice. If the experiment targets people in jurisdictions with stricter consent requirements, adapt the consent flow before launch.