Is Twemoji for Chrome safe?

Clean risk

Twemoji for Chrome replaces page emoji with CDN images, sending image requests to jsDelivr or Cloudflare.

Twemoji for Chrome runs on HTTP and HTTPS pages and scans page content for emoji. When it finds emoji, it swaps them for remote SVG images from a Twemoji CDN, causing the browser to request those images from the CDN and potentially include the page referrer and the user's IP address.

360.by.roderickv0.0.8Chrome Web Store
0Risk
Who publishes it

360.by.roderick - 1 other listing from the same operator, none carrying a finding

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
360.by.roderick

Same store account

1 other listing published from this account, 7k+ users between them, none of them carrying a finding.

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 0.0.8. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Act on the current tab, but only after you click the extension

    activeTab

  • Run its own code inside the pages you visit

    scripting

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed Twemoji for Chrome contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • cdnjs.cloudflare.comwidely used

    Twemoji for Chrome sends data to cdnjs.cloudflare.com. A widely used service: 50 other extensions we have analysed send data here.

  • cdn.jsdelivr.netwidely used

    Twemoji for Chrome sends data to cdn.jsdelivr.net. A widely used service: 32 other extensions we have analysed send data here.

Updated 30 September 2026fopgafjdjlongoeblobbafbnapafcicg