At a glance
What this policy covers
Works with Salesforce
Requests are made to the active Salesforce origin selected by the workflow.
Local-first settings
Preferences, saved mappings, query history, saved packages, and Local Files are stored in the browser.
No sale of data
Lightning Connect does not sell Salesforce information or use it for advertising.
Information handled
Information used to provide the extension
Lightning Connect handles information only as needed to provide its Salesforce workspace features:
- Salesforce session information. The extension reads the Salesforce
sidcookie from supported Salesforce domains to make authorized Salesforce API requests using the session already active in Chrome. - Salesforce content you choose to work with. This can include object metadata, field definitions, records, query results, metadata components, source files, API responses, and operation results returned by your Salesforce org.
- Files and text you choose to supply. CSV, XLS, XLSX, pasted tabular data, code, and clipboard content are handled when you deliberately use import, copy, paste, Local Files, or related workflow features.
- Extension preferences and saved workspace items. This can include UI settings, query history, saved mappings, saved metadata-package configurations, and Local Files.
Purpose limitation
How information is used
Information is used solely to perform the feature you initiate: displaying Salesforce context, retrieving or editing permitted records, executing a query, preparing or executing an import, retrieving metadata, working with source files, exporting results, or saving local workspace preferences.
Lightning Connect does not use Salesforce information for behavioral advertising, does not sell it, and does not require a separate remote proxy as part of its default architecture. Salesforce data is requested only from the Salesforce origin selected by the workflow.
Browser-local data
Local storage & retention
Saved preferences and workspace items are stored with chrome.storage.local on the browser profile where the extension is installed. Local Files are scratch files in the extension cache and are not automatically synchronized with Salesforce.
Salesforce session availability is determined from the browser’s Salesforce cookie. If the session is unavailable or expired, the extension reports the issue and asks you to sign in to Salesforce again.
You can remove browser-local extension data by clearing the extension’s stored data or removing the extension. Deleting a saved configuration or Local File from its workspace removes that local item from the extension’s storage.
Chrome permissions
Why the extension asks for permissions
Your choices
You decide what is processed
Use only the workflows and actions you intend to use. Review staged data, selected metadata, generated packages, and deployment or CRUD operations before proceeding. Salesforce permissions, field-level security, API limits, and session state may limit what the extension can access or do.
For sensitive or production data, follow your organization’s Salesforce policies and use appropriate care when exporting, copying, importing, or deploying changes.
Updates & questions
Changes to this policy
This policy may be updated when Lightning Connect changes its data practices or features. The current version will be published on this page with a revised update date.
For product questions, bug reports, or privacy feedback, open an issue in the Lightning Connect GitHub repository ↗.