Deerlight Third-Party Services

1. How to read this notice

This notice identifies the principal third-party categories, triggers, and information involved for Deerlight. 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

• Lumenlan Platform and intelligent services: supply shared identity, authorization, usage management, security records, and model selection. For AI extraction, retrieval, or organization, Deerlight sends the knowledge excerpt, feature category, and usage information needed to complete the request.
• Kite: only after you grant the required permission and request delegation or import does Deerlight exchange project or shelf content, task state, candidates, evidence, results, or write-back records. Authorization can be revoked, but revocation does not erase lawfully retained records or an already imported copy.
• Alibaba Cloud storage: when enabled, stores original documents, attachments, or imported content. Knowledge entries are also kept in Deerlight.
• Public code hosts: after you submit an allowed public repository address, Deerlight requests and imports the selected content. Addresses containing sign-in credentials or pointing to a non-public network are rejected. The host receives ordinary network-request information.
• Compatible tools: Claude, Codex, Kite, or another compatible tool may use relevant capabilities only after receiving project authorization. The tool independently processes information you enter, display, or store there; Deerlight keeps necessary integration action records.

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.