Privacy Policy

Effective date: 2026-01-19 | Last updated: 2026-03-10

WeLiao (韦聊) ("we", "us", or "our") is developed and operated by Nanjing Lingdong Century Media Co., Ltd. (南京领动世纪传媒有限公司). We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our mobile application ("App").

Developer Information:
App Name: WeLiao (韦聊)
Developer: Nanjing Lingdong Century Media Co., Ltd. (南京领动世纪传媒有限公司)
Contact Email: vliaochat@gmail.com

                Key Points:
                We do NOT sell your personal information
Messages are transmitted via the Matrix protocol
Most data is stored locally on your device
You can delete your account and data at any time
App Name: WeLiao (韦聊) | Developer: Nanjing Lingdong Century Media Co., Ltd.

            

1. Information We Collect

1.1 Account Information

Matrix user ID (username) and authentication credentials
Phone number (for registration and account recovery)
Profile information you provide (display name, avatar image)

1.2 Communications Data

Text messages you send and receive
Media content (photos, videos, voice messages) you share
Message metadata (timestamps, read receipts, delivery status)
Group chat information (group names, member lists)

1.3 Device Information

Device type and model
Operating system and version
App version
Device language settings
Network connection type (WiFi/cellular)
Push notification token — APNs token on iOS; on Android, the applicable manufacturer channel token (FCM, MiPush, HMS, OPush, or VPush) based on your device brand — used solely to deliver notifications to your device

1.4 Media and Files

Photos and videos you choose to share (accessed only when you select them)
Voice recordings you create for voice messages
QR codes you scan (processed locally on device)

2. Device Permissions

Our App requests the following permissions, which you can manage in your device settings:

Permission	Purpose	When Used
Camera	Take photos and videos to share in chats; scan QR codes	Only when you tap the camera button or scan feature
Microphone	Record voice messages; record videos with audio	Only when you hold the voice message button or record video
Photo Library (Read)	Select existing photos and videos to share	Only when you choose to pick media from your library
Photo Library (Write)	Save received media to your device	Only when you choose to save an image or video
Notifications	Receive message notifications when the app is in the background or closed; display incoming call alerts	When new messages arrive or an incoming call is received

Note: You can deny any permission, but some features may not work without them. You can change permissions at any time in your device's Settings. Revoking the Notifications permission will stop all push notifications but will not affect in-app messaging.

2.1 Background/Silent State Data Processing

As an instant messaging app, limited data processing activities occur in the background or silent state to ensure you receive messages and call notifications promptly. The following describes each activity in detail:

Background Activity	Data Involved	Purpose	Processing Method
Receiving Push Notifications	Push token, notification payload (sender name, message preview summary, call signal)	Notify you of new messages or incoming calls when the app is not open	Handled by the OS vendor push channel (APNs/FCM/MiPush/HMS/OPush/VPush); our app code does not actively run during this process and does not collect any additional personal information
Incoming Call Wake-up	Call push signal (caller identifier, room ID)	Display the incoming call screen when a call push notification is received in the background	The system call screen is triggered via push notification; no background audio recording, no location access, no contacts reading occurs
Message Sync	Matrix sync request (incremental messages, read receipts, presence status)	Fetch new messages received during offline period when you reopen the app	Executed only when the app returns to the foreground — not a true background activity; communicates with the Matrix server via HTTPS/TLS encryption

This App does NOT perform the following activities in the background/silent state:

Does not collect GPS location data or perform geofencing in the background
Does not scan, read, or upload your photo library, images, or videos in the background
Does not read your contacts, call logs, SMS, or calendar in the background
Does not collect device identifiers (such as IMEI, IMSI, MAC address, etc.) in the background
Does not scan or collect installed app lists in the background
Does not perform user behavior tracking, profiling, or ad targeting in the background
Does not record audio or video in the background

3. Third-Party Services and SDKs

Our App uses the following third-party services and software development kits (SDKs). We require third-party SDK providers to protect your personal information in accordance with applicable laws.

3.0 Personal Sensitive Information Collection Statement

In accordance with applicable laws and regulations, the following table details, item by item, whether this App and its integrated third-party SDKs collect each type of personal sensitive information, including the associated SDK/function, purpose, and processing method:

Personal Information Type	Collected?	Associated SDK/Function	Purpose	Processing Method	Involved SDKs
IMEI (International Mobile Equipment Identity)	Not collected	—	—	—	—
IMSI (International Mobile Subscriber Identity)	Not collected	—	—	—	—
Device MAC Address	May be accessed during voice/video call establishment	flutter_webrtc (WebRTC SDK)	WebRTC ICE candidate gathering requires network interface enumeration, which may expose the device MAC address on Android 9 and below	Used solely for establishing peer-to-peer call connections; not stored, uploaded, or used for any other purpose; on Android 10+, the system returns a randomized MAC address	flutter_webrtc
SUPI	Not collected	—	—	—	—
SUCI	Not collected	—	—	—	—
Installed App List	Not collected	—	—	—	—
Location (GPS positioning)	Not collected	—	—	—	—
Contacts/Address Book	Not collected	—	—	—	—
Call Logs	Not collected	—	—	—	—
Calendar	Not collected	—	—	—	—
SMS	Not collected	—	—	—	—
Phone Number	Only when voluntarily entered by user during registration/login	Ronglian Cloud (server-side REST API, not a client-side SDK)	Send SMS verification codes for registration, login, and password reset	After user input, transmitted from our server to Ronglian Cloud SMS gateway via HTTPS encrypted API; the phone number is never read automatically from the device	Ronglian Cloud
Photos/Images	Only when user actively chooses to send	Matrix SDK	Send image messages in chat	After user selects from gallery, uploaded to Matrix server via HTTPS/TLS encryption for delivery to recipient; photos are never collected in the background	Matrix SDK
Audio/Video	Only when user actively initiates	Matrix SDK (voice/video messages), flutter_webrtc (audio/video calls)	Send voice messages, video messages; make voice and video calls	After user actively records or initiates a call, voice/video messages are uploaded to Matrix server via HTTPS/TLS encryption; call audio/video streams are transmitted peer-to-peer via DTLS/SRTP encryption; audio/video is never recorded or collected in the background	Matrix SDK, flutter_webrtc

Declaration: For personal information types marked as "Not collected" in the above table, neither this App nor any of its integrated third-party SDKs will collect, store, or transmit such information during operation. For types marked as "Only when user actively initiates/chooses", access occurs only when the user explicitly triggers the corresponding function, and no background collection takes place.

3.0.1 Common "Not Collected" Declaration — Applicable to SDKs that do not collect any of the 14 sensitive information types

The following SDKs do not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video) during operation. This declaration applies to:

