Privacy policy

For the Stylespec browser extension. Effective 27 August 2026. Last updated 27 August 2026.

The short version. Stylespec collects nothing, stores nothing on any server, and makes no network requests of its own. There are no analytics, no telemetry, no accounts and no remote code. Nothing you type is transmitted anywhere by this extension, with one exception you trigger explicitly and can see happen: the Multiplexer, described below.

Who is responsible

Stylespec is a free, open-source browser extension published by an individual developer. There is no company, no server infrastructure and no third-party processor involved, because the extension has no back end. The complete source is published at github.com/bilal62/stylespec and every claim on this page can be verified by reading it.

What the extension does not do

It does not collect or transmit personal information.
It does not read, collect, store or transmit the content of web pages, including the responses your AI assistant gives you.
It does not contain analytics, telemetry, crash reporting or ads.
It does not load or execute remote code. All code ships in the package.
It does not sell or share data with anyone, because it holds none.
It does not require an account, a sign-in or a payment.
It does not track your browsing history or activity across sites.

What is stored, and where

Everything the extension saves is stored by your own browser. None of it reaches the developer or any third party.

Data	Where it lives	Why
Your styles, including any you write yourself	`chrome.storage.sync`	So your library follows your signed-in browser profile between devices. Synced by the browser itself, under your browser account, not by this extension.
Preferences: theme, favourites, keyboard behaviour, per-site on and off, custom Multiplexer targets	`chrome.storage.sync`	So the extension behaves the way you set it up.
A pending Multiplexer job, holding the prompt you just sent	`chrome.storage.session`	So the destination tab can pick the prompt up as it loads. Held for seconds, cleared automatically, and never written to disk.
Which origins you have granted access to	The browser’s own permission store	So a site you turned on stays on for your next visit.

You can delete all of it at any time from the extension’s settings page using Reset all settings, or by uninstalling the extension, which removes its storage with it.

Your prompts

When you pick a style, the extension writes the style instruction into the chat box you are already typing in. It goes into your visible draft, where you can read, edit or delete it before you send anything. From that point the text is handled by the website you are on, exactly as if you had typed it yourself, and it is subject to that website’s own privacy policy rather than this one.

The extension reads the text of the chat box for two narrow purposes: to know whether the box is empty, and to attach the style instruction to what you have written. It does not read anything else on the page, and it never reads an assistant’s response.

The Multiplexer, the one time text leaves the page

If you tick a target in the Multiplexer before sending, the prompt you just wrote is delivered to that assistant, and to nothing and nobody else. It travels one of two ways:

in the destination’s own web address, for assistants that accept a prompt that way, in which case nothing is injected into the page; or
typed into that site’s chat box by the extension, for assistants that do not, which requires that you have already granted the extension access to that site.

This is the same path your prompt would take if you opened the tab and pasted it in by hand. The prompt is not routed through any server belonging to the developer, because there is no such server. Nothing about the request, the response or the destination is logged, and the extension arms for a single prompt and then switches itself off.

Permissions, and why each exists

Permission	What it is for
`storage`	Saving your styles and preferences in your own browser.
`activeTab`	Letting the toolbar popup see which site you are on, so it can name that site when you ask to turn the extension on there. Granted only when you click the toolbar icon.
`scripting`	Registering the extension on a site you have just approved, so it works there on your next visit.
Host access	Declared for a fixed list of well-known AI assistant sites. There are no mandatory broad host permissions: any other site is opt-in, one origin at a time, through a Chrome prompt you see and accept.

Opening a Multiplexer tab needs no permission at all. The extension never injects into, reads from or registers itself on an origin you have not explicitly approved.

Children

The extension is not directed at children and collects no information from anyone, including children.

Changes to this policy

If the extension’s behaviour ever changes in a way that affects this policy, this page will be updated and the date at the top will change. The page is versioned in git, so the full history of what it has said is public. Material changes will also be noted in the release notes.

Contact

Questions, corrections or privacy concerns: please open an issue at github.com/bilal62/stylespec/issues. Public issues are preferred, because an answer that is useful to you is usually useful to somebody else.