TechnicalCollectible prompt
Privacy-first cookie banner that blocks scripts
Add a privacy-first cookie consent banner to my {{tech_stack}} site. Third-party tools we use: {{integrations}}. Read the existing code first.
Step 1: list every cookie, stored item and third-party script the site loads, with its purpose and category: necessary, preferences, analytics or marketing. If we only use necessary cookies and cookieless analytics, tell me we may not need a banner.
Step 2, once I confirm, the banner:
- Nothing optional loads until someone agrees; block the scripts themselves
- Equally prominent Accept all and Reject all buttons on the first screen, plus Choose settings
- Categories off by default, and no cookie wall
- Closing the banner counts as no consent
- Store the choice with a date and policy version; ask again after 6 to 12 months or when the tools change
- A Cookie settings link in the footer to change or withdraw consent anytime, which stops the scripts too
- Honor the Global Privacy Control signal as an opt-out
- With Google tags, consent mode set to denied by default
Accessibility: keyboard usable, 4.5:1 contrast, fits a 320px screen, and never hides the focused element.
This isn't legal advice, so flag anything to confirm for my regions. When you're done, list the files changed, how to test each choice, and anything you assumed.
Technicalnvoka.com/library/nvoka-privacy-first-cookie-consent-bannerScan to open
Technical
Privacy-first cookie banner that blocks scripts
Add a consent banner that truly blocks tracking until people agree, with a real Reject all button.
Curated by Nvoka
Claude CodeCursorLovableCodex
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 2 filledYour prompt
Add a privacy-first cookie consent banner to my {{tech_stack}} site. Third-party tools we use: {{integrations}}. Read the existing code first.
Step 1: list every cookie, stored item and third-party script the site loads, with its purpose and category: necessary, preferences, analytics or marketing. If we only use necessary cookies and cookieless analytics, tell me we may not need a banner.
Step 2, once I confirm, the banner:
- Nothing optional loads until someone agrees; block the scripts themselves
- Equally prominent Accept all and Reject all buttons on the first screen, plus Choose settings
- Categories off by default, and no cookie wall
- Closing the banner counts as no consent
- Store the choice with a date and policy version; ask again after 6 to 12 months or when the tools change
- A Cookie settings link in the footer to change or withdraw consent anytime, which stops the scripts too
- Honor the Global Privacy Control signal as an opt-out
- With Google tags, consent mode set to denied by default
Accessibility: keyboard usable, 4.5:1 contrast, fits a 320px screen, and never hides the focused element.
This isn't legal advice, so flag anything to confirm for my regions. When you're done, list the files changed, how to test each choice, and anything you assumed.