Consent and Privacy
Overview
UniSignIn is built on first-party data. Profiles, segments and insights belong to your organization and are never shared with other UniSignIn customers. Where the GDPR applies, UniSignIn follows the consent your visitors give in your consent management platform (CMP) through the IAB TCF framework.
What needs consent
Where the GDPR applies:
| Feature | Consent needed |
|---|---|
| Storing data on the visitor's device | Consent under your CMP |
| Visitor profiles, and targeting and segments based on them | TCF purpose 1 |
| Sharing segments with Google Ad Manager and Prebid | TCF purposes 1 and 4 |
When your page has a TCF consent tool, UniSignIn waits for the visitor's choice before storing data or sharing segments with ad systems. Where the GDPR doesn't apply, these features work without a consent signal.
Without consent
Visitors who don't give consent still get a working site:
- Experiences targeted by page context, such as URL, category or time of day, are still shown.
- Experiences that need the visitor profile or a segment don't match.
- The visitor isn't counted in the Audience Overview.
To grow consent, see Consent Rate Optimization and the Consent Recovery experience.
Personal data
- Personal details, such as names, email addresses and phone numbers, can't be used for targeting and are never sent to the page or to ad systems.
- Segment IDs shared with ad systems are codes, not personal data.
- Email open and click tracking only applies to registered users you send newsletters to.
Deleting data
When a user deletes their account, their profile is removed from UniSignIn segments and targeting, and they are removed from connected integrations such as Mailchimp and Iterable.
Bots
Bots and invalid traffic are recognised and don't get a profile, so they don't distort your segments, insights or ad audiences.
Stay ahead in first-party data
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.