3.2 Google ML Kit (Barcode Scanning)
3.3 SDWebImage
3.4 SQLite / Drift Database
3.5 Flutter Secure Storage
3.6 Dio (HTTP Client)
3.8 cached_network_image
3.9 go_router
3.10 flutter_screenutil
3.11 phosphor_flutter
3.13 Apple Push Notification Service (APNs)
3.14 Firebase Cloud Messaging (FCM)
3.15 Xiaomi Push (MiPush)
3.16 Huawei Push Kit (HMS Push)
3.17 OPPO PUSH Client SDK (com.heytap.msp)
3.18 vivo Push (VPush)
3.19 Honor Push SDK (com.hihonor.push)
3.20 Huawei Performance Acceleration Library (com.huawei.hms.stats)

Information Type	Collected?	Purpose	Method	Scope
IMEI	Not collected	—	—	—
IMSI	Not collected	—	—	—
Device MAC Address	Not collected	—	—	—
SUPI	Not collected	—	—	—
SUCI	Not collected	—	—	—
Installed App List	Not collected	—	—	—
Location	Not collected	—	—	—
Contacts	Not collected	—	—	—
Call Logs	Not collected	—	—	—
Calendar	Not collected	—	—	—
SMS	Not collected	—	—	—
Phone Number	Not collected	—	—	—
Photos/Images	Not collected	—	—	—
Audio/Video	Not collected	—	—	—

Note: The push notification SDKs listed above (APNs, FCM, MiPush, HMS Push, OPush, VPush, Honor Push) may collect device identifiers such as OAID, Android ID, or device tokens for the sole purpose of delivering push notifications. These identifiers are not part of the 14 sensitive information types listed above. See each SDK's individual section below for details on purpose, method, and scope of these identifiers.

3.1 Matrix Protocol (matrix.org)

Purpose: Core messaging infrastructure for sending and receiving messages
Data processed: User ID, messages, media files, contact lists
Data location: Matrix homeserver (may be located outside your country)
Privacy Policy: https://matrix.org/legal/privacy-notice

                Sensitive Information Declaration:
                
                    Information TypeCollected?PurposeMethodScope
IMEINot collected———
IMSINot collected———
Device MAC AddressNot collected———
SUPINot collected———
SUCINot collected———
Installed App ListNot collected———
LocationNot collected———
ContactsNot collected———
Call LogsNot collected———
CalendarNot collected———
SMSNot collected———
Phone NumberNot collected———
Photos/ImagesCollected only when user actively sendsSend image messages in chatUser selects from gallery; uploaded to Matrix server via HTTPS/TLS encryptionOnly images actively selected by the user; no background scanning or collection
Audio/VideoCollected only when user actively initiatesSend voice/video messages; make voice and video callsUser actively records or initiates a call; voice/video messages uploaded to Matrix server via HTTPS/TLS; call streams transmitted peer-to-peer via DTLS/SRTPOnly during active recording or calls initiated by the user; no background recording or collection

            

3.2 Google ML Kit (Barcode Scanning)

Purpose: QR code scanning for adding friends and joining groups
Personal information collected:
- Camera images: processed locally on device only, never uploaded to any server
- SDK diagnostic data (collected automatically): per-installation identifier (identifies the app installation instance, not the user), device information (manufacturer, model, OS version, available ML hardware accelerators), application information (package name, version), performance metrics (processing latency), API configuration (image format, resolution), feature events (initialization, detection events)
Processing method: Image data is processed entirely on-device; diagnostic/analytics data is transmitted to Google servers via HTTPS encryption. Google does not share this data with third parties
Privacy Policy: https://developers.google.com/ml-kit/terms

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). Camera images are processed entirely on-device and never uploaded. The SDK only collects anonymous installation identifiers and device diagnostic data for performance optimization. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.3 SDWebImage

Purpose: Efficient image loading and caching
Data processed: Image URLs and cached images
Data location: Local device storage only

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.4 SQLite / Drift Database

Purpose: Local storage of messages and app data for offline access
Data processed: Messages, contacts, settings
Data location: Local device storage only - not transmitted to any server

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.5 Flutter Secure Storage

Purpose: Secure storage of login credentials and session tokens
Data processed: Authentication tokens, Matrix access tokens
Data location: iOS Keychain / Android Keystore (encrypted, local only)

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.6 Dio (HTTP Client)

Purpose: Network requests to our backend API (registration, profile, group management, version check, etc.)
Data processed: Request payloads including user credentials, profile data, and API responses
Data transmission: All requests are sent over HTTPS/TLS to our servers
SDK source: Open-source Flutter package (dio on pub.dev)

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.7 flutter_webrtc (WebRTC — Voice & Video Calls)

Purpose: Enable peer-to-peer voice and video calls within the app
Personal information collected: Audio and video streams during an active call; IP addresses (local and public IP addresses exposed through ICE candidates during call establishment); STUN/TURN server negotiation data
Processing method: Media streams are encrypted via DTLS/SRTP; direct peer-to-peer (P2P) connection is preferred; when P2P is unavailable, data is relayed through TURN servers; call signaling is handled through the Matrix homeserver
Data location: Media does not pass through our servers when a direct P2P connection is established
SDK source: Open-source Flutter WebRTC package (Hubei Jizhiyun Technology Co., Ltd.)

Sensitive Information Declaration:

Information Type	Collected?	Purpose	Method	Scope
IMEI	Not collected	—	—	—
IMSI	Not collected	—	—	—
Device MAC Address	May be accessed during call establishment	Establish peer-to-peer voice/video call connections	WebRTC ICE candidate gathering enumerates network interfaces, which may expose the device MAC address on Android 9 and below	Only when user actively initiates a voice/video call; not stored, uploaded, or used for any other purpose; on Android 10+, the system returns a randomized MAC address
SUPI	Not collected	—	—	—
SUCI	Not collected	—	—	—
Installed App List	Not collected	—	—	—
Location	Not collected	—	—	—
Contacts	Not collected	—	—	—
Call Logs	Not collected	—	—	—
Calendar	Not collected	—	—	—
SMS	Not collected	—	—	—
Phone Number	Not collected	—	—	—
Photos/Images	Not collected	—	—	—
Audio/Video	Collected only when user actively initiates a call	Real-time voice and video calling	Audio/video streams transmitted peer-to-peer via DTLS/SRTP encryption; when direct connection is unavailable, relayed through TURN server	Only during active calls initiated by the user; streams are not recorded, stored, or uploaded; no background audio/video collection

Additionally, IP addresses (ICE candidates) are collected during call establishment for connection purposes, which are not part of the 14 sensitive information types listed above.

3.8 cached_network_image

Purpose: Efficient loading and local caching of remote images (avatars, shared photos)
Data processed: Image URLs and downloaded image files
Data location: Cached files stored locally on device only
SDK source: Open-source Flutter package

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.9 go_router

