Social Media Toolbox runs entirely in your browser. It has no backend server, and the developer never receives your data.
All of the following lives in the browser’s extension storage on the machine you installed it on. None of it is transmitted to the developer.
| Data | Why it exists | How long it stays |
|---|---|---|
| Model configs — name, provider, model ID, API key, and relay Base URL | To call the AI provider you chose, and to let you keep several keys side by side | Until you delete the config or uninstall the extension |
| Preferences — interface language, AI output language, comment style, number of drafts, persona instruction, reply method, panel location, theme | To keep the extension behaving the way you set it up | Until you reset them or uninstall the extension |
| X API parameters — query ID, X’s public web bearer token, feature flags | X rotates these when it ships a new frontend, which breaks sending. Keeping them editable means you can fix it without waiting for an update. | Until you restore defaults or uninstall the extension |
| The post you are currently working on — its text, author name, author handle, post ID, and the tab it came from | The side panel is a single window shared across tabs; it needs to know which post and which tab a reply belongs to | Session-scoped — discarded when you close the browser |
Two kinds of request leave your browser, both triggered by you and both going to a party you already have an account with.
| Goes to | What is sent | When |
|---|---|---|
| The AI provider in your active config — Anthropic, OpenAI, Google, or DeepSeek — or the relay Base URL you entered instead | The text of the post, the author’s display name, the comment style you picked, your persona instruction, any one-off extra instruction you typed, and your API key for authentication | Each time you press Generate, and once when you press Test connection |
| X (x.com), through your existing logged-in session | The comment text you chose and the ID of the post you are replying to | Only when you press Reply |
AI requests are billed to your own account and are governed by that provider’s privacy policy and terms. Because the request goes directly from your browser to the provider, the developer has no way to see, log, or retain any of it.
If you configure a relay Base URL, your prompts and your API key go to that host instead of the provider’s official endpoint. That host is chosen by you and is outside the developer’s control — only point it at a service you trust.
| Permission | What it is used for |
|---|---|
| storage | Saving your configs and preferences on this device |
| scripting | Placing the AI comment button under posts on the supported sites |
| tabs | Knowing which tab a post came from, so a reply composed in the side panel is sent on the right tab |
| sidePanel | Showing the comment panel in the browser side panel instead of over the page |
| Access to x.com and twitter.com | Reading the text of the post you clicked, and sending your reply on your behalf |
| Access to xiaohongshu.com | Declared for planned Xiaohongshu support. The current version contains no Xiaohongshu code: it reads nothing and sends nothing there. |
| Access to the AI provider endpoints | Sending your generation request to the provider you configured, or to your relay |
Page access is used only in response to something you clicked. The extension does not read posts in the background, and it does not act on any site other than the ones listed above.
The extension talks to a provider only if you configured it, and to a platform only while you are using it there. Their handling of your data is covered by their own policies:
Your key is stored through the browser’s extension storage, which is readable by this extension and sandboxed away from ordinary web pages. It is not encrypted at rest, because the browser offers extensions no encrypted storage to use — anyone with access to your browser profile on this machine could read it, in the same way they could read a saved password.
There is no account to close and no server-side copy to request or delete, because none is ever created. Data already sent to an AI provider or to X is held by them under their own policy, and any deletion request for it goes to them.
Data handled by this extension is used only to provide the feature you invoked — drafting a comment and, if you choose, sending it. It is never sold or transferred to third parties for advertising, credit assessment, or model training, and it is never used for any purpose unrelated to the feature you asked for. This is a consequence of the design: the extension has no server, so the developer has no access to your data.
This extension is a tool for social media creators and is not directed at children under 13. It does not knowingly collect information from them — or, in fact, from anyone, since it collects nothing centrally.
If the extension ever starts handling data differently, this page and the date above are updated in the same release that changes the behaviour, and the change is described in that release’s notes on the Chrome Web Store. The policy is versioned alongside the extension, so the copy you are reading matches the version you have installed.
For questions about this policy or about how your data is handled, use the developer contact on this extension’s Chrome Web Store listing, under the Support tab.
Social Media Toolbox 完全在你的浏览器里运行。它没有任何后端服务器，开发者也不会收到你的任何数据。
以下内容全部保存在你安装扩展的这台设备的浏览器扩展存储中，不会传输给开发者。
| 数据 | 为什么需要 | 保存多久 |
|---|---|---|
| 模型配置 —— 名称、服务商、模型 ID、API Key、中转站 Base URL | 用于调用你选择的 AI 服务商，也让你可以同时保留多套 Key 随时切换 | 直到你删除该配置或卸载扩展 |
| 偏好设置 —— 界面语言、AI 输出语言、评论风格、候选条数、人设指令、发送方式、面板位置、主题 | 让扩展保持你设定的行为 | 直到你恢复默认或卸载扩展 |
| X 接口参数 —— Query ID、X 的公开 web bearer、feature flags | X 每次前端发版都会轮换这几项，轮换后发送会失败。做成可编辑的，你就不必等扩展更新才能修好 | 直到你恢复默认或卸载扩展 |
| 当前正在处理的帖子 —— 正文、作者昵称、作者 @handle、帖子 ID，以及它来自哪个标签页 | 侧边栏是所有标签页共用的一个窗口，它需要知道这条回复属于哪条帖子、该发到哪个标签页 | 会话级 —— 关闭浏览器即丢弃 |
只有两类请求会离开你的浏览器，都由你主动触发，且都发往你本来就有账号的一方。
| 发往 | 发送内容 | 什么时候 |
|---|---|---|
| 你当前激活配置里的 AI 服务商 —— Anthropic、OpenAI、Google 或 DeepSeek —— 或你填写的中转站 Base URL | 帖子正文、作者显示名、你选的评论风格、你的人设指令、你临时填写的附加要求，以及用于鉴权的 API Key | 每次你点击「生成」时，以及你点击「测试连接」时各一次 |
| X（x.com），通过你已登录的会话 | 你选定的评论内容，以及你要回复的那条帖子的 ID | 仅在你点击「回复」时 |
AI 请求计费在你自己的账号上，受该服务商的隐私政策与服务条款约束。由于请求是从你的浏览器直接发往服务商的，开发者无法查看、记录或留存其中的任何内容。
如果你填写了中转站 Base URL，你的提示词和 API Key 会发往那个地址，而不是服务商的官方端点。该地址由你自己选择，不在开发者的控制范围内 —— 请只填写你信任的服务。
| 权限 | 用途 |
|---|---|
| storage | 在本设备保存你的配置和偏好设置 |
| scripting | 在受支持站点的帖子下方放置 AI 评论按钮 |
| tabs | 识别帖子来自哪个标签页，好让在侧边栏写好的回复发到正确的标签页 |
| sidePanel | 把评论面板显示在浏览器侧边栏，而不是盖在页面上 |
| 访问 x.com、twitter.com | 读取你点击的那条帖子的正文，并代你发送回复 |
| 访问 xiaohongshu.com | 为计划中的小红书支持预留。当前版本不含任何小红书相关代码：不读取、也不发送任何内容。 |
| 访问 AI 服务商接口 | 把你的生成请求发往你配置的服务商或中转站 |
页面访问权限只在你点击之后才被使用。扩展不会在后台读取帖子，也不会在上列站点之外的任何网站上做任何事。
只有你配置过的服务商才会被调用，只有你正在使用的平台才会被访问。他们如何处理你的数据，适用他们各自的政策：
你的 Key 保存在浏览器为扩展提供的存储里，只有本扩展可读，普通网页访问不到。它没有加密存储，因为浏览器并未向扩展提供可用的加密存储 —— 能访问这台机器上你的浏览器配置文件的人就能读到它，就像能读到你保存的密码一样。
没有账号需要注销，也没有服务端副本可供索取或删除，因为它从来就不存在。已经发给 AI 服务商或 X 的数据由他们按各自的政策保管，相关删除请求需要向他们提出。
本扩展处理的数据只用于实现你主动调用的功能 —— 生成评论，以及在你选择时发送评论。它绝不会为了广告、信用评估或模型训练而出售或转让给第三方，也绝不用于与你所请求功能无关的任何目的。这是设计的必然结果：扩展没有服务器，开发者也就无法接触你的数据。
本扩展是面向社交媒体创作者的工具，并非面向 13 岁以下儿童。它不会有意收集儿童的信息 —— 实际上也不收集任何人的信息，因为它不做任何集中收集。
如果扩展今后对数据的处理方式发生变化，本页与上方日期会随改变行为的那个版本一同更新，并在该版本的应用商店发版说明中写明变更内容。本政策随扩展一同版本化，你读到的这一份对应的就是你装着的那个版本。
关于本政策或数据处理方式有任何疑问，可通过本扩展在 Chrome 应用商店页面「支持」标签下的开发者联系方式与我们联系。