Privacy Policy for Admin Toolkit for Salesforce

Last updated: October 5, 2026

Admin Toolkit for Salesforce is an independent Chrome extension for Salesforce metadata administration. It is not affiliated with, endorsed by, or sponsored by Salesforce.

Data the Extension Handles

The extension may handle:

• Salesforce session cookies for Salesforce domains, used only to connect to the Salesforce org where the user is already signed in.
• Salesforce user and organization identity fields returned by Salesforce, such as name, username, email address, user ID, organization ID, organization name, and instance name, used to identify the active session and org.
• Salesforce metadata, setup data, org limits, event log file metadata, login history, setup audit trail rows, and records returned by user-run queries or requests.
• Salesforce object schema data used by Object Schema, including global describe results, installed-package namespaces, object and field describes, active picklist values, formulas, and reference targets.
• User-entered Apex, SOQL, SOSL, REST paths, request bodies, metadata search terms, workspace selections, and local edits.
• Salesforce list view and report definitions shown in SheetD's file details, including the list view's generated SOQL and a report's format, report type, scope, filters, and created/last-modified user names, together with the rows those list views and reports return. When a report's results exceed the 2,000-row limit of Salesforce's report API, the extension requests the same report as a workbook export from that same Salesforce endpoint over the existing session.
• Salesforce configuration and security-posture data read by Org Review, including org limits, license counts, Health Check score and risk settings, security settings metadata such as password and session policy, permission set and permission set group assignments, object and field permissions, authentication providers, OAuth token metadata (app name, user, last-used date), certificate labels and expiration dates, installed package versions, Apex class source and test coverage, flow and trigger inventories, failed job records, and the names of connected apps and named credentials together with named-credential and remote-site endpoint URLs. Org Review does not request credential values, certificate private keys, or OAuth token values.
• Local extension preferences and state such as language, selected workspace folders, selected namespaces, search settings, UI settings, recent/favorite tools, and sanitized operation history or receipts.

How Data Is Used

The extension uses this data only to provide the user-facing extension features:

• Browse, find, search, inspect, and download Salesforce metadata.
• Build package.xml selections.
• Run Salesforce REST, SOQL, SOSL, data export, and anonymous Apex actions initiated by the user.
• View Salesforce setup audit trail, event log files, login history, org summary, and limits.
• Build an interactive object relationship map and display field details selected by the user.
• Open Salesforce list views, reports, and CSV/XLSX imports in a spreadsheet grid and — only for rows that carry a record Id resolving to one Salesforce object, and only after review and confirmation — update those Salesforce records.
• Store bounded, organization-specific SheetD update receipts locally so users can select recorded prior values and submit an explicitly reviewed rollback update.
• Record the user's own review decisions for Winter '27 release notes locally so they persist between visits.
• In Transaction Timeline, on the user's request, send one REST call or anonymous Apex the user entered under a temporary trace flag, then download the debug logs it produced and draw them in the page. To do this the extension creates a debug level and a 15-minute trace flag on the signed-in user (or, when the user already has one, borrows that trace flag and puts its settings back afterwards) and removes them when the run ends. By default the request is a dry run: a REST call is sent inside a Composite request that fails on purpose at its last step, and anonymous Apex ends with a failing assertion, so Salesforce rolls every change back. A run for real, which saves changes, is offered only in a sandbox, scratch org or Developer Edition, after confirmation; Apex REST endpoints and sObject Tree calls cannot be rolled back and run only that way. To suggest Apex REST endpoints, the extension reads the org's active Apex classes once per org (and again when the user asks) and keeps only the endpoint paths, HTTP methods and class names it finds; the class source is not stored. So the user can run a request again, the extension keeps the last 10 requests the user traced (the method, path and body, or the Apex, and the mode chosen) in its local storage; the page's Clear button forgets them. The logs and the drawing stay in the page's memory and are discarded when the tab closes; the operation history records only the time, Salesforce host, request kind, mode, outcome and number of logs.
• In Org Review's cleanup workflow, and only in a Salesforce sandbox org, delete one permission set assignment the user has previewed and confirmed by typing its record Id. The extension refuses this action in a production org, re-checks the assignment immediately before sending, and records the outcome locally. No other Org Review action writes to Salesforce.

Data Sharing and Transfers

Browser API requests containing Salesforce data, identity data, authentication information, and user-entered requests are sent only to the Salesforce org selected by the user. The extension does not transfer this data to developer-operated servers. One exception to the single-org rule: Org Review reads the public Salesforce Trust status for the org's instance from api.status.salesforce.com. That request carries no credentials and no org data — only the instance name — and its response is shown in the report.

The extension does not sell user data, does not use user data for advertising, does not use user data for credit-worthiness or lending purposes, and does not share user data with data brokers or advertising platforms.

The extension does not include usage analytics or telemetry.

Local Storage

Workspace preferences, search data, pending edits, recent/favorite tools, sanitized operation history, and bounded SheetD update receipts may be stored locally in Chrome browser storage on the user's device. SheetD workbooks are not persisted. SheetD receipts contain only the successful update time, Salesforce object, record IDs, changed field names, and prior and updated values; they are limited to the newest 50 events and 2 MB per Salesforce organization. Operation history is limited to the most recent 100 entries and excludes session tokens and authorization headers. Files find is scoped to the loaded workspace tree. Org Review keeps a bounded local record per Salesforce org and user: the last run's redacted summary, a baseline of finding signals for change detection (at most 1,000 groups), cleanup tasks the user creates (at most 200, each with bounded notes), and a log of sandbox cleanup actions (at most 200 entries holding record Ids, timestamps, and outcome only — no names or credentials). The rendered report itself is not persisted and is rebuilt on each run. Winter '27 Release Note Review keeps the user's own review decisions per release note — status, applicability, a comment of at most 10,000 characters, and the note revision reviewed — in browser storage keyed by Salesforce host; no Salesforce data is stored by that page. Transaction Timeline keeps the last 10 requests the user traced (method, path and body, or Apex, and the mode chosen) so they can be run again; its Clear button removes them, and the debug logs it downloads are never stored. It also keeps, per Salesforce host, the Apex REST endpoint paths, HTTP methods and class names found in the org's Apex classes, for up to a day. Users can clear feature-specific saved data from the extension UI where offered; removing the extension clears its Chrome-managed local storage.

Remote Code

The extension does not load or execute remotely hosted JavaScript or WebAssembly. Extension JavaScript, HTML, CSS, and third-party spreadsheet code are packaged with the Chrome extension. Responses from the selected Salesforce org are treated as data and are not executed as code.

Human Access

The developer does not have access to Salesforce data handled locally by the extension. The extension does not send this data to developer-operated infrastructure.

Chrome Web Store Limited Use Disclosure

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions or support, use the support contact provided on the Chrome Web Store listing.