个人数据类型清单

Below is a structured list of personal data types a social chat application might collect or process. Actual collection depends on product features, platform (mobile/web/desktop), user settings, permissions, and legal requirements.

1. Identity and account data

• User identifiers: username, account ID, user handle, display name
• Contact details: phone number, email address, recovery email/phone
• Authentication data: password hashes, 2FA tokens, backup codes, single sign-on identifiers, public keys/Key IDs (for E2EE)
• Profile attributes: profile photo, status message, bio, pronouns, language, country, time zone
• Age/date of birth; age gate confirmation
• Government ID (only if required for age verification, KYC, or trust-and-safety processes)

2. Social graph and contacts

• Address book entries (names, phone numbers, emails) if contact matching is enabled
• Friend lists, followers/following, block/mute lists
• Group memberships, roles (e.g., admin), invites and join history
• Non-user data: phone numbers or emails of individuals not using the service, used for contact discovery

3. Device and network identifiers

• Device IDs (OS device ID, vendor/device model), app instance IDs
• Mobile advertising identifiers (IDFA/GAID), push notification tokens
• SIM/Carrier info (MCC/MNC), OS version, app version, device language/locale
• IP address, user agent, connection type, rough network location derived from IP

4. Location data

• Precise geolocation (GPS, Wi-Fi/Bluetooth) when features require it (e.g., location sharing)
• Approximate location or time zone
• Location inferences (e.g., city/region) from IP

5. Communications content and metadata

• Message content: text, images, audio notes, video, files, links, stickers/emoji
• Call content (voice/video) when not E2EE; otherwise only for transmission
• Metadata: sender/recipient IDs, timestamps, message IDs, delivery/read receipts, forwarding flags, group IDs, call start/end times, participants, call quality metrics
• Attachments’ technical metadata (e.g., file type, size, hashes), link preview fetch data
• Content moderation artifacts (e.g., hashes, signatures) if scanning is used server-side or client-side

6. Usage, analytics, and telemetry

• Feature usage events (e.g., message sent, call initiated, settings changed)
• Session data: login/logout times, session tokens, last active timestamp
• Crash reports, performance metrics, error logs
• A/B testing variants, experiment enrollment

7. Security, fraud, and integrity data

• Login history, failed login attempts, risk scores
• Device integrity/attestation signals, jailbreak/root detection indicators
• Spam/abuse reports, mute/block actions, automated abuse-detection signals
• Audit logs (admin actions, key changes, session revocations)
• Cryptographic artifacts for E2EE: public keys, key fingerprints/safety numbers, session state metadata, key transparency proofs

8. Payment and commercial data

• Subscription status, plan type, renewal dates
• Payment method tokens (via payment processors), billing address (if collected), transaction history
• Gift purchases, in-app purchases, refunds/chargeback records
• Tax-related data where required by law

9. Marketing and advertising data

• Marketing preferences and consent flags (opt-in/out)
• Campaign attribution data, referral codes, install source
• Advertising segments and identifiers, if ad-supported
• Email/SMS engagement metrics (opens, clicks)

10. Support and operational communications

• Helpdesk tickets, chat with support, call recordings (with notice), email threads
• User-provided screenshots, diagnostic dumps
• Identity verification artifacts for account recovery

11. Inferences and profiling

• Predicted interests or likelihood to engage with features
• Spam/abuse likelihood scores
• Churn risk or quality-of-service segments

12. Special category/sensitive data (context-dependent)

• Sensitive data under GDPR (e.g., health, biometric, racial/ethnic origin, religious beliefs, sexual orientation) may be present if users share it in messages, profiles, or media
• Biometric data only if features explicitly collect/process it (e.g., face/voice unlock or identity verification)
• Under CCPA/CPRA, sensitive personal information (e.g., precise geolocation, account logins with credentials, government IDs)

13. Children’s data (where applicable)

• Age, parent/guardian contact and consent records, usage controls for minor accounts

14. Data from third parties and integrations

