How to enable cross-domain consent
Cross-domain consent is useful when you want to collect user's consent across multiple domains using a single cookie banner.
Cross-domain consent is useful when you want to collect user's consent across multiple domains using a single cookie banner. It is good for the user experience when you redirect users to multiple websites/domains. You can see a video of the functionality here.
Follow these steps to enable cross-domain consent. We assume that you have already added your domains inside the domain management panel, and onboarding is complete for all domains.
1. Install Secure Privacy script on all domains.
2. Click on All Domains and navigate to Domains page.
3. Scroll the table to the right, where you can see Domain Consent Group.
4. Edit the column Domain Consent Group for all the domains on which you want to enable cross-domain consent.
5. Make sure that the enable of each group is the same. For example in the below image the Group name is GroupA.
6. Once done, cross-domain consent is enabled for these domains.
California DROP Act (CPRA) 2026: Compliance Requirements and DSAR Automation
California just made consumer privacy deletion requests unavoidable at scale. Starting August 1, 2026, every registered data broker must connect to a state-operated platform, retrieve consumer deletion requests every 45 days, and process them—automatically, verifiably, and repeatedly. Miss a deadline and face $200 per-request daily penalties. Fail to propagate deletions to vendors and face enforcement scrutiny that has already produced settlements exceeding $1.5 million.
- Data Protection
- Privacy Governance
OneTrust vs. Captain Compliance vs. Secure Privacy: Which Privacy Platform Fits Your Compliance Need...
Privacy governance has outgrown the cookie banner. In 2026, organizations managing GDPR, CPRA, LGPD, and a growing roster of US state privacy laws need platforms that orchestrate consent, automate DSAR fulfillment, maintain living records of processing, and generate audit-ready evidence—not just display a compliance pop-up.
GDPR Compliance for Mobile Apps (2026): Consent, SDKs, and Practical Implementation
Your mobile app displays a consent banner when users first launch it. Your privacy policy lists the data you collect. Your app store listing includes Apple's Privacy Nutrition Label. And yet, when regulators test your app with network monitoring tools, they discover that analytics SDKs are firing before users interact with the consent interface, advertising identifiers are being transmitted without explicit opt-in, and third-party trackers are active despite users declining consent.
- Legal & News
- Data Protection