Is Neat Tab safe?

Medium risk

Neat Tab sends new-tab search terms to its search servers with persistent install identifiers.

When you type in the new-tab search box, Neat Tab requests suggestions from neatfor.me using the text you entered. When you submit a search, it opens search.neatfor.me with the search term plus stored identifiers such as e_uid, install week, install year, channel, and click ID.

neatfor.mev1.0.4Chrome Web Store
45Risk
Who publishes it

neatfor.me - no other listings under this identity

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

Publisher
neatfor.me
Website
neatfor.me/contact.html

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

Publishers can request a review.

Findings

New-tab search terms sent with persistent install identifiers.

Searches from Neat Tab's new-tab box go to Neat Tab search endpoints with stored per-install values: userId, utm_uid, installation week, and year, which can link searches to the same browser install.

Severity
Medium unwanted
Type
Unexpected
CWE
CWE-359
Source
Dynamic sandbox
What actually happens
You did this

The user searches from the Neat Tab new-tab page.

The extension did this

The extension sends the search term to Neat Tab endpoints with stored per-install identifiers.

Captured request
GEThttps://search.neatfor.me/e363375d-1c7f-4ce0-bfa1-68692ede5729
Fields in the request
  • Search box text
    weather tomorrow (illustrative)

    The words entered into the new-tab search box reveal what the user is looking for.

  • Stored install identifiers
    d7f3a1b2-9c4e-4f31-8a22-6a5c1e0f8b91 (illustrative)

    Persistent values from extension storage can connect multiple searches to the same browser installation.

Observation

Observed during dynamic analysis: the new-tab UI is the trigger path for this behavior, and the confirmed flow is tied to user search actions rather than background browsing.

What it can do

Permissions this extension asks for, as declared in version 1.0.4. 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 neatfor.me

    *://neatfor.me/*

  • Store data in your browser

    storage

Where it sends data

Destinations our analysis observed Neat Tab 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.

  • neatfor.me

    Neat Tab sends data to neatfor.me. No other extension we have analysed sends data here.

  • search.neatfor.me

    Neat Tab sends data to search.neatfor.me. No other extension we have analysed sends data here.

Updated 30 September 2026gnbpmmjbonbalohgccanofpfbobdbmpj