<think>

Let me analyze the changes:

1. PrivacyPolicyScreen.tsx:
   - Updated LAST_UPDATED date from '2026年4月4日' to '2026年4月28日'
   - Added detailed third-party SDK disclosure section:
     - Added JPush (极光推送) with provider details, purpose, collected data, and privacy policy link
     - Added Expo推送服务 with provider details, purpose, and collected data

2. TermsOfServiceScreen.tsx:
   - Updated LAST_UPDATED date from '2026年4月4日' to '2026年4月28日'
   - Added section 6.4 about third-party SDKs (JPush) and reference to privacy policy

These changes are:
- Documentation/legal text updates
- Related to privacy and terms screens
- Adding third-party SDK disclosure (JPush)

The primary type should be: docs (documentation changes)
Scope could be: profile or privacy/terms related
Description should focus on the third-party SDK disclosure update

This is different from the previous commit which was about notification integration. This commit is about updating legal/policy documents to disclose third-party SDKs.

Let me craft a conventional commit message:

type: docs
scope: profile or privacy
description: update privacy policy and terms to disclose third-party SDKs

Body could explain:
- Added JPush SDK disclosure with provider info, data collected, privacy policy link
- Added Expo push service disclosure
- Updated terms of service to reference third-party SDKs
- Updated last update dates

Breaking changes: None

Footer: Could reference related issue if any, but none provided.

Let me write the commit message:

```
docs(privacy): update privacy policy and terms to disclose third-party SDKs

- Add JPush SDK disclosure with provider details, data collection purposes, and privacy policy link
- Add Expo push service disclosure with provider and collected data information
- Update terms of service to reference third-party SDK usage

- Update document dates to April 28, 2026
```

I need to verify this is sufficiently distinct from the previous commit. The last one was "feat(notification): integrate expo-notifications..." so using "docs(privacy)" with this specific focus on third-party SDK disclosure makes sense and clearly differs from the prior notification feature work.

</think>
docs(privacy): update privacy policy and terms to disclose third-party SDKs

- Add JPush SDK disclosure with provider details, data collection purposes, and privacy policy link
- Add Expo push service disclosure with provider and collected data information
- Update terms of service to reference third-party SDK usage per privacy policy
- Update document dates to April 28, 2026

src/screens/profile/PrivacyPolicyScreen.tsx

@@ -28,7 +28,7 @@ const THEME_COLORS = {
 };
 
 // 政策最后更新日期
-const LAST_UPDATED = '2026年4月4日';
+const LAST_UPDATED = '2026年4月28日';
 
 // 隐私政策内容
 const PRIVACY_SECTIONS = [
@@ -157,7 +157,16 @@ const PRIVACY_SECTIONS = [
     title: '七、第三方SDK目录',
     content: `为了保障App的稳定运行或实现特定功能，我们可能接入第三方SDK。截至本隐私政策更新之日，我们主要使用以下服务：
 
-• Expo推送服务：用于消息推送功能。可能收集设备标识符、设备信息。
+1. 极光推送（JPush）
+• 提供方：深圳市和讯华谷信息技术有限公司
+• 使用目的：实现消息推送功能，向您的设备发送通知提醒
+• 收集的个人信息：设备标识符（Registration ID、Android ID、IMEI、OAID）、设备型号、操作系统版本、IP地址、应用列表信息
+• 隐私政策：https://www.jiguang.cn/privacy
+
+2. Expo推送服务
+• 提供方：Expo（650 Industries, Inc.）
+• 使用目的：辅助消息推送通道管理
+• 收集的个人信息：设备推送令牌（Push Token）、设备标识符
 
 如您后续接入其他第三方SDK（如微信登录、分享等功能），我们将在本章节更新相关说明，并告知您对应SDK收集的信息类型和用途。更新后的SDK目录将在应用内公布，请以最新版本为准。`,
   },

src/screens/profile/TermsOfServiceScreen.tsx

@@ -28,7 +28,7 @@ const THEME_COLORS = {
 };
 
 // 协议最后更新日期
-const LAST_UPDATED = '2026年4月4日';
+const LAST_UPDATED = '2026年4月28日';
 
 // 协议条款内容
 const TERMS_SECTIONS = [
@@ -99,7 +99,9 @@ const TERMS_SECTIONS = [
 
 6.2 您同意我们可以按照《隐私政策》的规定收集、使用、存储和分享您的个人信息。
 
-6.3 我们将采取合理的技术和管理措施保护您的个人信息安全，但不对因不可抗力或第三方原因导致的信息泄露承担责任。`,
+6.3 我们将采取合理的技术和管理措施保护您的个人信息安全，但不对因不可抗力或第三方原因导致的信息泄露承担责任。
+
+6.4 本应用集成了极光推送（JPush）等第三方SDK，用于实现消息推送等功能。第三方SDK可能会收集和处理您的设备标识符、设备信息等必要数据。具体的第三方SDK信息请参见《隐私政策》中的"第三方SDK目录"章节。`,
   },
   {
     title: '七、免责声明',