平台私隱政策及資料刪除

1. 營運者與適用範圍 / Operator and scope

Play Lazy Limited 營運 WhatsApp Center，供獲授權網站及 App 共用一個 WhatsApp Business 發信號碼；BNI 是第一個預定接入的 App，各分會毋須另接自己的號碼。Center 的正式共存接駁及發送尚未啟用，BNI 亦尚未接入 Center。

Play Lazy Limited operates WhatsApp Center, designed for authorised websites and apps to share one WhatsApp Business sender. BNI is the first intended client; individual chapters do not need separate numbers. Production coexistence onboarding and sending in Center are not yet enabled, and BNI has not yet been integrated as a Center client.

Meta App 目前顯示為 BNI Chapter Platform。本政策涵蓋 Center 與仍保留的 BNI Meta／WhatsApp 接駁功能及事件接收服務。BNI 原有分會接駁介面尚未移除。來源 App／分會的會員、報名、付款及活動資料，另受該 App／分會的私隱政策規管。

The Meta app is currently named BNI Chapter Platform. This policy covers Center and the retained BNI Meta/WhatsApp connection and webhook services. The existing chapter-specific connection interface has not been removed. Membership, registration, payment and event records in a source app or chapter are also governed by that app's or chapter's privacy policy.

2. 處理的資料及用途 / Data and purposes

通知請求包括收件電話、範本名稱及語言、通知參數，以及來源 App 提供的收件同意確認，用於核對權限及處理指定通知。發送紀錄包括來源 App、請求與訊息識別碼、內容雜湊、狀態及時間，用於防止重複請求、追蹤進度及處理故障。Center 依賴來源 App 確認同意，並非獨立收集所有收件同意證明。

Notification requests include the recipient's number, template name and language, notification parameters and the source app's confirmation of consent. These are used to authorise and process requested notifications. Records include the source app, request and message IDs, content hashes, status and timestamps for duplicate prevention, status tracking and troubleshooting. Center relies on consent confirmation from the source app rather than independently collecting all evidence of consent.

接駁資料包括 WhatsApp Business 帳戶及電話識別資料、發信號碼、授權憑證及期限、接駁與同步狀態。既有 BNI 整合亦處理相關管理員及分會識別資料、範本及通知內容。管理及安全資料包括帳戶名稱、密碼雜湊、登入工作階段、登入限流及伺服器存取紀錄。

Connection data includes WhatsApp Business account and phone identifiers, the sending number, credentials and expiry, and connection/synchronisation status. The retained BNI integration also processes relevant administrator and chapter identifiers, templates and notification content. Administration and security data includes usernames, password hashes, sessions, login rate-limit data and server access logs.

3. 手機 App 共存及 webhook / Coexistence and webhooks

共存流程旨在保留現有 WhatsApp Business App 號碼。Meta 可能傳送聊天、聯絡人、歷史訊息或媒體資訊；授權流程可讓號碼持有人選擇不分享聊天記錄。BNI 事件接收服務驗證簽名並完成原有處理後，將事件轉交同一主機的 Center。轉交及驗證期間會處理事件內容。

The coexistence flow is intended to retain the existing WhatsApp Business App number. Meta may deliver chats, contacts, history or media information; the authorisation flow allows the number holder to decline history sharing. The BNI webhook validates signatures, performs its existing processing and forwards events to Center on the same host. Event content is processed during validation and forwarding.

現有程式不保存 webhook 中的聯絡人名單、歷史訊息正文或媒體，亦不建立聊天收件匣；只保存接駁、整體同步進度、生命週期及必要發送狀態。這不代表手機 Business App、來源 App 或 Meta 不保存其自身資料。

The current code does not retain webhook contact lists, history message bodies or media, and does not create a chat inbox. It retains connection, aggregate synchronisation, lifecycle and necessary delivery-status information. This does not mean that the Business App, source apps or Meta do not retain their own data.

4. 接收者、存取及 Cookie / Recipients, access and cookies

服務由 AWS 新加坡主機託管；發送通知時，必要的收件電話及內容會交予 Meta／WhatsApp，資料可能在香港以外處理。憑證存放於伺服器。Center 平台管理員可查看跨 App 管理紀錄，各 API client 只可查閱自己的通知紀錄；既有 BNI 接駁則按分會權限存取。平台不出售 WhatsApp 授權資料或以其作廣告用途。Meta／WhatsApp 的獨立處理受其政策規管。

The service is hosted on AWS in Singapore. Necessary recipient numbers and content are sent to Meta/WhatsApp when sending notifications, and data may be processed outside Hong Kong. Credentials are stored server-side. Center platform administrators can view cross-app management records; API clients can only retrieve their own notification records. The retained BNI integration uses chapter-based permissions. We do not sell WhatsApp authorisation data or use it for advertising. Meta/WhatsApp's independent processing is governed by its policies.

Center 管理後台使用必要的工作階段 Cookie 維持登入及保護操作；Center 公開首頁沒有分析或廣告追蹤程式。本段不代替來源 App 的 Cookie 說明。

Center administration uses necessary session cookies for login and operation protection. The public Center homepage has no analytics or advertising trackers. This does not replace the source apps' cookie disclosures.

5. 保留方式 / Retention

Center 排隊中的收件電話及通知內容暫存於私密資料庫。程式嘗試發送後，或將逾時發送標記為結果未明、將不再獲准的項目取消時，會清除該列原始通知內容，保留識別資料、雜湊及狀態。來源 App 和備份不會因該列清除而同步刪除。

Queued recipient numbers and notification content are temporarily held in Center's private database. The code clears a record's original notification payload after a send attempt, when marking a stale sending attempt as unknown, or when cancelling an item that is no longer authorised. Identifiers, hashes and status remain. This does not simultaneously delete source-app data or backups.

Center 在處理 webhook 時清理超過七天的暫存發送狀態事件；這不是全部通知紀錄的七天刪除期限。目前未有涵蓋通知紀錄、接駁資料、登入資料、伺服器日誌及備份的統一自動刪除期限。查閱、更正及刪除要求由人員核實及處理，並非即時自動刪除；目前沒有固定完成時限承諾。

When processing webhooks, Center removes temporary delivery-status events older than seven days; this is not a seven-day deletion period for all notification records. There is currently no uniform automatic deletion period covering notification records, connection data, login data, server logs and backups. Access, correction and deletion requests are verified and handled manually, not instantly or automatically; no fixed completion time is currently promised.

6. 查詢、刪除及撤銷授權 / Requests, deletion and revocation

1. 電郵 whatsphone@gmail.com，主旨註明「WhatsApp Center／BNI Chapter Platform 資料查詢或刪除」。提供來源 App／分會名稱、大約通知日期、要求範圍，以及 request/message ID（如有）。首次聯絡毋須附身份證或完整聊天；請勿傳送密碼、Token、App Secret 或 client key。
2. 我們會核實您對資料或帳戶的權限，按需要索取最少額外資料定位紀錄，再回覆處理結果，以及任何需要保留的資料與原因。涉及來源 App／分會資料時，會協調該 App／分會處理。
3. 清除 Center 資料不代表同時清除來源 App、備份、Meta 或手機資料。要求涉及備份時，我們會說明可處理範圍。
4. 具權限的帳戶持有人可透過 Meta 商業整合／已連接應用程式設定撤銷 BNI Chapter Platform 的存取。撤銷授權與刪除資料屬不同操作，亦可能中斷共用號碼對所有接入 App 的服務，應先協調。一般收件人要求刪除資料，毋須刪除手機 WhatsApp Business 帳戶。