Purpose: In-app navigation and deep linking
Data processed: Navigation routes and URL parameters (processed locally, not transmitted)
Data location: Local only
SDK source: Open-source Flutter package

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.10 flutter_screenutil

Purpose: Responsive UI scaling across different screen sizes and densities
Data processed: Device screen dimensions (read-only, not transmitted)
Data location: Local only
SDK source: Open-source Flutter package

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.11 phosphor_flutter (Icon Library)

Purpose: UI icon rendering
Data processed: None — icon assets bundled locally with the app
Data location: Local only
SDK source: Open-source Flutter package

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All data is processed locally on the device. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

3.12 Ronglian Cloud (SMS Verification Service — 容联云)

Purpose: Send SMS verification codes for registration, login, and password reset
Service provider: Beijing Ronglian Yitong Information Technology Co., Ltd. (容联云)
Integration method: Server-side REST API call (not a client-side SDK); your device does not communicate directly with Ronglian's servers
Personal information collected: Phone number, SMS verification code content
Processing method: Your phone number is transmitted from our server to Ronglian's SMS gateway via HTTPS-encrypted REST API; Ronglian then delivers the verification code SMS to your phone
Data location: Ronglian infrastructure (mainland China)
Privacy Policy: https://www.yuntongxun.com/about/privacy

                Sensitive Information Declaration:
                
                    Information TypeCollected?PurposeMethodScope
IMEINot collected———
IMSINot collected———
Device MAC AddressNot collected———
SUPINot collected———
SUCINot collected———
Installed App ListNot collected———
LocationNot collected———
ContactsNot collected———
Call LogsNot collected———
CalendarNot collected———
SMSNot collected———
Phone NumberCollected only when user voluntarily entersSend SMS verification codes for registration, login, and password resetUser manually enters phone number; our server transmits it to Ronglian Cloud SMS gateway via HTTPS-encrypted REST API; the client app does not communicate directly with Ronglian serversOnly the phone number actively entered by the user; the device's SIM phone number is never read automatically
Photos/ImagesNot collected———
Audio/VideoNot collected———

            

3.13 Apple Push Notification Service (APNs)

Purpose: Deliver push notifications (new messages, incoming calls) to iOS devices
Data processed: Device APNs token; notification payload (sender, preview snippet if enabled, call signal)
Data transmission: Token and minimal payload are sent to Apple's APNs servers to route notifications
Data location: Apple infrastructure (United States and other Apple data centers)
Privacy Policy: https://www.apple.com/legal/privacy/

Sensitive Information Declaration: This service does not collect any of the 14 types of personal sensitive information. For the complete item-by-item declaration, see Section 3.0.1.

Device identifiers collected by this SDK:

Identifier	Purpose	Method	Scope
APNs Device Token	Route push notifications to the correct iOS device	Generated by iOS system and transmitted to Apple APNs servers via TLS encryption	One token per app installation; changes if the app is reinstalled; used solely for push notification delivery

3.14 Firebase Cloud Messaging (FCM) — Android (Google devices / standard Android)

Purpose: Deliver push notifications (new messages, incoming calls) to Android devices on Google Play services-enabled ROMs
Personal information collected: FCM registration token (device push identifier), Firebase Installation ID (FID), Android ID, app package name and version, device model, OS version; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Encrypted via HTTPS and transmitted to Google FCM servers
Data location: Google infrastructure (United States and other Google data centers)
Privacy Policy: https://firebase.google.com/support/privacy

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information. For the complete item-by-item declaration, see Section 3.0.1.

Device identifiers collected by this SDK:

Identifier	Purpose	Method	Scope
FCM Registration Token	Route push notifications to the correct Android device	Generated by Google Play Services and transmitted to Google FCM servers via HTTPS	One token per app installation; used solely for push notification delivery
Firebase Installation ID (FID)	Identify the app installation instance for push services	Auto-generated by Firebase SDK; transmitted to Google servers via HTTPS	Per-installation identifier; not linked to user identity; used solely for push service management
Android ID	Device identification for push notification routing	Read from Android system settings; transmitted to Google FCM servers via HTTPS	Per-device identifier reset on factory reset; used solely for push notification delivery; not used for advertising or user profiling

3.15 Xiaomi Push (MiPush) — Xiaomi / Redmi / POCO devices

Purpose: Deliver push notifications to Xiaomi, Redmi, and POCO devices via Xiaomi's system-level push channel
SDK provider: Beijing Xiaomi Mobile Software Co., Ltd.
Personal information collected: OAID (anonymous device identifier), encrypted Android ID, MiPush registration token, app package name and version, device manufacturer, device model, OS version, network type (WiFi/cellular), carrier info, notification bar settings; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Transmitted via encrypted channel to Xiaomi push servers; de-identified processing applied
Data location: Xiaomi infrastructure (mainland China and overseas Xiaomi data centers)
Privacy Policy: https://dev.mi.com/console/doc/detail?pId=1822

Identifier	Purpose	Method	Scope
OAID (Anonymous Device ID)	Device identification for push notification routing	Read via Mobile Security Alliance (MSA) SDK interface; transmitted to Xiaomi push servers via encrypted channel	Anonymous device identifier; resettable by user; used solely for push notification delivery; de-identified processing applied
Encrypted Android ID	Supplementary device identification for push routing	Android ID encrypted before transmission to Xiaomi push servers	Encrypted before transmission; used solely for push delivery; not used for advertising or user profiling
MiPush Registration Token	Route push notifications to the correct device	Generated by MiPush SDK; transmitted to Xiaomi servers via encrypted channel	Per-app-installation token; used solely for push notification delivery

3.16 Huawei Push Kit (HMS) — Huawei devices

Purpose: Deliver push notifications to Huawei devices via Huawei Mobile Services (HMS) push channel (Note: Honor devices use the independent Honor Push SDK — see Section 3.19)
SDK provider: Huawei Technologies Co., Ltd.
Personal information collected: AAID (anonymous application identifier), HMS push token, app package name and version, device model, OS version, network type (WiFi/cellular), country code; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Encrypted via HTTPS and transmitted to Huawei push servers; de-identified processing applied
Data location: Huawei cloud infrastructure (mainland China and overseas Huawei data centers)
Privacy Policy: https://consumer.huawei.com/en/privacy/privacy-policy/

Identifier	Purpose	Method	Scope
AAID (Anonymous App ID)	Application identification for push notification routing	Generated by HMS Core; transmitted to Huawei push servers via HTTPS	Anonymous per-app identifier; resettable by user; used solely for push notification delivery; de-identified processing applied
HMS Push Token	Route push notifications to the correct device	Generated by HMS Push SDK; transmitted to Huawei servers via HTTPS	Per-app-installation token; used solely for push notification delivery

3.17 OPPO PUSH Client SDK (com.heytap.msp) — OPPO / OnePlus / realme devices

