隐私政策 · 垃圾账号清理器(X / 推特)

最后更新:2026 年 11 月 5 日 · 适用版本:1.7.42 及以后

一句话:这个扩展完全在你的浏览器里运行。它没有服务器、没有账号体系、 没有统计埋点,不会把你的任何数据发送给开发者或第三方。

1. 我们处理哪些数据,为什么

扩展的唯一用途是帮你在 X(twitter.com / x.com)上隐藏并拉黑垃圾账号。为了做到这一点, 它会在你浏览时读取页面内容,并把你的配置保存在本地:

数据用途存放位置
你自己设置的规则(正文 / 昵称 / 简介关键词、豁免名单、执行节奏) 按你的要求判定哪些内容需要隐藏 本机 chrome.storage.local
判定结果与待拉黑队列:账号名、显示名、简介片段、命中原因、时间 让你在弹窗里检查、修改、删除;决定是否执行拉黑 本机 chrome.storage.local
账号公开资料缓存(关注数、粉丝数、创建日期等) 避免重复查询同一账号,减少请求 本机 chrome.storage.local
运行统计(今日入池、今日已拉黑) 在弹窗里显示进度 本机 chrome.storage.local

以上数据不会离开你的设备。扩展不使用 storage.sync,因此也不会同步到你的 Google 账号。

2. 网络请求

扩展只与 X 平台自身的域名通信 —— x.com / twitter.com, 以及 X 用来分发前端脚本的静态资源域名 abs.twimg.com;全部使用你自己已登录的会话:

不存在开发者服务器、中转服务或第三方 API。扩展不会把你的浏览记录、账号信息、 规则配置或统计结果发送到 X 平台之外的任何地方。

3. Cookie

扩展申请了 cookies 权限,但只读取 x.com 下的一个 cookie:ct0。 它是 X 自己的 CSRF 校验令牌,调用 X 的拉黑接口时必须带上。这个值只用于构造请求头, 不写入、不修改、不存储、不上传。

4. 我们不会做的事

5. 数据删除

6. 权限说明

7. 儿童

本扩展不面向 13 岁以下儿童设计,也不会有意处理儿童的个人信息。

8. 变更

本政策如更新,会同步修改本页顶部的日期,并在扩展的更新说明中注明。

9. 联系方式

问题、疑问或投诉:请到 github.com/pexih/x-spam-blocker-legal/issues 提交 Issue, 这是本项目唯一的对外反馈渠道。

10. 与 X Corp. 的关系

本扩展是独立开发的第三方工具,与 X Corp. 没有任何关联,也未获得其背书或授权。 “X”仅用于说明适用的平台。

Privacy Policy · X (Twitter) Spam Account Cleaner

Last updated: November 5, 2026 · Applies to version 1.7.42 and later

In one sentence: this extension runs entirely in your browser. There is no server, no account system and no analytics — none of your data is sent to the developer or any third party.

1. What data is processed

The extension's only purpose is to hide and block spam accounts on X. To do that it reads page content while you browse and stores your configuration locally:

All of it lives in chrome.storage.local on your device. The extension does not use storage.sync and never transmits this data anywhere.

2. Network requests

Requests go only to X's own domains — x.com / twitter.com, plus abs.twimg.com, the static-asset host X uses to serve its front-end scripts — and always with your own signed-in session: public profile lookups and block actions that you configured or clicked yourself. There is no developer server, no relay and no third-party API.

3. Cookies

The cookies permission is used to read exactly one cookie on x.com: ct0, X's own CSRF token, required as a request header when calling X's block endpoint. It is never written, modified, stored or transmitted.

4. What we never do

5. Deleting data

Remove individual entries or clear the queue from the popup. Uninstalling the extension makes Chrome delete all of its chrome.storage.local data. You do not need to contact us — we never had your data.

6. Permissions

storage for local config and queue; alarms for scheduled batches; cookies for the ct0 token; host permissions limited to x.com and twitter.com, where the entire feature set lives.

7. Children

Not directed to children under 13, and no personal data from children is knowingly processed.

8. Changes

If this policy changes, the date at the top is updated and the change is noted in the extension's release notes.

9. Contact

Questions, concerns or complaints: please open an issue at github.com/pexih/x-spam-blocker-legal/issues, the only public support channel for this project.

10. Affiliation

This is an independent third-party tool. It is not affiliated with, endorsed by, or sponsored by X Corp. "X" is used only to describe the platform it works on.