私隱政策 / Privacy Policy

中文

1. 本政策涵蓋甚麼

Inside Health Limited（「我們」）營運 Inside Health／深入看健康網站 insidehealth.io，並使用 Inside Health Publisher 及相關內部編採工具管理自有內容和處理新聞來源。本政策說明這些服務涉及的個人資料如何被收集、使用、保存及處理。

公眾網站提供內容、搜尋和健康計算工具。內部編採工具供我們自己業務使用；公眾瀏覽網站不需要連接 Facebook、Instagram 或 Threads 帳號。

私隱查詢、資料查閱、更正或刪除要求，請電郵至 [email protected]。

2. 我們處理哪些資料及用途

請不要向我們寄送完整病歷、帳號密碼、驗證碼或 API token。網站計算工具不能提供診斷或治療；使用時仍有一般網頁及分析資料處理，不能將工具頁視作保密醫療服務。

3. Cookie、分析與第三方內容

網站目前載入 Google Analytics 和 Cloudflare 的網站分析服務，用以了解流量和使用情況；亦使用第三方字型資源，部分頁面可嵌入 YouTube 影片。這些服務可能收到你裝置發出的請求及相關網絡、裝置和使用資訊。採用 YouTube 私隱加強嵌入模式不代表完全沒有資料傳輸。

你可透過瀏覽器限制或刪除 cookie，或限制第三方內容；部分功能或分析可能因此受影響。這不會自動刪除已保存的資料。網站讀者不應假設分析只會在另外按下同意按鈕後才開始。

第三方服務的處理亦受其政策規管：Google／YouTube、Cloudflare、Meta。

4. Meta 及 Threads 接駁

Inside Health Publisher 是我們現有的 Meta App。功能可用範圍取決於已取得的權限、平台審批及帳號授權。Threads 來源讀取目前仍在測試，並未提供可讀取任意公開帳號的完整服務；本政策本身不會擴大平台權限。

我們會按適用的平台條款處理 API 資料，不會把 API 存取當作素材再發布授權。撤銷帳號連接與刪除已保存的副本是兩件事；刪除要求請參閱資料刪除說明。

5. 接收資料的對象及境外處理

按上述目的，有需要的內部工作人員，以及提供網站託管、網絡安全、分析、電郵、儲存或內容處理的供應商可能接收資料。新聞文字研究亦可能使用 AIHubMix 及其路由的模型服務；這不表示所有社交 API 資料都可交給這些服務。API 資料交由外部 AI 處理前，必須先確認平台限制及供應商安排允許相關用途。

供應商可能在香港以外處理資料。我們會就受委託處理的個人資料採取適當的合約或其他保障安排。只有在有適用依據且實際需要時，才會為法律要求、處理爭議或保障權利而披露資料。我們不會出售你的個人資料，亦不會將查詢內容用於無關的直接促銷。

6. 保存、保安與刪除

我們只會在達到上述目的所需期間內保存可識別個人的資料，並考慮平台的刪除要求及適用法律。保存期限按資料用途而定，包括查詢是否完成、連接是否仍需要、素材是否仍有編採用途，以及是否確有法律或爭議處理需要；不會只因有編採或操作紀錄而無限期保存全部原始個人資料。

我們會採取與風險相稱的存取限制及其他實際可行的保安措施。資料傳送或儲存仍有風險，本政策不作零風險保證。

經核實的刪除要求會涵蓋我們控制的相關使用中副本及可識別個人的衍生資料。備份、快取及供應商副本亦須按適用要求處理；不能將備份作為繼續一般使用已刪除資料的理由。實際範圍及任何合理、適用的保留理由會在回覆中交代。

7. 你的選擇及權利

你可要求查閱或更正我們持有的個人資料，並可提出刪除、停止特定處理或撤銷連接的要求。我們可能需要合理的資料以核實身份及定位記錄，並會按適用法律及平台要求處理。若無法全部照辦，會說明原因；本政策不將任何特定法律豁免自動套用於所有新聞資料。

一般私隱查詢及刪除要求的步驟載於資料刪除說明。外部平台、其他發布者及獨立第三方控制的資料，須另向相關方提出要求。