Purpose: Deliver push notifications to OPPO, OnePlus, and realme devices via OPPO's system-level push channel
SDK provider: Guangdong Huan Tai Technology Co., Ltd.
Personal information collected: OAID (anonymous device identifier), Android ID, OPush registration token, app package name and version, device model, OS version, network type (WiFi/cellular), IP address, notification bar settings; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Transmitted via encrypted channel to OPPO push servers; de-identified processing applied
Data location: OPPO infrastructure (mainland China and overseas OPPO data centers)
Privacy Policy: https://open.oppomobile.com/new/developmentDoc/info?id=11228

Identifier	Purpose	Method	Scope
OAID (Anonymous Device ID)	Device identification for push notification routing	Read via MSA SDK interface; transmitted to OPPO push servers via encrypted channel	Anonymous device identifier; resettable by user; used solely for push notification delivery; de-identified processing applied
Android ID	Supplementary device identification for push routing	Read from Android system settings; transmitted to OPPO push servers via encrypted channel	Per-device identifier; used solely for push delivery; not used for advertising or user profiling
OPush Registration Token	Route push notifications to the correct device	Generated by OPush SDK; transmitted to OPPO servers via encrypted channel	Per-app-installation token; used solely for push notification delivery
IP Address	Network routing for push notification delivery	Automatically captured during network connection to OPPO push servers	Used solely for push delivery network routing; not stored long-term; not used for location tracking

3.18 vivo Push (VPush) — vivo devices

Purpose: Deliver push notifications to vivo devices via vivo's system-level push channel
SDK provider: Vivo Mobile Communication Co., Ltd.
Personal information collected: OAID (anonymous device identifier), VPush registration token, app package name and version, device model, OS version, network type (WiFi/cellular), notification bar settings; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Transmitted via encrypted channel to vivo push servers; de-identified processing applied
Data location: vivo infrastructure (mainland China and overseas vivo data centers)
Privacy Policy: https://www.vivo.com.cn/about-vivo/privacy-policy

Identifier	Purpose	Method	Scope
OAID (Anonymous Device ID)	Device identification for push notification routing	Read via MSA SDK interface; transmitted to vivo push servers via encrypted channel	Anonymous device identifier; resettable by user; used solely for push notification delivery; de-identified processing applied
VPush Registration Token	Route push notifications to the correct device	Generated by VPush SDK; transmitted to vivo servers via encrypted channel	Per-app-installation token; used solely for push notification delivery

3.19 Honor Push SDK (com.hihonor.push) — Honor devices

Purpose: Deliver push notifications to Honor devices via Honor's independent system-level push channel
SDK provider: Shenzhen Honor Software Technology Co., Ltd.
Personal information collected: OAID (anonymous device identifier), Honor Push registration token, app package name and version, device model, OS version, network type (WiFi/cellular), notification bar settings; notification payload (sender, preview snippet if enabled, call signal)
Processing method: Transmitted via encrypted channel to Honor push servers; de-identified processing applied
Data location: Honor cloud infrastructure (mainland China and overseas Honor data centers)
Privacy Policy: https://developer.honor.com/cn/docs/11002/guides/sdk-data-security

Identifier	Purpose	Method	Scope
OAID (Anonymous Device ID)	Device identification for push notification routing	Read via MSA SDK interface; transmitted to Honor push servers via encrypted channel	Anonymous device identifier; resettable by user; used solely for push notification delivery; de-identified processing applied
Honor Push Registration Token	Route push notifications to the correct device	Generated by Honor Push SDK; transmitted to Honor servers via encrypted channel	Per-app-installation token; used solely for push notification delivery

                About Notification Content: Notification payloads contain only the minimum data required to route and display the alert (e.g., sender name, a brief message preview, or a call signal). Full message content is fetched directly from the Matrix homeserver by the app after the notification is received. You can disable message previews in Settings → Notifications → Show Preview. The appropriate push channel (APNs, FCM, MiPush, HMS, OPush, VPush, or Honor Push) is selected automatically based on your device platform and manufacturer.
            

                About Device Identifiers: The device identifiers collected by the push SDKs listed above (such as OAID, AAID, Android ID, Firebase Installation ID) are anonymized or de-identified identifiers. They are not directly personally identifiable information. These identifiers are used solely to identify the target device for push notification delivery. Neither we nor the third-party SDK providers associate these identifiers with your real identity.
            

3.20 Huawei Performance Acceleration Library (com.huawei.hms.stats)

Purpose: Improve app performance and stability on Huawei devices; collect app performance metrics (e.g., startup time, frame rate, crash reports) to optimize user experience
SDK name: Performance Acceleration Library (性能加速库)
SDK provider: Huawei Software Technologies Co., Ltd. (华为软件技术有限公司)
Personal information collected: App performance data (startup time, page rendering time, frame rate), device model, OS version, app version, anonymous crash/ANR logs; no user identity information is collected
Processing method: Encrypted via HTTPS and transmitted to Huawei servers; de-identified processing applied
Data location: Huawei cloud infrastructure (mainland China and overseas Huawei data centers)
Privacy Policy: https://developer.huawei.com/consumer/cn/doc/development/graphics-Guides/sdk-data-security-0000001050700772

Sensitive Information Declaration: This SDK does not collect any of the 14 types of personal sensitive information (IMEI, IMSI, Device MAC Address, SUPI, SUCI, Installed App List, Location, Contacts, Call Logs, Calendar, SMS, Phone Number, Photos/Images, Audio/Video). All collected data is anonymous performance metrics used solely for app optimization. For the complete item-by-item declaration with purpose, method, and scope, see Section 3.0.1 Common "Not Collected" Declaration.

4. How We Use Your Information

Provide messaging service: Deliver your messages to intended recipients
Account management: Create and maintain your account, authenticate your identity
Feature functionality: Enable features like voice messages, photo sharing, group chats
Push notifications: Send timely alerts for new messages and incoming calls via APNs (iOS) or the appropriate Android push channel (FCM / MiPush / HMS / OPush / VPush) selected automatically by device manufacturer; push tokens are used solely for notification routing and are never used for advertising or profiling
Service improvement: Fix bugs and improve app performance
Customer support: Respond to your inquiries and support requests
Legal compliance: Comply with applicable laws and regulations

5. Data Storage and Security

5.1 Local Storage

Messages and media are cached locally on your device for offline access
Login credentials are stored in iOS Keychain (encrypted)
Local data is deleted when you uninstall the App or delete your account

5.2 Server Storage

Messages are transmitted through and stored on Matrix homeservers
Server data retention follows the Matrix homeserver operator's policies

5.3 Security Measures

All network communications use HTTPS/TLS encryption
Credentials are stored using platform-native secure storage
We implement industry-standard security practices

6. Data Retention

