From b2ef96b5f7453b2486f7fb309c5a81441cdcc592 Mon Sep 17 00:00:00 2001 From: RomanDenysov Date: Sat, 7 Feb 2026 14:36:11 +0100 Subject: [PATCH] docs: remove "Why Consentify?" comparison table from README Co-Authored-By: Claude Opus 4.6 --- README.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/README.md b/README.md index 963ded8..0ca9664 100644 --- a/README.md +++ b/README.md @@ -35,17 +35,6 @@ consent.client.set({ analytics: true }); consent.client.get('analytics'); // true ``` -## Why Consentify? - -| | Consentify | CookieBot | CookieYes | DIY | -|---|---|---|---|---| -| Bundle size | ~2 KB | 140 KB+ | 90 KB+ | varies | -| Script blocking | `guard()` | manual | manual | manual | -| SSR support | native | none | none | manual | -| Headless (own UI) | yes | no | no | yes | -| Zero dependencies | yes | no | no | varies | -| Price | Free / OSS | from $12/mo | from $9/mo | Free | - ## The Full Integration: Blocking Google Analytics Until Consent This is what consent management is actually for -- preventing tracking scripts from loading until the user explicitly opts in. `guard()` handles the entire lifecycle: wait for consent, load the script, and optionally clean up if consent is revoked.