Skip to content
AI Voice Agents
AI Voice Agents10 min0 views

iOS App Store Privacy Disclosures for AI Voice (2026): Guideline 5.1.2(i)

Apple's November 2025 update to App Review Guidelines added explicit third-party AI disclosure requirements. Here is what AI voice agent apps must include in 2026.

Apple updated guideline 5.1.2(i) in November 2025 to require explicit disclosure when personal data is shared with third-party AI. As of 2026, every AI voice agent app on the App Store has to declare what data goes to which AI provider — and obtain explicit user consent.

Background

Apple's App Review Guidelines have always required disclosure when sharing personal data with third parties. The November 2025 update to 5.1.2(i) makes the AI clause explicit: "You must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so." Apple does not define "third-party AI" precisely, so developers must interpret broadly: GPT, Claude, Gemini, Whisper, ElevenLabs, Deepgram, AssemblyAI, and any service that processes user data through models.

In addition, Apple's Privacy Nutrition Labels (the App Store privacy section) added more data-type options in 2026 and made third-party SDK signatures + privacy manifests mandatory for many SDKs. AI voice agent apps must populate the label honestly: voice recordings, transcripts, contact info, and audio metadata are all in scope.

Architecture

```mermaid flowchart LR User[User] -- consent --> App[iOS App] App -- data flow --> Manifest[Privacy Manifest] Manifest --> AppStore[App Store Review] App -- voice/transcript --> AI[Third-Party AI Provider] App -- declare --> NutritionLabel[Privacy Nutrition Label] ```

Hear it before you finish reading

Talk to a live CallSphere AI voice agent in your browser — 60 seconds, no signup.

Try Live Demo →

CallSphere implementation

CallSphere's iOS clients across the six verticals (real estate, healthcare, behavioral health, legal, salon, insurance) include explicit per-feature consent flows:

  • Real Estate (OneRoof) — On first call attempt, the iOS client surfaces a sheet listing exactly what audio leaves the device and to which providers (Pion Go gateway 1.23 → NATS → 6-container pod with CRM, MLS, calendar, SMS, audit, transcript). See /industries/real-estate.
  • Healthcare — Same plus a HIPAA-specific BAA disclosure and explicit "PHI may be transmitted" consent. See /industries/healthcare and /lp/healthcare.
  • /demo browser path — Browser cookie banners cover the same ground. See /demo and /privacy.

37 agents · 90+ tools · 115+ DB tables · 6 verticals · HIPAA + SOC 2 · $149/$499/$1499 · 14-day /trial · 22% affiliate at /affiliate.

Build steps with code

```xml

NSPrivacyAccessedAPITypes NSPrivacyCollectedDataTypes NSPrivacyCollectedDataType NSPrivacyCollectedDataTypeAudioData NSPrivacyCollectedDataTypeLinked NSPrivacyCollectedDataTypeTracking NSPrivacyCollectedDataTypePurposes NSPrivacyCollectedDataTypePurposeAppFunctionality \`\`\`

```swift // Surface explicit consent UI before first AI call func ensureAIConsent() async -> Bool { if UserDefaults.standard.bool(forKey: "ai_consent_v2") { return true } let consent = await AIConsentSheet.present( providers: ["OpenAI Realtime (USA)", "Internal CallSphere AI Pod"], dataTypes: [.voice, .transcript, .contactName]) if consent { UserDefaults.standard.set(true, forKey: "ai_consent_v2") } return consent } ```

Pitfalls

  • Buried disclosure inside Terms of Service — Apple now requires the AI disclosure to be specifically visible at the consent moment, not in fine print.
  • Outdated Privacy Nutrition Label — If you add a new AI provider, you must update the label before the next submission or risk rejection.
  • Missing PrivacyInfo.xcprivacy — Required for many SDKs as of 2026; Xcode 15+ will warn.
  • Tracking-related domains — If you use third-party analytics that the AI provider also uses, treat as Tracking and obtain ATT consent.
  • Children's app categories — Heightened review for any AI on apps targeting under-13 users.

FAQ

Does the rule apply to first-party AI? No — only third-party AI. If you self-host the model on your own VPC it counts as first-party.

Still reading? Stop comparing — try CallSphere live.

CallSphere ships complete AI voice agents per industry — 14 tools for healthcare, 10 agents for real estate, 4 specialists for salons. See how it actually handles a call before you book a demo.

What about anonymous voice samples? If they could be re-identified through voice biometrics, treat as personal data.

Does Whisper running on-device count? No — purely on-device inference does not trigger 5.1.2(i).

Is consent required every call? No — once per material change in providers or data types.

Can I share voice samples with multiple AI providers? Yes if explicitly disclosed and consented.

Sources

See CallSphere's privacy practice at /privacy, try the /demo, or start a /trial.

Share

Try CallSphere AI Voice Agents

See how AI voice agents work for your industry. Live demo available -- no signup required.