Knote Privacy Policy

Last updated: 24 August 2026

Knote is a Chrome extension for notes tied to web pages. This policy describes everything it does with data. It is short because Knote does very little.

The short version

Knote stores your notes in chrome.storage.local in your Chrome profile. There is no Knote server or account, and Knote does not transmit your notes or browsing URLs to us or to third parties. We cannot access your notes through Knote. Chrome’s local extension storage is not end-to-end encrypted, so it should not be treated as encrypted storage against someone or software with access to your device or browser profile.

Before Knote reads notes or browser addresses, it shows this disclosure and asks you to agree. If you choose Not now, Knote remains paused and does not read notes, rules, granted-site state, or tab and navigation addresses. Your existing local data, if any, is left untouched.

What Knote can see

The addresses of tabs open in Chrome and their top-level navigations. Knote compares these addresses against the notes you saved so it can update each tab’s toolbar count and show the notes about the current page. This comparison happens entirely on your computer. Knote does not transmit the addresses or keep a history of pages you visited. An address is stored only when you deliberately tie a note to that page.

This is what the “Read your browsing history” permission warning Chrome shows at install time refers to. The tabs and webNavigation permissions let Knote read open-tab and top-level navigation addresses for local matching. Knote uses them for that user-facing feature and does not create a browsing-history log.

No page content. Knote requests no access to any website when you install it. It does not read page text, images, form values, cookies, or page storage. If you enable the optional on-page badge for a site, Knote injects only the code needed to display and update that badge on the origin you granted.

What Knote stores

All of this lives in chrome.storage.local on your computer:

• Your notes — the title and body text you wrote, their status, and when they were created and changed.
• The pages a note is tied to. How much of the address is stored depends on how you tied it:
  • A prefix link — the default — stores only the site and the path, for example https://example.com/docs/guide. The query string and the fragment are never stored. If the page you captured had a session token or a search term in its address, it does not reach storage, your exported file, or anywhere else.
  • An exact link stores the full address including the query string and fragment, because that is what makes it exact. Knote tells you this before you create one, and you have to choose it deliberately.
  • A rule link stores only the parts of the address your rule marked as identifying — for example a document or topic identifier. Manually attached rule links may also keep an opening address rebuilt from the rule and those identifiers; unrelated query parameters are not copied. Rules with wildcard paths or missing identity captures may have no opening address.
• Any URL rules you wrote, which are patterns you typed yourself.
• Your preferences — theme and language.

Chrome separately records the website permissions you grant. Knote reads that permission state to show the Site access list and register or remove the optional on-page badge. It does not keep a second copy of that grant list in chrome.storage.local.

Site access

Knote asks for access to a website only when you turn on the on-page badge for that site, and only for that site. You grant it one site at a time, from inside Knote, and you can see the full list and remove any of them at any time under Site access in the Manager.

Removing access stops Knote injecting anything into that site immediately. Revoking it from Chrome’s own extension settings works too; Knote notices and updates its own list.

Everything else — matching, the side panel, the toolbar count — works on every site without any access at all.

What Knote does not do

• No analytics, telemetry, crash reporting, or usage tracking of any kind.
• No advertising, and no data sold, shared, or transferred to anyone.
• No accounts, sign-in, or cloud sync.
• No network requests by Knote. It does not contact any server, including ours.
• No use of your notes for training anything.

Chrome Web Store Limited Use

Knote complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data handled by Knote is used only to provide Knote’s single purpose: creating local notes tied to web pages and surfacing those notes on matching pages. Knote does not use or transfer this data for advertising, profiling, creditworthiness, lending, or any unrelated purpose.

Data you export

Exporting writes a Markdown file of your notes, or a JSON file of your rules, to wherever you choose to save it. What happens to that file afterwards is up to you — Knote has no further involvement with it.

Prefix links keep their promise in exports too: the query string and fragment are absent there as well.

Deleting your data

Chrome clears Knote’s chrome.storage.local data when you remove the extension. Knote has no server-side copy to request or delete. Uninstalling does not delete Markdown or JSON files you exported, files you previously imported, backups, or copies you created outside the extension; remove those separately if you no longer want them. You can also delete individual notes at any time from the side panel or the Manager.

Children

Knote is not directed at children. It has no account or backend and does not transmit users’ notes or browsing data to the developer, regardless of age.

Changes to this policy

If this policy changes, the updated version will be published here and the date at the top will change. Because Knote stores nothing remotely, a change to this policy cannot retroactively affect data you have already created.

Contact

Questions can be directed to the maintainer at https://github.com/unickhow.