Data Type	Retention Period
Account information	Until you delete your account
Messages (local)	Until you delete them or uninstall the App
Messages (server)	Per Matrix homeserver policy
Media cache	Automatically cleared periodically or when you clear cache
Push notification token (APNs / FCM / MiPush / HMS / OPush / VPush)	Refreshed automatically by the OS or manufacturer SDK; removed from our servers when you log out or delete your account

7. Data Sharing

We do NOT sell your personal information.

We may share limited data with:

Matrix homeserver operators: For message delivery (necessary for the service to function)
Other users: Your profile information and messages are shared with people you communicate with
Push notification providers: Your device push token and a minimal notification payload are shared with the applicable push service provider (Apple APNs, Google FCM, Xiaomi MiPush, Huawei HMS, OPPO OPush, or vivo VPush) solely for the purpose of delivering notifications to your device
SMS service provider (Ronglian Cloud): Your phone number is shared with Ronglian Cloud solely to deliver verification code SMS messages during registration or password reset
Law enforcement: Only when legally required by valid legal process

8. International Data Transfers

Your data may be transferred to and processed in countries other than your country of residence, including but not limited to:

Matrix homeservers: May be located outside your country
Apple (APNs): United States and other Apple data centers
Google (FCM): United States and other Google data centers
Xiaomi (MiPush), Huawei (HMS), OPPO (OPush), vivo (VPush): Mainland China and overseas data centers operated by the respective manufacturer — applicable only when you use a device from that manufacturer
Ronglian Cloud (SMS): Mainland China — applicable only during SMS verification

By using WeLiao (韦聊), you acknowledge and consent to the transfer of your information to countries that may have different data protection laws than your country of residence. We take reasonable steps to ensure your data is handled securely in accordance with this Privacy Policy.

9. Your Rights

You have the right to:

Access: View your personal data stored in the App
Correction: Update your profile information at any time
Deletion: Delete your account and associated data
Data portability: Export your data (contact us for assistance)
Withdraw consent: Revoke permissions in device settings

How to Delete Your Account

Open WeLiao (韦聊)
Go to Settings → Account Settings → Delete Account
Enter your password to confirm
Your account and data will be permanently deleted

Alternatively, email us at vliaochat@gmail.com with subject "Account Deletion Request". We will process your request within 30 days.

10. California Privacy Rights (CCPA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):

Right to know: What personal information we collect, use, and share
Right to delete: Request deletion of your personal information
Right to opt-out: We do not sell personal information, so no opt-out is necessary
Right to non-discrimination: We will not discriminate against you for exercising your rights

See our "Do Not Sell My Personal Information" page for more details.

11. Children's Privacy

WeLiao (韦聊) is not intended for users under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately at vliaochat@gmail.com.

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes:

We will update the "Last updated" date at the top of this policy
We may notify you through the App or via email
Your continued use of the App after changes constitutes acceptance

13. Governing Law

This Privacy Policy shall be governed by the laws of the People's Republic of China. Any disputes arising from or related to this Privacy Policy shall first be resolved through friendly negotiation; if negotiation fails, you agree to submit the dispute to the competent People's Court in Nanjing, Jiangsu Province, China.

14. Contact Us

If you have any questions, comments, or suggestions about this Privacy Policy or our data practices, please contact us:

App Name: WeLiao (韦聊)

Developer: Nanjing Lingdong Century Media Co., Ltd. (南京领动世纪传媒有限公司)

Privacy inquiries: vliaochat@gmail.com

General support: vliaochat@gmail.com

We will respond to your request within 15 business days.

隐私政策

生效日期：2026-01-19 | 最后更新：2026-03-10

南京领动世纪传媒有限公司（以下简称"我们"）是韦聊（WeLiao）的开发者和运营者，非常重视用户的隐私和个人信息保护。本隐私政策说明我们在您使用韦聊移动应用（"应用"）时如何收集、使用、披露和保护您的信息。在使用本产品前，请您务必仔细阅读并充分理解本隐私政策。

开发者信息：
应用名称：韦聊（WeLiao）
开发者：南京领动世纪传媒有限公司
联系邮箱：vliaochat@gmail.com

                要点：
                我们不会出售您的个人信息
消息通过 Matrix 协议传输
大部分数据存储在您的设备本地
您可以随时删除账户和数据

            

1. 我们收集的信息

1.1 账户信息

Matrix 用户 ID（用户名）和身份验证凭据
手机号码（用于注册和账户恢复）
您提供的个人资料信息（显示名称、头像）

1.2 通讯数据

您发送和接收的文字消息
您分享的媒体内容（照片、视频、语音消息）
消息元数据（时间戳、已读回执、送达状态）
群聊信息（群名称、成员列表）

1.3 设备信息

设备类型和型号
操作系统和版本
应用版本
设备语言设置
网络连接类型（WiFi/蜂窝网络）
推送通知令牌——iOS 上为 APNs 令牌；Android 上根据设备品牌使用对应厂商通道令牌（FCM / MiPush / HMS / OPush / VPush）——仅用于向您的设备发送通知

1.4 媒体和文件

您选择分享的照片和视频（仅在您选择时访问）
您为语音消息创建的录音
您扫描的二维码（在设备本地处理）

2. 设备权限

我们的应用请求以下权限，您可以在设备设置中管理这些权限：

权限	用途	使用时机
相机	拍摄照片和视频在聊天中分享；扫描二维码	仅当您点击相机按钮或扫描功能时
麦克风	录制语音消息；录制带音频的视频	仅当您按住语音消息按钮或录制视频时
相册（读取）	选择现有照片和视频进行分享	仅当您选择从相册中选取媒体时
相册（写入）	将收到的媒体保存到您的设备	仅当您选择保存图片或视频时
通知	在应用处于后台或关闭时接收消息通知；显示来电提醒	当有新消息到达或接到来电时

注意：您可以拒绝任何权限，但某些功能可能无法正常使用。您可以随时在设备的"设置"中更改权限。关闭通知权限将停止所有推送通知，但不影响应用内的消息收发。

2.1 后台/静默状态下的数据处理

作为即时通讯应用，为保障您及时收到消息和来电通知，本应用在后台或静默状态下存在有限的数据处理活动。以下逐项说明：

后台活动	涉及的数据	目的	处理方式
接收推送通知	推送令牌、通知载荷（发件人名称、消息预览摘要、来电信号）	在您未打开应用时，及时通知您收到新消息或来电	由操作系统厂商推送通道（APNs/FCM/MiPush/HMS/OPush/VPush）处理；我们的应用代码在此过程中不主动运行，不会采集任何额外个人信息
来电信号唤醒	来电推送信号（呼叫方标识、房间ID）	在后台收到来电推送时，唤起来电界面供您接听	通过推送通知触发系统来电界面；不会在后台录音、不会获取位置、不会读取通讯录
消息同步	Matrix同步请求（增量消息、已读回执、在线状态）	您重新打开应用时，从Matrix服务器拉取离线期间的新消息	仅在应用回到前台时执行，并非真正的后台活动；通过HTTPS/TLS加密与Matrix服务器通信

