Baseline visit v1 schema · facts legacy-derived · descriptive report

www.pinterest.com

Requested addresshttps://www.pinterest.com/

Sep 28, 2026, 12:07 PM UTC

cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe stopped, or could not read in full, a request that may have carried its test value, so input-capture detection is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: evidence was cut short before completion (the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe stopped, or could not read in full, a request that may have carried its test value, so input-capture detection is incomplete; and 1 more). Counts for the affected evidence are lower bounds; families that completed carry only their ordinary limits. The evidence receipt states the exact per-visit quality.

Scan report ready for www.pinterest.com: 136 recorded request rows.

Comparison Reportv1 schema · facts legacy-derived · descriptive reportrequest evidence incomplete

Brave-list blocking off/on comparison

Recorded final address https://www.pinterest.com/ (opens in a new tab)

The selected visit did not finish collecting request evidence. Request counts are lower bounds; Run quality records the reason.

ShareDownloads the No blocking visit's request CSV, source report and correction context in a ZIP. Follows the evidence switcher below.PDF + evidence (opens in a new tab)Downloads a ZIP containing the PDF for every recorded visit, exact source JSON, correction context and file hashes. The scanner renders it on request.

What this actually means

pinterest.com triggered fingerprint-like browser API patterns.

2 browser-fingerprinting heuristics matched. These are heuristic review signals, not proof of fingerprinting intent.

≥6cross-site domains
≥105cross-site requests
2fingerprint-like patterns

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Worth checking

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds.

The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.

at least 136 retained requests observed in one controlled visit.

Worth checking

at least 10 retained requests matched Brave Shields filter lists

at least 10 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.

The hand-curated service catalog separately matched at least 0 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete. and The "Brave-list blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete.

The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.

2 disqualifying conditions named by the report's claim policy.Show matched requests

Context

Privacy policy read; it made no statement this scan can check

None of the statements this scan knows how to check appear in the policy text, so nothing was compared against this visit's evidence (no catalogued tracking companies observed to check against it). That is a limit of the automated check, not a finding about the site either way.

Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

Policy at https://{label}.pinterest.com/en/privacy-policy; 0 checkable statements matched; no catalogued tracking companies observed to check against it.

Context

Other third-party operators were identified outside the tracking-service catalog

Google were named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as tracking services.

Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking. This scan could not identify 2 of the 6 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

at least 105 retained cross-site requests across at least 6 retained third-party hosts.Show third-party requests

Context

Requests were dispatched to major-platform domains the catalog does not carry

This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.

Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload. These domains are not counted as catalog-matched requests. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

at least 6 retained cross-site domains seen overall.Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

No google-analytics.com or googletagmanager.com requests.Show catalog-matched requests

Nothing observed

No third-party cookies observed

The automated visit did not observe third-party cookies.

This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.

8 cookies total in this report.

Context

Input-monitoring signal involving a script from another domain

Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain, whose operator this scan did not establish.

This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Stack attribution records the script origins present in the bounded registration call chain; a cross-site origin in that chain does not by itself establish that the cross-site script registered the listener, because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain, so the card says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected); treat this card as a review prompt rather than proof.

104 interaction-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain and 41 input-listener registrations with https://accounts.google.com/, https://*.pinimg.com/ and https://www.gstatic.com/ in the registration call chain

Worth checking

Behavioral fingerprinting heuristics matched

2 behavioral heuristics matched: Offline audio rendering heuristic and Canvas fingerprinting heuristic.

These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup. They are review prompts for this visit, not proof of cross-site identity tracking.

1 offline render with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering and 1 canvas matched; reads: canvas.toDataURL

Brave Shields Comparison

No blocking and Brave-list blocking: two visits, no comparable metric delta

No blocking: 16,602msBrave-list blocking: 16,145ms
These two visits do not support a side-by-side comparison, so no deltas are shown.
  • The "No blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete.
  • The "Brave-list blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete.

Each visit's own evidence still stands: use the “Evidence shown” switcher below to inspect either visit's tables, and both visits are in the downloaded JSON.

Measurement limits

12 conditions affect how this evidence reads

This report

  • Brave-list blocking comparison runs should be collected under matched crawl conditions, and the blocking run is a simulation with Brave's engine and default lists in this scanner's browser, not a live Brave visit. Differences can still reflect timing, experiments, cache state, consent state, or bot detection.
  • The two visits ran in randomized order; the "No blocking" visit ran first.

Both visits

  • Each visit in this report is one automated, headless Chromium visit from a fixed en-US / UTC profile, with no scrolling, clicking, or consent interaction. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Counts are a lower bound: trackers that load only after interaction or consent are not observed; Service Workers are blocked, and Web Worker or WebSocket traffic may be incomplete. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled. Cookie and storage figures are an end-of-visit snapshot, with storage keys read from the top frame only.
  • The page did not reach network idle before the scan window ended.
  • The synthetic form-input probe stopped one or more navigations started while it ran, so this visit's request evidence is incomplete.
  • The synthetic form-input probe did not complete its test, so input-capture conclusions for this visit are incomplete.
  • Read the site's privacy policy (https://{label}.pinterest.com/en/privacy-policy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.

No blocking visit only

  • The synthetic form-input probe stopped, or could not read in full, one or more requests that may have carried its test value, so input-capture conclusions for this visit are incomplete.
  • This scan typed a synthetic test value into 1 form field with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.

Brave-list blocking visit only

  • Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.
  • This scan typed a synthetic test value into 2 form fields with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.

This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.

Report ID
20260928-04eb8e626ab019e0b63d3e2436f0a455
Site
www.pinterest.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe stopped, or could not read in full, a request that may have carried its test value, so input-capture detection is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.

This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.

Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. How detector accuracy is measured.

Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .