Privacy Policy
X to Karakeep — Chrome extension
This extension does not collect, transmit, store, or sell any personal data, browsing history, or analytics — by anyone other than you. It has no backend server of its own. Everything it does happens directly between your browser, X (x.com/twitter.com), and the Karakeep instance you configure yourself.
What data the extension touches, and where it goes
- Tweet content you save (URL, text, author handle) is read from the X page or X's own bookmarks API and sent directly from your browser to your own Karakeep instance's URL, using the API key you provided. It never passes through any server we operate — we don't have one.
- Your Karakeep URL and API key are stored only in Chrome's built-in
chrome.storage, on your device (synced via your own Google account if Chrome sync is on). We never see them. - The
ct0cookie for x.com is read locally to authenticate the background sync's request to X's bookmarks endpoint, using your own already-logged-in session. It is used only in that request header and is never stored, logged, or sent anywhere else. - Sync bookkeeping (last sync time, which X account was active, which tweet IDs
have already been synced) is stored locally in
chrome.storageso the extension can show you status and avoid duplicate saves. This never leaves your browser.
Third parties
The only two destinations any request from this extension ever goes to are:
- X (x.com/twitter.com) — to read your bookmarks and post pages, using your own session.
- Your own Karakeep instance — whatever URL you entered in the extension's settings. This is self-hosted software; we do not operate or have access to it.
No analytics, advertising, or tracking services are used by this extension, at all.
Remote code
This extension does not download or execute any remotely hosted code. All logic ships inside the extension package. Network requests it makes are for data (saving/reading bookmarks), never for loading executable code.
Changes to this policy
If this ever changes, this page will be updated and the extension's version bumped accordingly.