本应用在后台/静默状态下不会执行以下行为：

不会在后台采集GPS位置信息或进行地理围栏监控
不会在后台扫描、读取或上传您的相册、图片或视频
不会在后台读取您的通讯录、通话记录、短信或日历
不会在后台采集设备标识符（如IMEI、IMSI、MAC地址等）
不会在后台扫描或收集已安装应用列表
不会在后台进行用户行为追踪、画像分析或广告投放
不会在后台录制音频或视频

3. 第三方服务和 SDK

为了给您提供更好的服务，在您授权同意的前提下，我们的应用使用以下第三方服务和软件开发工具包（SDK）。我们会要求第三方SDK提供方依法保护您的个人信息。

3.0 个人敏感信息收集情况说明

根据相关法律法规要求，以下逐项说明本应用及所集成的第三方SDK对各类个人敏感信息的收集情况，包括是否收集、由哪个SDK/功能收集、收集目的及处理方式：

个人信息类型	是否收集	关联的SDK/功能	收集目的	处理方式	涉及的SDK
IMEI（国际移动设备识别码）	不收集	—	—	—	—
IMSI（国际移动用户识别码）	不收集	—	—	—	—
设备MAC地址	音视频通话建立连接时可能被访问	flutter_webrtc（WebRTC SDK）	WebRTC建立通话连接时需要枚举网络接口收集ICE候选地址，在Android 9及以下版本可能获取到设备真实MAC地址	仅用于建立点对点通话连接，不存储、不上传、不用于其他用途；Android 10及以上系统返回随机化MAC地址	flutter_webrtc
SUPI	不收集	—	—	—	—
SUCI	不收集	—	—	—	—
软件安装列表	不收集	—	—	—	—
位置信息（GPS定位）	不收集	—	—	—	—
通讯录/联系人	不收集	—	—	—	—
通话记录	不收集	—	—	—	—
日历	不收集	—	—	—	—
短信	不收集	—	—	—	—
本机电话号码	仅在注册/登录时由用户主动输入	容联云（服务端REST API，非客户端SDK）	发送短信验证码，用于注册、登录和密码重置	用户主动输入后，由我们的服务器通过HTTPS加密API传输至容联云短信网关发送验证码；不会自动读取本机号码	容联云
图片	仅在用户主动选择发送时访问	Matrix SDK	在聊天中发送图片消息	用户从相册主动选择后，通过HTTPS/TLS加密上传至Matrix服务器发送给接收方；不会在后台自动采集图片	Matrix SDK
音视频	仅在用户主动操作时访问	Matrix SDK（语音/视频消息）、flutter_webrtc（音视频通话）	发送语音消息、视频消息；进行语音通话和视频通话	用户主动录制或发起通话后，语音/视频消息通过HTTPS/TLS加密上传至Matrix服务器；通话音视频流通过DTLS/SRTP加密点对点传输；不会在后台自动录制或采集音视频	Matrix SDK、flutter_webrtc

声明：上表中标注"不收集"的个人信息类型，本应用自身及所集成的全部第三方SDK在运行过程中均不会收集、存储或传输。标注为"仅在用户主动操作时访问"的信息类型，仅在用户明确触发相应功能时才会访问，且不会在后台自动采集。

3.0.1 通用"不收集"声明 — 适用于不收集14类个人敏感信息的SDK

以下SDK在运行过程中不收集14类个人敏感信息（IMEI、IMSI、设备MAC地址、SUPI、SUCI、软件安装列表、位置信息、通讯录/联系人、通话记录、日历、短信、本机电话号码、图片、音视频）中的任何一项。本声明适用于：

3.2 Google ML Kit（条码扫描）
3.3 SDWebImage
3.4 SQLite / Drift 数据库
3.5 Flutter Secure Storage
3.6 Dio（HTTP网络客户端）
3.8 cached_network_image（图片缓存）
3.9 go_router（路由导航）
3.10 flutter_screenutil（响应式布局）
3.11 phosphor_flutter（图标库）
3.13 Apple 推送通知服务（APNs）
3.14 Firebase 云消息传递（FCM）
3.15 小米推送（MiPush）
3.16 华为推送（HMS Push）
3.17 OPPO PUSH 客户端SDK（com.heytap.msp）
3.18 vivo推送（VPush）
3.19 荣耀推送SDK（com.hihonor.push）
3.20 华为性能加速库（com.huawei.hms.stats）

信息类型	是否收集	收集目的	收集方式	收集范围
IMEI	不收集	—	—	—
IMSI	不收集	—	—	—
设备MAC地址	不收集	—	—	—
SUPI	不收集	—	—	—
SUCI	不收集	—	—	—
软件安装列表	不收集	—	—	—
位置信息	不收集	—	—	—
通讯录/联系人	不收集	—	—	—
通话记录	不收集	—	—	—
日历	不收集	—	—	—
短信	不收集	—	—	—
本机电话号码	不收集	—	—	—
图片	不收集	—	—	—
音视频	不收集	—	—	—

说明：上述推送类SDK（APNs、FCM、小米推送、华为推送、OPPO推送、vivo推送）可能收集设备标识符（如OAID、Android ID、设备推送令牌等），仅用于推送通知的路由和送达。这些标识符不属于上述14类个人敏感信息。各推送SDK收集设备标识符的目的、方式和范围详见下方各SDK的详细说明。

以下为第三方SDK信息汇总（含SDK名称、所属公司、收集的个人信息类型、处理方式及用途）。我们要求第三方SDK提供方依法保护您的个人信息，并对其个人信息处理活动负责。

