Privacy

XingDun IM Privacy Policy

Version: 2026.07.13 Effective date: July 13, 2026

This Policy explains the categories, purposes, methods, retention rules, and third-party services involved when XingDun IM processes personal information to provide enterprise instant messaging services, as well as the rights available to you. We follow the principles of specific purpose, minimum necessity, openness, transparency, and security protection.

1. Scope and Roles

This Policy applies to the XingDun IM iOS client and supporting services. The operator is responsible for processing personal information within the scope of product accounts, core communications capabilities, and platform security. When an enterprise independently determines how member information is processed for human resources or internal administration, that enterprise must separately fulfill its obligations as a personal information processor.

Information that can no longer identify an individual after anonymization is not personal information. We will not disable basic functions unrelated to a non-essential permission merely because you refuse that permission.

2. Accounts, Profiles, and Enterprise Relationships

  • Account identifiers: username, user ID, Tencent UserID, enterprise code, and any phone number or email address you choose to bind, used for registration, sign-in, and identity recognition.
  • Profile information: nickname, avatar, signature, gender, date of birth, department, and information you voluntarily provide, used for display and the enterprise contact directory.
  • Authentication information: password hashes, business sign-in credentials, UserSig, and credential versions, used to verify identity and establish secure sessions. Sensitive client credentials are stored in the system Keychain.
  • Enterprise relationships: enterprise, department, role, friends, block list, groups, and customer-service relationships, used to control communications and business permissions.

3. Communications, Collaboration, and User Content

When you actively use chats, groups, location sharing, red packets, calls, workbench features, feedback, or reporting, we process text, emoji, images, audio, video, locations, files, amounts and receipt records, call status, report evidence, and message metadata. This processing supports transmission, synchronization, display, read receipts, favorites and pinned items, search, security audits, dispute handling, and troubleshooting.

Message recipients and authorized enterprise members may view content you send as permitted by the relevant feature. Deleting a local message does not necessarily delete copies retained by recipients or audit records retained as required by law.

4. Device, Network, and Log Information

  • Device model, operating system and app version, Bundle ID, language, and network connection status, used for compatibility, routing, and connection optimization.
  • IP address, request time, API results, sign-in and device status, crash reports, and error logs, used for security, auditing, and troubleshooting.
  • APNs device token, TIMPush registration identifier, and VoIP push identifier, used for offline message and incoming-call notifications and not for advertising tracking.
  • Logs follow the minimum-necessary principle. Passwords, UserSig, JWT, phone numbers, and similar data are hidden or masked.

5. System Permissions and On-Device Capabilities

  • Notifications: receive new-message, call, and business alerts.
  • Camera and microphone: capture chat media, record voice messages, and make audio or video calls.
  • Photo library: select or save images and videos in chats. Files are accessed through the system file picker only within the scope you select.
  • Face ID and local network: the current version does not call Face ID or local-network discovery APIs and does not request those permissions. If these features are introduced later, we will first provide a clear purpose and request authorization separately.
  • Permissions are requested only when the corresponding feature is activated and can be disabled in iOS Settings. Disabling a permission affects only related features.

6. Purposes and Legal Bases for Processing

  • Perform the User Agreement and provide registration, sign-in, enterprise member administration, messaging, calls, notifications, and collaboration.
  • Use optional permissions, process sensitive personal information, or provide non-essential features after obtaining consent or separate consent where required.
  • Fulfill legal obligations, protect account, communication, and system security, and handle reports, abuse, disputes, and regulatory requirements.
  • Protect an individual’s life, health, or property in an emergency, or process information in other circumstances permitted by law.

7. Entrusted Processing, Sharing, and Third-Party SDKs

To provide core capabilities, we use Tencent Cloud Instant Messaging and TIMPush; Tencent Cloud RTC Room Engine, TXLiteAVSDK, and TUIVoIPExtension; Apple APNs; and open-source components that operate only on the device or through specified resource addresses. Depending on the feature, these services process user identifiers, device and network information, message transmission data, push identifiers, audio and video streams, and minimum incoming-call routing information. The first release does not enable call recording and does not place UserSig, secret keys, or message bodies in offline push notifications.

