Identifier sync request to two documented data brokers after acceptance
After consent was accepted, the browser sent cookie identifiers to Keystone Identity Graph and Brightpath Data Co. on article pages.
- Why it matters
- Identifier syncing lets recipients match a visitor across services. Both recipients have documented broker registrations.
- Conditions
- Consent accepted · US-West · desktop Chromium
- Confidence basis
- Readable request contents in 3 repeated sessions.
- Limits of this finding
- What either company did with the identifier afterward is not observable.
- What you can do
- Reject optional cookies in the site’s consent dialog.
Evidence records (2)
R-DL-0311Consent acceptedt+00:00:04
GET https://sync.keystoneid.example/match
Redacted request parameters for R-DL-0311 Parameter Value partner_uid 9c1e••••••••(redacted) src dailyledger.example R-DL-0314Consent acceptedt+00:00:05
GET https://pixel.brightpath.example/p
Redacted request parameters for R-DL-0314 Parameter Value uid bp_••••••(redacted) ref dailyledger.example/world