{"_id":"5adf75322078f400032ad592","project":"5661bda6f5a87e0d00db3285","version":{"_id":"5661bda7f5a87e0d00db3288","project":"5661bda6f5a87e0d00db3285","__v":9,"createdAt":"2015-12-04T16:21:59.490Z","releaseDate":"2015-12-04T16:21:59.490Z","categories":["5661bda8f5a87e0d00db3289","5661cd4bf183880d004d3195","5666281e3fcf5a0d000ef16b","56902d2e18c3920d00be8b5f","56afc7545b1f01170014dc31","56f9a06a4d2b4f3400edb648","5761c2fe207db7170022fc51","5925d868feb3f90f000a7595","5925db7af33cb40f007604fa"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"Learning the PushSpring UI","version_clean":"1.0.0","version":"1.0"},"category":{"_id":"5925db7af33cb40f007604fa","project":"5661bda6f5a87e0d00db3285","version":"5661bda7f5a87e0d00db3288","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-05-24T19:14:02.619Z","from_sync":false,"order":2,"slug":"best-practices","title":"Best Practices"},"user":"5661cc12f183880d004d3193","githubsync":"","__v":0,"parentDoc":null,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2018-04-24T18:19:30.232Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":3,"body":"GDPR is all the buzz, and for good reason. These regulations have a direct influence on how a major portion of the advertising world operates. Let’s take a look at how GDPR influences the way PushSpring does business.  \n[block:api-header]\n{}\n[/block]\n**What is GDPR?** \n\nThe General Data Protection Regulation (GDPR) takes effect May 25, 2018, and is designed to give consumers in the European Union more control and transparency over their personal data. Moreover, the GDPR defines personal data broadly so as to include pseudonymous digital identifiers such as cookie IDs, IP addresses and mobile advertising IDs. \n\nAs part of PushSpring's commitment to compliance, we are implementing some important updates to our approach to data collection in the EU.\n\n[block:api-header]\n{}\n[/block]\n**Who is affected by the GDPR?** \n\nWhile PushSpring does not have a physical presence in the EU (i.e., an office), non-EU established companies are still required to adhere to the standards set by the GDPR in a specific instance.  In cases where companies process personal data about EU data subjects in connection with “monitoring” the behavior of EU data subjects, GDPR should be applied. In other words, processing personal data of EU data subjects for marketing purposes would subject PushSpring to the GDPR.\n[block:api-header]\n{}\n[/block]\n**How has PushSpring responded?** \n\nIn response, PushSpring has implemented a variety of mechanisms that will effectively stop any collection of EU-based device data going forward. In particular, when any of our data collection technology is used on a device, our systems are able to detect whether or not the device is located in the EU. For EU-based devices, our data center immediately deletes that data prior to processing. As a result, the PushSpring platform will not process the data of EU data subjects and will not be subject to GDPR requirements.\nPushSpring will continue to offer ethically sourced audience data at scale for digital marketers in non-GDPR countries such as the US and Canada, in full compliance with local laws as well as DAA guidelines governing data collection, use, and processing.","excerpt":"","slug":"gdpr-pushspring","type":"basic","title":"GDPR & PushSpring"}
GDPR is all the buzz, and for good reason. These regulations have a direct influence on how a major portion of the advertising world operates. Let’s take a look at how GDPR influences the way PushSpring does business. [block:api-header] {} [/block] **What is GDPR?** The General Data Protection Regulation (GDPR) takes effect May 25, 2018, and is designed to give consumers in the European Union more control and transparency over their personal data. Moreover, the GDPR defines personal data broadly so as to include pseudonymous digital identifiers such as cookie IDs, IP addresses and mobile advertising IDs. As part of PushSpring's commitment to compliance, we are implementing some important updates to our approach to data collection in the EU. [block:api-header] {} [/block] **Who is affected by the GDPR?** While PushSpring does not have a physical presence in the EU (i.e., an office), non-EU established companies are still required to adhere to the standards set by the GDPR in a specific instance. In cases where companies process personal data about EU data subjects in connection with “monitoring” the behavior of EU data subjects, GDPR should be applied. In other words, processing personal data of EU data subjects for marketing purposes would subject PushSpring to the GDPR. [block:api-header] {} [/block] **How has PushSpring responded?** In response, PushSpring has implemented a variety of mechanisms that will effectively stop any collection of EU-based device data going forward. In particular, when any of our data collection technology is used on a device, our systems are able to detect whether or not the device is located in the EU. For EU-based devices, our data center immediately deletes that data prior to processing. As a result, the PushSpring platform will not process the data of EU data subjects and will not be subject to GDPR requirements. PushSpring will continue to offer ethically sourced audience data at scale for digital marketers in non-GDPR countries such as the US and Canada, in full compliance with local laws as well as DAA guidelines governing data collection, use, and processing.