Peeper accesses the microphone only after you start listening. The app records short three-second audio samples and sends them over an encrypted HTTPS connection to the PeeperLab service for identification. The server analyzes each temporary audio file and deletes that file after the prediction is complete. Ordinary predictions do not retain the submitted audio. Peeper does not access the microphone while the app is closed.

With permission, Peeper uses the device location while the app is open to select an appropriate regional model. The precise latitude and longitude remain on the device. The selected region identifier, such as Northeast or Oregon, may accompany an analysis request.

Emailing or sharing results is always initiated by you and uses the sharing or mail tools on your device. If you explicitly report an incorrect detection or confirm an observation, PeeperLab may retain limited diagnostic metadata such as the predicted species, confidence, app version, region, and time. Evaluation polling is disabled in beta and production builds.

Expo supports application builds and updates, and ngrok carries encrypted traffic to the active PeeperLab host. Those providers may process ordinary network and device metadata only as needed to provide their services, under protections consistent with this policy and their own privacy commitments. Peeper itself does not maintain user profiles or a history of your precise locations.

You can stop audio collection by ending a listening session and can revoke microphone or location access at any time in iOS Settings. Ordinary audio samples are deleted automatically after each prediction, so there is no account-based audio history to delete. To ask about or request deletion of diagnostic metadata submitted through an explicit feedback action, contact Richard at the address below. You may also request assistance with any privacy question by email.

Questions, correction requests, and privacy concerns can be sent directly to Richard Podolsky.