Is SeaMeet Snap Recorder & Meeting Notes safe?
SeaMeet syncs Google Calendar event details to meet.seasalt.ai using tokens accepted from page messages.
SeaMeet's Google Calendar content script accepts token-change messages without checking the sender's origin, then stores those tokens in the calendar page's localStorage. When a Calendar event is saved, it reads the event title, times, location, description, guests, meeting link, recurrence, and calendar name and sends them to meet.seasalt.ai under the stored SeaMeet account.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itSeasalt AI, Inc - no other listings under this identity, 3 shared hostnames
Seasalt AI, Inc - no other listings under this identity, 3 shared hostnames
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 3 hostnames
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed SeaMeet Snap Recorder & Meeting Notes 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.
- meet.seasalt.ai
SeaMeet Snap Recorder & Meeting Notes sends data to meet.seasalt.ai. No other extension we have analysed sends data here.