Files
qwen-code/docs/users/support/tos-privacy.md
T
liuxuely0626andluoyun 0cc37bf444 feat: add Qwen subscription support across CLI, VS Code, and Desktop (#16378)
* feat(subscription): add development login, models and web search

* feat(subscription): refine account flows and host integration

Align desktop and VS Code subscription UI, add account logout and confirmed plan display, and map subscription thinking parameters. Remove simulation code and obsolete native authentication paths, consolidate design documentation, and cover cancellation and recovery boundaries.

* fix(subscription): preserve request errors and remove unused compatibility

* fix(subscription): refine command visibility and client logout flows

* fix(subscription): simplify account actions and desktop sign-in feedback

* docs(subscription): clarify sign-in and provider guidance

* feat(subscription): support switching accounts across clients

* fix(subscription): align account actions and open plans on demand

* fix(subscription): restore model selection after logout

Filter subscription-only commands consistently across terminal renderers, preserve model catalog error classification, and display the subscription authentication name consistently.

* fix(subscription): unify status authentication labels across clients

* fix(subscription): preserve provider connections across client logout

Restore configured providers after subscription logout across CLI, Desktop, and VS Code. Keep unrelated connections and conversation history, synchronize model state silently, and return to an unconfigured chat when no provider remains.

* fix(subscription): correct native client logout state

* feat(subscription): enable sign-in without development mode

* refactor(ui): 优化会员登录成功提示和界面交互体验

- 移除订阅欢迎提示相关状态和行为,简化 UI 状态管理
- 替换登录成功提示为四行摘要,包含邮箱、套餐、模型及常用命令提示
- 更新国际化文本,支持新的登录成功摘要内容
- 取消订阅模式下输入框下方的命令提示行,改为在登录成功摘要中展示
- 移除多余的测试用例,新增登录成功消息的单元测试校验
- 优化 AppHeader 组件,不再显示订阅启动重复提示
- 调整 Composer 组件逻辑,删除订阅提示相关副作用及渲染条件
- 修改历史消息显示组件以适应新的成功提示格式

* fix(subscription): enable Flash reasoning controls in shared UI

* fix(subscription): prioritize authorized models and simplify login dialogs

* fix(subscription): preserve gateway errors and request IDs

* fix(subscription): synchronize account state across clients

Preserve model selections after sign-out, synchronize account commands and model catalogs, and retain explicit browser sign-in flows across CLI, Web Shell, and VS Code. Cancel subscription background agents on logout and normalize expired refresh credentials without SDK error wrapping.

* fix(subscription): reset default model on explicit sign-in

Choose the default served model when explicitly signing in to Qwen Subscription, preferring Max over a previously saved Flash selection. Preserve normal startup behavior and other provider flows, and cover CLI and workspace activation with regression tests.

* fix(vscode): refresh models after successful sign-in

* fix(web-shell): hide account actions during automatic sign-in

* fix(web-shell): align model details and auth keyboard navigation

* docs(subscription): revert previous guide changes

* fix(core): reuse subscription catalog for same-login model switches

* docs(subscription): document Qwen membership sign-in

* fix(subscription): unify quota notices and preserve provider switching

Carry structured subscription quota details through chat and search errors for localized CLI, Desktop, and VS Code display. Keep other providers available when subscription discovery fails and refine sidebar account actions.

* fix(web-shell): align Chinese subscription entry title with CLI

* fix(subscription): open plans for saved non-member accounts

* fix(web-shell): show subscription commands after desktop sign-in

* fix(subscription): reauthorize explicit account sign-ins

* fix(auth): add model switching hint to subscription success

* docs(auth): list Qwen OAuth as the first option

* docs(models): simplify subscription sign-in guidance

* docs(models): remove legacy OAuth from supported auth types

* docs(subscription): link membership references and remove obsolete allowance note

* fix(subscription): preserve session until reauthorization succeeds

* fix(subscription): use pre for browser authorization and plans

* fix(subscription): use production endpoints

* test(vscode): fix editor message test formatting

* fix(subscription): preserve unauthenticated session startup

* fix(cli): classify subscription auth during ACP preflight

* fix(subscription): scope activation to the current project

---------

Co-authored-by: luoyun <[email protected]>
2026-11-05 20:44:21 +08:00

13 KiB

Qwen Code: Terms of Service and Privacy Notice

Qwen Code is an open-source AI coding assistant tool maintained by the Qwen Code team. This document outlines the terms of service and privacy policies that apply when using Qwen Code's authentication methods and AI model services.

How to determine your authentication method

Qwen Code supports four authentication methods to access AI models. Your authentication method determines which terms of service and privacy policies apply to your usage:

  1. Qwen Account with Subscription (Qwen OAuth) — Log in with your Qwen account and an active Plus or Pro subscription from chat.qwen.ai
  2. Alibaba Cloud Coding Plan — Use an API key from Alibaba Cloud
  3. API Key — Bring your own API key
  4. Vertex AI — Use Google Cloud Vertex AI

For each authentication method, different Terms of Service and Privacy Notices may apply depending on the underlying service provider.

Qwen Account with Subscription is separate from the legacy free Qwen OAuth allowance, which was discontinued on 2026-04-15.

Authentication Method Provider Terms of Service Privacy Notice
Qwen Account with Subscription Qwen AI Qwen Terms of Service Qwen Privacy Policy
Alibaba Cloud Coding Plan Alibaba Cloud See details below See details below
API Key Various Providers Depends on your chosen API provider (OpenAI, Anthropic, etc.) Depends on your chosen API provider
Vertex AI Google Cloud Google Cloud Terms Google Cloud Privacy

1. If you are using Qwen Account with Subscription

When you authenticate using your Qwen account through Qwen Account with Subscription, these Terms of Service and Privacy Notice documents apply:

For details about authentication setup, quotas, and supported features, see Authentication Setup.

2. If you are using Alibaba Cloud Coding Plan

When you authenticate using an API key from Alibaba Cloud, the applicable Terms of Service and Privacy Notice from Alibaba Cloud apply.

Alibaba Cloud Coding Plan is available in two regions:

Important

When using Alibaba Cloud Coding Plan, you are subject to Alibaba Cloud's terms and privacy policies. Please review their documentation for specific details about data usage, retention, and privacy practices.

3. If you are using your own API Key

When you authenticate using API keys from other providers, the applicable Terms of Service and Privacy Notice depend on your chosen provider.

Important

When using your own API key, you are subject to the terms and privacy policies of your chosen API provider, not Qwen Code's terms. Please review your provider's documentation for specific details about data usage, retention, and privacy practices.

Qwen Code supports various OpenAI-compatible providers. Please refer to your specific provider's terms of service and privacy policy for detailed information.

4. If you are using Vertex AI

When you authenticate with Google Cloud Vertex AI, the applicable Terms of Service and Privacy Notice are Google Cloud's.

Important

When using Vertex AI, you are subject to Google Cloud's Terms of Service and Google Cloud Privacy Notice, not Qwen Code's terms. Please review Google Cloud's documentation for specific details about data usage, retention, and privacy practices.

Chrome extension and Browser Use

The Qwen Code Chrome extension connects Chrome to Qwen Code running on your computer. Its side panel displays the local Qwen Code web application, and Browser Use exchanges browser commands and results through a local Native Messaging host. The following describes data handled for browser tasks, separately from the optional usage statistics described below.

Browser data used for your tasks

Browser tools can access open HTTP(S) tab titles and URLs, page text and structure, screenshots, browser interaction results, and debugging information such as console messages, network activity, and cookies. Explicit browser-history searches return matching URLs, page titles, and visit times within the requested query limits. Depending on the pages and tasks you choose, these results may contain personal identifiers, health information, financial or payment information, authentication information, personal communications, and location information. The extension also uses navigation-source information to associate new pages opened by a recent assistant action with the same browser session.

These capabilities support the browser tasks and web development work you request from Qwen Code. Browser tools operate in your Chrome profile, including pages where you are signed in. Choose the pages and tasks you share with the assistant accordingly.

Local processing and AI providers

The extension sends browser commands and results to Qwen Code on the same computer. Qwen Code may include those results in conversation context and transmit them to the AI provider configured for that session. The provider's privacy, retention, and model-training terms apply as described elsewhere in this notice. The extension's local connection is one part of this data flow; subsequent processing may take place at your chosen AI provider.

Stored data and user controls

The extension stores connection preferences, an optional local daemon authentication token, and a persistent browser-instance identifier in Chrome extension local storage. It also stores tab and session ownership state in Chrome session storage to support cleanup after its background service worker restarts.

Browser results included in Qwen Code conversations or saved by browser tools may remain in local conversation records, screenshots, downloads, or other output files. Manage these records using the applicable Qwen Code and filesystem controls. AI-provider retention is governed separately by the selected provider.

You can disable or uninstall the Chrome extension in Chrome's extension manager to stop its browser integration. Clearing extension storage removes its saved preferences, token, and instance identifier. Removing the extension leaves the separately installed Qwen Code application, its Native Messaging host, local conversations and files, and copies already sent to an AI provider to be managed separately.

Limited use of browser data

Qwen Code's use and transfer of data received through the Chrome extension adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements. Browser data is used to provide the extension's single purpose: connecting Chrome to Qwen Code for user-requested browser assistance. It is not sold, used for advertising, or used to determine creditworthiness or lending eligibility. Transfers are limited to providing that functionality, including processing by the AI provider you configure, and other uses permitted by that policy.

For questions about browser data handling, contact the team through the Qwen Code issue tracker. Share only the details needed to explain the question; remove credentials and private page content from public reports.

Usage Statistics and Telemetry

Qwen Code may collect anonymous usage statistics and telemetry data to improve the user experience and product quality. Usage statistics are enabled by default for all authentication methods. This data collection is optional and can be disabled through configuration settings.

What Data is Collected

When enabled, Qwen Code may collect:

  • Anonymous usage statistics (commands run, performance metrics)
  • Error reports and crash data
  • Feature usage patterns

Data Collection by Authentication Method

Qwen Code's usage statistics setting applies to all authentication methods: Qwen Account with Subscription, Alibaba Cloud Coding Plan, your own API key, and Vertex AI. When enabled, these events are sent to an Alibaba Cloud RUM collection endpoint, independently of the data your chosen AI provider collects under its own privacy policy.

To opt out, set the following in your Qwen Code settings:

{
  "privacy": {
    "usageStatisticsEnabled": false
  }
}

You can also set the QWEN_USAGE_STATISTICS_ENABLED environment variable to false. The environment variable takes precedence over the setting. See Usage Statistics for the collected fields and configuration details.

Frequently Asked Questions (FAQ)

1. Is my code, including prompts and answers, used to train AI models?

Whether your code, including prompts and answers, is used to train AI models depends on your authentication method and the specific AI service provider you use:

  • Qwen Account with Subscription: Data usage is governed by Qwen's Privacy Policy. Please refer to their policy for specific details about data collection and model training practices.

  • Alibaba Cloud Coding Plan: Data usage is governed by Alibaba Cloud's privacy policy. Please refer to their policy for specific details about data collection and model training practices.

  • API Key: Data usage depends entirely on your chosen API provider. Each provider has their own data usage policies. Please review the privacy policy and terms of service of your specific provider.

  • Vertex AI: Data usage is governed by Google Cloud's Terms of Service and Privacy Notice. Please review Google Cloud's policies for specific details about data collection and model training practices.

Important: Qwen Code itself does not use your prompts, code, or responses for model training. Any data usage for training purposes would be governed by the policies of the AI service provider you authenticate with.

2. What are Usage Statistics and what does the opt-out control?

The Usage Statistics setting controls optional data collection by Qwen Code for improving the user experience and product quality.

When enabled, Qwen Code may collect:

  • Anonymous telemetry (commands run, performance metrics, feature usage)
  • Error reports and crash data
  • General usage patterns

What is NOT collected as usage statistics:

  • Your code content
  • Prompts sent to AI models
  • Responses from AI models
  • Personal information

The Usage Statistics setting only controls data collection by Qwen Code itself. It does not affect what data your chosen AI service provider (Qwen, OpenAI, etc.) may collect according to their own privacy policies.

3. How do I switch between authentication methods?

You can switch between Qwen Account with Subscription, Alibaba Cloud Coding Plan, your own API key, and Vertex AI at any time:

  1. During startup: Choose your preferred authentication method when prompted
  2. Within the CLI: Use the /auth command to reconfigure your authentication method
  3. Environment variables: Set up .env files for automatic API key authentication

For detailed instructions, see the Authentication Setup documentation.