隐私政策 · Privacy Policy
中文
本扩展用于识别并隐藏、屏蔽 X（推特）评论区里的色情引流账号。除了你主动加入的「共享黑名单」服务外，我们（扩展开发者）不接收任何数据；不出售任何数据，也不使用任何统计或广告服务。下面说明扩展在你的浏览器里读取了什么、会发送到哪里。
1. 扩展读取的信息
仅在 x.com / twitter.com 页面上，扩展读取你正在浏览的帖子的公开内容：评论作者的显示名、@账号名、评论文字、是否带图片或视频，以及被回复的原帖文字。扩展不读取私信、不读取你的密码，也不访问其他网站的内容。
2. 信息会被发送到哪里
| 接收方 | 发送的内容 | 什么时候发送 |
|---|---|---|
Jev 决策服务（默认 TypeSafe 官方接口 api.typesafe.ai，或你在设置里填写的其他 Jev 兼容地址） |
待判定评论的显示名、@账号名、评论文字、是否带媒体、原帖文字，以及同一帖子下最多 30 条其他评论作为参考；你的 Jev API Key 用于身份验证 | 开启「浏览时自动识别」并填写了 API Key 时，浏览帖子评论区时发送。Jev 服务如何处理这些数据由其自身的隐私政策约定 |
| X（x.com） | 屏蔽请求（被屏蔽账号的 @账号名） | 识别为黄推且设置为「隐藏并屏蔽」时，以你当前登录的 X 账号发起，与你在 X 网页上手动屏蔽相同 |
共享黑名单服务 xblocker.gastrackerapp.com（由本扩展开发者运营，需要你主动加入，默认关闭） |
被屏蔽账号的公开信息：X 数字 ID、@账号名、显示名、注册时间、粉丝数/关注数/发帖数、是否认证；评论文字（可在设置中关闭，关闭后只发去表情后文本的哈希）；帖子 ID 和评论 ID；判定依据（分数、规则信号）；一个随机生成的安装 ID 和扩展版本号。不包括你自己的 X 账号、Cookie、Jev API Key 或浏览记录 | 在「高级设置 → 上报」选择「共享黑名单」并确认同意后，被屏蔽的账号会先存入本机发件箱，每分钟批量发送。用于生成所有用户共用的黑名单 |
| 你自己填写的上报地址（可选，默认不开启） | 与上一行相同的内容 | 仅当你在「高级设置 → 上报」选择「自定义地址」时发送 |
共享黑名单服务的数据保留：评论文字保存 30 天后删除（只保留哈希）；上报明细保存 180 天；共享黑名单只保存汇总结果（账号 ID、被多少人屏蔽、原因代码）。对外分发的黑名单只包含账号 ID 和原因代码。你可以凭安装 ID 申请删除自己上报的数据；被列入黑名单的账号可以申诉移除。
3. 保存在你本机的信息
- 设置（包括 Jev API Key）：保存在浏览器的扩展存储（
chrome.storage.local），不会发送到 x.com 页面。 - 检测与屏蔽记录：保存在本机的 IndexedDB，最多 80,000 条，超出后自动删除最旧的记录。
- 临时状态（多个 x.com 标签页之间的屏蔽协调）：保存在
chrome.storage.session，关闭浏览器后清除。
这些数据只在你的浏览器里，开发者无法访问。
4. 你的控制权
- 在「记录」页可以导出或清空全部记录。
- 可以随时关闭「浏览时自动识别」，或选择「只隐藏」而不屏蔽。
- 不填写 Jev API Key 时，扩展只用本地关键词和规则判断，不会向 Jev 发送任何内容。
- 卸载扩展会删除扩展保存的全部本地数据。
5. 数据用途限制
上述数据仅用于识别、隐藏和屏蔽色情引流账号这一单一用途：不用于广告、不出售或转让给第三方、不用于判断信用或放贷资格，也不由开发者人工查看。
6. 变更与联系
本政策如有变更，会更新本页并修改生效日期。隐私相关问题（包括申请删除你上报的数据）请联系 privacy@gastrackerapp.com；其他问题请联系 support@gastrackerapp.com。被列入共享黑名单的账号可通过 申诉页 申请移出。
English
This extension detects porn-spam accounts in X (Twitter) replies and hides or blocks them. Apart from the opt-in shared blocklist service, we (the developer) receive no data; we sell no data and use no analytics or advertising services. This page explains what the extension reads in your browser and where it is sent.
1. What the extension reads
Only on x.com / twitter.com, the extension reads public content of the posts you are viewing: reply authors' display names, @handles, reply text, whether a reply has media, and the text of the original post. It does not read direct messages or passwords, and does not access other websites.
2. Where information is sent
| Recipient | What is sent | When |
|---|---|---|
Jev decision service (by default the official TypeSafe endpoint api.typesafe.ai, or another Jev-compatible URL you enter in settings) |
Display name, @handle, reply text, media flag and original post text of the replies being judged, plus up to 30 other replies from the same post as context; your Jev API key for authentication | While "auto-detect while browsing" is on and an API key is set, when you view a post's replies. The Jev service's own privacy policy governs how it handles this data |
| X (x.com) | Block requests (the @handle being blocked) | When a reply is classified as spam and the action is "hide and block", sent with your signed-in X session — the same as blocking manually on X |
Shared blocklist service xblocker.gastrackerapp.com (run by the developer of this extension; opt-in, off by default) |
Public info of blocked accounts: X numeric ID, @handle, display name, account creation date, follower/following/post counts, verified flag; reply text (can be turned off — then only a hash of the normalized text is sent); post and reply IDs; detection basis (score, rule signals); a randomly generated install ID and the extension version. It does not include your own X account, cookies, Jev API key or browsing history | After you choose "Shared blocklist" under Advanced settings → Report and confirm, blocked accounts are queued in a local outbox and sent in batches every minute, to build a blocklist shared by all users |
| Your own report URL (optional, off by default) | Same as the row above | Only if you choose "Custom URL" under Advanced settings → Report |
Retention on the shared blocklist service: reply text is deleted after 30 days (only the hash is kept); report details are kept for 180 days; the shared blocklist keeps aggregates only (account ID, number of independent reporters, reason codes). The distributed blocklist contains account IDs and reason codes only. You can request deletion of your reports by install ID; listed accounts can appeal for removal.
3. What is stored on your device
- Settings (including your Jev API key): in the browser's extension storage (
chrome.storage.local); never passed to x.com pages. - Detection and block records: in local IndexedDB, up to 80,000 entries; the oldest are deleted automatically beyond that.
- Temporary state (coordination between open x.com tabs): in
chrome.storage.session, cleared when the browser closes.
This data stays in your browser; the developer cannot access it.
4. Your controls
- Export or delete all records on the Records page.
- Turn off auto-detection at any time, or choose "hide only" instead of blocking.
- Without a Jev API key, the extension uses local keywords and rules only and sends nothing to Jev.
- Uninstalling the extension deletes all of its local data.
5. Limited use
The data above is used solely to detect, hide and block porn-spam accounts. It is not used for advertising, not sold or transferred to third parties, not used to determine creditworthiness or for lending, and not read by humans on the developer's side.
6. Changes and contact
If this policy changes, this page and its effective date will be updated. Privacy questions (including deletion requests for your reports): privacy@gastrackerapp.com. Other questions: support@gastrackerapp.com. Accounts on the shared blocklist can request removal via the appeal page.