Hi there,

Thank you for reporting the issue, and I’m glad to hear that you found the extension useful overall! I’ve just released a fix for the bug you mentioned.

The problem was caused by the way the extension handled cookies for domains with compound top-level domains (TLDs) like .co.uk, .co.jp, .gov.br, etc. Previously, when creating snapshots or exporting cookies, it was mistakenly including all cookies for domains sharing that TLD (e.g., exporting cookies for `telegraph.co.uk` would also capture cookies for `google.co.uk`).

This issue has now been resolved. The extension has been updated with an improved public suffix heuristic that correctly identifies the root domain, ensuring that only the cookies for the current site (e.g., `telegraph.co.uk`) are captured.

Could you please update to the latest version of the extension and try again? Let me know if the fix works for you, or if you encounter any further issues. Your feedback is highly appreciated!

-----------
Edit - 2026/01/30:

"Hey! Thanks so much for the feedback and for catching that specific edge case with 'westerntelegraph'. You were exactly right—the previous version was using a 'contains' check which was a bit too aggressive.

I've pushed a fix in version 2.0.3 that switches to Strict Domain Matching. It now checks the domain hierarchy specifically, so it will correctly include subdomains like .clerk.telegraph.co.uk but will properly exclude unrelated sites that just happen to share a suffix like .westerntelegraph.co.uk. Thanks again for helping refine this!"

Best regards,
Neeno