Wolt 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 Wolt?
Chrome (Chromium) scan of 2026-11-13 17:24:54 UTC.
Headline for the Before choice window
We observed 16 signal families across 41 scripts, with 10 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, 15 of 17 observed signal families appeared in every run and 2 appeared in some runs only.
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.
- 17 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 families16all before choicerange 15–17 over 3 valid runsView evidence
- API surfaces90all before choicerange 85–101 over 3 valid runsView evidence
- Scripts41all before choicerange 24–75 over 3 valid runsView evidence
- Destinations23all before choice14 third-partyrange 14–42 over 3 valid runsView evidence
- Data-flow-linked transmissions10all before choice62 correlated onlyrange 3–25 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.
- Also measured in FirefoxRadar has a separate Firefox scan of this platform. Numbers are never merged across browsers. Open the Firefox report
- 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.
Runs in this scenario (3)
Each repeat is a separate visit in a fresh profile. Only valid runs enter the counts.
- 1st of 3 repeatsValidThe run completed and enters comparisons.
- 2nd of 3 repeatsValidThe run completed and enters comparisons.
- 3rd of 3 repeatsValidThe run completed and enters comparisons.
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 167 requests, 47 of them to 8 other registrable domains (median of 3 valid runs).
- external registrable domains 8
- requests 167
- runs valid 3
- third party requests 47
17 signal families accessed before any consent choice: Canvas, WebGL, Audio, 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, Battery, Plugins and MIME types, Math / engine behaviour.
- runs valid 3
- signal families 17
20 third-party cookie keys observed before any consent choice.
- runs valid 3
- third party cookie keys 20
Reject all: 16 requests after the choice against 167 before any choice, 7 to 2 other registrable domains (median of 3 valid runs).
- external registrable domains 2
- requests 16
- requests before choice 167
- runs valid 3
- third party requests 7
Accept all: 83 requests after the choice against 167 before any choice, 65 to 15 other registrable domains (median of 3 valid runs).
- external registrable domains 15
- requests 83
- requests before choice 167
- runs valid 3
- third party requests 65
GPC enabled: 167 requests in the whole observation window against 167 before any choice, 47 to 8 other registrable domains (median of 3 valid runs).
- external registrable domains 8
- requests 167
- requests before choice 167
- runs valid 3
- third party requests 47
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 6 registrable domains (9 rows); the candidate set is unvalidated.
- registrable domains 6
- rows 9
Across 1 checked Before choice run, the policy page the scanner found named 0 of the observed third-party organisations, did not name 5, and named 0 that were not observed.
- named and observed 0
- named not observed 0
- observed not named 5
- runs checked 1
Questions, answered from the evidence
- Did the scan observe canvas image reads?
- Yes, in Before choice: 4 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 font probing?
- No. It could be measured and was not observed in the 12 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: 4 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 WebRTC connection set-up?
- No. It could be measured and was not observed in the 12 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?
- No. It could be measured and was not observed in the 12 valid runs. 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, Accept all, GPC enabled: 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 candidate identifier values sent to another party?
- Yes, in Before choice, Accept all: 6 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 12 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 12 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 2 requests, Reject all 5 requests, Accept all 18 requests, GPC enabled 2 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: Accept all 19 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 Microsoft?
- Yes: Accept all 16 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 Apple?
- Yes: Before choice 1 request, GPC enabled 1 request (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 Meta?
- Yes: Accept all 2 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
- 55 of 100Method NR-SCORE-1
- Coverage
- 100%9 of 9 items measured; the floor is 70%
- Percentile
- 34in a corpus of 288 scored platforms
- Rank
- 185 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 | 47 third-party requestsBefore choice, median of 3 valid runs, rounded up | 1 point per 10 units, at most 8 | 5 | |
| External registrable domains contacted before any choice | 8 external registrable domainsBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 16 | 16 | |
| Third-party cookies set before any choice | 1 third-party cookie keysBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 8 | 2 | |
| Fingerprint-like technique observations before any choice | 2 techniques (canvas, fonts, audio or WebGL, WebRTC)Before choice, median of 3 valid runs, rounded up | 4 points per unit, at most 12 | 8 | |
| Candidate identifiers shared with other registrable domains | 0 receiving registrable domainsBefore choice, median of 3 valid runs, rounded up | 2 points per unit, at most 8 | 0 | No evidence id |
| 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 after Reject all | 2 external registrable domainsReject all, median of 3 valid runs, rounded up | 2 points per unit, at most 10 | 4 | |
| External registrable domains contacted with Global Privacy Control enabled | 8 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: 45. Score: 100 minus 45 = 55. An item that could not be measured takes nothing off and lowers the coverage.
- 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 100%: 9 of 9 scoring items were measured. An item that could not be measured deducts nothing.
- 1 deduction 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.