In short
BrandPulse processes the content it inspects on your device, and that content is never sent to us. Some features do involve our servers — activating a licence, syncing your settings if you switch that on, or applying a policy your organisation set — and this policy sets out exactly which, and exactly what each one carries.
Accounts: No account to capture, generate, design or export. Sign in only for a paid plan.
01Scope
This policy applies to the BrandPulse browser extension published by ExtHive, on every browser where it is distributed.
It does not cover the websites you use BrandPulse on. Those sites have their own privacy policies, and using our extension does not change how they treat your data.
The general ExtHive Privacy Policy covers everything not specific to this extension, including your rights and how to exercise them.
02Permissions and why each one exists
Browsers ask you to approve permissions at install time. Here is every permission BrandPulse requests and the feature that requires it. We do not request permissions for features we have not built.
| Permission | Why it is needed |
|---|---|
storage | Keeps your brand kits, designs, captured text and settings on your own device. |
activeTab | Reads the page you explicitly invoke BrandPulse on. Granted by Chrome for that one tab, in response to that one gesture, and revoked when the tab navigates. |
scripting | Runs the content extractor on that tab, once, on that gesture. It is registered for no website and never runs on its own. |
contextMenus | Provides the right-click entry — which is also the gesture that grants access to the page, since a button inside the side panel cannot. |
sidePanel | The main interface. |
alarms | Schedules the licence check-in and cloud sync on paid plans. A free install schedules nothing and contacts nothing. |
ext-hive.com/api | Three of our own endpoints — licence validation, sync and hosted generation. It grants no access to any website you visit, and a free install never calls any of them. |
api.anthropic.com (optional) | Requested only if you choose to use your own API key, at the moment you add it. Never requested at install. |
03What happens to each kind of data
The table below lists every category of data BrandPulse touches, how it is handled, and whether it ever leaves your device. Only if enabled means it stays local unless you turn on a feature that needs otherwise, or are on a plan that includes one. Only if you subscribe means it does not apply to you at all on the free plan — it exists solely because a payment has to be billed and a licence delivered.
| Data | Handling | Leaves device? |
|---|---|---|
| Brand kits and designs | Stored on your device. On a paid plan they are also copied to our servers so your own machines match — that is the sync feature and it can be left alone. They are your colours, fonts, voice settings and layouts; we never read them for any other purpose. | Only if enabled |
| Pages you capture | Extracted on your device from a page you explicitly invoked BrandPulse on, and kept on your device (the 50 most recent). The text is sent to a model only when you press Generate — to Anthropic with your own key on the free tier, or through our server on a paid plan. It is never synced, never stored on our servers, and never used to train anything. | Only if enabled |
| Logos, images and fonts you upload | Stored in your browser's local database and used only to render your designs on your own machine. They are never uploaded, including on paid plans — a design that arrives on a second device shows a placeholder until you add the file there too. | No |
| Your own API key, if you use one | Stored on your device like any other setting, never synced, never included in a backup file you export, and never passed to a web page. It is sent only to Anthropic, as the credential for your own requests. We never see it. | No |
| Your licence key and a per-browser identifier, if you subscribe | Free users can stop reading here: with no licence there is nothing to check and nothing is sent. On a paid plan the extension registers your key against the browser you activated it on and re-checks it with ext-hive.com a few times a day, so the subscription can be honoured on your own devices, stop when it ends, and stay within the number of devices your plan covers. What travels is the licence key and a random identifier generated on that browser — not a hardware or advertising ID, not derived from your machine, and reset if you reinstall. We store when each device first activated and when it was last seen, so you can recognise and remove your own devices. | Only if you subscribe |
| Hosted generation usage, if you subscribe | On a paid plan we count the AI tokens each generation used, against a one-way fingerprint of your licence rather than your name or email, so your monthly allowance can be enforced and shown to you. We record the count, never the prompt or the output — the text passes through and is not written down. | Only if you subscribe |
| Your subscription, if you buy one | Payment is handled by Paddle as merchant of record, who take your email, billing address and card details under their own privacy policy — we never see or store a card number. What we keep is your email address, your Paddle customer and subscription identifiers, which plan you are on, and a record that a licence was issued to you (the date and a one-way fingerprint, never the key itself). | Only if you subscribe |
| Personal information, analytics and telemetry | The extension asks for none and collects none: no sign-up to use it, no user identifier on the free tier, no telemetry, no analytics, and no record anywhere of which pages you capture or what you generate. | No |
04Accounts and features that use our servers
Everything BrandPulse does works with no account at all: capture, all nine output formats, the complete Design Studio and unwatermarked export, using your own API key or Chrome's on-device AI. An ExtHive licence is needed only for the paid tiers, and only three things about it touch our servers — validating the licence, syncing your brand kits and designs between your own machines, and running hosted generation so you do not have to manage an API key. Your captured articles are never part of any of that.
These are the only parts of BrandPulse that involve ExtHive servers. Everything else runs on your device.
| Feature | What it sends | Optional? |
|---|---|---|
| Licence validation | On a paid plan the extension re-checks your subscription with ext-hive.com a few times a day, sending the licence key and a random per-install identifier so the plan can be honoured on your own devices and stay within the number your plan covers. | No — included in the plan |
| Cloud sync | On a paid plan your brand kits and designs are copied to our servers so your machines match. Captured articles and generated posts are never synced, and uploaded logos and fonts stay on the device they were added to. | Yes — off by default |
| Hosted generation | On a paid plan, writing a post sends the captured text and your brand voice settings to our server, which forwards them to Anthropic using our key and meters the tokens against your monthly allowance. Free users send the same thing directly to Anthropic with their own key instead. | Yes — off by default |
Deleting your account removes the data held for these features. Where a feature is optional, turning it off stops any further data being sent and deletes what was already stored, as set out under Retention below.
05What we never collect
To be explicit, BrandPulse does not collect, transmit or store any of the following:
- your browsing history or the list of sites you visit;
- the content of pages you view, beyond the moment-in-time processing described above;
- keystroke logs or clipboard contents;
- device fingerprints, advertising identifiers or location data;
- anything used to build an advertising or behavioural profile.
We do not sell data, we do not share it with data brokers, and we do not use your content to train machine learning models.
06Local storage on your device
BrandPulse uses your browser’s extension storage to keep your preferences. That storage is sandboxed to the extension: other websites and other extensions cannot read it.
You can clear it at any time from the extension’s settings, or by removing the extension. Uninstalling deletes all local extension data permanently.
If you have enabled a feature that stores data with us — settings sync, or a plan that applies an organisation policy — uninstalling does not by itself delete that copy. Turning the feature off or deleting your account does, on the timeline set out under Retention.
If you enable your browser’s built-in extension sync, your browser vendor — not ExtHive — may sync those preferences across your own devices under their privacy policy.
07Retention
What you capture and generate stays on your device: the 50 most recent captures and your posts, brand kits and designs persist until you delete them, and uninstalling the extension removes all of it with no copy kept anywhere. On a paid plan, brand kits and designs you sync are held on our servers while your subscription is active and deleted with your other subscription records; deleted items are kept as a marker with no content for 30 days so that a second device cannot resurrect them, then purged. Captured article text and generated posts are never stored on our servers at all — on hosted generation the text passes through and is not written down, and only a token count is recorded. Device activations are kept while the subscription is active; remove a device and the row is marked inactive rather than deleted, so a key removed from a machine cannot silently re-register there. Subscription records — your email, plan, status and licence issuance history — are kept while the subscription is active and for up to seven years after it ends, which is the period tax law requires us to be able to evidence a sale. That is the same period stated in the general ExtHive Privacy Policy; the two must always agree. Paddle keeps its own billing records under its own policy and schedule. Ask us at any time and we will delete everything that obligation does not require us to keep.
08Extension store disclosures
Extension stores require developers to declare their data handling. Our declarations for BrandPulse state that we do not sell or transfer user data to third parties beyond the approved use cases, do notuse or transfer it for purposes unrelated to the extension’s single purpose, and do not use or transfer it to determine creditworthiness or for lending.
BrandPulse’s use of information received from browser APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. What the extension reads is used only for the single disclosed purpose described above, and never for advertising, profiling or model training.
Those declarations match this policy. If you ever find a discrepancy between what a store listing says and what this page says, please tell us at support@ext-hive.com and we will correct it.
09Your rights and how to use them
Because BrandPulsekeeps your data on your own device by default, you can exercise most privacy rights directly: view your data in the extension’s settings, export it where an export exists, and delete it by clearing storage or uninstalling.
For anything held in your account — a licence record, synced settings, an organisation policy or a support email — write to support@ext-hive.com. Your full set of rights, and the timeframes we work to, are set out in the general Privacy Policy.
10Changes to this policy
If BrandPulse’s data handling changes, we will update this page and the date at the top before the change ships. A change that would send data off your device where it previously did not will always be announced in advance and, where the law requires, made subject to your consent.
Questions about this document?
Write to support@ext-hive.com and a person will answer, usually within 1 business day.