Security and data handling
How Org Loom processes records, saves your work, and controls access. Choose the version you use.
Connection and credentials
The canvas runs in a VS Code webview. Its requests go to the local extension host, which calls Salesforce APIs over HTTPS using the connected Salesforce user. It does not call Org Loom Apex endpoints or require package objects, a hosted Org Loom account, or an Org Loom token service.
Authentication through Salesforce CLI: Org Loom requests an OAuth access token for your selected connection from the locally installed Salesforce CLI. This token authorizes API requests as your user, subject to your Salesforce permissions. Org Loom keeps it in extension-host memory; it is not saved to disk by the extension or passed to the canvas interface.
Salesforce CLI manages authentication and token renewal. Any refresh token issued by Salesforce is managed by the CLI. Org Loom does not request, use, or store that refresh token directly; when a fresh access token is required, Org Loom requests one from the CLI.
To reconnect to the same account, Org Loom stores connection details such as your username and Salesforce org and user IDs in VS Code SecretStorage. These identify the connection; they do not grant access to Salesforce. The extension verifies the org and user on connection and reconnection, and requires explicit confirmation before connecting to production.
See the extension setup guide.
Where your data lives
| Data | Where it is kept | What to know |
|---|---|---|
| Open canvas and loaded records | VS Code webview and extension-host memory | Records and edits are processed locally. Business records remain in Salesforce. |
| Recovery checkpoints (opt-in) | Local extension storage | Created only when local recovery is enabled. Snapshots let you restore your canvas to its last checkpoint after a crash, restart, or accidental tab closure. Encrypted snapshots contain canvas data and original values used for upload comparisons, scoped to the Salesforce org and user. Each snapshot expires seven days after its last update. Expired snapshots and their encryption keys are deleted automatically while the extension is running, or when it next starts. |
| Recovery encryption keys (opt-in) | VS Code SecretStorage | Created when recovery is enabled and a checkpoint is saved. These keys decrypt your recovery snapshots and are encrypted at rest through VS Code’s SecretStorage service. They are deleted with the associated snapshots when recovery is disabled, discarded, or expires, or when you disconnect. |
| Selected connection identity | VS Code SecretStorage | Remembers which Salesforce account you connected to so the extension can reconnect to the same account when reopened, without requiring you to select it again. Stored details include your username and Salesforce org and user IDs; they identify the account but do not grant access to Salesforce. These details are encrypted at rest through VS Code’s SecretStorage service and removed when you disconnect. Salesforce CLI separately manages the credentials used to authorize the connection. |
| Upload tracking and receipts | VS Code SecretStorage | During upload, these entries are created to prevent duplicate uploads and update canvas records post upload. If a response is interrupted, this tracking helps distinguish confirmed results from unknown outcomes. Entries are scoped to your Salesforce org and user and store attempt identifiers, request hashes, object and record identifiers, operation types, and status or results. |
Permissions
Record operations use the connected user’s Salesforce permissions. Salesforce enforces object permissions, field-level security, record sharing, validation rules, and automation when requests run.
The managed package’s permission sets and per-user feature settings do not authorize or restrict extension features. Control extension access through your Salesforce user permissions, connected-app policies where applicable, and your organization’s VS Code and device policies.
Sharing an exported file is separate from Salesforce access: anyone who can read the file can read its exported values.
More detail and questions
Read the Trust page for an overview of security controls, the Privacy Policy for information handling, and the Terms of Service for use terms.
Security questions: security@orgloom.com
Privacy questions: privacy@orgloom.com