SDK 名称	所属公司	收集的个人信息类型	处理方式	使用目的	隐私政策
Matrix SDK	Matrix.org Foundation C.I.C.	用户ID（Matrix账户标识）、消息内容（文字、图片、音视频等媒体文件）、聊天联系人列表、群组成员信息	通过HTTPS/TLS加密传输至Matrix主服务器	核心即时通讯服务：发送和接收消息、同步联系人及群组信息	查看
容联云（短信验证服务）	北京容联易通信息技术有限公司	手机号码、短信验证码内容。说明：容联云短信服务通过服务端REST API调用（非客户端SDK），您的手机号码由我们的服务器通过加密接口传输至容联云短信网关，客户端不直接与容联云服务器通信	我们的服务器通过HTTPS加密REST API将手机号码传输至容联云短信网关	发送注册、登录、密码重置的短信验证码	查看
Google ML Kit（条码扫描）	Google LLC	相机图像（在设备本地处理，不上传）；SDK运行时自动收集：安装标识符（per-installation identifier）、设备信息（制造商、型号、操作系统版本）、应用信息（包名、版本号）、性能指标（延迟数据）、API配置信息（图像格式、分辨率）	图像在设备端本地处理；诊断分析数据通过HTTPS加密传输至Google服务器，不与第三方共享	扫描二维码添加好友或加入群组；诊断数据用于SDK性能优化	查看
flutter_webrtc（WebRTC）	开源组件（湖北捷智云技术有限公司）	通话期间的音频流、视频流、IP地址（通话建立时的ICE候选地址，包含本地IP和公网IP）、STUN/TURN服务器协商数据	媒体流通过DTLS/SRTP加密传输；优先建立点对点（P2P）连接，无法直连时通过TURN中继服务器转发	实现应用内的语音通话和视频通话功能	—
APNs（苹果推送通知服务）	Apple Inc.	APNs设备令牌（设备推送标识）、通知载荷（发件人名称、消息预览摘要、来电信号）	通过TLS加密传输至Apple服务器	向iOS设备发送新消息和来电推送通知	查看
FCM（Firebase云消息传递）	Google LLC	FCM注册令牌（设备推送标识）、Firebase安装ID（FID）、Android ID、应用包名及版本号、设备型号、操作系统版本、通知载荷	通过HTTPS加密传输至Google服务器	向Android设备（支持Google Play服务）发送新消息和来电推送通知	查看
小米推送（MiPush）	北京小米移动软件有限公司	OAID（匿名设备标识符）、加密的Android ID、设备MiPush注册令牌、应用包名及版本号、设备厂商、设备型号、操作系统版本、网络类型（WiFi/蜂窝）、运营商信息、通知栏设置状态、通知载荷	通过加密通道传输至小米推送服务器；采用去标识化处理	向小米/红米/POCO设备发送推送通知（仅安卓）	查看
华为推送（HMS Push）	华为技术有限公司	AAID（匿名应用标识符）、HMS推送令牌、应用包名及版本号、设备型号、操作系统版本、网络类型（WiFi/蜂窝）、国家码、通知载荷	通过HTTPS加密传输至华为推送服务器；采用去标识化处理	向华为设备发送推送通知（仅安卓）	查看
OPPO PUSH 客户端SDK（com.heytap.msp）	广东欢太科技有限公司	OAID（匿名设备标识符）、Android ID、OPush注册令牌、应用包名及版本号、设备型号、操作系统版本、网络类型（WiFi/蜂窝）、IP地址、通知栏设置状态、通知载荷	通过加密通道传输至OPPO推送服务器；采用去标识化处理	向OPPO/一加/realme设备发送推送通知（仅安卓）	查看
vivo推送（VPush）	维沃移动通信有限公司	OAID（匿名设备标识符）、VPush注册令牌、应用包名及版本号、设备型号、操作系统版本、网络类型（WiFi/蜂窝）、通知栏设置状态、通知载荷	通过加密通道传输至vivo推送服务器；采用去标识化处理	向vivo设备发送推送通知（仅安卓）	查看
荣耀推送SDK（com.hihonor.push）	深圳荣耀软件技术有限公司	OAID（匿名设备标识符）、荣耀推送注册令牌、应用包名及版本号、设备型号、操作系统版本、网络类型（WiFi/蜂窝）、通知栏设置状态、通知载荷	通过加密通道传输至荣耀推送服务器；采用去标识化处理	向荣耀设备发送推送通知（仅安卓）	查看
SQLite / Drift 数据库	开源组件	消息记录、聊天联系人信息、应用设置（仅本地存储，不上传至任何服务器）	仅在设备本地存储，不涉及网络传输	本地数据存储，支持离线访问聊天记录	—
Flutter Secure Storage	开源组件	身份验证令牌、Matrix访问令牌（仅加密存储于iOS Keychain / Android Keystore）	平台原生加密存储，不涉及网络传输	安全存储登录凭据和会话令牌	—
Dio（HTTP网络客户端）	开源组件	API请求载荷（含用户凭据、个人资料数据）	所有数据通过HTTPS/TLS加密传输至我们的服务器	与后端API服务器通信（注册、登录、资料管理等）	—

重要说明：

以上第三方SDK仅在对应设备品牌或功能被实际使用时才会激活。例如，小米推送SDK仅在小米品牌设备上运行，华为推送SDK仅在华为/荣耀设备上运行。
推送类SDK收集的设备标识符（如OAID、Android ID等）仅用于消息推送通知的路由和送达，绝不用于广告投放、用户画像或行为追踪。
所有涉及网络传输的个人信息均采用加密传输方式处理。

3.1 Matrix 协议 (matrix.org)

用途：发送和接收消息的核心消息基础设施
处理的数据：用户 ID、消息、媒体文件、联系人列表
数据位置：Matrix 主服务器（可能位于您所在国家/地区之外）
隐私政策：https://matrix.org/legal/privacy-notice

                本SDK个人敏感信息收集声明：
                
                    信息类型是否收集收集目的收集方式收集范围
IMEI不收集———
IMSI不收集———
设备MAC地址不收集———
SUPI不收集———
SUCI不收集———
软件安装列表不收集———
位置信息不收集———
通讯录/联系人不收集———
通话记录不收集———
日历不收集———
短信不收集———
本机电话号码不收集———
图片用户主动触发时收集在聊天中发送图片消息用户从相册主动选取后，通过HTTPS/TLS加密上传至Matrix服务器发送给接收方仅限用户主动选择的图片；不会在后台自动扫描或采集相册图片
音视频用户主动触发时收集发送语音消息、视频消息；进行语音通话和视频通话用户主动录制或发起通话后，语音/视频消息通过HTTPS/TLS加密上传至Matrix服务器；通话音视频流通过DTLS/SRTP加密点对点传输仅在用户主动录制或发起通话时访问；不会在后台自动录制或采集音视频

            

3.2 Google ML Kit（条码扫描）

用途：用于添加好友和加入群组的二维码扫描
收集的个人信息：
- 相机图像：仅在设备本地处理，不上传至任何服务器
- SDK运行诊断数据（自动收集）：安装标识符（per-installation identifier，用于标识应用安装实例，非用户身份标识）、设备信息（制造商、型号、操作系统版本、可用ML硬件加速器）、应用信息（包名、版本号）、性能指标（处理延迟）、API配置信息（图像格式、分辨率）、功能事件（初始化、检测事件）
处理方式：图像数据在设备端本地处理；诊断分析数据通过HTTPS加密传输至Google服务器，Google不会将该数据传输给第三方
隐私政策：https://developers.google.com/ml-kit/terms

