PC Gamer is named for identification only; no affiliation or endorsement is implied. Results are what an automated browser observed at one point in time, from one vantage point; they are not legal advice and not a legal determination.
Data as of How Radar measures
Scan details
What did Radar see on PC Gamer?
Chrome (Chromium) scan of 2026-11-13 19:22:02 UTC.
Headline for the Before choice window
We observed 15 signal families across 80 scripts, with 103 data-flow-linked transmissions, 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 15 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.
- 21 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 families15all before choicesame in all 3 valid runsView evidence
- API surfaces63all before choicerange 63–64 over 3 valid runsView evidence
- Scripts80all before choicerange 75–89 over 3 valid runsView evidence
- Destinations225all before choice131 third-partyrange 216–238 over 3 valid runsView evidence
- Data-flow-linked transmissions103all before choice343 correlated onlyrange 62–184 over 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.
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 (2)
What to know before you read the numbers: the window, other browsers and any run that did not count.
- Before choice: whole observation windowEvery 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 observedNo 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 804 requests, 756 of them to 130 other registrable domains (median of 3 valid runs).
- external registrable domains 130
- requests 804
- runs valid 3
- third party requests 756
15 signal families accessed before any consent choice: Canvas, WebGL, Navigator / device, Hardware (CPU, memory), Screen / window, Media devices and codecs, Permissions, Storage, Timing / performance, CSS / media capabilities, Client Hints, Locale / time zone, Network information, Plugins and MIME types, Math / engine behaviour.
- runs valid 3
- signal families 15
207 third-party cookie keys observed before any consent choice.
- runs valid 3
- third party cookie keys 207
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: 586 requests in the whole observation window against 804 before any choice, 538 to 107 other registrable domains (median of 3 valid runs).
- external registrable domains 107
- requests 586
- requests before choice 804
- runs valid 3
- third party requests 538
Of 9 techniques Radar observes, 4 were observed, 5 measurable and not observed, 0 not measured.
- not measured 0
- not observed 5
- observed 4
Candidate cookie values were found in requests to 49 registrable domains (344 rows); the candidate set is unvalidated.
- registrable domains 49
- rows 344
Questions, answered from the evidence
- Did the scan observe canvas image 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.
- 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.
- Did the scan observe audio or WebGL reads?
- Yes, in Before choice: 1 technique card 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.
- 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.
- Did the scan observe identifier-like values written to storage?
- Yes, in Before choice: 3 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.
- Did the scan observe third-party cookies?
- Yes, in Before choice, GPC enabled: 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.
- Did the scan observe candidate identifier values sent to another party?
- Yes, in Before choice: 7 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.
- Did the scan observe typed made-up 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.
- Did the scan observe hashed made-up contact details 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.
- Did the scan observe requests to Google?
- Yes: Before choice 44 requests, GPC enabled 35 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to PubMatic?
- Yes: Before choice 52 requests, GPC enabled 12 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Magnite?
- Yes: Before choice 38 requests, GPC enabled 18 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Amazon?
- Yes: Before choice 23 requests, GPC enabled 18 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to ByteDance?
- Yes: Before choice 18 requests, GPC enabled 18 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Index Exchange?
- Yes: Before choice 18 requests, GPC enabled 18 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to OpenX?
- Yes: Before choice 21 requests, GPC enabled 6 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to The Trade Desk?
- Yes: Before choice 11 requests, GPC enabled 9 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Yahoo?
- Yes: Before choice 12 requests, GPC enabled 5 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Sourcepoint?
- Yes: Before choice 8 requests, GPC enabled 8 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Sovrn?
- Yes: Before choice 8 requests, GPC enabled 7 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
- Did the scan observe requests to Adobe?
- Yes: Before choice 8 requests, GPC enabled 6 requests (median over the valid runs). Not a guarantee: observed from one location on one date. Not observed is not proof of absence.
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
- 46 of 100Method NR-SCORE-1
- Coverage
- 88%8 of 9 items measured; the floor is 70%
- Percentile
- 16in a corpus of 288 scored platforms
- Rank
- 225 of 288in the same corpus
Platform operators can reply to a score, ask for a correction or opt out by writing to hello@noxtica.com.
| Item | Observed | Rule | Points taken off | Evidence |
|---|---|---|---|---|
| Third-party requests before any choice | 759 third-party requestsBefore choice, median of 2 valid runs, rounded up | 1 point per 10 units, at most 8 | 8capped at 8 | |
| External registrable domains contacted before any choice | 130 external registrable domainsBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 16 | 16capped at 16 | |
| Third-party cookies set before any choice | 176 third-party cookie keysBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 8 | 8capped at 8 | |
| Fingerprint-like technique observations before any choice | 1 techniques (canvas, fonts, audio or WebGL, WebRTC)Before choice, median of 3 valid runs, rounded up | 4 points per unit, at most 12 | 4 | |
| Candidate identifiers shared with other registrable domains | 40 receiving registrable domainsBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 8 | 8capped at 8 | |
| Typed made-up values sent to other parties (unhashed forms) | 0 receiving partiesBefore choice, median of 3 valid runs, rounded up | 7 points per unit, at most 14 | 0 | No evidence id |
| Hashed contact details sent to other parties | 0 receiving partiesBefore choice, median of 3 valid runs, rounded up | 7 points per unit, at most 14 | 0 | No evidence id |
| External registrable domains contacted with Global Privacy Control enabled | 107 external registrable domainsGPC enabled, median of 3 valid runs, rounded up | 2 points per unit, at most 10 | 10capped at 10 |
Points taken off in total: 54. Score: 100 minus 54 = 46. 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.
- 5 deductions reached the cap of its table entry.
- 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.
What next
The report is four steps. This is the first; the others hold the detail behind these counts.