8. 政策更新

若資料用途、功能或供應商安排有重大變動，我們會更新本頁，並在需要時另行通知或取得所需同意。單純繼續瀏覽不會自動授權未披露的新用途。

English

1. Operator and scope

Inside Health Limited operates the Inside Health website at insidehealth.io and uses Inside Health Publisher and related internal editorial tools for its own content operations and source research. This policy covers personal data involved in those services. Public visitors do not need to connect a Facebook, Instagram or Threads account to read the website.

Contact [email protected] for privacy enquiries and requests to access, correct or delete personal data.

2. Data and purposes

We and our service providers may process page and search URLs, visit times, referrers, browser/device information, network identifiers such as IP addresses, and cookies or similar identifiers to deliver and secure the website, measure use and improve performance. Search terms appear in search URLs; do not enter private medical information or identifying details into search.

When you contact us, we process the contact details, messages, attachments and correspondence you provide to respond, investigate requests and maintain necessary handling records. Providing general enquiry information is voluntary, but missing contact or record-identification details may prevent us from completing a request.

For connected accounts, we process account identifiers, connection state, access credentials, content, media and relevant interaction information within the actual permission scope for authorized content management, publishing or analysis. Credentials are not published or exposed to ordinary website readers.

Editorial source tracing involves specific source accounts, post links, text, dates, images/videos and provenance to assess events, attribution and context. Access to a public post or file does not establish original authorship or permission to reuse it. Internal tools also process login sessions and necessary security and operation records.

Do not send passwords, verification codes, tokens or complete medical records. Website tools are not confidential clinical services and are still subject to ordinary web and analytics processing.

3. Cookies and external services

The website currently loads Google Analytics and Cloudflare analytics, uses external font resources and may embed YouTube videos. These services can receive network, device and usage information. YouTube privacy-enhanced embedding does not mean that no data is transmitted.

Browser settings can restrict or delete cookies or block external content, which may affect functionality. These controls do not delete previously retained data. Do not assume analytics waits for an additional consent-button click on this website. See the policies of Google/YouTube, Cloudflare and Meta.

4. Meta and Threads

Inside Health Publisher is our existing Meta app. Availability depends on permissions, platform approval and account authorization. Threads source reading remains in testing; general public-account access is not an established service. This policy does not expand API access or grant rights to republish creator material. Disconnecting an account and deleting retained copies are separate actions; see Data Deletion.

5. Recipients and processing locations

Relevant internal personnel and hosting, security, analytics, email, storage and content-processing providers may receive data for the purposes described above. Editorial text research may use AIHubMix and routed model services. This is not permission to send all social API data to those services: applicable platform restrictions and provider arrangements must permit the particular processing first.

Providers may process data outside Hong Kong. We will use appropriate contractual or other safeguards for processors handling personal data on our behalf. Disclosures for legal requirements, disputes or protection of rights must have an applicable basis and be necessary. We will not sell your personal data or use enquiry content for unrelated direct marketing.

6. Retention, security and deletion

Identifiable data is retained only as necessary for the stated purposes, subject to applicable law and platform deletion requirements. We consider enquiry resolution, continuing connection needs, editorial necessity and specific legal/dispute obligations; an editorial or operation record is not a reason to keep all underlying personal data indefinitely.

We will apply risk-appropriate access restrictions and other practicable safeguards, without guaranteeing risk-free transmission or storage. Verified deletion requests cover relevant active copies and identifiable derivatives under our control. Backups, caches and provider copies must also be handled under applicable requirements, not used to continue ordinary use of deleted information. Our response will explain scope and any applicable reason for retention.

7. Requests and updates

You may request access to or correction of your personal data and ask for deletion, withdrawal of a connection or cessation of particular processing. Reasonable identity and record-location checks may be necessary. Applicable law and platform requirements govern handling; we will explain any refusal or limitation rather than automatically claiming a blanket journalism exemption.

See Data Deletion for request steps. Data controlled independently by platforms or other publishers must be addressed with those parties. We will update this policy for material changes and provide notice or obtain consent where required; continued browsing alone does not authorize an undisclosed new purpose.