This document lists every third-party SDK integrated into Xiang. Column "Edition" indicates which client: iOS, AG (Android Google global), AC (Android China — Xiaomi/Vivo/Huawei).
Registration ID, device model, OS version, network state, Wi-Fi SSID, Wi-Fi BSSID, MAC address, coarse location; not initialized until you accept the Policy
Crash stack, device model, OS, app version, breadcrumbs (no user input); user-disableable
iOS Crash Report
Apple Inc.
System
iOS
System crash reporting (user-controlled in Settings)
Handled by Apple
6. System Capability Wrappers
SDK
Vendor
Version
Edition
Purpose
CoreLocation
Apple
System
iOS
"While in use" location (one-shot, discarded)
EventKit / UserNotifications / PhotosUI
Apple
System
iOS
Calendar write, notifications, photo write
androidx.browser (Custom Tabs)
Google
1.8.0
AG / AC
Apple web OAuth
androidx.security:security-crypto
Google
1.1.0-alpha06
AG / AC
Local token AES-256-GCM
Coil
OSS
2.7.0
AG / AC
Image loading
Retrofit / OkHttp / Moshi
Square (OSS)
2.11.0 / 4.12.0 / 1.15.1
AG / AC
HTTP & serialization
7. First-Party Analytics
We use our own client-side event batching with backend aggregation. No third-party analytics SDKs (no Firebase Analytics, Umeng, AppsFlyer, Mixpanel, Amplitude, Sensors, GrowingIO, TalkingData). Events go to POST /api/v1/track/events and are auto-purged after 90 days. See Data Collection Inventory.
8. Backend-Only Third Parties
The following are called only by our server; no client SDK is integrated and no end-user PII is sent:
MusicBrainz API — public metadata, no auth
Apple Music API (server-side) — public catalog
Spotify Web API (server-side client_credentials) — public catalog
Soundcharts — ISRC ↔ Spotify track mapping
OpenAI / DeepSeek — server-side generation of program notes and artist bios; no end-user PII transmitted
Alibaba Cloud Content Safety (Green) — server-side text moderation for nicknames/comments