Privacy Policy

Overview

This Privacy Policy describes how WordPlume handles information when you use the WordPlume browser extension or visit this marketing website. It should be read together with our Terms of Use. WordPlume is a bring-your-own-key (BYOK) writing assistant: you connect AI providers you trust, and the extension helps you run quick actions and chat on text you select in the browser.

WordPlume is designed so that inference does not pass through a WordPlume-operated backend. We do not require a WordPlume account, and we do not operate a centralized service that collects your writing, prompts, or model responses for WordPlume analytics in the way many web applications do.

The same policy text is also shown inside the extension under Settings → About. If anything here and the in-extension copy ever differ, the version bundled with your installed extension reflects the build you are running; this page reflects the published web version.

Scope

This policy covers:

• The WordPlume browser extension (currently distributed for Google Chrome, with Microsoft Edge and Mozilla Firefox planned). This is where settings, API keys, chat history, and AI requests are handled.
• This website (wordplume.com and pages such as this one), which provides product information, install links, and support resources. The website does not receive your extension prompts or chat content.

It does not govern third-party AI providers, websites you visit while using WordPlume, or your browser vendor’s own privacy practices. Those services have their own policies.

Data stored on your device

WordPlume stores data locally in your browser’s extension storage (for example, chrome.storage.local). This data remains on your device unless your browser’s sync, backup, export, or enterprise device-management features copy it according to settings you or your organization control.

Locally stored information may include:

• Extension settings, such as theme, interface language, translate target language, streaming preference, and shortcut configuration.
• Provider configuration, including which AI provider and model are active, custom base URLs for local or self-hosted endpoints, and API keys or tokens you enter.
• Custom actions and overrides for built-in quick actions.
• Sidebar chat sessions, including message history, session titles, and the provider/model used per session.
• Onboarding state, such as whether you completed the first-run walkthrough.
• Per-site UI preferences, such as hostname rules for showing or hiding the floating trigger on specific websites.

WordPlume does not upload this local storage to a WordPlume account server. Uninstalling the extension or clearing extension data in your browser removes locally stored WordPlume data from that browser profile, subject to how your browser handles deletion.

Data sent to AI providers

When you run a quick action or send a chat message, the extension sends requests from your browser directly to the AI provider or local inference endpoint you selected. Examples include cloud APIs (OpenAI, Anthropic, Google, Mistral, OpenRouter, Groq, Cohere, Together, and others supported in the extension) or local runtimes such as Ollama, LM Studio, LocalAI, and Jan.

Depending on what you run, a request may include:

• Your prompt or follow-up message.
• System or action instructions configured for that command.
• Text you selected on the active page.
• Prior messages in the current chat session (for multi-turn chat).
• Additional page context, only if you explicitly enable that option (see below).
• Your API key or bearer token, sent to authenticate with the provider you configured.

Those transmissions are subject to that provider’s privacy policy, security practices, terms of use, logging, and data retention rules. WordPlume does not control third-party providers and cannot guarantee how they handle your data. If you use a local endpoint on your machine or network, requests typically stay within that environment, but you are responsible for securing that endpoint.

WordPlume does not route your prompts through a WordPlume inference server, sell your writing, or use your content to train WordPlume models (WordPlume does not operate such models).

Optional page context

WordPlume can optionally include page content as context when you have little or no text selected. This feature is off by default and only applies when you turn it on for a session.

When enabled, the extension reads visible text from the active tab’s page (for example from main, article, or the page body) up to a size limit, and may include the page title. That text is included in the request sent to your configured AI provider. It is not sent to WordPlume servers.

Be mindful on pages that contain sensitive, confidential, or personal information. You can disable page context at any time in the sidebar before sending a message.

Browser permissions

The extension declares browser permissions solely to provide its documented features. On Chrome, these include:

• storage to save settings, API keys, and chat history locally.
• activeTab and tabs to work with the page you are on, open the side panel, and support optional page-context features tied to the active tab.
• sidePanel to show the WordPlume sidebar UI.
• scripting to inject the content script that powers selection UI and in-page interactions where needed.
• <all_urls> host access so the extension can run on the sites where you write, communicate with provider endpoints you configure, and connect to local inference URLs such as localhost.

The content script runs on pages you visit so WordPlume can detect text selection and show its UI. It does not continuously send page content anywhere unless you explicitly run an action or chat that includes that content.

This website

The WordPlume marketing site is static informational content. We do not ask you to sign in here, and we do not collect extension prompts or chat history through this site.

The site may use:

• Local storage in your browser to remember your light/dark theme preference for this website only (key: wordplume.website.theme).
• Google Fonts to load the Inter and JetBrains Mono typefaces. When your browser requests those font files, Google may receive standard request metadata (such as IP address and referrer) under Google’s privacy policy.

This website does not use WordPlume-branded analytics, advertising trackers, or cookies for cross-site profiling at the time this policy was published. If that changes, we will update this section.

Install links may send you to the Chrome Web Store or other third-party distribution pages governed by those platforms’ policies.

Your choices

You control most privacy-relevant behavior:

• Choose which AI provider and model to use, including local-only options.
• Decide whether to enter cloud API keys at all.
• Select only the text you want to send before running an action.
• Enable or disable optional page context per session.
• Delete individual chat sessions or clear extension data from your browser.
• Disable the floating trigger globally or on specific hostnames in Settings.
• Review each provider’s data handling before connecting production or sensitive workflows.

Retention and deletion

WordPlume retains locally stored data for as long as it remains in your browser’s extension storage. Chat history persists until you delete sessions or remove extension data.

Data held by third-party AI providers follows their retention schedules, not WordPlume’s. Consult your provider’s documentation for deletion, opt-out, and enterprise controls.

Security

API keys and settings are stored using your browser’s extension storage APIs. Requests to cloud providers use HTTPS when the endpoint supports it. No system is perfectly secure: protect your device, browser profile, and API keys, especially on shared machines.

If you believe an API key used with WordPlume was exposed, rotate or revoke it with the provider promptly.

Children

WordPlume is not directed at children under 13 (or the minimum age required in your jurisdiction). Do not use the extension if you are not old enough to use the AI services you connect under applicable rules.

International users

Because AI requests go directly from your browser to the provider or endpoint you configure, data may be processed in countries where that provider operates. If you have cross-border data requirements, choose providers and deployment models (including self-hosted endpoints) that meet your obligations.

Changes to this policy

We may update this Privacy Policy when WordPlume changes materially (for example, new data flows, permissions, or website practices). We will revise the effective date at the top of this page when we do. Continued use of WordPlume after an update means you accept the revised policy to the extent permitted by law.

Contact

For privacy questions about WordPlume, use the Support page — the Chrome Web Store support form is preferred; email is listed there as a last resort. You can also review the disclaimer and product notices in the extension under Settings → About.