Lumenlan Kite Third-Party Services

1. How to read this notice

This notice identifies the principal third-party categories, triggers, and information involved for Lumenlan Kite. A relevant third party participates only when you choose the corresponding sign-in, payment, notification, storage, AI, import, delegation, or integration feature.

Vendors and services may change by platform, region, availability, and product settings. A material change receives an additional notice at the relevant feature.

2. Principal current third parties and purposes

• Local coding agents and their vendors: Claude Code, Codex, OpenCode, GitHub Copilot CLI, Qoder, Trae, Kimi Code, and similar tools run on your device and may send prompts, context, or usage under your vendor account, subscription, configuration, and privacy terms. Kite does not represent those vendors or obtain a subscription for you.
• Lumenlan Platform: supplies shared account, membership, orders, notifications, and cross-product authorization. Kite submits account and event information needed for fulfilment and notifications; Platform operational statistics do not receive terminal content.
• Alibaba Cloud storage: stores content and necessary information you select when cloud archives, uploads, downloads, or temporary transfer are enabled. Retention depends on product benefits, your settings, transfer state, and security requirements.
• Feishu, WeCom, DingTalk, or a custom notification service: only after you configure notifications does Kite send the selected short notification and session locator. The destination then processes it under its rules. Do not expose a notification secret or configure an untrusted destination.
• Voice transcription provider: audio or a necessary excerpt is sent only if the feature is configured, the interface identifies the provider, and you expressly consent and use it. It must remain disabled without a trustworthy configured provider.

3. Your choices and controls

• If you do not select a third-party sign-in, payment, notification, AI model, repository import, or delegation, that choice does not trigger the corresponding transfer, though the dependent feature may be unavailable.
• Revoke an unnecessary authorization, push permission, subscription, or integration credential in the Lumenlan product, device OS, third-party account, or purchase channel. Earlier transaction, security, or audit records may still be lawfully retained.
• Before sending content to an AI, agent, notification service, public repository, or sharing recipient, remove unnecessary personal data, secrets, and trade secrets and verify the destination, permission range, and possible processing region.
• Third-party availability, fees, and independent processing are governed by their terms. Lumenlan reasonably controls processors it selects but cannot manage a personal account or local tool that you deliberately connect on your behalf.

4. International transfer, security, and contact

A third party you select may process data internationally. Where applicable, we use minimization, access control, transport protection, and necessary contractual measures and obtain separate consent before enablement when required. Also read the terms and privacy notice presented by that third party.

Questions about this notice or a third-party data flow: privacy@lumenlan.com. Service faults: support@lumenlan.com.