// clean reader view · scoped

Refine: clean readable pages after a click.

Refine turns noisy web pages into focused text-first article views after a user clicks the extension, with activeTab-first access, local extraction where practical, no tracking, no account, and no background reading.

Request updates → Privacy posture

// Workflow preview

Open a noisy page. Click once. Read.

Refine is being shaped around the practical parts of reading: comfortable width, local extraction where practical, low permissions, no tracking, and a clean way back to the original page.

Before

After

Readable title

scoped · implementation pending

// Product basics

What it does.

Category: clean reader view.
Workflow pain: useful articles are buried inside visual clutter, popups, heavy layouts, and reader tools that ask for more page access than users expect.
Status: scoped; implementation pending.
Trust posture: user-triggered `activeTab` access, local reader payload where practical, no tracking, no account, no broad host permissions by default.

// Problem

Noisy pages make focused reading harder.

Refine is being tested for people who regularly read cluttered web pages without leaving the browser.

// Workflow

Click, clean, read, return.

V1 runs only after user action, creates a clean reading view, preserves basic local preferences, and returns users to the original page without background page processing.

// Not this

Clean reading, not a reading platform.

Refine V1 will not ship chat, cloud sync, accounts, highlights, research dashboards, broad host access, or automated background page processing.

Product notes

Refine is scoped for making noisy pages readable after a user action, without becoming a research dashboard or account-based reading service.

Core action: clean the current page into a readable view.
Permission posture: activeTab-first, user-triggered, no broad host access by default.
Trust: local extraction where practical, no tracking, no account.
Status: scoped; implementation pending.

Expected V1 Permissions

activeTab: access the current page only after the user clicks Refine.
scripting: run the readability workflow on the active tab if needed.
storage: save local preferences such as text size, width, or theme.

Trust posture

Refine should process locally where practical, avoid collecting page content by default, avoid tracking, avoid accounts/cloud requirements, and explain every permission before Chrome Web Store submission.

View Refine permission registry →