A plain-language account of what this extension reads, what it stores, and — the short version — what it never sends anywhere.
Nothing this extension reads leaves your browser, except to places you yourself point it at. There is no analytics, no tracking, no server run by the developer of this extension. Everything below explains exactly what that means in practice.
Purpose
What this extension does
This extension enhances the content-editing experience inside Optimizely SaaS CMS — the admin interface at *.cms.optimizely.com. It does three related things, all scoped to that one interface:
Shows which content item is currently open in the editor.
Lets you dock your own configured tools into the CMS sidebar and full-page extension view.
Lets you add custom formatting buttons to the CMS’s rich text editor.
It does not run on, or request access to, any other website.
Data it reads
Only what’s on the CMS page itself
While you have a page open at *.cms.optimizely.com/ui/cms or /ui/extensions, the extension reads:
Content identifiers
The GUID, display name, link, and content type of whatever item is currently open in the editor — read from the CMS’s own page data, the same information already visible on your screen.
CMS extension registry
The CMS’s own list of installed extensions, so this extension can add your configured tools alongside the real ones.
Rich text editor state
Which formatting toolbar is present on a given field, so custom style buttons can be added to it.
This is content metadata — identifiers and titles, not the private data of any person. The extension does not read passwords, payment details, or any site outside the CMS domain above.
Storage
Where any of this actually lives
Your settings
The environments, tools, and style buttons you configure are saved with Chrome’s built-in chrome.storage.sync, which syncs across your own signed-in Chrome browsers the same way your bookmarks do. This is Google’s sync infrastructure, governed by your own Google account — the developer of this extension has no access to it.
Currently open content
Which item you have open right now is cached per-tab in chrome.storage.session — cleared automatically when you close the tab. Never synced, never written to disk.
Refresh timing
A timestamp per configured environment, in chrome.storage.local, so your configured tools’ names and icons don’t get re-checked more than once every 15 minutes. No content in it — just a clock.
Network requests
The only places this extension sends anything
By default, this extension makes zero network requests of its own. Two things happen only if you configure them yourself:
Tools you dock into the sidebar. If you add a tool, the extension loads that URL in a sandboxed frame and passes it a token and the current content ID — both defined by you when you set the tool up. This is the same as opening that URL yourself; the developer of this extension is not a party to it.
Optional remote configuration. If you set a Remote Config URL (an advanced, opt-in feature for sharing one configuration across a team), the extension fetches JSON from that URL. It is never set by default, and only ever points wherever you typed.
Neither of these is the extension’s own server — the developer of this extension operates no backend that any of your data passes through.
What’s explicitly out of scope
Sold or shared with third parties
Never
Used for advertising
Never
Analytics or telemetry of any kind
None collected
Browsing history outside the CMS domain
Never read
Passwords, payment, or health information
Never accessed
Used to determine creditworthiness or for lending
Never
Your control
Turning any of this off
Everything this extension does is visible and reversible from its own Options page:
Remove a configured environment, tool, or style button at any time — deletions save immediately.
Clear a Remote Config URL to stop that one optional fetch entirely.
Uninstalling the extension removes all of the above from Chrome sync on your next sign-in, the same as removing any other synced browser setting.
Changes to this policy
If what this extension reads, stores, or sends ever changes, this page will be updated and the version number in the header above will move. There is no silent versioning — if the practices described here change, this text changes with them.
Contact
Questions about this policy or the extension’s behavior can be raised through the Chrome Web Store listing’s support channel.