What did Radar see on Capcom?

Chrome (Chromium) scan of 2026-11-13 02:15:19 UTC.

Headline for the Before choice window

We observed 6 signal families across 1 script during the observation window before any consent choice, measured in Chrome (Chromium) 153 on linux from tr-workstation.

  • Measured in Chrome (Chromium) 153 on linux from tr-workstation.
  • Across 3 valid runs, all 6 observed signal families appeared in every run.

Read this first

  • This report describes one scan: Chrome (Chromium) 153.0.8010.12, region tr-workstation, method version NR-v0.3.0.
  • Scans of another browser, region or method version are separate and never merged into it.
  • Counts describe what Radar observed in this scan; they are not a rating.
  • 19 limitations are recorded for this scan. Read the limitations

Choose a window

Counts in this scan

Radar loaded the page four ways, each time in a fresh browser profile. Pick a window; every number below follows it.

Showing Before choice: 3 of 3 runs valid.

  • Signal families6all before choicesame in all 3 valid runsView evidence
  • API surfaces18all before choicesame in all 3 valid runsView evidence
  • Scripts1all before choicesame in all 3 valid runsView evidence
  • Destinations2all before choice0 third-partysame in all 3 valid runsView evidence
  • Data-flow-linked transmissions0all before choice1 correlated onlysame in all 3 valid runsView evidence

Means over valid runs, rounded to whole numbers. Counts describe what Radar observed in this browser, region and method version; they are not a rating.

The four windows side by side

One group per count: the same measure in each window. A window without a valid run shows why and is never drawn as zero.

Means over valid runs, rounded for the chart. Reject all and Accept all count events after the choice only.

How these four counts were measured

Each window starts from a fresh browser profile. You are looking at Before choice.

Stage 1 of 5: Fresh profile

Every situation starts in a new browser profile of its own and loads the same entry page, so no cookie, storage or consent state carries over from one situation to the next.

One fresh browser profile branches into four situations, each run in a new profile of its own. Before choice: no consent action, the whole observation window is counted. Reject all: the most comprehensive rejection control is used, and only events after the action settled are counted. Accept all: the most comprehensive acceptance control is used, and only events after the action settled are counted. GPC enabled: the Global Privacy Control signal is sent with no consent action, and the whole window is counted. Events before a consent action are reported separately and never added.

For Before choice

Notes about this scan (3)

What to know before you read the numbers: the window, other browsers and any run that did not count.

  • Also measured in Firefox
    Radar has a separate Firefox scan of this platform. Numbers are never merged across browsers. Open the Firefox report
  • Before choice: whole observation window
    Every event from navigation until the 10 s observation window ends. No consent action is taken in these runs, so all events are before choice.
  • No consent interface observed
    No consent interface observed from our test location in Türkiye on 13 Nov 2026, in 3 runs of this scenario. It describes this scan only, not what the platform shows from other places or on other days.

Runs in this scenario (3)

Each repeat is a separate visit in a fresh profile. Only valid runs enter the counts.

  • 1st of 3 repeatsValidNo consent interface observed.
  • 2nd of 3 repeatsValidNo consent interface observed.
  • 3rd of 3 repeatsValidNo consent interface observed.

From the evidence

Findings and questions

Sentences made of observed numbers, and questions answered only from what this scan observed.

What the numbers say

  • Before any consent choice the browser sent 18 requests, 0 of them to 0 other registrable domains (median of 3 valid runs).

    • external registrable domains 0
    • requests 18
    • runs valid 3
    • third party requests 0
  • 6 signal families accessed before any consent choice: Canvas, Navigator / device, Screen / window, Storage, Locale / time zone, Plugins and MIME types.

    • runs valid 3
    • signal families 6
  • 0 third-party cookie keys observed before any consent choice.

    • runs valid 3
    • third party cookie keys 0
  • Reject all: no consent interface was found to act on (0 of 3 runs valid), so its stage is not compared.

    • runs total 3
    • runs valid 0
  • Accept all: no consent interface was found to act on (0 of 3 runs valid), so its stage is not compared.

    • runs total 3
    • runs valid 0
  • GPC enabled: 18 requests in the whole observation window against 18 before any choice, 0 to 0 other registrable domains (median of 3 valid runs).

    • external registrable domains 0
    • requests 18
    • requests before choice 18
    • runs valid 3
    • third party requests 0
  • Of 9 techniques Radar observes, 1 was observed, 6 measurable and not observed, 2 not measured.

    • not measured 2
    • not observed 6
    • observed 1

