Microphone permission is not a blank check
An app should request microphone access in context and explain what happens when the mic is active. A visible listening state and a clear pause control reduce ambiguity.
Declining permission should not trap the user. Text fallback and a later path to enable voice are practical alternatives.
Ask whether audio and transcripts are retained
Live processing, raw recording and transcript storage are different data practices. A privacy policy should state which one occurs, why, for how long and with which service providers.
Campaign memory may need structured summaries, but that does not automatically require indefinite storage of raw audio.
Likeness needs separate consent
Turning a selfie into a fantasy character should be opt-in, race-aware and reversible. The source photo's deletion policy should be explained before upload, and the player should be able to remove the generated likeness later.
A preview can demonstrate the feature before purchase without uploading or processing the user's real photo.
Account controls should be complete
Look for account deletion, data export or access instructions, purchase restoration and a human support route. No behavioral advertising or cross-app tracking is a meaningful distinction for an intimate creative product.
Living Party provides Apple-only account identity, optional likeness, captions and text fallback, and publishes its current data practices on the product privacy page.
Frequently asked questions
Does a voice RPG always record audio?
No. Apps may stream audio for live processing without retaining a recording, but each product's privacy policy should explain its actual practice.
Should a selfie be required?
No. Character likeness is best treated as a separate optional feature with clear consent and deletion controls.
Can I play without microphone access?
A product with text fallback can support play without voice, although the experience may differ.