Repository navigation
feat(ios): ask for consent before sending audio to AssemblyAI - #227
Merged
Merged
Conversation
App Review 5.1.2(i) requires clearly disclosing where personal data goes, third-party AI included, and getting explicit permission first. The listening window now won't open until the user agrees, in a sheet that names AssemblyAI, lists what is sent (the voice while dictating, the text before the cursor, recent dictations, key terms with contact names) and links the privacy policy. Every path to the microphone goes through startListening(), so one gate covers the button, the keyboard's blurt://start and in-app dictation. Consent is versioned (AIConsent): sending something new means a new version, and everyone is asked again. Settings' About section links the privacy policy too. The debug -BlurtStartListening flag grants consent, since scripted runs can't tap through the sheet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nbisht-aai
approved these changes
Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
App Review 5.1.2(i) requires disclosing where personal data goes (third-party AI included) and getting explicit permission first. The iPhone app had no such step.
startListening()(the button, the keyboard'sblurt://start, in-app dictation), so it's checked there.AIConsent): sending something new means a new version, and users are asked again.-BlurtStartListeningflag grants consent so scripted runs keep working.Stacked on #226.
How it was tested
scripts/ios-check.sh: 134/134 tests (3 new forAIConsent),BlurtiOSCorecoverage 96.69%, analyze and periphery clean.Concurrency review of the coordinator change: no issues.
Settings verified in the simulator. The sheet appears once a key is saved; worth a tap-through on review.
I read AGENTS.md and this doesn't reintroduce anything deliberately removed
Docs updated (iOS README, DESIGN.md)
🤖 Generated with Claude Code