Is Common Room safe?
Common Room reads its cr-token cookie and sends it as a bearer token to the Common Room GraphQL API.
When Common Room syncs authentication, it reads the cr-token cookie for Common Room domains and uses it to query the Common Room GraphQL API. It stores the token, serviceDoc details, and selected community ID in Chrome sync storage for extension use.
Who publishes itCommon Room - no other listings under this identity, 3 shared hostnames
Common Room - 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 Common Room 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.
- api.commonroom.io
Common Room sends data to api.commonroom.io. No other extension we have analysed sends data here.