本SDK个人敏感信息收集声明：本SDK不收集上述14类个人敏感信息中的任何一项（IMEI、IMSI、设备MAC地址、SUPI、SUCI、软件安装列表、位置信息、通讯录、通话记录、日历、短信、本机电话号码、图片、音视频）。相机图像仅在设备本地处理，不上传至任何服务器。SDK仅收集匿名安装标识符和设备诊断信息用于性能优化。各信息类型逐项声明（含收集目的、收集方式、收集范围）详见3.0.1节通用"不收集"声明。

3.3 SDWebImage

用途：高效的图片加载和缓存
处理的数据：图片 URL 和缓存的图片
数据位置：仅限本地设备存储

本SDK个人敏感信息收集声明：本SDK不收集上述14类个人敏感信息中的任何一项（IMEI、IMSI、设备MAC地址、SUPI、SUCI、软件安装列表、位置信息、通讯录、通话记录、日历、短信、本机电话号码、图片、音视频），所有数据仅在设备本地处理。各信息类型逐项声明（含收集目的、收集方式、收集范围）详见3.0.1节通用"不收集"声明。

3.4 SQLite / Drift 数据库

用途：本地存储消息和应用数据以供离线访问
处理的数据：消息、联系人、设置
数据位置：仅限本地设备存储 - 不传输到任何服务器

3.5 Flutter Secure Storage

用途：安全存储登录凭据和会话令牌
处理的数据：身份验证令牌、Matrix 访问令牌
数据位置：iOS 钥匙串 / Android Keystore（加密，仅限本地）

3.6 Dio（HTTP 网络客户端）

用途：向我们的后端 API 发起网络请求（注册、个人资料、群组管理、版本检查等）
处理的数据：请求载荷，包括用户凭据、个人资料数据及 API 响应
数据传输：所有请求通过 HTTPS/TLS 加密发送至我们的服务器
SDK 来源：开源 Flutter 包（pub.dev 上的 dio）

3.7 flutter_webrtc（WebRTC — 语音与视频通话）

用途：在应用内实现点对点语音和视频通话
收集的个人信息：通话期间的音频流、视频流；IP地址（通话建立时的ICE候选地址，包含本地IP和公网IP，用于建立通话连接）；STUN/TURN服务器协商数据
处理方式：媒体流通过DTLS/SRTP加密传输；优先建立点对点（P2P）连接，无法直连时通过TURN中继服务器转发；通话信令通过Matrix主服务器处理
数据位置：建立直接P2P连接时，媒体流不经过我们的服务器
SDK 来源：开源Flutter WebRTC包（湖北捷智云技术有限公司）

本SDK个人敏感信息收集声明：

信息类型	是否收集	收集目的	收集方式	收集范围
IMEI	不收集	—	—	—
IMSI	不收集	—	—	—
设备MAC地址	通话建立时可能被访问	建立点对点音视频通话连接	WebRTC建立通话连接时枚举网络接口收集ICE候选地址，在Android 9及以下版本可能获取到设备真实MAC地址	仅在用户主动发起音视频通话时访问；不存储、不上传、不用于其他用途；Android 10及以上系统返回随机化MAC地址
SUPI	不收集	—	—	—
SUCI	不收集	—	—	—
软件安装列表	不收集	—	—	—
位置信息	不收集	—	—	—
通讯录/联系人	不收集	—	—	—
通话记录	不收集	—	—	—
日历	不收集	—	—	—
短信	不收集	—	—	—
本机电话号码	不收集	—	—	—
图片	不收集	—	—	—
音视频	用户主动触发时收集	实时语音通话和视频通话	音视频流通过DTLS/SRTP加密点对点传输；无法直连时通过TURN中继服务器转发	仅在用户主动发起通话时访问；不录制、不存储、不上传；不会在后台自动采集音视频

此外，通话建立时会收集IP地址（ICE候选地址）用于建立连接，不属于上述14类敏感信息。

3.8 cached_network_image（图片缓存）

用途：高效加载和本地缓存远程图片（头像、分享的图片）
处理的数据：图片 URL 和下载的图片文件
数据位置：缓存文件仅存储在本地设备
SDK 来源：开源 Flutter 包

3.9 go_router（路由导航）

用途：应用内导航和深度链接
处理的数据：导航路由和 URL 参数（本地处理，不传输）
数据位置：仅限本地
SDK 来源：开源 Flutter 包

3.10 flutter_screenutil（响应式布局）

用途：在不同屏幕尺寸和密度下实现响应式 UI 缩放
处理的数据：设备屏幕尺寸（只读，不传输）
数据位置：仅限本地
SDK 来源：开源 Flutter 包

3.11 phosphor_flutter（图标库）

用途：UI 图标渲染
处理的数据：无 —— 图标资源随应用本地打包
数据位置：仅限本地
SDK 来源：开源 Flutter 包

3.12 容联云（短信验证服务）

用途：在注册、登录和密码重置时发送短信验证码
服务提供方：北京容联易通信息技术有限公司
接入方式：通过服务端REST API调用（非客户端SDK集成），您的客户端设备不会直接与容联云服务器通信
收集的个人信息：手机号码、短信验证码内容
处理方式：您的手机号码由我们的服务器通过HTTPS加密REST API传输至容联云短信网关，容联云负责将短信验证码发送至您的手机
数据位置：容联云基础设施（中国大陆）
隐私政策：https://www.yuntongxun.com/about/privacy

                本服务个人敏感信息收集声明：
                
                    信息类型是否收集收集目的收集方式收集范围
IMEI不收集———
IMSI不收集———
设备MAC地址不收集———
SUPI不收集———
SUCI不收集———
软件安装列表不收集———
位置信息不收集———
通讯录/联系人不收集———
通话记录不收集———
日历不收集———
短信不收集———
本机电话号码用户主动输入时收集发送注册、登录、密码重置的短信验证码用户手动输入手机号码后，由我们的服务器通过HTTPS加密REST API传输至容联云短信网关发送验证码；客户端不直接与容联云服务器通信仅限用户主动输入的手机号码；不会自动读取设备SIM卡号码
图片不收集———
音视频不收集———

            

3.13 Apple 推送通知服务（APNs）

用途：向 iOS 设备发送推送通知（新消息、来电提醒）
处理的数据：设备 APNs 令牌；通知载荷（发件人、消息预览摘要（如已开启）、来电信号）
数据传输：令牌及最小化载荷发送至 Apple APNs 服务器以路由通知
数据位置：Apple 基础设施（美国及其他 Apple 数据中心）
隐私政策：https://www.apple.com/legal/privacy/

本服务个人敏感信息收集声明：本服务不收集14类个人敏感信息中的任何一项。各信息类型逐项声明详见3.0.1节。

本SDK收集的设备标识符：

标识符	收集目的	收集方式	收集范围
APNs设备令牌	将推送通知路由至正确的iOS设备	由iOS系统生成，通过TLS加密传输至Apple APNs服务器	每个应用安装实例一个令牌；重新安装后会变更；仅用于推送通知送达