ChatGPT Security & Privacy Scorecard

by OpenAI OpCo, LLC · iOS

90
Overall trust score
Trustworthy
94
Security
88
Privacy

Usage and behavioral data is collected and shared with Segment, Statsig, Datadog, and Sentry for analytics, performance monitoring, and crash reporting. Stripe and RevenueCat handle payment and subscription data. Auth tokens are protected with biometric binding and device-only storage, and no advertising identifiers are accessed.

Best for

Daily AI assistant users comfortable with analytics

Findings

  • 0 critical
  • 2 high
  • 2 medium
  • 1 low
  • 10 info

3 issues identified across security and privacy analysis.

Top security issues

  • Sentry session replay SDK active with sentryReplayUnmask modifier present — health data and AI conversations at risk of cloud capture if sample rates non-zero
  • Skybridge WKWebView JS bridge exposes native payment checkout and account-linking to chatgpt.com web content without confirmed origin validation
  • Custom URL schemes openai:// and chatgpt:// invocable by any device app without caller identity verification, reaching payment and settings deep link routes

Top privacy issues

  • 25+ HealthKit biometric categories including insulin delivery, AFib burden, and menstrual flow continuously synced to OpenAI servers via incremental HKAnchoredObjectQuery
  • Segment analytics with server-side configurable destinations — complete routing targets not auditable from binary; open question whether health data attributes or installed-app detection results enter event payloads
  • 18 social and messaging app schemes queried via canOpenURL() including privacy-sensitive Signal and Telegram installation status — potential fingerprinting if results reach analytics pipelines

Full analysis

ChatGPT

ChatGPT is OpenAI's official AI assistant app. Chat with an AI to ask questions, write, brainstorm, and solve problems. Supports voice conversations and image analysis.

What This Means for You

If you enable HealthKit sync, your biometric health data including blood glucose, insulin delivery, and heart rate is uploaded to OpenAI's servers and may be captured by a session recording service that operates outside OpenAI's direct control.

Recommendation: Use With Caution

Review OpenAI's health data sharing and Sentry session replay settings before enabling HealthKit sync. The app has strong security practices overall, but session replay carries moderate risk to sensitive data including AI conversations and health metrics. Users who do not enable HealthKit sync face a lower risk profile.

Best For: General users comfortable with OpenAI's AI services, analytics telemetry, and health data sharing practices

Key Findings

Data Security - 2 findings (2 info)

Network Security - 0 findings

Code Safety - 2 findings (1 medium, 1 low)

Privacy - 5 findings (1 medium, 4 info)

Privacy Concerns

What Data is Collected

  • Personal information: name, email address, phone number, payment details
  • Health and biometric data: blood glucose, insulin delivery, blood pressure, menstrual flow, heart rate, sleep data, and 20+ additional HealthKit categories (when HealthKit sync is enabled)
  • AI conversation history (stored server-side at OpenAI)
  • Device information: device type, operating system, installed app presence for 18 social and messaging apps
  • Usage data: feature interactions, A/B test group assignments, app performance metrics
  • Photos and files uploaded by the user

Third-Party Data Sharing

The following third parties may receive your data:

  • Segment - Product analytics with server-side configurable routing; complete data destinations are not fully auditable
  • Statsig - Feature flags and A/B testing; receives device properties to personalize features
  • Datadog - App performance monitoring and error logging
  • Sentry - Crash reporting and session replay recording (potential capture of screen content including health data and conversations)
  • Auth0 - Authentication and session management
  • RevenueCat - Subscription and purchase management
  • Stripe - Payment processing
  • LiveKit - Real-time voice and video communications
  • Apple AdServices - Search ads attribution (Apple-only, no advertising ID used)

Understanding the Scores

Security: 94/100
Privacy: 88/100

Security Breakdown

  • Data Security: 95/100 - Authentication tokens are stored with biometric binding and device-only protection; conversation history is not stored locally
  • Network Security: 100/100 - All connections enforce HTTPS with no exceptions across all app targets
  • Code Safety: 94/100 - No secrets found in the app binary; web-to-native bridge has server-side kill switches but origin validation could not be fully confirmed

Privacy Breakdown

  • Data Collection: 88/100 - Collects extensive health biometric data and device information when features are enabled; analytics pipeline scope partially server-configured
  • Data Sharing: 90/100 - Data flows to several third-party services; Segment's server-side routing means not all destinations are visible in the app
  • User Control: 96/100 - Health data sync is opt-in with clear permission prompts; Safari search extension is opt-in; biometric keychain access is user-controlled

Positive Security Features

  • No secrets, API keys, or credentials found hardcoded in the app binary
  • All network connections enforce strict HTTPS with no exceptions across the main app and all five extensions
  • Conversation history is stored on OpenAI's servers only - no local database on your device
  • Login tokens are protected with biometric authentication and cannot sync to iCloud
  • No advertising ID (IDFA) access - the app does not participate in cross-app advertising tracking
  • Secure OAuth login flow with proper session cleanup on logout
  • Server-side kill switches on payment and account-linking bridge operations for rapid risk mitigation

Areas for Improvement

GDPR / CCPA Compliance

The app's privacy practices could be strengthened by:

  1. Session Replay Data Scope Transparency
    Users enabling HealthKit sync should receive clear disclosure that a third-party session recording service may capture health data displayed on screen, with explicit controls to disable session replay independently of other analytics.

  2. Analytics Destination Transparency
    Segment's server-side routing means the full list of companies receiving analytics data is not visible in the app. Publishing a complete list of Segment destinations in the privacy policy would strengthen user control.

  3. Installed App Detection Disclosure
    The app checks whether 18 specific apps are installed on your device to populate share options. Users should be informed if any of these results flow into analytics or profiling pipelines.

Security Enhancements

  1. File Protection Strengthening
    Locally cached images, uploaded files, and crash reports could be protected with the strongest iOS file encryption class, making them inaccessible while the device screen is locked, even after an initial unlock.

  2. App Link Origin Validation
    The payment and account-linking web bridge could benefit from confirmed origin checks to ensure only trusted web content can trigger native payment flows, reducing risk if the web layer is ever compromised.

Technical Context

App Type: AI assistant with health data integration, payments, camera access, and social sharing
Classes Analyzed: iOS binary (symbols analysis)
Third-Party Services: 17 third-party services identified
Context Tags: health, sensitivedata, payments, aiassistant, camera, social

About This Analysis

This security analysis was conducted by CITT (Can I Trust That), an independent security analysis service. We perform static code analysis on iOS applications to help users make informed decisions about app security and privacy.

App Details

Developer: OpenAI
Version: 1.2026.097 (Build 24313104440)
Analysis Date: 2026-04-17
Package: com.openai.chat

Analysis Limitations

  • Static analysis only (code review without running the app)
  • Based on iOS app version 1.2026.097 analyzed on 2026-04-17
  • May not reflect server-side security controls
  • Cannot detect all runtime behaviors
  • Session replay sample rates and Segment routing destinations are configured server-side and were not visible in the binary

Versions & scan history

ScanDateOverall score
#2 (current) 90/100