Nitro Privacy Policy

Summary

Nitro runs entirely inside your browser. It has no servers of its own, includes no analytics or tracking, and transmits nothing to the developer or to any third party. The only thing it stores is your own preferences.

Last updated: July 14, 2026

This policy describes what the Nitro for Blueshift Chrome extension (“Nitro”) accesses, what it stores, and what it does with that information. Nitro is built and maintained by Chris Fletcher (“the developer”).

What Nitro accesses

To do its job, Nitro reads content on two websites, and only those two:

• app.getblueshift.com (Blueshift’s Email Studio and Journey Builder), where Nitro reads the pages you are editing so it can show the size meter, track unsaved changes, and add its panels.
• app.getbee.io (the email editor embedded inside Blueshift), where Nitro reads the editor content to power Liquid highlighting and the design tools.

Some features (such as the Shared Asset Configurator) fetch your templates and shared assets from Blueshift’s own API, using the session you are already signed in with. That content is processed locally in your browser to render previews and apply your changes, and is then discarded. Nitro never saves it, and it never leaves the Blueshift and Bee services it already lives in.

What Nitro stores

One thing: your preferences. Which features are switched on, and their options, are saved through Chrome’s built-in extension storage (chrome.storage.sync). Google syncs this storage across the browsers you are signed in to, the same way it syncs your bookmarks. The developer has no access to it.

What Nitro never collects

• No email content, templates, or shared assets are collected or retained.
• No personal information, account details, or credentials are collected.
• No analytics, telemetry, or usage statistics are gathered.
• No data is sent to the developer or to any third-party service.
• No data is sold, shared, or used for advertising, ever.

Browser permissions

Nitro requests the minimum set of permissions Chrome offers for what it does:

• storage: to save your preferences, as described above.
• Host access to app.getblueshift.com and app.getbee.io: so the extension can run on Blueshift’s editor pages. Nitro does not run on, read, or touch any other website.

Chrome Web Store disclosure

Nitro’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. In short: the data Nitro handles is used only to provide the features you see, and for nothing else.

Changes to this policy

If a future version of Nitro changes what it accesses or stores, this policy will be updated before that version ships, and the date at the top will change. Significant changes will also be called out in the extension’s Chrome Web Store listing.

Contact

Questions about this policy are welcome. Reach out through the contact page.