Anycubic Forge Console Privacy Policy

Convenience translation. If this English translation differs from the Chinese original, the Chinese original prevails.

Published: August 15, 2026
Effective: August 15, 2026

Anycubic Forge Console (the “Client”) is an unofficial third-party client compatible with Anycubic printers. This policy explains what information is processed when you use the Client, why it is processed, how it is stored and shared, and the choices available to you. Anycubic cloud services remain governed by Anycubic's official privacy policy.

1. Scope

This policy covers account sign-in, AI model configuration, printer management and control, cloud files, print history, notifications, camera and time-lapse access, OrcaSlicer connectivity, and log analysis provided by the Client. It does not govern Anycubic's official apps and websites, OrcaSlicer, your browser, or other third-party services.

2. Information processed

The Client processes only information needed for the feature you choose:

• Account and session data: Anycubic username, password, selected region, access token, session identifier, nickname, avatar, and cloud quota. The password is submitted to the official sign-in endpoint and is not retained as ordinary business data.
• Printer and print data: printer name, model, device identifier, online state, settings, temperatures, fans, lights, filament, progress, layers, remaining time, error codes, job details, history, notifications, and control results.
• Files and diagnostic content: uploaded G-code or 3MF files, names, sizes, hashes, slicing metadata, cloud and local printer files, thumbnails, device logs, reports, errors, and time-lapse files.
• Camera and video data: printer and channel identifiers, temporary tokens, encryption parameters, and audio/video or file-transfer data when you actively enable camera or time-lapse functions.
• OrcaSlicer data: Orca API key, selected printer, account session, printer state, filament information, sliced files, and print parameters.
• AI configuration and requests: provider, billing mode, API format, endpoint, authentication method, model ID, reasoning mode, and encrypted API key. Connectivity tests send a minimal request to your chosen provider. Filament calibration sends the 1–20 images you select, the analysis prompt, and model ID to that provider.
• Message notifications: selected printers and events, language, channel, task name, event time, exception reason, and error code. Email uses 1–5 recipient addresses and a provider mode. PushPlus stores up to five encrypted friend tokens obtained through one-time QR binding. The cloud token, printer MQTT key, and private SMTP password needed for server-side monitoring are encrypted at rest. Explicit sign-out clears the background token and pauses monitoring. Messages exclude progress and layer counts.
• Network and runtime data: IP address, request time and path, response status, browser and operating-system information, network state, and error logs generated by the server or reverse proxy.
• Operator configuration: global MQTT, log-export, time-lapse, Wiki, AI-calibration, system SMTP, and PushPlus settings stored in the service database. MQTT service passwords, callback secrets, the system SMTP password, and the PushPlus administrator user token and secretKey are encrypted with the application's persistent secret.
• Browser-local data: session cookies, language and theme preferences, printer aliases, log-analysis history identifiers, and static assets cached by the mobile Service Worker.

Cloud messages, printer names, filenames, uploaded content, and raw device logs are preserved in their source language.

3. Purposes

Information is used to authenticate the account, maintain the session, retrieve printer and cloud data, execute commands you explicitly request, transfer files and time-lapses, provide real-time status and camera access, connect OrcaSlicer, run diagnostics and AI-assisted calibration, protect the service, troubleshoot compatibility, and meet applicable legal obligations. The Client does not use this information for advertising profiles or marketing.

4. Cookies and local storage

Necessary cookies maintain the signed-in session and language preference. Local storage may retain interface preferences and functional identifiers. Refusing or clearing necessary storage can sign you out or disable some functions. The Client does not use cookies for cross-site advertising tracking.

5. Third-party services

The Client does not sell personal information. Data required for a selected feature may be sent to:

• Anycubic services for authentication, account data, MQTT, cloud files, history, device control, video credentials, and time-lapse functions;
• Agora/Shengwang for real-time camera or time-lapse transport; see the Shengwang SDK privacy policy;
• Anycubic Wiki or related content services for error-code references;
• your selected AI provider for model testing and filament-calibration analysis; and
• the operator's or your selected SMTP provider for individually addressed notification and test emails; a failed custom provider is never silently replaced with system SMTP;
• PushPlus for WeChat delivery of approved HTML notification fields; and
• hosting infrastructure such as servers, databases, reverse proxies, DNS, certificates, backups, and security services.

Each third party processes data under its own terms, policies, limits, and billing rules. Configure only endpoints and models you are authorized to use.

6. Retention and deletion

Sessions expire and are cleared on sign-out. Runtime printer data is normally held in memory or short-lived caches. Time-lapse MP4 files are temporary. Orca credentials remain until rotated or deleted. AI configuration remains until you delete it; calibration images and responses are temporary and are not written to calibration history. Message preferences, encrypted private SMTP configuration, and active PushPlus friend tokens remain until changed or deleted; sent and finally failed per-recipient delivery records are removed after seven days. Message bodies, complete recipient addresses, tokens, secretKey, AccessKey, QR parameters, friend tokens, and credentials are not written to logs. Log packages and reports remain until you delete them or the service cleans them up. Anycubic controls retention of data stored in its cloud.

Signing out of the Client does not close your Anycubic account or delete Anycubic cloud files and history. Use the relevant product controls or contact the service operator to request deletion of Client-held information.

7. Security

Reasonable safeguards include access controls, session protection, encryption of stored secrets, transport protection, upload limits, log redaction, and periodic cleanup. Protect your Anycubic password, session cookie, Orca API key, AI provider keys, SMTP password, PushPlus administrator token and secretKey, and other credentials. Rotate any credential exposed in chat, logs, or screenshots before deployment. Prefer HTTPS for external clients. Internet services and remote device control cannot be guaranteed completely secure.

8. Your choices and rights

Subject to applicable law, you may request access, correction, a copy, deletion, restriction, withdrawal of consent, or an explanation of how Client-held personal information is processed. You may also sign out, clear browser data, or stop using a feature. Requests concerning Anycubic accounts and cloud data must be directed to Anycubic through its official channels.

9. Children

The Client is primarily intended for adults and controls equipment with hot and moving parts. Minors must use it under a guardian's direction and supervision. Where required by law, a parent or guardian must consent before a child uses the service.

10. Changes and contact

This policy may be updated when features, services, or laws change. Material changes will be communicated through the sign-in page, an in-product notice, or another prominent channel. For privacy or security questions, use the contact channel published by the service operator.