Privacy policy clauses for Snapchat Pixel
Snapchat Pixel is a tracking code that websites install to measure the effectiveness of Snapchat advertising campaigns. It records user actions on your website and sends this data to Snap Inc, enabling advertisers to track conversions, optimize campaigns, and build audience segments for retargeting.
Free scan · No signup · Results in 60 seconds
What data Snapchat Pixel collects
Your privacy policy must disclose each of the following data types when you use Snapchat Pixel.
When does Snapchat Pixel trigger privacy obligations?
Installing Snapchat Pixel immediately begins collecting page events and device information from all visitors—this is not deferred by consent. In GDPR jurisdictions (EU, UK, EEA), this triggers Article 6 lawfulness obligations the moment the pixel fires: you must have a legal basis (typically consent under Article 7, or legitimate interest under Article 6(1)(f)) *before* pixel deployment. Article 13/14 transparency obligations apply—you must disclose to visitors that Snap Inc processes their data in the US. The ePrivacy Directive Article 5(3) further requires prior consent for non-essential cookies or tracking technologies; although Snapchat Pixel uses no documented cookies, the pixel itself is a tracking mechanism requiring consent. In CCPA/CPRA jurisdictions (California), pixel deployment triggers Section 1798.100 disclosure obligations: you must inform consumers that their device information and page event data is being sold or shared with Snap Inc. If you have 100+ California residents or $25M+ revenue, CPRA compliance (including opt-out rights under Section 1798.120) applies. In all jurisdictions, the first concrete step is: document what personal data Snapchat Pixel actually collects from your specific implementation, confirm you have a lawful basis or valid consent mechanism active *before* the pixel loads, and update your privacy notice to name Snap Inc as a data processor with a link to their privacy policy.
