社群連接隱私政策

X 平臺增補 / X platform addendum — 2026-11-09

本增補僅適用於 X，與下方保留的 2026-10-07 歷史條文分開閱讀；歷史準備狀態不是其他平臺今日連接狀態的聲明。負責者及聯絡方式維持不變。本階段只準備 Rich Orange 自有帳號的連接，尚未執行 X 真實授權或收集 X 帳號資料；RC1981 尚未啟用。回調部署不代表帳號已連接。

This addendum applies only to X and is separate from the preserved historical provisions dated 2026-10-07 below; those preparation statements do not describe the current connection status of other platforms. The controller and contact details remain unchanged. This phase prepares a connection for Rich Orange's own account. No live X authorization or collection of X account data has occurred; RC1981 is not enabled. Deploying a callback does not mean an account is connected.

啟用前須取得擁有人另行明確同意。規劃權限僅 users.read、tweet.read、tweet.write；不要求 offline.access、電子郵件、私訊、追蹤者清單、廣告或位置權限。必要資料限於擁有人明確指定的 X 帳號 ID、使用者名稱、實際權限、Token 到期資訊及加密存取 Token，用於身份核對及維持已批准連接。OAuth state 與 PKCE 驗證資料只供單次授權安全使用；不要求 X 密碼，不讀取其他帳號私人內容、不抓取資料、不建立人物畫像、不訓練 AI、不出售或提供廣告資料。

Activation requires separate, express Owner consent. Planned scopes are limited to users.read, tweet.read and tweet.write; offline.access, email, direct messages, follower lists, advertising and location access are excluded. Necessary data is limited to the explicitly designated owner's X account ID, username, granted scopes, token expiry and encrypted access token for identity verification and the approved connection. OAuth state and PKCE material support one-time authorization security. We do not request X passwords, read other accounts' private content, scrape data, profile people, train AI on X data, sell data or provide it for advertising.

X 依其自身政策處理授權與 API 請求。獲批准後，必要資料由既有美國 Vultr 服務處理，按平臺及品牌分離、加密並限制服務身份存取；Cloudflare 提供 DNS，本回調採 DNS-only。Token、驗證碼及完整回調 URL 不寫入一般日誌。現階段不儲存貼文內容，沒有對外資料分享或自動發布；未來發布正文、結果及保存期限須在功能批准前另行披露。

X processes authorization and API requests under its own policies. Once approved, necessary data is processed on the existing US Vultr service, encrypted and separated by provider and brand with restricted service access. Cloudflare supplies DNS; this callback uses DNS-only routing. Tokens, authorization codes and full callback URLs are excluded from ordinary logs. This phase does not store post content, share account data externally or enable automatic publishing. Future publishing content, receipts and retention must be disclosed before that feature is approved.

本階段沒有真實 X 資料可保留，亦不取得刷新 Token。啟用真實連接前，必須完成到期憑據清理、撤銷及必要資料刪除驗收；未完成則維持停用。擁有人可在 X 的已連接應用程式設定撤銷授權，並聯絡 contact@richorangesoftware.com 要求停止處理、更正或刪除。若日後保存 X 內容，須依 X 要求或帳號擁有人請求儘速處理，並遵守適用的 24 小時期限；不能履行時停止 API 存取。請勿寄送密碼或 Token。

There is no live X data to retain at this stage and no refresh token is requested. Before live activation, expiry cleanup, revocation and necessary data deletion must pass acceptance; otherwise access remains disabled. Owners may revoke access in X's connected-app settings and contact contact@richorangesoftware.com to request cessation, correction or deletion. If X content is stored later, requests from X or the account owner must be handled as soon as possible and within the applicable 24-hour deadline; API access must stop if these obligations cannot be met. Do not send passwords or tokens.