Privacy Policy & Consent Framework
Learn how NexusSSP handles programmatic telemetry, device signals, user privacy consent frameworks (GDPR, CCPA, COPPA), and cookieless identity resolution.
1. Information We Collect in Programmatic Auctions
NexusSSP operates as a Supply-Side Platform (SSP) and Ad Tech infrastructure. When bid requests are processed via OpenRTB 2.5, our system evaluates pseudonymized signals such as IP address (hashed/truncated for geo-location), User Agent, Device Type, and Publisher Ad Unit placement sizes. We do not store personally identifiable information (PII) like real names or raw street addresses.
2. IAB TCF v2.2 & Privacy Frameworks
NexusSSP natively supports IAB Europe Transparency and Consent Framework (TCF v2.2), US Privacy String (CCPA / CPRA), and Global Privacy Control (GPC). Consent strings are parsed in real-time before forwarding bid requests to demand-side partners (DSPs).
3. First-Party Identity Resolution (UID2 & RampID)
To maintain buyer addressability in cookie-less environments, NexusSSP supports publisher first-party identity modules including Unified ID 2.0 (UID2) and LiveRamp RampID. All email hashes processed through identity modules are salted and double-SHA256 encrypted on the client side.
4. Data Retention & Security Specs
Auction telemetry and event impression logs are aggregated and retained for 90 days for publisher reporting and billing reconciliation, after which raw auction log files are permanently deleted.