Privacy policy — OmniScript Data Inspector

Last updated: 31 October 2026

The short version

• The panel reads the page you inspect while DevTools is open. It does not send analytics or telemetry.
• Inspected data and captured calls stay in memory until DevTools closes. You can choose to save files or copy data.
• Test calls are off by default. If you enable them, the panel can send a call you compose to the selected script’s own org, using the page’s session.

What it reads

The panel uses the browser’s DevTools APIs to read the selected OmniScript’s live data, definition and header, including its labels. It scans the document, open shadow roots and accessible frames to find scripts. You can change the data and definition property names in Settings.

The Calls tab reads request and response bodies for captured OmniStudio traffic, including Data Mappers, Integration Procedures and Remote Actions. It uses the page’s origin and component identifiers to build designer and record links.

Load file… in Compare data reads the JSON file you select into memory. It does not upload the file. The panel does not read your clipboard.

Test calls and page actions

Allow test calls is off at every DevTools start and is never remembered. When enabled, it lets you send a captured call with edited input, or re-run a designer preview, through the page’s own session to the selected script’s frame origin. No test call is sent while recording is paused. Re-run as it was asks for confirmation each time.

A test call runs server-side logic and may change records if that logic performs writes. Only run calls whose effects you understand. The response is temporarily held on the page until the panel reads it, for at most one minute, and then deleted.

The panel does not edit the OmniScript’s data directly. Go to this step and Previous step ask the running script to show an earlier step. Scanning sets window.__omniHosts and window.__omniPeekCache; Inspect element sets window.$omni. Highlighting draws a temporary outline on the page.

What is stored in your browser

The extension uses storage.local on this computer. These entries are not synced:

• The tab order, once changed, and flags recording which short tours you have seen.
• Mask values at start, if enabled. This flag is separate from the current Mask values switch.
• With Remember my settings enabled (off by default), panel preferences, views, property names and the watch list for the last 50 scripts. Stored watch entries include paths, expressions you typed, alert choices and script Type/SubType/Language. Expressions may contain values you typed into comparisons. Values read from the script’s data are not stored.

Turning off Remember my settings removes the saved preferences and watch list. Inspected data, captured calls, filter text and the history of reads are not saved in extension storage. They stay in memory until DevTools closes. Captured calls can remain across page reloads unless Clear on reload is enabled.

Files, clipboard and external links

Save file, Export and Debug bundle save files only when you request them. A debug bundle includes panel settings, the last 12 data reads, the definition and tab state. Copy actions put the selected content on your clipboard. These files and copies may contain org data.

Mask values replaces values with placeholders in exports and copies. A masked debug bundle still contains script names and settings. Review files before sharing them.

Designer links, record links and help links open when you click them. Support links open Ko-fi or buycoffee.to; those websites have their own privacy policies. The extension does not attach inspected org data to these links.

Permissions and analytics

The extension declares the storage permission and no host permissions. It uses DevTools access to inspect the page. It does not include analytics, telemetry, advertising or crash reporting, and does not send inspected data to the author.

Data you retrieve from your org is your responsibility

The panel shows data from the inspected page and captured calls. Optional test calls use the page’s existing Salesforce session. What that data contains, and what happens to it once you look at it, is outside the extension's control and squarely within yours.

Be aware that an OmniScript's data JSON or a captured call can carry personal data, customer records, and internal identifiers. Request payloads may also carry session tokens.

So, concretely:

• Where you point it matters. Prefer a scratch org, a sandbox, or test records when you are exploring or capturing screenshots. Anything you capture from a production org is production data.
• Exports and copies are ordinary data. Pressing "Save file" or "Export" writes org data to your disk, and copying puts it on your clipboard, where other applications and clipboard managers can read it. Neither has any protection unless you turned on Mask values first. Where it then goes — a ticket, a chat message, a shared drive, a colleague's laptop — is entirely your decision.
• Screenshots and screen shares count too. The panel is designed to make data legible, which also makes it legible to whoever is watching your screen.
• Your own obligations still apply. Your organisation's policies, any confidentiality agreements it is under, and data protection law such as the GDPR govern this data regardless of which tool you viewed it through. Using this extension does not change what you are permitted to do with what you see.

The author provides this tool as-is and accepts no responsibility for how data retrieved through it is handled, stored, or disclosed. This is a plain description of how the tool works, not legal advice — if you handle regulated or confidential data, follow your organisation's guidance.

Changes

If any of this ever changes, the policy will be updated and the change disclosed on the store listing before the update ships.

Contact

Mikołaj Skrzypczyński — mskrz@proton.me

This is an independent, unofficial developer tool. It is not affiliated with, endorsed by, or sponsored by Salesforce, Inc.