Privacy Policy – Config Snapshot for Salesforce Data 360
The short version: the extension reads your Data 360 configuration from your own Salesforce org and saves it as a file on your computer. Nothing is sent to me or to anyone else.
This policy covers the Chrome extension only. The website's own policy is here.
What the extension accesses
- The URL of the active tab, only on Salesforce domains (
*.lightning.force.com,*.my.salesforce.com,*.my.salesforce-setup.com), to know which org you are looking at. - Your Salesforce session cookie (
sid) for that org's My Domain, to call the Salesforce REST API as you. The cookie is read when you open the panel and before each export. It stays in the panel's memory and is never stored, logged or sent anywhere other than your own Salesforce org. - Configuration metadata from Salesforce APIs, through read-only GET requests: data model objects and fields, data streams, mappings, segments, activations, calculated insights, identity resolution rules and data graphs. The extension doesn't request customer records.
What the extension doesn't do
- It doesn't send data to me or to any third party. There is no analytics, telemetry or remote code.
- It doesn't change anything in your org – it sends GET requests only.
- It doesn't read the content of web pages, forms or other websites.
Where your data goes
The export is built in your browser and downloaded as a .zip file to your computer. What happens to the file next is up to you. It can contain names and IDs from your org and literal values used in segment or activation filters. The Redact filter values option replaces those values before the file is created.
Local storage
The panel remembers your last choices (modules, data space, options) in the extension's local storage, on your computer. Session data is never stored.
Changes to this policy
If the extension's data handling changes, I'll update this page and the effective date above.
Contact
Szymon Lewandowski – contact@szymonlewandowski.pl. You can also open an issue on GitHub.