Is Gather 1.0 Meetings (Classic) safe?

Low risk

Gather 1.0 Meetings (Classic) is low risk.

Gather 1.0 Meetings (Classic) sends the signed-in Gather user ID and email-derived profile details to its telemetry endpoint.

When its content script runs on Google Calendar, it asks the extension service worker for the current Gather user and sets that ID in Amplitude telemetry. It also derives profile properties from the user's email, including employee status and email-domain organization ID, and sends them to scope2.gather.town.

extension-developerv0.0.98Extension ID nmgegmkaijcgdgkfjhlbbaoabldoaehjChrome Web Store
20Risk
Who publishes it

Gather Presence, Inc. - 1 other listing from the same operator, none carrying a finding

Publisher
extension-developer
Declared legal entity
Gather Presence, Inc.
Registered address
2261 Market St #4095, San Francisco, CA 94114, US
Registered contact
Sam Smith

Same store account

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

AI-assisted analysis.

Gather 1.0 Meetings (Classic) findings

Gather Calendar script sends your Gather ID and email details to Amplitude

MediumunwantedCWE-359Static analysis

Code analysis shows that on Google Calendar pages the extension reads the signed-in Gather user and passes their ID, email and email domain to an Amplitude analytics endpoint on gather.town.

What actually happens

You did this

You open Google Calendar while signed in to Gather.

The extension did this

The extension looks up your Gather ID and email and sets them as analytics profile properties.

The code that does this

Identity lookup on Calendar startup

Readable version

setUserInfo

deobfuscated/content-script.js
const setUserInfo = (email) => {    amplitudeIdentify(constants_1.AmplitudeIdentifyOperations.SET, constants_1.MetricsUserProperties.EMAIL, email);    amplitudeIdentify(constants_1.AmplitudeIdentifyOperations.SET, constants_1.MetricsUserProperties.IS_EMPLOYEE, email.endsWith("@gather.town"));    const [_, emailDomain] = (0, stringHelpers_1.getEmailParts)(email);    if (emailDomain) {        amplitudeSetGroup(constants_1.MetricsGroupTypes.ORG_ID, emailDomain);    }};

Profile values set on the analytics client

  • User ID
    (Gather account uid)

    Ties analytics events to your Gather account.

  • Email
    (account email)

    Your email is stored as an analytics user property.

  • Employee flag
    true / false

    Whether the email ends with @gather.town.

  • Org group
    (email domain)

    The email domain is set as the organisation group.

Configured analytics destination

    • scope2.gather.town

    Amplitude HTTP API endpoint on a gather.town subdomain, set as serverUrl; no traffic captured.

Observation

Static analysis finding. This behaviour was identified by reading the shipped extension code and has not yet been reproduced in a live run. The trigger conditions and the exact data sent are read from the code, not from an observed capture.

What Gather 1.0 Meetings (Classic) can do

Permissions this extension asks for, as declared in version 0.0.96. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 0.0.98, which we have not unpacked yet.

  • Read and change your data on api.staging.gather.town

    https://api.staging.gather.town/

  • Read and change your data on api.gather.town

    https://api.gather.town/

  • Store data in your browser

    storage

Gather 1.0 Meetings (Classic) version history

  1. 0.0.95

    Mar 4, 2026

  2. 0.0.96

    Mar 4, 2026

  3. 0.0.98

    Nov 12, 2026

Where Gather 1.0 Meetings (Classic) sends data

  • scope2.gather.town

    Found in its code · only this extension

Chrome Web Store listing

Versions
0.0.98 latest of 3 seen since March 4, 2026
Store rating
4.8 from 19 ratings
Last updated
June 12, 2026
Size
1.27 MiB
Privacy policy
www.gather.town
Updated November 20, 2026