AICL · PRIVACY POLICY
Privacy Policy
What information AICL processes, which features send data to cloud services, and how you can make a privacy request.
1. Who is responsible
MingHan Li, based in mainland China, is the operator responsible for personal information processed for AICL’s website, desktop application and related account, AI and community services. Support and privacy contact: 1509310650@qq.com. Legal form and public contact address are to be confirmed (待定).
Paddle is separately responsible for its checkout and transaction processing under the Paddle Privacy Policy. Other providers may have their own responsibilities and policies.
2. Information we process
| Category | Examples and when it is used |
|---|---|
| Account and access | Email address, display name, password authentication information, account identifiers, verification and session records. |
| AI tasks and projects | Prompts, conversation context, code, selected files, reference images, screenshots, generated assets, tool results and relevant task metadata processed for features you use. |
| Usage and purchases | Task and model usage, credit grants and deductions, order references, purchase and refund status, and payment-related information needed to fulfil and reconcile an order. Payment-card details are entered with the checkout provider. |
| Community material | Your public display name, published descriptions and assets, tags, and any shared source bundle, plus interactions with that content. |
| Technical and support data | IP address, browser or device information, app version, events, errors, service logs, correspondence, and attachments or diagnostic bundles you submit. A diagnostic bundle may include conversation logs when you explicitly select those sessions. |
The desktop application stores project files, settings and session material locally. Cloud AI, search, publishing and support features also transmit the relevant data to AICL servers and service providers. Running a desktop application does not mean all processing stays on your device.
Some information comes from service providers, such as a payment confirmation, or from another user when they publish or share material containing your information. Do not submit secrets or personal data you are not authorised to disclose.
3. Purposes and legal bases
AICL does not use your inputs, images, source code or generated results to train or fine-tune AI models. To maintain and improve AICL, we use necessary operational metrics and feedback or diagnostic attachments you actively submit. We do not routinely inspect complete private works, conversations, images or source projects for product improvement. Support staff may review the materials you select to reproduce and resolve the reported issue; diagnostic attachments may include selected conversation logs. Optional analytics is subject to the choices below. The selected retention period for diagnostics is 90 days after issue closure, subject to the exceptions and implementation status in section 6. Upstream providers' practices are a separate verification item described below.
We use information to create and secure accounts; provide AI, project and community features; meter and deliver paid usage; resolve errors and support requests; investigate abuse; and meet applicable legal obligations.
Where a legal basis is required, providing requested services and fulfilling orders relies on performance of a contract; necessary security and service maintenance may rely on legitimate interests; records needed for legal duties rely on those duties; and processing requiring consent will rely on that consent. Consent controls for optional analytics must be completed before this draft takes effect; the current testing configuration is described below.
Account, task and purchase information necessary for a requested feature is needed to supply that feature. You can choose not to submit optional material, but withholding necessary information may prevent us from completing the corresponding request. A materially different purpose, including any new model-training use of your content, requires an appropriate basis and notice, and consent where required.
4. Recipients and AI services
The following list reflects the deployed configuration checked on 18 October 2026 and the planned paid-beta models. Only the providers involved in a feature receive its relevant information.
- Hosting: Alibaba Cloud infrastructure in Singapore hosts AICL's cloud account, database, storage and AI gateway services. The public website uses Vercel. These services process the account, content, network and operational information needed to serve their features.
- Text AI: the paid-beta plan uses DeepSeek, which receives the prompts, conversation context and relevant code or files needed for the request.
- Image AI: Seedream through ByteDance's Volcengine receives image prompts and any submitted reference images. The configured service endpoint is in Beijing.
- 3D and texturing: Meshy receives the prompts, reference images and model or texture files relevant to the requested operation. The planned texturing model is Meshy 6 Lite.
- Existing test routes: the current test configuration also retains Google/Gemini and Kimi through a Meshy-operated AI gateway, and other Meshy model routes. The planned paid-beta routes have not yet been applied to every account. Those providers may process data for accounts or features using those routes.
- Search: AICL's search service forwards requested search terms to Brave and returns search results.
- Analytics: product events are stored in AICL's database and sent to the configured PostHog US service. These may include an account identifier, app or device information and event properties. Automatic capture and session replay are disabled in the checked configuration.
- Payments: Paddle processes checkout, order, fraud-prevention, tax, refund and dispute information for purchases made through Paddle.
- Email and support: AICL receives correspondence, selected diagnostics and attachments you submit. The public contact address is 1509310650@qq.com, using Tencent QQ Mail; messages and attachments sent there are processed through that mail service. Alibaba Cloud DirectMail is configured as an email option, but production sending was not verified.
- Publication and legal requests: content you publish is made available to its audience. Information may also be disclosed where legally required or necessary to address a valid rights claim or abuse.
Provider-specific retention, model-training use, processing locations beyond those identified above and applicable contractual safeguards remain to be confirmed (待定). This draft does not promise that every provider deletes requests immediately or excludes all submitted data from training.
5. Local storage, cookies and analytics
The website stores a language preference locally. Account and desktop features use authentication storage and local preferences. Hosting providers may keep necessary request logs.
The paid-beta policy is to enable optional analytics only after the required consent flow is in place. Where prior consent is required, analytics must remain off until the user agrees. Users must be able to decline or withdraw optional analytics without losing the core service. Necessary authentication, billing and security processing is explained separately and is not optional product analytics.
Implementation status: in the configuration checked on 18 October 2026, AICL event storage and PostHog analytics were enabled, while automatic capture and session replay were disabled. Existing opt-out controls do not establish prior consent. The new consent flow still requires implementation and verification before this policy takes effect. AICL's own raw analytics retention target is 30 days; the actual PostHog plan and deletion capabilities remain to be confirmed.
Clearing browser or app storage can reset preferences or sign you out. It does not delete information already held by AICL or a provider.
6. Retention and deletion
The following retention rules have been selected for the paid beta. They distinguish local files, temporary delivery, published works and operational records.
| Data | Selected retention rule |
|---|---|
| Local projects, conversations and exports | You control their storage and deletion on your device. Account deletion does not automatically erase local work. |
| Temporary cloud delivery files | 30 days after task completion, then cleanup. This includes files held for delivery and download retries. Keep your own copy. |
| Published community works | Hosted while published. Withdrawal stops new public access immediately and starts cleanup of AICL's primary storage, with a target of 30 days. Copies already downloaded and existing licences are handled separately. |
| Private request content | We do not retain full private requests indefinitely by default. Local work remains on your device; cloud processing and task recovery use only necessary content. Temporary delivery and selected support materials follow their own rules. |
| Ordinary operational and error logs | 30 days from recording, with secrets and full private content excluded. Necessary incident evidence may be isolated for a documented longer period. |
| Security and anti-abuse logs | 90 days from recording, subject to applicable duties and necessary investigations. |
| AICL's optional analytics events | 30 days from recording, collected only under the applicable consent rules. PostHog retention and deletion must be verified separately for the actual plan. |
| Support messages and selected diagnostic attachments | 90 days after the issue is closed, unless necessary material must remain for a dispute or legal duty. |
| Account data | Kept while needed for the account. A verified erasure request removes user-facing access promptly, with primary-system cleanup targeted within 30 days, subject to applicable legal deadlines and exceptions. |
| Credit and transaction records | Purchased credits are not erased merely due to inactivity. Necessary payment, tax, reconciliation and dispute records follow applicable retention duties; those record-specific periods are still being verified. |
Daily local database and usage-ledger backups currently have a 14-day rotation setting. Deleted data must leave backups through rotation after primary-system cleanup; restoration must reapply deletion records. This is not a promise that every copy disappears 14 days after a request. File backups and third-party copies require separate verification.
To request access or erasure, contact 1509310650@qq.com. Deleting a local conversation, uninstalling the app or signing out does not erase all cloud and provider data. We may verify ownership proportionately and retain records legally required to remain. Provider deletion requests must follow the relevant provider's process.
Implementation status: these are confirmed launch targets, not a claim that cleanup is already operating. Temporary-file cleanup, community withdrawal, full account erasure, log and support cleanup, backup deletion replay and provider handling still require implementation and verification before this draft takes effect. Exact task-recovery fields, third-party retention and statutory record periods remain to be confirmed (待定). The current account-deletion control must not be treated as complete cloud-data erasure.
7. International processing
The operator is based in mainland China; the public contact address remains to be confirmed (待定). Current cloud hosting is in Singapore; the configured Seedream service endpoint is in mainland China, and PostHog uses its US service. Other AI, hosting, payment and email providers may process information in additional locations associated with the service used.
A service endpoint does not by itself establish every storage or support-access location. Provider agreements, training and retention settings, applicable transfer safeguards and any legally required representative or additional contact details are to be confirmed (待定). Required safeguards must be in place before processing that requires them begins.
8. Your rights and requests
Depending on applicable law, you may have rights to access, correct, delete or receive a copy of your personal data; restrict or object to certain processing; withdraw consent without affecting earlier lawful processing; and complain to a competent data-protection authority.
Send requests to 1509310650@qq.com, identifying the account and the request. We may seek proportionate information to verify ownership and will respond within applicable legal time limits. Please do not email passwords or full payment-card details. Contact Paddle directly for data it controls as the transaction provider.
9. Age, security and policy changes
The initial overseas paid test is intended only for adults aged 18 or older. If you believe a person under 18 has provided personal information for that test, contact us so we can investigate and address it.
We use access controls and technical protections appropriate to the service, but no system can guarantee complete security. Review the files, screenshots and logs you choose to share.
We will date policy updates and provide notice or seek consent for material changes where required. The Terms of Service and Refund Policy explain the related service and purchase arrangements.