Mobile Support

Contact

Report problems in the Pisper issue tracker or email the developer.

Include the Pisper version, operating-system version, device model, selected Runtime mode, and exact error message. Do not include API keys, pairing tokens, private prompts, personal files, contact details, or other sensitive information in a public issue.

Model requests fail

Confirm that the selected provider is reachable, the provider credential is valid, and the model is available to your account. Provider traffic goes directly from your selected Runtime to that provider.

Desktop pairing fails

Confirm that Pisper Desktop is running and remote access is enabled. On the same LAN, allow local-network access in mobile system settings, select the discovered Desktop, and approve the request on Desktop. If discovery is unavailable or the devices are in different locations, scan a newly generated QR code or enter its address, pairing code, and TLS fingerprint manually.

A device capability is unavailable

Enable the capability in Pisper, then grant the corresponding camera, contacts, foreground location, notification, or local-network permission in system settings. Pisper continues to work with reduced functionality when optional permissions are denied.

Delete local data

Delete individual sessions and files in Pisper where available. To remove all app-local data, use the operating system's app storage controls or uninstall Pisper. Data sent to an AI/search provider or stored by a paired Desktop Runtime must be deleted through that provider or Runtime.

Billing

Pisper currently has no subscriptions or in-app purchases. Provider usage and billing are governed by the provider account that you configure.