Ulta Beauty 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 Ulta Beauty?
Chrome (Chromium) scan of 2026-11-13 15:55:24 UTC.
Headline for the Before choice window
We observed 16 signal families across 61 scripts, with 100 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 16 observed signal families appeared in every run and 1 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.
- 18 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–16 over 3 valid runsView evidence
- API surfaces68all before choicerange 62–75 over 3 valid runsView evidence
- Scripts61all before choicerange 55–70 over 3 valid runsView evidence
- Destinations111all before choice65 third-partyrange 103–115 over 3 valid runsView evidence
- Data-flow-linked transmissions100all before choice457 correlated onlyrange 71–146 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 762 requests, 512 of them to 66 other registrable domains (median of 3 valid runs).
- external registrable domains 66
- requests 762
- runs valid 3
- third party requests 512
16 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, Battery, Plugins and MIME types, Math / engine behaviour.
- runs valid 3
- signal families 16
63 third-party cookie keys observed before any consent choice.
- runs valid 3
- third party cookie keys 63
Reject all: 28 requests after the choice against 762 before any choice, 27 to 5 other registrable domains (median of 3 valid runs).
- external registrable domains 5
- requests 28
- requests before choice 762
- runs valid 3
- third party requests 27
Accept all: 128 requests after the choice against 762 before any choice, 103 to 20 other registrable domains (median of 3 valid runs).
- external registrable domains 20
- requests 128
- requests before choice 762
- runs valid 3
- third party requests 103
GPC enabled: 731 requests in the whole observation window against 762 before any choice, 488 to 66 other registrable domains (median of 3 valid runs).
- external registrable domains 66
- requests 731
- requests before choice 762
- runs valid 3
- third party requests 488
Of 9 techniques Radar observes, 3 were observed, 4 measurable and not observed, 2 not measured.
- not measured 2
- not observed 4
- observed 3
Candidate cookie values were found in requests to 18 registrable domains (218 rows); the candidate set is unvalidated.
- registrable domains 18
- rows 218
Across 1 checked Before choice run, the policy page the scanner found named 2 of the observed third-party organisations, did not name 14, and named 0 that were not observed.
- named and observed 2
- named not observed 0
- observed not named 14
- runs checked 1
Questions, answered from the evidence
- Did the scan observe canvas image reads?
- 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 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: 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 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, Reject all, Accept all, GPC enabled: 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 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?
- 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.
- 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.
- Did the scan observe requests to Google?
- Yes: Before choice 116 requests, Accept all 18 requests, GPC enabled 125 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 22 requests, Reject all 3 requests, Accept all 11 requests, GPC enabled 22 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 OneTrust?
- Yes: Before choice 12 requests, Reject all 1 request, Accept all 1 request, 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 Adobe?
- Yes: Before choice 9 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 Pinterest?
- Yes: Before choice 8 requests, Accept all 1 request, 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 The Trade Desk?
- Yes: Before choice 6 requests, Accept all 2 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 Criteo?
- Yes: Before choice 5 requests, Accept all 2 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 Xandr (Microsoft)?
- Yes: Before choice 5 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 Index Exchange?
- Yes: Before choice 4 requests, GPC enabled 4 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 3 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 PubMatic?
- Yes: Before choice 3 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 Akamai?
- Yes: Before choice 2 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.
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
- 36 of 100Method NR-SCORE-1
- Coverage
- 100%9 of 9 items measured; the floor is 70%
- Percentile
- 2in a corpus of 288 scored platforms
- Rank
- 279 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 | 513 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 | 68 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 | 48 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 | 16 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 after Reject all | 5 external registrable domainsReject all, median of 3 valid runs, rounded up | 2 points per unit, at most 10 | 10 | |
| External registrable domains contacted with Global Privacy Control enabled | 66 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: 64. Score: 100 minus 64 = 36. 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.
- 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.