{"_id":"58ed2045f2bce21900301384","category":{"_id":"58ed1bdc068f780f00f64602","__v":0,"project":"55de06fa57f7b20d0097636b","version":"55de06fa57f7b20d0097636e","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-04-11T18:09:32.839Z","from_sync":false,"order":11,"slug":"data-transfer-and-integration","title":"Data Transfer and Integration"},"project":"55de06fa57f7b20d0097636b","user":"55de06e19db51a0d0064947d","__v":0,"parentDoc":null,"version":{"_id":"55de06fa57f7b20d0097636e","project":"55de06fa57f7b20d0097636b","__v":14,"createdAt":"2015-08-26T18:35:38.642Z","releaseDate":"2015-08-26T18:35:38.642Z","categories":["55de06fb57f7b20d0097636f","55f1962e3936d52d00fb3c8f","55f1970339e3e8190068b2b8","55f1970d229b772300779a1f","55f1971cfd98c42300acc605","55f1d5c7fd98c42300acc69f","563cbfe4260dde0d00c5e9d4","5644cf437f1fff210078e690","57dc1bbd3ed3450e00dc9ea7","58a600a2243dd30f00fd8773","58ed1bdc068f780f00f64602","58f13b3a4f0ee50f00e24e81","58f173f792f9020f009cad16","591b42f8e633fd0f00077c5a"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2017-04-11T18:28:21.972Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":4,"body":"PushSpring requires all partners accessing its data to comply with NAI Code of Conduct related to data transfer, access, security, and retention.  The complete NAI Code of Conduct is available here: [http://www.networkadvertising.org/2013_Principles.pdf](http://www.networkadvertising.org/2013_Principles.pdf)\nRelevant language from this document is included below: \n**Section E**:\n2.  Members shall contractually require that all parties to whom they provide Non-PII collected across web domains owned or operated by different entities not attempt to merge such Non-PII with PII held by the receiving party or to re-identify the individual without obtaining the individual’s Opt-In Consent. This requirement does not apply where the Non-PII is proprietary data of the receiving party.\n\n**Section F**:\n3.  Members that collect, transfer, or store data for use in Interest-Based Advertising and/or Ad Delivery and Reporting shall provide reasonable Security for that data.\n\n4.  Members engaged in Interest-Based Advertising and/or Ad Delivery and Reporting shall retain Non-PII and PII collected for these activities only as long as necessary to fulfill a legitimate business need, or as required by law.","excerpt":"","slug":"data-security","type":"basic","title":"Compliance Requirements"}

Compliance Requirements


PushSpring requires all partners accessing its data to comply with NAI Code of Conduct related to data transfer, access, security, and retention. The complete NAI Code of Conduct is available here: [http://www.networkadvertising.org/2013_Principles.pdf](http://www.networkadvertising.org/2013_Principles.pdf) Relevant language from this document is included below: **Section E**: 2. Members shall contractually require that all parties to whom they provide Non-PII collected across web domains owned or operated by different entities not attempt to merge such Non-PII with PII held by the receiving party or to re-identify the individual without obtaining the individual’s Opt-In Consent. This requirement does not apply where the Non-PII is proprietary data of the receiving party. **Section F**: 3. Members that collect, transfer, or store data for use in Interest-Based Advertising and/or Ad Delivery and Reporting shall provide reasonable Security for that data. 4. Members engaged in Interest-Based Advertising and/or Ad Delivery and Reporting shall retain Non-PII and PII collected for these activities only as long as necessary to fulfill a legitimate business need, or as required by law.