Skip to main content

Microphone permissions in the Pi Browser and specific Pi apps

Because the Pi Browser functions as a gateway to experimental Web3 tools and third-party applications, it sometimes requires hardware access.

Microphone permissions for the Pi Browser and Pi Network apps are requested to enable voice-based ecosystem features and decentralized applications (dApps).

While the main Pi Network mining app primarily requires network access and occasionally contacts (for your Security Circle), the Pi Browser acts as a Web3 gateway where third-party community applications operate. Because it functions like a standard mobile web browser (such as Chrome or Safari), it requests hardware permissions to fully support those features

Why the Pi Browser and Apps Need Microphone Access

The microphone permission is not used for basic mining or managing your Pi Wallet. Instead, it is utilized for specific interactive features within the ecosystem:

  • Voice Chat in Pi Chatrooms: The Pi Network features native community chatrooms. Some integrated features or future updates allow for voice notes or voice-based communication among Pioneers.
  • Third-Party Web3 dApps: The Pi Browser hosts decentralized utilities built by community developers. If a developer creates a gaming dApp with voice chat, a social media app with audio recording, or a customer service tool, the Pi Browser must have microphone access to pass that capability to the app.
  • Future Biometric or KYC Upgrades: While the standard identity verification (KYC) primarily relies on the camera for liveness checks and ID scanning, some automated verification systems globally utilize audio cues to verify a live human presence.