你的隐私，认真对待。

1. 插件如何使用数据

X Partner 用于自定义 X 的显示昵称与页面布局。扩展在你打开的 X 页面内识别账号标识、显示名、导航入口与页面模块，以应用你选择的设置。未登录时，设置只留在本机。登录后，每次修改都会把全部插件设置保存到你的账号：昵称、原显示名、账号标识、编辑时间、页面布局、功能开关、屏蔽关键词、界面语言和 Grok 收起状态。会员到期后这份设置仍留在账号里。不保存帖子正文、X 登录凭据或 API Key。

本机仍使用 Chrome 扩展存储，并保留 Chrome 同步副本；是否经 Chrome 同步到其他浏览器由你的 Chrome 账号决定。账号副本按每一项的修改时间合并：昵称按每条自己的修改时间合并，删除会留下删除记录，避免旧设备把已删昵称或屏蔽词恢复回来。

开启「自动展开帖子」后，扩展优先读取页面已加载的全文；缺少全文时，仅为屏幕附近的折叠帖子使用当前 X 会话向 X 按需请求详情，一次一条，间隔至少 3 秒。必要时读取 X 静态资源中的接口标识，不执行下载的代码。正文仅暂存在当前页面内存，刷新或关闭页面后清除；关闭功能会停止补读。X 会话凭据不会发送给我们。

关键词的匹配只在浏览器内进行。屏蔽词列表在登录后随其他设置保存到账号。当前版本不会把帖子正文发送到我们的服务器。

「Grok 平铺展示」只调整 X 原生 Grok 抽屉的显示位置。扩展不读取、保存或自动发送聊天内容；你主动使用 Grok 时，交互由 X 处理。

2. 登录与账号记录

只有在你主动登录时，网站才会处理你的邮箱地址、登录验证记录、账号标识与会话。邮箱用于发送验证码和识别账号；其他记录用于保持登录以及连接插件中的同一账号。Google 登录为可选方式，邮箱登录独立保留。会员方案与有效期由服务器保存并提供给登录后的官网与插件。

选择 Google 登录时，你会前往 Google 完成身份验证。我们仅申请身份与邮箱权限（openid email），接收 Google 的稳定账号标识、邮箱及验证状态，用于登录和关联本产品账号；不索取 Google 密码、邮件内容、通讯录或 Drive 文件。Google 账号标识与本产品账号的绑定保存在服务器中；Google 返回的身份与访问令牌仅用于当前验证，不写入账号数据库。对于 Google 未管理的第三方邮箱，首次关联还需通过邮箱验证码确认当前归属。

网站使用仅限当前域名的必要安全 Cookie 保持登录；旧网站登录状态不跨域传递，切换到新官网需重新登录。Google 授权及邮箱关联过程中还使用短期 Cookie 和临时授权记录，防止伪造、错配或重复使用登录请求。插件独立保存自己的登录凭据，不进行 Chrome 同步，也不向 X 页面提供账号或凭据。网站与插件分别退出。服务器以摘要形式保存验证码和会话令牌，并使用来源 IP 的摘要限制异常请求；不在应用数据库中保存原始 IP。

Pro 订阅由 Creem 收款。卡号和账单地址由 Creem 处理，不进入我们的服务器。我们保存订单号、账号关联、方案、标价、实付金额、渠道、订单状态、创建与完成时间、会员有效期和续订状态，用于开通、续期、取消和查询。取消续订后，当前已付周期继续有效，到期后不再扣款。获准账号仍可通过内部免扣款确认开通，实际收款为 0，且不自动续费。旧的模拟订单和会员记录仍保留，但不授予新权益。

3. 服务提供者与数据传输

网站托管于日本服务器，通过 Cloudflare 提供 HTTPS 访问与网络转发；这些基础设施提供者会处理传输请求所需的网络信息，例如 IP 地址。验证码由邮件服务发送，邮件提供者会处理收件邮箱和验证码邮件。因此使用网站可能涉及跨境数据传输。

