Summarize long articles without sending data to a third party (BYOK)

Privacy · September 2026

Every AI summary has a hidden travel itinerary: your article's text leaves your browser and goes somewhere to be processed. The question is where. For most AI reader tools, the answer is "through our servers first." For BYOK tools, the answer is "directly to the AI provider you chose." That difference matters more than most privacy policies let on.

What actually happens in a normal AI reader

When you click "summarize" in a typical subscription assistant, three parties touch your content: the extension, the vendor's backend, and the AI model. The vendor's server is in the middle — it receives the full page text, forwards it, and often caches or logs the interaction under its own retention policy. Legitimate, but it means the company behind your reading tool sees a running record of what you read: every medical article, every legal document, every competitor's page. Browsing history is behavioural data — as the EFF documents on behavioral tracking, what you read is profiled and monetised far beyond the service you knowingly signed up for.

The BYOK alternative

BYOK — bring your own key — removes the middleman. The extension holds your API key for a provider like OpenAI or DeepSeek. When you summarize a page, the text goes from your browser straight to that provider's API. No vendor server in between, no vendor retention policy, no aggregate reading profile.

Two practical benefits fall out of the same design:

1. No usage quotas. The tool vendor isn't paying for your tokens, so they can't meter them. Your costs are whatever your chosen provider charges you directly — often pennies per hundred summaries with efficient models, or zero with a free-tier key.
2. No subscription needed to justify servers. This is why BYOK tools like GlenSum can be one-time purchases instead of monthly plans.

Setting up BYOK takes about two minutes

1 · Get an API key

Create a key in your AI provider's console (OpenAI, DeepSeek, or any OpenAI-compatible service). Paste it into GlenSum's settings — the key is stored locally in your browser profile, not on our servers.

2 · Or skip the key entirely

GlenSum also ships with built-in free model options that work with zero setup, so you can try the whole workflow before touching an API console.

Honest limits of BYOK

• You're responsible for your own API costs (tiny for summaries, but real).
• BYOK protects page content from the tool vendor — your chosen AI provider still processes the text under its own policy. Pick a provider you trust.
• One-time setup: if you never want to think about keys, the built-in free models are the middle path.