Block Cookies with 'Prior Consent'
Secure Privacy enables you to block cookies from being placed on a visitors computer until you have recieved explicit consent.
What is prior consent?
The GDPR and the European ePrivacy Directive require getting explicit consent before using cookies other than those necessary for the website to work properly. That means when a visitor comes to your website, you have to hold all your cookies until they agree to get them. You’ll show them the cookie banner and if they opt-in, you send the cookies. If they remain passive or if they don’t agree, you have to keep blocking the cookies from getting into their computers. Here are some GDPR cookie banner examples.
There are many websites with cookie banners, but without prior consent installed. They are not ePrivacy and GDPR compliant, and thus risk fines. These banners will send tracking cookies as soon as the visitor lands on the website. They ask for consent, but since there is no blocking mechanism in place, they insert cookies even when visitors are passive or decline the consent request. Law-wise, these banners serve no purpose.
Prior consent tools allow you to block all the cookies other than those that must be injected straight into your visitor’s computer until they agree on that. With Secure Privacy, you can easily set it up and manage it through the admin dashboard.
Do I need prior consent?
Yes, if you track your users’ personal data by using tracking technologies, then you need to ask for prior consent. Hence, you need a tool for blocking the cookies before getting the consent.
How can I install prior consent?
Once you set up an account with Secure Privacy, you’ll be able to set up prior consent on your website. We have created a detailed step-by-step system to help get the system installed correctly.
Does Your Software Count as High-Risk AI? A Practical EU AI Act Guide
Your engineering team just shipped a new AI feature. It screens job applicants, ranks them by predicted fit, and surfaces a shortlist for the hiring manager. You didn't think of it as "regulated" — it's just a scoring model. But under the EU AI Act, which enters full enforcement on August 2, 2026, that feature is almost certainly a high-risk AI system — subject to mandatory risk assessments, technical documentation, human oversight mechanisms, and EU database registration before it touches a single CV.
- AI Governance
WCAG Cookie Banner Requirements: Make Your Consent Accessible and Compliant
Your legal team just signed off on the cookie banner. Your developer shipped it. It blocks tracking scripts before consent, offers a Reject All button, and logs every choice. On paper, it is GDPR-compliant.
- Data Protection
- Privacy Governance
Privacy Engineering Best Practices: How to Build Privacy Into Systems by Design
Your product team is three days from shipping a feature that processes location history, inferred demographics, and browsing behaviour to power personalised recommendations. Legal reviews the privacy notice. Security scans for vulnerabilities. Nobody asks the fundamental question: should this system collect all of this in the first place, and if it does, what happens to the data when a user asks for it to be deleted?
- Data Protection
- Privacy Governance