Questions, answered from the evidence

Did the scan observe canvas image reads?
Yes, in Before choice: 2 technique cards list the script, the stage and the evidence. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Observed
Did the scan observe font probing?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe audio or WebGL reads?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe WebRTC connection set-up?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe identifier-like values written to storage?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe third-party cookies?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe candidate identifier values sent to another party?
No. It could be measured and was not observed in the 6 valid runs. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not observed
Did the scan observe typed made-up values sent to another party?
Not measured: no form field was typed into in any valid run. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not measured
Did the scan observe hashed made-up contact details sent to another party?
Not measured: no form field was typed into in any valid run. Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
Not measured

Not a guarantee: observed from one location on one date. Not observed is not proof of absence.

Descriptive score

Score of this scan

A versioned arithmetic over what was observed: it starts at 100 and every deduction is listed with its evidence.

Score
96 of 100Method NR-SCORE-1
Coverage
88%8 of 9 items measured; the floor is 70%
Percentile
94in a corpus of 288 scored platforms
Rank
14 of 288in the same corpus
Not a legal assessment. Not a guarantee. Observed from one location on one date.

Platform operators can reply to a score, ask for a correction or opt out by writing to hello@noxtica.com.

Write to hello@noxtica.com

Every deduction of the score: 100 minus 4 points
ItemObservedRulePoints taken offEvidence
Third-party requests before any choice0 third-party requestsBefore choice, median of 3 valid runs, rounded up1 point per 10 units, at most 80No evidence id
External registrable domains contacted before any choice0 external registrable domainsBefore choice, median of 3 valid runs, rounded up2 points per unit, at most 160No evidence id
Third-party cookies set before any choice0 third-party cookie keysBefore choice, median of 3 valid runs, rounded up2 points per unit, at most 80No evidence id
Fingerprint-like technique observations before any choice1 techniques (canvas, fonts, audio or WebGL, WebRTC)Before choice, median of 3 valid runs, rounded up4 points per unit, at most 124
Candidate identifiers shared with other registrable domains0 receiving registrable domainsBefore choice, median of 3 valid runs, rounded up2 points per unit, at most 80No evidence id
Typed made-up values sent to other parties (unhashed forms)0 receiving partiesBefore choice, median of 3 valid runs, rounded up7 points per unit, at most 140No evidence id
Hashed contact details sent to other parties0 receiving partiesBefore choice, median of 3 valid runs, rounded up7 points per unit, at most 140No evidence id
External registrable domains contacted with Global Privacy Control enabled0 external registrable domainsGPC enabled, median of 3 valid runs, rounded up2 points per unit, at most 100No evidence id

Points taken off in total: 4. Score: 100 minus 4 = 96. An item that could not be measured takes nothing off and lowers the coverage.

Items that could not be measured

  • External registrable domains contacted after Reject all: no consent interface was detected in this scan, so Reject all could not be tried. This is a finding about the page, not a failure of the measurement.
  • Score method NR-SCORE-1: the score starts at 100 and each measured item takes the points of its table entry, listed here with the observed count and the evidence it cites.
  • Coverage is 88%: 8 of 9 scoring items were measured. An item that could not be measured deducts nothing.
  • 1 item was not measured: External registrable domains contacted after Reject all.
  • Counts: median over the valid runs of the scenario, rounded up; a count taken from rows (third-party cookie keys, shared identifiers, typed values) counts a row when it was observed in at least half of the valid runs of the scenario.

The score method, with the table of deductions

What next

The report is four steps. This is the first; the others hold the detail behind these counts.