<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:admin="http://webns.net/mvcb/"
	xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
	xmlns:content="http://purl.org/rss/1.0/modules/content/">

	<channel>

	<title>&#45; CircleID</title>
	<link>https://www.circleid.com/blogs/</link>
	<description>Postings from  on CircleID</description>
	<dc:language>en</dc:language>
	<dc:rights>Copyright 2026, unless where otherwise noted.</dc:rights>
	<dc:date>2026-04-08T19:45:00+00:00</dc:date>

	
	<item>
		<title> GDPR - Territorial Scope and the Need to Avoid Absurd and Inconsistent Results (Featured Blog)</title>
		<guid isPermaLink="true">https://circleid.com/posts20180214_gdpr_territorial_scope_need_to_avoid_absurd_inconsistent_results</guid>
		<link>https://circleid.com/posts20180214_gdpr_territorial_scope_need_to_avoid_absurd_inconsistent_results</link>
		<description><![CDATA[There is an urgent need to clarify the GDPR's territorial scope. Of the many changes the GDPR will usher in this May, the expansion of EU privacy law's territorial scope is one of the most important. The GDPR provides for broad application of its provisions both within the EU and globally. But the fact that the GDPR has a broad territorial scope does not mean that every company, or all data processing activities, are subject to it. <a href="https://circleid.com/posts20180214_gdpr_territorial_scope_need_to_avoid_absurd_inconsistent_results">More...</a>]]></description>
		<dc:date>2026-04-08T12:45:00-07:00</dc:date>
	</item>
	

	</channel>
</rss>