Tencent Cloud Computing (Beijing) Co., Ltd. provides Tencent Cloud Instant Messaging and TIMPush. Shenzhen Tencent Computer Systems Company Limited develops and provides RTC Room Engine, TXLiteAVSDK, and related audio and video components. See Me > About XingDun IM > Third-Party SDK Statement for complete provider names, purposes, data boundaries, and links to applicable rules.

Except where consent is not required by law, we do not provide personal information to unrelated third parties, publicly disclose it, or sell it. If a merger, division, or change of operator occurs, we will identify the recipient and require continued protection. If the processing purpose changes, we will obtain renewed consent.

8. Storage Location and Retention

Personal information collected and generated in the People’s Republic of China is generally stored within China. If cross-border provision becomes necessary in the future, we will identify the overseas recipient, purpose, method, information categories, and rights channel, and complete separate-consent and other legally required procedures.

Account and enterprise profile information is retained while the account is active and for the period needed to complete deactivation. Messages and collaboration records are retained according to enterprise configurations, communication-service rules, and dispute-handling needs. Security, sign-in, and operational logs are retained for periods required by law and risk control. Local caches are removed within the implemented boundaries when sign-out, deactivation, or cleanup features are triggered. Information is deleted or anonymized when the applicable period expires.

9. Security Protection and Incident Response

  • We use transport protection, access controls, credential isolation, Keychain storage, log masking, permission tiers, and audit measures.
  • Server-side secrets, including Tencent SecretKey and callback secrets, are not included in the iOS client. UserSig is issued by the server for each session.
  • If a security incident may affect your rights and interests, we will initiate a response, control the impact, and provide information about the incident, potential effects, and remedial measures as required by law.

10. Your Personal Information Rights

You may use Profile, Device Management, Privacy & Agreements, messaging features, and Account Security to access, correct, copy, or delete relevant information, withdraw consent, manage system permissions, and request account deactivation. If an operation is unavailable directly, or if you need to restrict processing, transfer a copy, or request an explanation of a rule, submit a request through Me > Help & Feedback.

We may verify your identity to protect account security. Requests will be handled within the period required by law. If a request affects another person’s rights, data lawfully administered by an enterprise, or a legal retention obligation, we will explain the result or why the request cannot be completed.

11. Withdrawal of Consent and Account Deactivation

Withdrawing consent does not affect the validity of processing performed on the basis of consent before withdrawal. After withdrawal, the client signs out of instant messaging, stops notification registration, and clears local sessions. You must provide consent again before resuming use.

Account deactivation is different from withdrawing consent. Deactivation disables all devices, removes the active business account, and begins a controlled recovery and deletion process. Messages already received by other users, enterprise records, and data retained as required by law are not necessarily deleted immediately. See the XingDun IM Account Deactivation Rules for details.

12. Minors and Sensitive Personal Information

Information relating to children under 14 is sensitive personal information. XingDun IM is primarily intended for adults in enterprises and does not permit children to register independently. Where it is genuinely necessary to process children’s information or sensitive personal information such as identity documents, financial accounts, precise location, health data, or biometric data, the processing must have a specific purpose, be strictly necessary, use enhanced protection, and obtain separate consent or guardian consent as required by law. See the dedicated rules for details.

13. Updates and Contact

If the processing purposes, information categories, third-party services, or methods for exercising rights change materially, we will update the Policy version and request renewed consent where required by law. If you decline the new version, services dependent on the relevant processing will no longer be available.

You may review the version and consent record at Me > Privacy & Agreements and submit privacy inquiries, complaints, deletion or deactivation requests, or minor-protection requests through Me > Help & Feedback. The operator’s legal name, registered address, and other formal contact details are those published on the About page, official website, or in an enterprise notice.