CommenOK · 2026-09-30-operator-v2
隱私政策
誰在處理資料
CommenOK 由酷礦國際餐飲有限公司營運，統一編號 50805158。個資及服務聯絡：tc-peat@outlook.com。本政策適用於工作區使用者，以及透過連接的 Instagram 帳號留言或互動的粉絲。
資料來源、類別與用途
您提供登入 Email、密碼及流程設定；密碼以加鹽雜湊儲存。我們從您授權的 Meta API 與 Webhook 取得 Instagram 帳號識別碼、用戶名稱、顯示名稱（name）、頭像網址（profile_picture_url）、授權權杖、貼文與留言、私訊及互動事件、追蹤狀態與發送回執。系統另處理登入工作階段、條款與隱私告知確認的版本及時間、刪除請求狀態與故障紀錄。用途為提供登入與帳號連接、執行您啟用的回覆流程、確認追蹤、避免重複發送及處理支援與安全問題；不出售個資。
處理方式、地區與對象
正式網站 commenok.com 由 DigitalOcean 新加坡區域主機處理及保存應用程式資料，使用 HTTPS 接收連線與事件。Cloudflare 提供網域及 DNS 解析，目前未啟用其網站代理或 WAF。Meta、DigitalOcean、Cloudflare 與寄信供應商可能依各自服務跨境處理相關資料；新加坡主機位置不代表所有供應商資料僅在新加坡處理。只有提供服務必要的營運人員與服務提供者接觸相關資料；依法應提供時，可能提供予有權機關。重大處理地區或供應商變更將更新揭露。
保存期限
服務啟動及運行期間每小時執行清理：原始事件自接收起 30 天後刪除；執行紀錄、事件去重紀錄及通知自最後更新或建立起 90 天後清理；發送回執在 90 天後清空。發送動作的雜湊識別碼、狀態及時間可持續保留以防重送，直到刪除工作區資料。流程、帳號憑證及登入帳號目前未設自動到期刪除；條款與隱私告知確認的版本及時間按登入帳號保存，沒有自動到期清理，需在處理登入帳號刪除時一併處理；單純刪除工作區資料不會刪除這些確認紀錄。刪除確認碼與完成狀態亦無自動清理。您可依下述方式請求處理。若服務停止，清理延至下次啟動；已建立加密異地主機外備份並完成隔離還原驗證；自動排程及備份保存輪替尚未完成。工作資料刪除不會立即抹除已存在的備份副本；如需刪除備份中資料，請於請求中一併說明，由營運者核實處理。
密碼重設郵件
當您申請重設密碼時，我們透過 Resend 寄送驗證碼，向其提供收件 Email 與驗證信內容，不提供您的密碼。寄件網域使用東京區域設定，但不代表所有服務資料僅於日本處理；服務供應商可能跨境處理郵件及投遞紀錄。驗證碼與重設憑證各有效10分鐘；伺服器待寄內容以加密方式暫存，寄送成功即移除，失效資料於下次每小時清理移除。防濫用紀錄使用 Email／連線來源的金鑰雜湊，保留一小時後於清理時移除。Resend 的處理另受其 隱私政策規範。
流程分析、標籤與團隊
啟用相關功能時，我們保存工作區內的粉絲雜湊識別碼、您設定的標籤、分流連結、流程各階段及連結點擊請求計數，用於分析與月活躍人數去重；不把確認已追蹤當作新增粉絲。應用程式不另外保存點擊者的 IP 或 User-Agent；連線供應商仍可能處理網路紀錄。漏斗與分流快照保存90天，標籤自最後更新保存90天，月活躍去重紀錄約保存100天（依月份清理）。追蹤連結目的網址及雜湊識別持續保留至工作區資料刪除，90天後停止計數，以維持舊連結可用。團隊成員可存取同工作區流程及分析；擁有者管理成員，邀請24小時到期。
安全及必要儲存
Instagram 密碼只應輸入官方頁面，我們不索取。多用戶服務以 AES-GCM 加密權杖及原始事件，並以工作區識別資料隔離；這不表示所有欄位均已加密。帳號顯示名稱及頭像網址另在伺服器記憶體快取，讀取效期為 5 分鐘，不另外寫入資料庫；逾期項目不再供新查詢使用，並在後續清理或程式停止時移除。顯示頭像時，您的瀏覽器直接向 Meta 的 cdninstagram.com 或 fbcdn.net 網域載入圖片，該服務會收到網路請求所需的 IP 位址及瀏覽器資訊；本服務設定不傳送來源頁網址。登入 Cookie 用於維持登入，瀏覽器本機儲存記住語言偏好。加密無法保證在主機或金鑰被取得時仍完全安全。
您的權利與選擇
您可請求查詢、閱覽、複製、補充、更正、停止蒐集處理利用或刪除資料。請寄信至聯絡信箱，說明帳號及請求範圍；我們會合理核實身分，依適用法定期限處理，不要求密碼或權杖。拒絕提供登入資料將無法建立帳號；不授予 Instagram 權限則無法使用相關自動回覆功能。粉絲可不參與互動或聯絡帳號經營者及我們提出請求。使用本工具的經營者仍應向粉絲提供適當告知並確保合法處理。
Creem 測試結帳
僅在您選擇測試結帳時，Creem 測試環境可能處理結帳所需的 Email、方案、測試訂閱與交易識別資料；本服務保存測試付款意圖、同意及狀態以核對測試流程。目前未啟用真實扣款，也不將測試事件追溯收費。請勿在測試環境提供真實付款卡資料。Creem 可能依其服務跨境處理資料；正式收費前將補充實際帳務留存與付款告知。
CommenOK · 2026-09-30-operator-v2
Privacy Policy
Who handles your data
CommenOK is operated by 酷礦國際餐飲有限公司, Taiwan business registration number 50805158. Contact tc-peat@outlook.com for privacy and service requests. This policy covers workspace users and fans who comment or interact with connected Instagram accounts.
Sources, categories and purposes
You provide your login email, password and workflow settings. Passwords are stored as salted hashes. Authorized Meta APIs and webhooks provide Instagram account IDs, usernames, display names (name), profile image URLs (profile_picture_url), access tokens, posts, comments, messages, interaction events, follow status and sending responses. We also process login sessions, the version and timestamp of terms and privacy acknowledgements, deletion-request status and operational records. These support sign-in, account connections, enabled reply workflows, follow checks, duplicate prevention, support and security. We do not sell personal data.
Processing, locations and recipients
The production website commenok.com processes and stores application data on a DigitalOcean server in Singapore and receives connections and events over HTTPS. Cloudflare provides domain registration and DNS resolution; its website proxy and WAF are not currently enabled. Meta, DigitalOcean, Cloudflare and the email provider may process relevant data across borders under their respective services. A Singapore server does not mean all provider data is processed only in Singapore. Relevant data is accessed by personnel and providers necessary to operate the service, and competent authorities where legally required. Material changes to processing locations or providers will be disclosed.
Retention
Cleanup runs at startup and hourly while the service is running. Raw events are removed after 30 days from receipt. Runs, event deduplication records and notices are cleaned after 90 days from their last update or creation; sending responses are cleared after 90 days. Hashed action identifiers, status and timestamps may remain to prevent duplicate sends until workspace data is deleted. Workflows, account credentials and login accounts currently have no automatic deletion deadline. Terms and privacy acknowledgement versions and timestamps are retained per login account without automatic expiry and must be handled when the login account is deleted. Deleting workspace data alone does not remove these acknowledgement records. Deletion confirmation codes and completion status also have no automatic cleanup. You may request action as described below. Offline cleanup resumes at the next startup. Encrypted off-host backups and an isolated restore check have been completed; automated scheduling and backup retention rotation are not yet implemented. Deleting active data does not immediately erase existing backup copies. Include backup data in a deletion request so the operator can verify and handle it.
Password recovery emails
When you request a password reset, Resend receives your email address and verification message, but not your password. The sending domain uses the Tokyo region; this does not guarantee that all service data stays in Japan. Providers may process messages and delivery logs across borders. Verification codes and reset credentials each expire after 10 minutes. Server-queued message content is encrypted, removed after successful submission, and otherwise removed by hourly cleanup after expiry. Abuse prevention stores keyed hashes of email and connection source, eligible for cleanup after one hour. See the Resend Privacy Policy for its handling.
Workflow analytics, tags and teams
When enabled, we store workspace-scoped hashed fan identifiers, your tags, routed links, workflow stages and link request counts for analytics and monthly contact deduplication. A verified follow is not classified as a newly acquired follower. The application does not separately store a clicker’s IP address or User-Agent; network providers may still process connection logs. Funnel data and route snapshots are retained for 90 days, tags for 90 days after update, and monthly deduplication records for approximately 100 days, rounded by month. Tracked destinations and hashed identifiers remain until workspace deletion so old links continue working; counting stops after 90 days. Team members can access workflows and analytics in the same workspace. Owners manage membership and invitations expire after 24 hours.
Security and essential storage
Enter your Instagram password only on the official site; we do not request it. The multi-user service encrypts tokens and raw events with AES-GCM and separates data by workspace. This does not mean every database field is encrypted. Display names and avatar URLs are also cached in server memory with a five-minute freshness period and are not separately written to the database. Expired entries are no longer served for new queries and are removed during later cleanup or process shutdown. To display an avatar, your browser requests the image directly from Meta’s cdninstagram.com or fbcdn.net domains, which receive the IP address and browser information needed for the request. The service suppresses the referring page URL. A session cookie maintains sign-in, and local browser storage remembers your language. Encryption cannot guarantee protection if the host or encryption keys are compromised.
Your rights and choices
You may request access, copies, corrections, supplementation, cessation of collection, processing or use, or deletion. Email the contact address with the account and scope of your request. We will reasonably verify identity and respond within applicable statutory periods without requesting passwords or tokens. Without login details an account cannot be created; without Instagram permissions the relevant automation cannot operate. Fans may choose not to interact and may contact the account operator or us about their data. Workspace operators remain responsible for appropriate notices and lawful handling of their fans’ data.
Creem test checkout
Only when you choose test checkout, Creem’s test environment may process the email, plan, test subscription and transaction identifiers needed for checkout. We retain test payment intents, consent and status to verify the test flow. Real collection is not enabled and test events are not billed retroactively. Do not provide real payment-card details in the test environment. Creem may process data across borders under its service. Actual billing retention and payment disclosures will be completed before live charging.