XMore data privacy: local storage, cloud accounts and Agent
Your library and its search indexes live in the browser. Sync connects directly to X, account services use the XMore cloud, and optional Agent tag suggestions send the current item through the Companion to your chosen model service after you enable them.
Sync uses your existing X session
The extension uses your existing browser session to request your selected data directly from X. It temporarily reads the X session cookies needed to identify the account and authenticate requests. Raw cookie values are not stored in the XMore database or sent to the XMore cloud or model services.
Local X bookmark search and indexes stay in the browser
Synced or imported post content, relationship caches, search queries, full-text indexes and semantic vectors are stored in the current browser. The built-in multilingual semantic model runs on the device.
Use the bookmark search guide or likes search guide to see how these local records are searched. The library covers content that has successfully synced or imported.
Cloud services handle identity and access
XMore cloud services handle sign-in, device sessions, subscription and access state, and bound X account details such as the user ID, username, display name and avatar URL. XMore requires an account and valid access rights, including for local library features.
The public website uses Cloudflare for hosting, security and aggregate web analytics. When configured, public pages also use Google Analytics 4 and first-party analytics cookies to measure visits and button clicks. The privacy policy describes these website analytics; local library contents are kept separate.
Optional Agent tag suggestions have a separate outbound data path
Agent is off by default. It requires the Companion, the necessary browser permission, a connected model service and your choice to enable tag suggestions. Opening a post can then send its text and required context to that service. Providers process these requests under their own account settings and policies. Turning Agent off stops new model requests; local search and manual tags still require valid XMore access.
Protect your local copy and understand deletion
Clearing extension data, uninstalling the extension or losing the device can remove the local library. Keep original X archive files separately. An original archive preserves its own contents; it may not include later tags or newly synced posts.
Account-scoped content, source relationships and search results remain separated. Manually created tag structures are shared within the local device library.
Read the privacy policy (Chinese) and extension privacy disclosures (Chinese) for the detailed permissions, providers and deletion process.
Common questions
Is local semantic search the same as optional Agent?
Local semantic retrieval uses the built-in model on your device. Optional Agent tag suggestions use a separate connection to your selected model service.
Does local-first mean that XMore works indefinitely without online access?
XMore requires sign-in and valid access rights. Account and entitlement checks use online services even though library records and search computation are local.
Will deleting my cloud account also erase the browser library?
Cloud account deletion and clearing local extension data are separate processes. Review the privacy policy and preserve the data you need before either action.
Where can I ask about permissions or deletion?
Use the contact page (Chinese). The formal privacy policies describe the account deletion request process and data retention details.
morePRIVATE X LIBRARY
YOUR X, REMEMBERED
Make your saved posts useful again.
Build a local X library from your bookmarks, likes and own posts.
Add XMore to Chrome