Data handling

Know where
your conversation goes.

A practical overview of audio, captions and account data in the current Parley desktop preview.

Translation audio

Parley sends the selected capture audio to a cloud translation service. In managed mode, audio goes through Parley’s server. In personal API mode, the desktop app connects to your selected provider with your credentials. The provider’s terms and privacy policy govern its handling of audio.

Choose your capture source carefully. A meeting process or system audio source can contain more than the conversation you intend to translate. Get permission from participants before capturing or translating their audio.

Captions and credentials on your computer

Caption history and preferences are stored locally in the desktop app’s private directory. Exporting SRT creates a subtitle file that you control. Personal API credentials are configured in the desktop app, using private configuration or environment variables; this website does not receive your model API keys.

This website

The caption demonstration plays preset text. It does not record audio, access your microphone or call a translation model. Product screenshots use sample conversations and device settings.

Sign-in uses server-issued HttpOnly session cookies. Account balances and orders are retrieved through authenticated, account-scoped endpoints. Hosting and sign-in services necessarily process requests used to operate the site; this page does not claim zero data collection.

Purchases and account access

Purchases and wallet top-ups use the site’s account and checkout pages. The app and website need the same account to recognise credit and the personal API licence. A displayed QR code alone does not confirm payment.

This overview describes current product behavior, rather than promising retention periods or contractual terms that have not been published. Review your selected provider’s policies before sending sensitive audio.

Read the setup guide → View pricing →