Lingying Third-party Information Processing Disclosure
Version: 2026-10-04
Effective date: The date this version is first published on jusi.pro
Personal information controller: 北京燕婉科技有限公司
Contact: In-app “Help & tickets”; yanwancy@gmail.com
This disclosure supplements the Lingying Privacy Policy. A category listing does not authorize disclosure to every provider. Unused features do not process corresponding data merely because they appear here.
1. Service categories and data scope
| Category | Trigger and necessary data | Purpose, role and location |
|---|---|---|
| Cloud infrastructure | Account, web workspace, hosting and support use: accounts, conversations, selected attachments, projects, scheduled tasks, tickets and operational records | Our controlled core services/storage currently operate in Shanghai, China. Infrastructure participates in entrusted processing; this does not establish that model or backup chains are all in Shanghai. |
| Alibaba Cloud SMS | Code requests: receiving number, verification code and delivery/verification status | Login and account-security SMS; US numbers involve international routes. Receiving locations and retention depend on the actual SMS product and route. |
| Model gateways and upstream model services | AI requests: prompts, necessary context, model parameters, selected attachments/extracted content, tool output and authorized screens | Conversation, code, image and title generation; requests may pass through gateways to upstream services. Locations, retention and training rules require verification by recipient. Product display names do not describe the full chain. |
| Alipay (China) Network Technology Co., Ltd. | Purchases and lawful transaction processing: order identifiers, amounts, product descriptions, payment/refund results; independent checkout authentication | CNY payments, original-channel refunds and reconciliation. Independent payment services follow Alipay terms and privacy rules. Lingying does not send chats, source code or screens to payment interfaces. |
| PayPal (the buyer’s provider depends on the applicable PayPal agreement; our cross-border merchant account agreement is with PayPal Pte. Ltd.) | When choosing PayPal for a USD membership: merchant order references, product description, USD amount, payment and verification results; checkout authentication is collected independently by PayPal | One-time USD membership payments, verification, fulfillment and reconciliation, involving an independent overseas payment provider. See the PayPal Privacy Statement and applicable checkout agreement. Lingying does not send chats, source code or screens to payment interfaces, or collect full card details, payment passwords or payment verification codes. |
| Mail services | Emails you send to support: address, body and voluntary attachments | Questions, complaints and rights requests. The Gmail address may involve overseas processing; in-app tickets are an alternative. |
| Browser/OS notification capability | After affirmative permission: task identifier, type, completion status and opening destination | Completion alerts without full chat, attachment or code bodies. Current services do not promise continuing push after the page/program exits. |
| User-enabled plugins, browser pages and external services | Authorized connections and tasks: necessary page/file content, tool results and connection information | Scope follows the selected service, permissions and task. Independent services have their own rules. Review the actual provider and authorization when enabling. |
2. Recipient details and rights
2.1 We must provide legally required recipient identity, contact, location, purpose, role and duration information for the actual scenario. Independent or overseas processing requires specific notice and applicable procedures; accepting this disclosure does not replace separate consent required by law.
2.2 Ask through tickets or email about recipients for a particular task, processing rules and rights assistance. Refusing optional third parties affects dependent functions only. Stop tasks, revoke plugins or OS permissions as available; earlier lawful processing and statutory retention follow the Privacy Policy.
2.3 Material recipient or scope changes require lawful updates and notice. Updating this list does not replace required separate or renewed consent. This disclosure does not authorize access to an unselected whole local workspace.