CBL

About

================================================================================
CBL — Clean Browse Ledger
================================================================================

Strips utm_source, fbclid, gclid and more before pages load. Audits cookies, logs consent, and analyzes cookie policies. On-device.


──────────────────────────────────────────────────────────────
5 KEY FEATURES 
──────────────────────────────────────────────────────────────

• Pre-load URL cleaning — strips utm_source, fbclid, gclid, msclkid, and affiliate parameters before the page loads, with a full before/after record saved to history.

• Cookie inspection — snapshots all cookies for any domain with full detail: name, domain, path, expiration, remaining lifetime, secure, HttpOnly, SameSite, session vs. persistent, and partitioned flag.

• Consent detection — automatically logs when you click cookie banner buttons (Accept All, Reject All, Save Preferences, etc.) with a confidence level and the button text.

• Cookie policy analysis — when consent is detected, fetches the site's privacy policy and runs local keyword analysis to surface advertising cookies, data sharing, third-party vendors, opt-out language, and more.

• 100% on-device — no network requests, no telemetry, no analytics, no cloud processing. All data stays in chrome.storage.local.


──────────────────────────────────────────────────────────────
DESCRIPTION 
──────────────────────────────────────────────────────────────

CBL — Clean Browse Ledger keeps an honest record of the tracking that follows you as you browse, and quietly cleans URLs before they load. No telemetry, no data sent anywhere. Everything runs locally.


WHAT IT DOES

Pre-load URL Cleaning
Before a page loads, CBL strips tracking parameters and redirects to the clean URL. This covers utm_source, utm_medium, utm_campaign, fbclid, gclid, msclkid, and affiliate identifiers. Both the original and cleaned URL are saved to history.

Cookie Inspection
For any site you visit, CBL can snapshot all cookies for that domain, including subdomains. Each entry records the name, domain, path, expiration, remaining lifetime, secure, HttpOnly, SameSite policy, session vs. persistent status, and partitioned flag. Cookie values are not stored — only the length.

Consent Detection
When you click a cookie banner button — Accept All, Reject All, Save Preferences, or similar — CBL logs the action with the button text and a confidence level (certain, probable, or unknown).

Cookie Policy Capture and Analysis
When consent is detected, CBL finds the site's privacy policy, fetches the text, and runs a local keyword analysis. The report surfaces advertising cookies, analytics, personalization, data selling, named third-party vendors (40+ recognized), opt-out choices, retention periods, and consent withdrawal options. Results are labeled "what the policy says" — CBL makes no claim about what the site actually does.

Referral Source Attribution
CBL attributes tracking to its source: gclid to Google Ads, fbclid to Meta, msclkid to Microsoft Advertising, and UTM parameters by utm_source value. The HTTP referrer is also recorded.

History and Export
The History page shows a full timeline of events per domain: cleaned URLs, consent actions, cookie snapshots, and policy records. Filter by event type, search by domain, and export as JSON.

Custom Rules
Add your own parameter-stripping rules, enable or disable them individually, preview changes before saving, and import or export your rule set. A denylist exempts specific domains from cleaning.

Badge
A green badge on the extension icon shows how many URLs were cleaned and cookies found for the current tab.


PRIVACY

• All data is stored locally using chrome.storage.local — nothing leaves your device.
• Zero network requests to any third party.
• No analytics, telemetry, or crash reporting of any kind.
• Cookie policy analysis is local keyword matching — no AI, no cloud.
• Uncertain findings are labeled "unknown" rather than guessed at.


TECHNICAL

• Manifest V3
• Plain HTML, CSS, and JavaScript — no third-party frameworks
• URL cleaning via declarativeNetRequest and webNavigation
• Storage via chrome.storage.local only


CBL is not a privacy shield or ad blocker. It does not block trackers or ads. It cleans URLs, records consent actions, and surfaces what cookie policies say — so you know what you agreed to and what followed you.