Is 2048 Classic Game safe?

Low risk

2048 Classic Game sends a persistent UUID to Google Analytics every 60 minutes and writes the extension's runtime ID into visited page DOM.

The extension generates a UUID on first install, stores it in chrome.storage.local, and posts it to Google Analytics (GA4 Measurement Protocol) on startup and every 60 minutes. When the quickAccess feature is enabled, a content script running on all pages injects HTML elements whose IDs include the extension's runtime ID, allowing any in-page script to detect the extension's presence.

Part of this rating comes from analysis signals we haven't published as detailed findings yet.

Matthew Watsonv1.1.0Chrome Web Store
17Risk

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 1.1.0. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    <all_urls>

  • Store data in your browser

    storage

  • Run its own code inside the pages you visit

    scripting

  • Schedule its own background tasks

    alarms

Where it sends data

Destinations our analysis observed 2048 Classic Game 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.

  • www.google-analytics.comwidely used

    2048 Classic Game sends data to www.google-analytics.com. A widely used service: 388 other extensions we have analyzed send data here.

Updated 30 September 2026kgfeiebnfmmfpomhochmlfmdmjmfedfj