siavash K.
I stopped using this service during onboarding
I stopped using this service during onboarding because the identity verification requirements were far too invasive for the level of protection offered in return The verification flow appeared to require extremely sensitive personal data, including biometric data such as facial scans, and potentially other telecom/device-related identifiers. Data at this level is not ordinary KYC information. If such information is ever leaked, mishandled, or exposed, the consequences for a person can be severe and long-lasting. You can replace a password. You cannot replace your face, biometric profile, or deeply linked device/subscriber data What makes this even worse is that the legal framework around this process seems heavily one-sided. The terms appear to impose broad limitations of liability, allow extensive third-party processing and sharing, cap damages at a very small amount relative to the sensitivity of the data involved, and also remove the possibility of class action relief. In practical terms, users are asked to assume extraordinary privacy and security risk, while the companies collecting and processing that data accept very little meaningful responsibility if something goes wrong That is not a fair trade. Asking people to hand over some of the most sensitive data they have, under terms like these, just so they can access a paid telecom service, is not just unreasonable — it is absurd I strongly encourage anyone considering this service to carefully read the verification terms, privacy policy, liability limitations, and dispute clauses before submitting any personal data ##### Replay Update ##### I am not arguing that you should not collect KYC data. If telecom regulations require identity verification, then collect what is legitimately necessary. That is not the core issue The real issue is accountability If a company chooses to collect highly sensitive personal data especially biometric data and other deeply identifying information then its legal responsibility should be proportionate to the sensitivity of that data. You cannot require users to hand over data they can never change, while at the same time limiting your liability to a trivial amount, allowing broad third-party sharing and processing, and stripping users of meaningful legal recourse such as collective action A company cannot reasonably say: “We are required to collect this level of data, we may share it with multiple parties involved in the process, and if something goes wrong your remedies are minimal.” That is not balanced risk allocation. That is an attempt to transfer nearly all of the downside to the user while retaining nearly all of the operational discretion for the company and its vendors. Responsibility must match the gravity of the data being collected. If you collect ordinary KYC information, that is one thing. If you collect biometric identifiers and other highly sensitive verification data, then the duty of care and the consequences for misuse, exposure, leakage, or mishandling should be correspondingly serious The point is simple: if you require people to assume extraordinary privacy and security risk, then you should also be willing to assume extraordinary responsibility when that risk materializes. Anything less is not a fair bargain!
Response from TelnyxApr 1, 2026
Hi Siavash, Thank you for sharing your concerns. Identity verification is a regulatory requirement across the telecom industry — carriers are required to verify the identity of customers purchasing phone numbers to prevent fraud, robocalling, and other abuse. This isn't unique to Telnyx. That said, your feedback about the transparency of verification terms is valuable. We take data privacy seriously and work with industry-standard, SOC 2-compliant verification partners. All biometric data used during verification is processed in accordance with applicable privacy laws, including BIPA and GDPR where relevant, and is not retained after verification is complete. We appreciate you taking the time to share this perspective, and we'll pass your feedback along to our product and compliance teams.



