Skip to content

Re-attribute Yahoo/AOL/Oath trackers from Verizon to Yahoo Inc#1179

Merged
philipp-classen merged 7 commits into
ghostery:mainfrom
deanPGM:fix/yahoo-verizon-reattribution
Jul 13, 2026
Merged

Re-attribute Yahoo/AOL/Oath trackers from Verizon to Yahoo Inc#1179
philipp-classen merged 7 commits into
ghostery:mainfrom
deanPGM:fix/yahoo-verizon-reattribution

Conversation

@deanPGM

@deanPGM deanPGM commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Re-attributes the Yahoo / AOL / Oath tracker family from the stale verizon org to a new yahoo_inc ("Yahoo"), and moves the 3 Tumblr patterns to the existing automattic org.

The verizon org is a Verizon Media / Oath umbrella; Verizon sold that business to Apollo funds in 2021 (now Yahoo Inc.) and Tumblr went to Automattic in 2019.

The verizon org file is kept (not archived) as a few unrelated patterns still reference it.

Sources: Apollo funds complete acquisition of Yahoo (2021), Verizon Media, Tumblr → Automattic (2019).

Comment thread db/organizations/yahoo_inc.eno Outdated
@@ -0,0 +1,14 @@
name: Yahoo Inc.
website_url: https://www.yahooinc.com/
privacy_policy_url: https://legal.yahoo.com/us/en/yahoo/privacy/index.html

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to the privacy_policy_url is also a privacy_contact field (please compare with other organization files).

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, added privacy_contact field.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you recall where you found the privacy contact? Looks like they handle it differently for each region. In the US version of the privacy policy that linked, I did not spot it.

I see one only in the EU version (https://legal.yahoo.com/ie/en/yahoo/privacy/index.html)
dpo-contact@yahooinc.com

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My mistake, the email I originally used looks like it's from their employee/contractor privacy policy. I've updated this PR to include the contact from the EU version dpo-contact@yahooinc.com.

Their US privacy policy links another email also in section 14(c), but unsure if we should use as its an external GDPR rep rather than their internal DPO.

Our Article 27 Representative can be contacted by email at YahooGDPRrepresentative@mhc.ie

Let me know what is best practice here as to what email and privacy policy to include, or if their US privacy policy + DPO email is sufficient.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is sometimes indeed confusing. Some companies have no email contact at all.

There is no hard rule, but most important is that if we include one that it does exist (which is the case here). Otherwise, it trying to find the best match if there conflicting options.

It is an uncommon example here to have the US privacy policy and the EU GDPR contact, but I think it makes sense. For a US company, I would also take the US privacy policy as the canonical source. And since it lacks a better option, going for the EU privacy contact address makes sense, since it is a email that at least explicitly exists to reach the privacy contact.

Comment thread db/organizations/yahoo_inc.eno Outdated
website_url: https://www.yahooinc.com/
privacy_policy_url: https://legal.yahoo.com/us/en/yahoo/privacy/index.html
country: US
description: Yahoo Inc. is an American media and technology company whose brands include Yahoo, AOL, and Yahoo Advertising (formerly Oath / Verizon Media). Trackers previously filed under the Verizon organization are re-attributed here.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Trackers previously filed under the Verizon organization are re-attributed here.

True, but does not need to be mentioned in this context. (It is fine to mention in the notes section).

As a rule of thumb, a good company description should be like something that could be the introduction to its Wikipedia entry.

@deanPGM deanPGM Jul 10, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the direction on this, I've adjusted the description based on your feedback.

Comment thread db/patterns/5min_media.eno Outdated
@deanPGM deanPGM requested a review from philipp-classen July 10, 2026 15:33
privacy_policy_url: https://legal.yahoo.com/us/en/yahoo/privacy/index.html
privacy_contact: privacy-inquiries@yahooinc.com
country: US
description: Yahoo Inc. is an American media and technology company whose brands include Yahoo, AOL, and Yahoo Advertising (formerly Oath / Verizon Media).

@philipp-classen philipp-classen Jul 10, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just noticed that AOL was also sold now to Bending Spoons:
https://www.forbes.com/sites/iainmartin/2025/10/29/aol-has-a-new-italian-owner-unicorn-startup-bending-spoons/

I would recommend to leave out AOL here in the description.

But it means also that the AOL entries will move to Bending Spoons. Currently, I see no Bending Spoons organization file. Either we keep the aol_* patterns for now at yahoo and do it in a next step, or you could add a organization entry for bending_spoons.eno in this PR and use it.

@philipp-classen

Copy link
Copy Markdown
Member

Merging now as it (leaving the Bending Spoon acquisition of AOL for a follow-up).

@philipp-classen philipp-classen merged commit 42ed95e into ghostery:main Jul 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants