Skip to content
Briefly

Privacy policy

What Briefly stores, and what leaves your browser

Written to be read rather than to be defensible. Every statement here describes something the extension actually does, and most of them can be checked from Chrome’s own dialogs without taking our word for anything.

Last updated: 29 September 2026 · Applies to the Briefly Chrome extension and this website

1. The short version

  • Briefly does nothing until you click its icon. It has no content script and no background activity, so it is not running on the pages you read.
  • By default, page text passes through our server with no identifier of you, so our model provider can summarise it. It is held in memory for one request and never stored. The request that checks your daily allowance and the request that carries your reading are separate calls, by design.
  • If you add an API key of your own, we receive nothing at all. Your page text goes from your browser directly to the provider you chose.
  • There is no analytics, no tracking and no advertising. We do not sell or share personal information, and there is no pipeline that could.
  • Everything you save stays on your device until you delete it.

2. What Briefly stores, and where

All of it is in chrome.storage.local, on your own machine. None of it is uploaded, backed up by us, or readable by us.

What Why it exists
Your consent record So the consent screen is shown once rather than every time.
Your provider, model and API key So Briefly knows where to send a request. The key is used as authentication to that provider and is sent nowhere else, ever.
Saved summaries The ones you chose to save: the page title, its URL, the claims and their source sentences. Unlimited, and never dropped to make room.
The summary you are looking at The claims, their source sentences, any translation, and the page title and URL, held in Chrome’s memory (chrome.storage.session) so the full tab can edit it. Never written to disk; gone when you close Chrome or revoke consent. The page text itself is not kept.
Your recent translation languages So the ones you use are one tap away. Language codes only.
An install identifier A random value generated on this device. It is sent only on the daily allowance check, and it never travels alongside page text.
Your daily allowance How many summaries on our key are left today, so Briefly can show you before you run out.

3. What is sent, and to whom

One request, made only when you click the Briefly icon on a page with a readable article in it. Where it goes depends on whether you have added an API key of your own, and the consent screen names the recipient before anything is sent.

If you have not added a key — the default

The request goes to Briefly’s server, which holds our API key and passes the text to Groq, our model provider. It contains the title and article text of the page you are on, and nothing else — no URL, no account, and no identifier of you or your install.

  • Our server does not store the text. It exists in memory for the length of one request and is written to no database, no log and no file.
  • Groq does not train on it. Their Services Agreement excludes using customer inputs and outputs for training or fine-tuning, on every plan.
  • This route has a daily limit. When you reach it, Briefly tells you and offers the option below; it does not silently keep sending.

Two separate requests, on purpose. The allowance check sends your install identifier and no page text, and returns an opaque token that records only that this install may use our key. The token is valid for one hour. The summarise request then sends the page title and article text with that token, and no install identifier of any kind — no account, cookie or device value. The part of our server that handles page text cannot tell whose reading it is.

To keep the daily limit fair, the server counts requests against a salted hash of your IP address and browser user-agent. It cannot be reversed without a secret held only on the server, it is deleted after 48 hours, and it is never joined to a page or to your install identifier.

Translation does not use our server at all. Chrome translates the claims on your device with its built-in translator, so neither we nor anyone else receives them. The only thing it adds to storage is your recent languages.

If you have added a key of your own

The request goes from your browser straight to the provider you chose, carrying the page text, the model id you selected, and your API key as authentication to them.

It does not pass through any server of ours. Briefly’s server is not in the path and receives nothing about it — not the page, not the URL, not the fact that it happened. There is no limit on this route.

What that provider then does with the text is governed by your agreement with them, not by this policy. We are not a party to it and cannot make promises on their behalf. Notably, Google states that prompts submitted on the free Gemini tier are used to improve its models; enabling billing on the project behind the key changes that. Briefly shows this warning beside the choice itself, and the setup guide explains it.

Two outcomes send nothing at all, on either route: a page with no readable article, and a page short enough that reading it is quicker than summarising it. Both say so on screen.

4. What Briefly never collects

  • Analytics, telemetry or usage events of any kind.
  • Your browsing history, or a record of which pages you summarised.
  • Your name, email address or account — there is no account.
  • Cookies, advertising identifiers or cross-site tracking.
  • Anything at all from pages you did not explicitly click the icon on.

We do not sell, rent or share personal information, and we do not use it for advertising or for training any model of our own. There is no data pipeline in the product that could do either.

5. Permissions, and what each is for

Permission What it is used for
activeTab Read the article in the tab you are on, granted by your click and only for that tab at that moment.
scripting Inject the extraction script into that tab at the moment of the click. It is the only way to read the article without a permanent script on every page.
storage Keep your settings, your key and your saved summaries, all locally.
Host access Reach Briefly’s server, asked for when you accept the consent screen, and the one provider you configure, asked for at the moment you add its key. Each is requested individually and revocable at any time.

Briefly requests no host access at install. A fresh install can reach nothing, which is why Chrome shows no site-access warning when you add it.

6. Other companies involved

  • Groq, Inc. is the model provider behind Briefly’s own key. If you have not added a key of your own, they receive your page text from our server to produce the summary, with no identifier of you attached. Their Services Agreement excludes using customer inputs and outputs for training or fine-tuning.
  • The model provider you choose, if you add your own key, receives your page text directly from your browser under the API agreement you hold with them. Their privacy terms govern what happens next, and our server is not involved. Thirteen are offered and you pick one.

There are no other third parties. There is no analytics vendor and no ad network.

7. How long anything is kept

  • On your device: until you delete it. Saved summaries, your key and your settings stay until you clear them or remove the extension.
  • Page text on our server: for the duration of the request that produced your summary. It is not written to storage or to logs.
  • The allowance token: one hour, then it expires and is discarded.
  • The salted hash that counts your allowance: 48 hours, then deleted.

8. Your choices

Because almost everything is local, most of these take effect immediately and need no request to us.

  • Stop Briefly reaching the network: remove your key in Settings, which also withdraws that provider’s host permission. Chrome’s own extension settings revoke Briefly’s access to any site, including our server, at any time.
  • Delete your data: clear your saved summaries in Briefly, or remove the extension, which deletes everything it stored.
  • Revoke a provider’s copy of your key: delete the key in that provider’s dashboard. It stops working instantly, everywhere.
  • Ask us anything about your data: email us. Since we hold no identifier for a free install, there is usually nothing of yours for us to find — which is the intended outcome rather than an evasion.

9. This website

These pages set no cookies, load no third-party fonts, scripts or images, and run no analytics. The only thing stored in your browser is your light or dark theme choice, which never leaves it.

Our web host records ordinary server access logs, as every web server does. We do not use them to build any profile of visitors.

10. Children

Briefly is not directed at children under 13 and we do not knowingly collect information from them. Since the extension collects no personal information from anyone, there is nothing of a child’s for us to hold.

11. Changes, and how to reach us

If this policy changes, the date at the top of this page changes with it and the new version is published here. A change that materially reduces your privacy would be announced in the extension itself, not only on this page.

Briefly is made by WaaFaa. Questions about this policy go to our support inbox.