contacts.addContact (MTProto / TDLib): This method allows adding a user to the contact list, even if their phone number isn’t initially known (e.g., if you found them by username).
It has an optional add_phone_privacy_exception flag. If this flag is set to true, it signals to the other user that the current user wishes to share their phone number, potentially triggering a UI prompt on the other user’s official client to “add contact and share number.” This is still subject to the other user’s explicit action and privacy settings.
Key Privacy Considerations for Custom Client Developers:
Transparency with Users: Be completely transparent with your users about what data your custom client collects, why, and how it’s used. This includes clear telegram number database explanations about accessing their phone’s contacts and how other users’ phone numbers might be handled.
>Adherence to Telegram’s Terms of Service: Custom clients must comply with Telegram’s API Terms of Service, which strictly prohibit spam, abuse, and unauthorized data collection. Misuse can lead to API access revocation and account bans.
Data Security: If your custom client stores any! user phone numbers (or other personal data) on its own servers, you are solely responsible for implementing robust security! measures (encryption, access control, regular audits) to protect that data from breaches.
Compliance with Regulations:
Ensure your custom client the growing relevance of sms communication in business complies with all relevant data protection regulations (e.g., GDPR, CCPA) concerning the collection, storage! and processing of personal! identifiable information (PII) like phone numbers. This includes providing users with rights to book your list access, rectify! and erase their data. It is against Telegram’s policies and often illegal to build clients that attempt to scrape phone numbers from groups! channels! or public profiles without explicit consent from the individuals whose numbers are being collected.