Press. Speak.
Stay connected.

Data handled by PTT Talk

Account and team data includes your email address, invitation and recovery status, administrator status, channel memberships and roles, device display names, and random service identifiers.

Security data includes public identity keys and prekeys, hashed access and invitation tokens, device status, key and membership epochs, safety-number material, and security audit events. Private encryption keys remain in the operating system's protected storage on the device.

Push and delivery data includes Apple or Google push tokens, encrypted mailbox and chat envelopes, delivery status, and timestamps. Push messages contain only a privacy-minimized wake signal; they do not contain voice audio, email addresses, channel names, message text, filenames, or captions.

The app uses the microphone only while you actively transmit or record a voice note. Live voice, text, files, voice notes, and video are encrypted on the sending device. Relays and object storage receive ciphertext, not plaintext content or decryption keys.

Operational data includes IP addresses and network source tuples used to route traffic and reject forged packets; floor, presence, relay, authentication, error, and rate-limit events; timestamps; service health; and aggregate operational counts. PTT Talk's supported metrics and support exports omit email addresses, raw account, device, mailbox, and channel identifiers, access tokens, encryption keys, and audio contents.

How data is used

PTT Talk uses this data to authenticate invited members, link or revoke up to two independently keyed devices, deliver encrypted voice, chat, attachments, and history, enforce channel membership and floor control, send privacy-minimized notifications, recover accounts with administrator approval, prevent abuse, diagnose failures, back up the instance, and maintain service security. It is not used for advertising or tracking.

Storage, retention, and recipients

Account, membership, device, and audit records are stored by the Instance Operator. Encrypted history and attachments are retained on the server for the channel's operator-selected period, from 1 to 365 days. Local encrypted history and attachment caches are limited to 30 days and 1 GB per device. Newly linked devices can receive future communications only and cannot retrieve earlier attachments or history.

Data is disclosed only as needed to provide the service: to the Instance Operator and its hosting, storage, email, backup, and network providers; to Apple or Google for privacy-minimized push delivery; and to authorized members' devices for the channels to which they belong. Network and relay operators can observe addresses, timing, and traffic volume even though communication content is encrypted. The software does not provide content to PTT Talk's developers.

The Instance Operator selects where the service is hosted. Data may therefore be processed in the countries where the operator and its providers run their systems. Server backups may retain deleted records until the operator's backup cycle expires.

Your choices and deletion

You may stop microphone, photo-library, or notification access in system settings. You may revoke a linked device from the app; revocation removes that device's server access, and deleting the app removes its local keys and local history.

You can request deletion of your account and associated server data from the Device section in the app, or contact your Instance Operator or administrator. Deletion removes the member from all channels, revokes the member's devices, de-identifies the account email, and deletes account delivery and key material. Security audit records, shared encrypted channel history, legal records, and backups may remain for their applicable retention periods. Removing a member rotates affected channel key epochs. Previously delivered ciphertext or data stored on other members' devices cannot be remotely erased by the server. If you cannot reach the operator, use the public project issue tracker linked below.

Security

PTT Talk uses end-to-end encryption, protected device key storage, authenticated transport, access controls, and replay and source validation. No security measure is perfect. If you believe an account, device, or instance has been compromised, contact the Instance Operator promptly so it can revoke access and rotate affected keys.

Children

PTT Talk is intended for private organizations and is not directed to children under 13. Instance Operators are responsible for choosing eligible members and for any additional consent requirements that apply to their organization.

Changes and contact

This policy may change as the product or applicable requirements change. The effective date above identifies the current version. Privacy and security questions should be sent to the administrator of your PTT Talk instance. Product questions and reproducible bugs may be opened in the public PTT Talk issue tracker. Security vulnerabilities must be reported privately through the repository's Security tab, not in a public issue.