Google 登录与 Chrome 同步由 Google 提供，相关处理遵循 Google 隐私政策；只有你选择 Google 登录后才会跳转至 Google。X 自身的服务由 X 提供。付款由 Creem 处理。我们不出售数据，不使用广告追踪或第三方分析脚本。我们仅为上述功能和运行服务处理数据。

4. 保存期限

• 验证码 5 分钟失效，插件一次性授权码 90 秒失效，登录会话最多 7 天有效。Google 临时授权与待验证邮箱关联记录 10 分钟失效，有效授权回调消费后不可复用。失效不代表数据库记录立即删除；过期会话、授权码、Google 临时记录和超过 24 小时的验证码记录会在后续登录请求时清理。超过 24 小时的限流记录会在后续相关请求时清理。
• 邮箱账号、Google 账号绑定、订单及会员记录目前没有自动删除期限。退出登录不会删除账号或历史记录；你可以按下述方式申请删除。
• AI 用量元数据目前没有自动删除期限；可申请随账号删除。登录后保存在服务器上的插件设置同样没有自动删除期限，退出登录、会员到期或卸载插件都不会删除这份账号副本，可申请随账号删除。本机设置保留至你删除或清除相应数据；页面临时正文不会写入扩展存储。邮件提供者与基础设施提供者可能按各自政策保留运行记录。

5. 你的选择与删除方式

你可以不登录账号，继续使用本机的昵称、布局和关键词屏蔽。登录后，修改和删除会在保存时更新账号副本。昵称删除会写入本机、Chrome 同步存储和已登录账号。

卸载插件会移除本机扩展数据，但不会自动删除网站账号、已保存的插件设置或历史会员记录。Chrome 同步数据也可通过 Chrome 自身设置管理；旧版导出的文件需要自行删除。

如需查询、更正或删除账号、Google 账号绑定及相关记录，请写到 [email protected]，并提供用于登录的邮箱以便核验。当前尚无网站自助注销入口。请不要发送验证码、密码或登录令牌。

6. 扩展权限

storage 用于保存昵称、布局与设置；identity 用于你点击登录后打开网站并接收授权结果；xpartner.kunvis.me 用于登录、账号状态，以及在已登录时保存和取回插件设置；payment.kunvis.me 兼容旧版插件账号入口；x.com / twitter.com 用于应用页面显示调整。扩展不请求所有网站或浏览历史权限。

7. 联系与更新

隐私问题请写到 [email protected]，并提供用于登录的邮箱以便核验。请不要发送验证码、密码或登录令牌。本页会随数据处理方式变化更新，并标注更新日期。

1. Data used by the extension

X Partner customizes display nicknames and the layout of X. It identifies account handles, display names, navigation items and page elements within the X pages you open to apply your settings. Until you sign in, settings stay on the device. After you sign in, each change saves the whole extension setup to your account: nicknames, original names, handles, edit times, layout, switches, blocked keywords, interface language and the Grok collapsed state. That copy remains after membership ends. Post text, X credentials and API keys are not saved.

The device also keeps Chrome extension storage and a Chrome sync copy. Your Chrome account decides whether Chrome syncs that copy to another browser. The account copy merges by each item’s edit time. Nicknames merge individually, and a deletion is kept so an older device cannot restore a nickname or blocked keyword you removed.

When automatic post expansion is enabled, the extension first uses full text already loaded by X. For nearby collapsed posts that lack full text, it requests details from X using your current X session, one at a time and at least 3 seconds apart. It may read interface identifiers from X static resources without executing downloaded code. Post text stays in page memory and is cleared when you reload or close the page. Turning the feature off stops additional requests. Your X session credentials are not sent to us.

Keyword matching runs only in the browser. The keyword list is saved with the rest of your settings after you sign in. This version does not send post text to our server.

Grok layout controls only reposition the display of X’s native Grok drawer. The extension does not read, save or automatically send conversations. Interactions you initiate with Grok are handled by X.

2. Sign-in and account records

If you choose to sign in, the website processes your email address, verification records, account identifier and sessions. Your email is used to deliver sign-in codes and identify your account. Other records keep you signed in and connect the same account to the extension. Google sign-in is optional; email sign-in remains independently available. Membership plans and expiry dates are stored by the server and provided to the signed-in website and extension.

