https://wiki.personaldata.io/w/api.php?action=feedcontributions&feedformat=atom&user=Pm88 2026-05-14T03:48:13Z User contributions MediaWiki 1.35.1 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59518 2019-08-01T14:17:45Z

<p>Pm88: /* Why it is important */</p> <hr /> <div>Drawn from the [https://www.webxray.org webXray project], this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * The domain ownership list needs to be populated to offer an index of simply where personal data is being sent, and where the legal ownership of the domains rests. <br /> * Without these fields, the filing of SARs is far more time consuming, and mass inspections of websites are barely intelligible. <br /> <br /> The third party tracking ecosystem is currently free to operate and monetise individuals personal data without transparency. The domain ownership list is a step to addressing this.<br /> <br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * Framework for contributions and easy format for submission.<br /> * contributions!</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59490 2019-07-31T10:59:03Z

<p>Pm88: </p> <hr /> <div>Drawn from the [https://www.webxray.org webXray project], this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * Framework for contributions and easy format for submission.<br /> * contributions!</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59489 2019-07-31T10:56:58Z

<p>Pm88: /* Wishlist WebXRay side */</p> <hr /> <div>Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * Framework for contributions and easy format for submission.<br /> * contributions!</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59488 2019-07-31T10:56:44Z

<p>Pm88: /* Wishlist WebXRay side */</p> <hr /> <div>Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * Framework for contributions and easy format for submission.<br /> * Bulleted list item<br /> contributions!</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59487 2019-07-31T10:56:31Z

<p>Pm88: /* Wishlist WebXRay side */</p> <hr /> <div>Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * Framework for contributions and easy format for submission.<br /> - contributions!</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59486 2019-07-31T10:55:35Z

<p>Pm88: </p> <hr /> <div>Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.<br /> <br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * ???</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59485 2019-07-31T10:54:57Z

<p>Pm88: </p> <hr /> <div>The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> ==What the database contains==<br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * ???</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59484 2019-07-31T10:54:20Z

<p>Pm88: /* What the database contains */</p> <hr /> <div>==What the database contains==<br /> The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].<br /> <br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * ???</div>

Pm88 https://wiki.personaldata.io/w/index.php?title=WebXray_domain_ownership_list&diff=59483 2019-07-31T10:52:28Z

<p>Pm88: /* What the database contains */</p> <hr /> <div>==What the database contains==<br /> <br /> The list is a JSON file. Each entry in the list has the following fields:<br /> <br /> id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable<br /> <br /> parent_id: if the entity has a parent owner, the id of the parent<br /> <br /> owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain<br /> <br /> aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')<br /> <br /> homepage_url: a string which is the url of the homepage of the service or company<br /> <br /> privacy_policy_url: a string which is the url of the privacy policy of the service or company<br /> <br /> notes: a string which has pertinent information as to why a domain was assigned to a given owner<br /> <br /> country: the ccTLD for the country in which the service or company is based<br /> <br /> uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.<br /> <br /> platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'<br /> <br /> domains: an array of domian names (strings) which are owned by the given service or company<br /> <br /> ==Why it is important==<br /> * adtech sucks! <br /> * third party tracking is the worst<br /> ==Why it is important to build it collaboratively==<br /> * can do SARs, and build the whole pipeline of support around that<br /> * can do visualisations, maybe not for the general public but at least for super users of PDIO to better understand progress<br /> <br /> ==What needs to be done for PDIO==<br /> * define format for the adtech entries<br /> * complexify the SAR tool in order to leverage third party situations<br /> <br /> ==Wishlist WebXRay side==<br /> * ???</div>

Pm88