Conjure — Privacy Policy
This policy explains what data Conjure collects, stores, and transmits, and why. It's written to be read in full. There's not much to hide because there's not much happening off your device.
the short version
Conjure does not have an account system, does not run a server, does not sync your data anywhere, and does not track you. Everything Conjure needs to work lives locally in your browser. The only exception is a single, opt-in call to a third-party license API, and only if you enter a Pro license key.
what Conjure stores, and where
Conjure stores the following locally, in your browser's extension storage. None of it leaves your device, except the license key sent to Polar.sh as described below:
- Your curated bookmark list, along with any renames or aliases you set (Pro)
- Your theme preference and new-tab-page settings (background image or color, drop shadow, fullscreen mode, date/time display)
- Your Pro license state, if you've activated a license key
Conjure also reads data that already exists in Chrome, live, without copying or exporting it anywhere:
- Your Chrome bookmark tree, read so bookmarks can appear as searchable results in the command palette. You pick a curated shortlist from it, and curated titles follow bookmark renames; Pro users can also search the full bookmark tree. Conjure does not create, delete, or reorganize your native bookmarks.
- Your open browser tabs (title, URL, recency), read so tabs can appear as searchable, switchable results in the palette. This is what lets Conjure act as a cross-window tab switcher.
what Conjure does not do
- No account or login of any kind.
- No cloud sync. Nothing about your bookmarks, tabs, or settings is uploaded anywhere.
- No backend that we operate. There is no Conjure server sitting between you and your data.
- No telemetry, no analytics, no usage tracking, in the codebase.
- No reading, modifying, or transmitting the content of the pages you visit. The command palette is injected as a self-contained overlay; it does not inspect or alter page content.
the one external call Conjure makes
If, and only if, you enter a Conjure Pro license key, Conjure calls Polar.sh's public license-key API to activate, periodically revalidate, and deactivate that key. This is a direct, no-auth API call made from the extension itself; there is no Conjure-run server in the middle. It happens roughly once every 24 hours to revalidate an active license, with a 7-day offline grace period so Pro continues working without a connection. If you never enter a license key, this call is never made.
Each call sends only what's needed to validate the
license: the license key, Conjure's Polar organization
ID, the activation ID Polar issued for this device, and
a device label such as
Conjure • Linux • 1a2b3c4d. The label is your
operating system name plus the first 8 characters of a
random ID Conjure generates the first time you activate,
so you can tell your activated devices apart. No
bookmark, tab, or browsing data is included.
permissions Conjure requests, and why
| Permission | Why it's needed |
|---|---|
bookmarks |
Read your bookmark tree so it can be searched from the palette. |
storage |
Store your curated list, settings, and license state locally. |
activeTab |
Give Conjure access to the current tab only when you open the palette with its shortcut or toolbar button, so it can show the overlay there. Conjure has no standing access to the sites you visit. |
scripting |
Inject the command palette overlay into that tab. |
tabs |
List and switch to your open tabs from the palette. |
alarms |
Schedule periodic Pro license revalidation. |
notifications |
Let you know when Conjure's keyboard shortcut isn't set, so you can assign one. |
favicon |
Show each result's site icon from Chrome's local favicon cache. No request is made to the site. |
children's privacy
Conjure is not directed at children and does not knowingly collect data from anyone, children included, since it does not collect data from anyone at all.
changes to this policy
If Conjure's data handling ever changes, for example if telemetry or analytics were ever introduced, this policy will be updated first, before the change ships, and the update will be reflected in the Chrome Web Store listing.
contact
Questions about this policy or how Conjure handles data can be sent to:
privacy@kuronaut.com
This policy applies to the Conjure Chrome extension only. It does not apply to third-party sites you may visit or link to through Conjure, including Polar.sh, whose own privacy policy governs the license-key API call described above.