When you choose Google sign-in, you go to Google to authenticate. We request only identity and email permissions (openid email) and receive your stable Google account identifier, email and verification status to sign you in and link your product account. We do not request your Google password, email contents, contacts or Drive files. The link between your Google identifier and product account is stored on our server. Google identity and access tokens are used only for the current verification and are not written to the account database. A third-party mailbox that Google does not manage must also be verified by an email code before its first association.

The website uses a necessary secure cookie scoped to its own hostname. Sign-in sessions are not shared across domains; moving from the old website to the new one requires signing in again. Google authorization and email linking also use short-lived cookies and temporary records to prevent forged, mismatched or replayed sign-in requests. The extension stores a separate sign-in credential that is not synced by Chrome or shared with X pages. You sign out of the website and extension separately. The server stores codes and session tokens as digests and uses a digest of the source IP address for request limits; raw IP addresses are not stored in the application database.

Creem collects payment for Pro. Card numbers and billing addresses are handled by Creem and are not stored on our server. We keep order numbers, account associations, plans, listed prices, amounts paid, payment channels, order status, creation and completion times, membership expiry and renewal status so we can activate, renew, cancel and show orders. After you cancel renewal, the period already paid stays active and no later charge is made. An approved account can still be activated by an internal no-charge confirmation, recorded as a payment of zero with no automatic renewal. Older simulated orders and memberships remain stored and do not grant new access.

3. Service providers and transfers

The website is hosted on a server in Japan and uses Cloudflare for HTTPS access and network forwarding. Infrastructure providers process network information needed to transmit requests, such as IP addresses. An email service delivers sign-in codes and processes recipient addresses and email content. Using the website may therefore involve international data transfers.

Google provides Google sign-in and Chrome sync under the Google Privacy Policy. The website redirects to Google only after you choose Google sign-in. X provides its own services. Creem processes payments. We do not sell data or use advertising trackers or third-party analytics scripts. We process data for the functions and service operations described here.

4. Retention

• Email codes expire after 5 minutes, one-time extension authorization codes after 90 seconds, and sessions after at most 7 days. Temporary Google authorization and pending email-link records expire after 10 minutes. A consumed valid authorization callback cannot be reused. Expiry does not immediately delete a database record. Expired sessions, authorization codes and temporary Google records, and verification records older than 24 hours, are cleaned up on later sign-in requests. Rate-limit records older than 24 hours are cleaned up on later relevant requests.
• Email accounts, Google account links, orders and membership records have no automatic deletion deadline currently configured. Signing out does not delete accounts or historical records. You can request deletion as described below.
• AI usage metadata currently has no automatic deletion schedule; you may request deletion with your account. Extension settings saved to your account after sign-in also have no automatic deletion schedule. Signing out, membership expiry and uninstalling do not delete that account copy; you may request deletion with your account. Settings on the device remain until you delete or clear them. Temporary post text is not written to extension storage. Email and infrastructure providers may retain operational records under their own policies.

5. Your choices and deletion

You can use nicknames, layout and keyword blocking on this device without an account. After you sign in, edits and deletions update the account copy when they are saved. Nickname deletion is written to local storage, Chrome sync and the signed-in account.

Uninstalling the extension removes its local data, but does not delete your website account, the settings saved to that account, or historical membership records. Chrome sync data can also be managed in Chrome settings. Files exported by older versions must be deleted separately.

To access, correct or delete your account, Google account link and related records, email [email protected] and include the address you use to sign in. There is no self-service account deletion page yet. Do not send verification codes, passwords or session tokens.

6. Extension permissions

storage saves nicknames, layouts and settings; identity opens the website after you choose to sign in and receives the authorization result; xpartner.kunvis.me supports sign-in, account status, and saving or restoring extension settings while you are signed in; payment.kunvis.me supports legacy account entry points; x.com / twitter.com enables page display adjustments. The extension does not request access to all websites or browsing history.

7. Contact and updates

Email [email protected] with privacy questions, and include the address you use to sign in. Do not send verification codes, passwords or session tokens. We will update this page and its date when data handling changes.