• Social login data (OAuth identifiers, profile basics)
• Data from connected services (cloud storage, calendars) for features like file sharing or scheduling
• Contact discovery or anti-abuse datasets from service providers
• App store or platform-provided install/attribution data

Regulatory notes for categorization

• GDPR: Most items above are “personal data” (Art. 4(1)). Some items may be “special categories” (Art. 9) if collected or observed (e.g., biometrics for identification, health data). Criminal offense data (Art. 10) could be processed in trust-and-safety contexts subject to legal bases and safeguards.
• CCPA/CPRA: Categories can map to identifiers; protected classification characteristics; commercial information; internet/electronic network activity; geolocation; audio/visual/sensory; professional/education information (if provided); biometric information; and inferences.
• Non-user data (e.g., address book entries) is personal data and requires appropriate notice, purpose limitation, and, where required, consent or opt-out mechanisms.

This list supports data mapping, Records of Processing Activities, privacy notices, and DPIAs by providing a comprehensive view of plausible data elements a social chat app may process. Actual data elements should be verified through a system-by-system data inventory.

以下は、SaaS型CRMが一般的に収集・処理し得る個人データの類型です（機能・設定により収集の有無は異なります）。

• 直接識別子: 氏名、別名、ユーザーID、社内ID
• 連絡先情報: 電子メール、電話番号、住所、役職、部署
• アカウント・認証情報: ログイン名、ハッシュ化パスワード、MFAトークン、ロール/権限
• プロフィール・職務情報: 会社名、職務/役割、購買権限、言語/タイムゾーン、プロフィール写真
• 商取引・契約情報: 見積・受注・契約内容、請求先情報、支払ステータス、価格・割引、契約期間、購買履歴
• 支払・請求関連メタデータ: 請求書番号、請求先住所、カード末尾4桁やトークン化ID（通常は決済代行側が保管）
• コミュニケーション記録: メール本文・件名・メタデータ、チャットログ、通話記録/録音、会議招待、メモ、添付ファイル
• マーケティング・同意情報: オプトイン/オプトアウト状況、チャネル別許諾、クッキー同意、配信停止リスト、プライバシー設定
• リードソース・参照情報: キャンペーンID、UTMパラメータ、紹介者、パートナーID、フォーム送信元
• 行動・利用履歴: メール開封/クリック、サイト閲覧履歴、イベントトラッキング、アプリ利用ログ、エンゲージメント指標
• デバイス・技術識別子: IPアドレス、Cookie ID、モバイル広告ID、ユーザーエージェント、ブラウザ指紋、接続タイムスタンプ
• 位置情報: 国/都市などの粗い位置情報、必要に応じてGPS等の精確位置情報
• ソーシャルメディア識別子: プロフィールURL、ハンドル名、公開経歴（例: LinkedIn, X）
• サポート/CSデータ: 問い合わせ内容、チケット履歴、対応記録、満足度スコア
• 画像・音声・映像: 名刺画像、プロフィール写真、ウェビナー録画、音声メモ
• 推測・プロファイリング情報: リードスコア、購買可能性、離反予測、意向分類、セグメント属性
• 認証・セキュリティログ: 成否ログイン、認可イベント、監査ログ、IPブロックフラグ
• 法務・コンプライアンス関連: 契約同意、規約同意履歴、KYC結果（該当時）、DPA受領
• 人口統計属性: 年齢帯、居住国、言語、職種、業界、会社規模（個人属性と結合される場合は個人データに該当）
• 特別カテゴリ/センシティブ情報（収集回避が原則）: 健康・生体認証・政治的意見・宗教・性的指向、社会保障番号/マイナンバー、金融口座情報、正確な位置情報、アカウントログイン＋パスワード等

留意事項（簡潔）:

• GDPR/CCPAの目的限定・データ最小化を適用し、必要な法的根拠（例: 契約履行、正当利益、同意）を確保してください。
• 特別カテゴリ/センシティブ情報はCRMの自由記述に混入しやすいため、フィールド制御、ユーザー教育、DLP/監査で記載防止・検出を実施してください。