Nitro Privacy Policy
This policy covers the Nitro for Blueshift Chrome extension. It is separate from the Studio 625 website and consulting services.
Summary
Nitro runs entirely inside your browser. It has no servers of its own, includes no analytics or tracking, and sends nothing you write or edit to the developer or to any third party. The only thing it stores is your own preferences. The one exception is the pages Chrome opens when you install or remove the extension, described under Installing and removing Nitro.
Last updated: July 30, 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. Bee is a white-label editor that other marketing platforms embed too. Nitro checks which site the editor is running inside, and stays completely inactive unless that site is Blueshift.
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.
One smaller thing is stored separately: where you drag Nitro’s panels on screen,
kept in chrome.storage.local. Window positions belong to one display and
should not follow you to a different machine, so that setting never syncs. The
developer has no access to it either.
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 by the extension.
- Nothing you write, edit, or view in Blueshift is sent to the developer or to any third-party service.
- No data is sold, shared, or used for advertising, ever.
Installing and removing Nitro
When you install Nitro, Chrome opens a welcome page on studio625.net. When you remove it, Chrome opens a short feedback page on the same site. Both are ordinary web pages, so loading them tells the web server what any visit tells it: your IP address, your browser’s user agent, and the time.
Like every page on studio625.net, those two include Vercel Analytics, which records an anonymous page view. It sets no cookies and builds no profile of you, but it does mean an install or an uninstall shows up in this site’s aggregate visit counts.
The extension itself sends nothing during either event. Neither visit can be connected to you, to your Blueshift account, or to anything you edited.
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 Nitro support page, or email chris@studio625.net.