Your reading, on your device

Privacy Policy

Your clips stay in your browser unless you request optional AI suggestions. XTOC has no telemetry, no uploads to the developer, and no automatic clip sync.

Last updated: October 16, 2026 · Extension policy

01 / What this policy covers

This policy describes the XTOC browser extension, maintained by Aries (HiAriesZhou). XTOC provides a table of contents and local clips for supported X.com and Twitter.com long-form articles. You do not need a separate XTOC account.

02 / What XTOC reads and saves

The extension reads article headings and page content to build the table of contents, navigate sections, and let you select a passage. It responds to scrolling, text selection, and clicks locally to operate these features; it does not send an activity log to the developer.

When you choose to save a passage, XTOC stores the selected text, nearby text for context, the source URL, article title, available author and publication information, and save timestamps. Tags and notes you add are also stored. Panel position, visibility, and clip settings are saved locally.

About “User activity” and “Website content”

These data categories describe interactions and content that the extension handles to provide its features. Local processing is still data processing. Reading headings or saving a selection does not mean that XTOC uploads your activity or article content.

03 / Why these permissions are needed

storage: Saves clips, article metadata, tags, notes, and preferences in chrome.storage.local, in your local browser profile. XTOC does not use Chrome sync storage.
activeTab: Lets the popup identify the active tab when you open it, check whether it is an X/Twitter page, and communicate with the article’s content script.
contextMenus: Adds the “Show Table of Contents” right-click menu on X.com and Twitter.com.
X / Twitter access: Article access and content scripts are limited to https://x.com/* and https://twitter.com/*. This lets XTOC read supported articles and display the reading panel. Optional AI separately requests host access for the provider you configure.

04 / No telemetry; optional AI requests

The extension includes no analytics, advertising trackers, or remote error reporting. It does not upload article content, saved clips, tags, notes, or usage activity to the developer. There is no XTOC backend or automatic cross-device synchronization for clips.

Opt-in AI suggestions: If you enable AI and configure an external OpenAI-compatible provider endpoint and API key, requesting suggestions sends that bookmark’s saved text (or clip text), title, and existing tag names directly to your configured provider only. Personal notes are not sent. The provider handles these requests under its own privacy policy.

Your API key is stored locally in extension session storage by default. If you choose “Remember on this device”, it is encrypted in the extension’s IndexedDB on this device. The key is sent only to your configured provider to authenticate requests.

Normal requests made by X/Twitter and Chrome’s extension distribution and update services are separate from XTOC’s local processing.

05 / Retention, deletion, and export

Saved data stays in your local browser profile until you delete it or remove the extension’s local data. There is no automatic expiry or server-side copy held by XTOC.

Review or delete: Open the extension’s Clips / Options page to review, edit, or delete clips. Deleting an article’s last clip also removes its saved article metadata.
Remove local extension data: Uninstalling XTOC removes its local extension storage, including settings. Export anything you want to keep first.
Export: Markdown and JSON files are generated locally only when you request them. They can include passages, surrounding context, source URLs, author information, timestamps, tags, and notes.

Downloaded exports are separate files. Deleting clips or uninstalling XTOC does not delete those files or copies you have shared or backed up. You control where they go.

06 / This website and external links

This website is a product guide and interactive demo. It does not read your extension’s clip library. The demo uses sample content and does not connect to extension storage.

Visiting the website involves normal network requests to its hosting provider, Vercel; local clip storage does not mean website visits are invisible to a hosting provider. Links to X/Twitter, GitHub, and the Chrome Web Store open services with their own privacy practices.

07 / Questions and policy changes

For privacy questions, email aries0331.dev@email.com. You can also inspect the extension source on GitHub. Avoid posting private clips or personal data in public issues.

This policy will be updated when the extension’s data handling changes. The date above identifies the latest revision.