Is Elements.cloud safe?
Elements.cloud places its auth token into page-visible DOM attributes on supported Salesforce, Jira, and Azure DevOps pages.
When the sidebar is inserted on supported Salesforce, Jira, and Azure DevOps pages, the content script retrieves the stored Elements auth token and writes it into an auth-token attribute on a q9-reference-model-editor element. Scripts running on those pages can read that DOM attribute, exposing the credential outside the extension context.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
Who publishes itElements.cloud - no other listings under this identity
Elements.cloud - no other listings under this identity
What this publisher told the store about itself, and the other listings that told it the same thing.
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 Elements.cloud 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.
- dev.azure.com
Elements.cloud sends data to dev.azure.com. 3 other extensions we have analyzed send data here.
- salesforce.com
Elements.cloud sends data to salesforce.com. 3 other extensions we have analyzed send data here.
- atlassian.net
Elements.cloud sends data to atlassian.net. No other extension we have analyzed sends data here.
- lightning.force.com
Elements.cloud sends data to lightning.force.com. No other extension we have analyzed sends data here.
- visualstudio.com
Elements.cloud sends data to visualstudio.com. No other extension we have analyzed sends data here.