Privacy policy
Updated 14 November 2026
- We do not sell data and do not show ads. The app and the site have no analytics or advertising trackers; the site sets no cookies.
- Voice is not recorded on our servers. Messages and the call log are stored on the phones.
- Data is stored on servers in Kazakhstan.
Who is responsible
The CPTT service is operated by IE LinkRO (individual entrepreneur), Republic of Kazakhstan. For questions about your data, write to info@cptt.net.
Sign-in
You sign in with Google (Android) or Apple (iPhone). We keep only the account identifier issued by the provider. We do not keep the account's email, name or photo. No phone number is needed and no SMS is used.
An employee of an organization connects a phone with a code from their administrator, without Google or Apple.
Spaces and devices
A space is a group of people who talk to each other. We keep: your name in the space (you enter it yourself; its members see it), the device number and name, channels and groups, invitations, membership and the administrator role. Communication does not work without them.
Voice, calls and video
Voice and video pass through our servers in real time and are not recorded there. If a space's administrator turns recording on, recordings are kept only on the members' phones and are erased after the period the administrator set. Calls are not recorded.
Messages and files
Messages are stored on the phones of the sender and the recipients. The server holds a text in memory only while delivering it. Files stay in the server's temporary storage until the recipients fetch them, but no longer than the redelivery period (12 hours by default).
Call log
The call log is stored only on your phone.
Device position
Only on Android, only in organization spaces where the administrator turned this feature on, and only with your permission in the phone's system settings. When the dispatch console asks, the phone reports its current position. The server keeps one last position per device: coordinates, accuracy and time. There is no movement history. The position is deleted with the device or when the feature is turned off.
Phone permissions
The app asks only for what communication needs, and only when it is needed:
- Microphone — to talk on the channel and in calls. Your voice is sent only while you transmit.
- Notifications — calls, messages and SOS.
- Camera — video in calls and photos for messages; on iPhone also the invitation QR code.
- Location — only on Android and only if the organization turned positions on, see Device position.
- Nearby devices (Android, Bluetooth) — so that phones of one group standing next to each other do not echo.
- Display over other apps, background work, full-screen notifications (Android) — the floating radio button and calls with the screen off.
- Focus status (iPhone) — if you turned it on in the sound settings: silence the radio while a Focus is on.
Encryption
Voice, video, messages and requests between the app, the browser and the servers travel over encrypted connections (TLS).
Notifications
To wake the app for a call, we keep a notification token from Google (Firebase Cloud Messaging) or Apple (APNs). A notification carries only technical details of the event — no voice and no message text.
Diagnostics
Only if you agreed (asked at first start, withdraw in the settings) and the space allows it. The phone sends a connection log: connection events, network type and carrier, phone model, system and app versions, app crash reports. Coordinates, names and the content of conversations are not included. The log is kept for one day, crash reports for up to 4 days.
Feedback to the developers
If you send feedback in the app, we receive the text, platform, app version, phone model and a random tag. Feedback is not linked to your account or space and is kept for 30 days.
Organization administrators
For sign-in to an organization's web admin we keep the administrator's email, a password hash and second-factor data. Administrator actions are written to the organization's audit log (14 days by default). The web admin uses a session cookie, only for sign-in.
The organization decides whether to turn on recording and device positions, and is responsible for its employees' data.
Payment
Payments are handled by Paddle, the seller and payment agent. Card details and the buyer's email stay with Paddle. We only have the subscription details: number of seats, period, end date.
Where data is stored
The servers holding data are in Kazakhstan (Almaty). Entry nodes in other countries only forward encrypted traffic to the servers and store nothing. Your IP address is used to establish the connection and to protect the service from abuse.
Who receives data
Only those the service cannot work without: Google and Apple — sign-in and notifications; Paddle — payment; the hosting provider — servers. They may process data outside Kazakhstan under their own privacy policies. We do not sell data or share it for advertising.
Retention
The account and space data are kept while the account exists and are deleted when it is deleted — see Delete your CPTT account. The periods for other data are given in the sections above.
Children
CPTT is not intended for children under 13 (under 16 in the EU).
Your rights
You can find out what data about you we keep, correct it or delete it. Your name and devices are changed in the app, and the account is deleted there too. For anything else, write to info@cptt.net.
Changes
We will announce significant changes to this policy on this page and update the date at the top.