Privacy Policy

1. Who this covers

This policy covers the Huminn browser extension, distributed through the Chrome Web Store, and the website at gethuminn.com. The two behave differently and are described separately: the extension collects nothing on its own, while the website uses ordinary web analytics. Section 7 covers the feedback form — the only thing you can deliberately send us — and section 8 covers the website.

2. What the extension stores, and where

Everything Huminn keeps is kept by your browser, on your machine, in one of three places.

• A local database (IndexedDB). Your feeds and the articles fetched from them — titles, summaries, links, images and publication dates. This never leaves your device and is never synchronized anywhere.
• Chrome’s synced storage. Your settings: theme, language, chosen search engine, typeface and text size, retention limits, and the shortcuts you pin to the New Tab. If you are signed into Chrome, Chrome replicates this between your own devices through your Google Account, in the same way it syncs bookmarks. It travels under Google’s terms, not ours, and we have no access to it.
• Session storage. A note of whether the summary panel is open, so the feature survives Chrome shutting the background worker down. Chrome discards it when the browser closes.

There is no user account, no device identifier and no profile. Huminn never transmits your feed list, your reading history, your bookmarks or your settings to us or to anyone else.

3. Connections the extension makes

Huminn is not a proxy: it fetches from your browser directly, so no intermediary of ours ever sees your traffic. The complete list of destinations it contacts:

• The feeds you subscribe to. Requested straight from each publisher on a background timer. Those publishers see the request the same way they would if you opened their site — your IP address, your user agent, the time. What they do with it is governed by their own privacy policy, not this one.
• gethuminn.com/suggested-feeds.json and gethuminn.com/suggested-previews.json. The catalog of suggested sources shown in the Discover panel, plus their preview images. These are plain file requests carrying no identifier of any kind. The site is hosted on Cloudflare Pages, whose edge keeps standard short-lived server logs; we do not join those logs to anything or use them to build any profile.
• Articles you click. The link opens in a normal tab. Huminn appends utm_source=gethuminn.com&utm_medium=extension to the URL so the publisher’s own analytics can tell that the visit came from a reader using Huminn — this is how independent publishers see that a referrer is worth supporting. The tag identifies the extension, never you, and links that already carry their own attribution are left untouched.

That is the whole list of what Huminn requests. It loads no remote code, no third-party scripts and no external fonts or trackers — everything it runs ships inside the package Chrome installs, as Manifest V3 requires. One further address exists that Huminn never requests itself: the page Chrome opens for you when you uninstall, described in section 7.

4. Summaries and translation run on your device

Huminn uses Chrome’s built-in AI — the Summarizer, Translator and Language Detector APIs. These models run locally, inside your browser. The text they process is not sent to us and is not sent to Google.

When you click the toolbar icon — or when Live Summary is switched on and you open a new article — Huminn reads the visible article text from the active tab and hands it to the local model. The text is held in memory for as long as it takes to produce the summary, and the finished summary is cached in your local database so returning to it is instant. Neither the text nor the summary is transmitted.

The first time you use a given language pair or summary format, Chrome downloads the corresponding model from Google. That download is a request to Google’s servers made by Chrome itself, governed by Google’s Privacy Policy. It carries none of your content.

5. Permissions, and what each one is for

Chrome shows a permission list at install time. Here is what Huminn asks for and why — each entry corresponds to a feature you can see.

6. What Huminn does not do

• No accounts, no sign-in, no email address collected.
• No analytics, telemetry, crash reporting or usage tracking inside the extension.
• No advertising, and no ad or tracking networks of any kind.
• No selling, renting or sharing of personal data. There is none to sell.
• No profile of what you read. Ordering is by publication date; there is no recommendation engine and nothing is scored.
• No injecting content into the pages you visit, no rewriting search results, no affiliate links.

7. Feedback you choose to send

Huminn has two places where you can tell us something, and both are entirely up to you. Nothing leaves your machine unless you type it and press a button — this is a form somebody fills in, not telemetry, and the extension never makes either request itself. It opens a page; what that page sends is your decision.

• When you uninstall. Huminn asks Chrome to open gethuminn.com/goodbye in a tab as it removes the extension, so there is one chance to say what went wrong. That address carries three things in its query string: the version you were on, how many whole days it had been installed, and how many feeds you had as a range (0, 1-3, 4-10, 11+) — never the feeds themselves. Opening the page stores nothing; closing the tab without answering ends it there.
• The “Say something” rows in Settings. One is an ordinary link to the Huminn listing on the Chrome Web Store, so you can rate it — what happens after that is between you and the store, and we are not told who left which review. The other opens gethuminn.com/feedback: the same form, carrying the same three things.

If you do submit the form, the row it creates holds: when it arrived, which of the two forms it was, the reason you picked (a fixed code such as bugs, never the translated wording you saw), whatever you wrote, the three items above, and the two-letter country our host reports. That is the entire row. There is no identifier, no session and no cookie, and your IP address is not stored — it is used to rate-limit the request as it arrives and then discarded. Two answers from the same person are indistinguishable from two answers by different people. Before you send anything, the form shows you the exact values it is about to send.

This is the only endpoint gethuminn.com has, and it only ever receives what somebody deliberately typed into it. Submissions are stored in a Cloudflare D1 database. If you would rather write to a human instead, [email protected] reaches the same person.

8. The website (gethuminn.com)

The extension and the website are separate, and the website is where the one piece of measurement lives. gethuminn.com uses Google Analytics 4 to count visits and see which pages people read. That involves cookies and sends your IP address and browsing data for this site to Google, under Google’s Privacy Policy. Any browser-level tracking protection, extension blocker or “do not track” setting stops it, and blocking it changes nothing about how the site works.

The site is hosted on Cloudflare Pages, which keeps standard short-lived request logs for delivery and abuse prevention. None of this reaches the extension, and none of it is connected to anything you do inside it.

9. Your control over your data

• Remove any feed in Settings; its stored articles go with it.
• Export your subscriptions to an OPML file at any time, and import them elsewhere. Your feed list is yours to take.
• Withdraw an optional permission from chrome://extensions without uninstalling anything.
• Uninstalling removes everything. Chrome deletes the local database and the extension’s storage with it. Settings that were synced are removed from your Google Account’s extension storage in the same way any other uninstalled extension’s data is.

Huminn holds no account of yours, so there is nothing to close and no deletion request to file. The one exception is feedback you chose to send: if you want it removed, write to [email protected] and quote enough of what you wrote for us to find it — the row carries no identifier, so the text is the only way to locate it. If you are in a jurisdiction with data-subject rights — the EU, the UK, California and others — they are satisfied by default for everything else: nothing about you is transmitted to us unless you type it and press send.

10. Children

Huminn is a general-audience news reader. It is not directed at children under 13 and does not knowingly collect anything from them — or, for that matter, from anyone.

11. Changes to this policy

If Huminn ever changes how it handles data, this page changes first and the date at the top moves with it. A change that meaningfully affects your privacy will also be called out in the extension’s Chrome Web Store release notes rather than shipped quietly.

12. Contact

Questions about this policy, or about anything Huminn does with data, go to [email protected]. You can also raise an issue through the support tab of the Chrome Web Store listing.