Is Kaptex safe? What data does it access?

The short answer: Kaptex only does something when you ask it to. It doesn't run in the background scanning your browsing activity, and it doesn't collect or transmit your page content without your action.

Why does Chrome ask for broad permissions?

Chrome extensions that inject buttons into websites must declare "host permissions" for all pages. This is a Chrome architecture requirement — not a signal about what the extension actually does. Kaptex uses these permissions only when you click the capture button on a supported site.

The extension never reads page content passively, never logs your browsing history, and never runs scripts on pages where you haven't interacted with it.

What is actually stored: - Your notebook metadata (notebook names and IDs, synced from your NotebookLM account) - Your daily usage counts (to enforce free-plan limits) - Your Google account email and auth token (to keep you signed in)

No page content is stored in Kaptex's database. When you capture something, it goes directly to NotebookLM — Kaptex acts as the bridge, not the destination.

Full details in the Privacy Policy at kaptex.io/privacy.