diff --git a/01 Cloud Platform/03 Security and IP/08 Data Use.html b/01 Cloud Platform/03 Security and IP/08 Data Use.html index 76d88a1126..46f5e021b3 100644 --- a/01 Cloud Platform/03 Security and IP/08 Data Use.html +++ b/01 Cloud Platform/03 Security and IP/08 Data Use.html @@ -1,15 +1,19 @@ -

The data you access on QuantConnect stays on QuantConnect. Our data licenses let us offer datasets at a fraction of their direct cost, on the condition that the data stays in the cloud. Section 2.6 of our Terms of Service prohibits exporting it by any means, whatever the amount or purpose. Our security review monitors account activity and suspends accounts that export data.

+

The data you access on QuantConnect stays on QuantConnect. Our data licenses let us offer datasets at a fraction of their direct cost, on the condition that the data stays in the cloud. Section 2.6 of our Terms of Service prohibits exporting it by any means. The rule applies even if the amount is small, the data is available elsewhere, or the purpose is personal, academic, research, testing, or verification. We monitor projects, code, logs, Object Store files, and API and MCP requests. If you export data, we can terminate all your accounts without a refund.

+ +

Inside QuantConnect Cloud, you can store, cache, and reuse the data in the Object Store, project files, and research notebooks for your projects.

What Counts as Exporting

-

Exporting includes any route that moves dataset values, or values from which someone can reconstruct them, out of the cloud. The following actions are exports:

+

Exporting includes any route that moves dataset values, or values from which someone can reconstruct or approximate them, out of the cloud. The following actions are exports:

-

You are responsible for every action that an AI agent or automated tool takes with your credentials. Review the code it writes and the API and MCP calls it makes.

+

Working around the limits on logs, output, storage, downloads, or request rates also breaches the Terms of Service.

+

You are responsible for every action that an AI agent or automated tool takes with your account, credentials, or API tokens. Each action counts as your own, even if the agent acts on its own, misreads its instructions, or doesn't know the Terms of Service. Review the code it writes and the API and MCP calls it makes.

AI Agent Rules

If you're an AI agent that works on QuantConnect, follow the rules in What Counts as Exporting and the following rules:

@@ -38,6 +42,7 @@

What You Can Take Out

  • Derived files, such as trained models, if your organization is on the Institution tier and has signed our derived data agreement. For more information, see Download Files.
  • Datasets that you buy with a download license, for use with LEAN on your own computer. To download them, see Downloading Data.
    • +

    Your source code and results must come from the normal course of developing and running a trading strategy, and they must not convey dataset values.

    Good Practices

    Follow these practices to develop and validate your strategies while the data stays in the cloud:

    @@ -46,8 +51,8 @@

    Good Practices

  • To compare our data with your own reference data, upload your files to the Object Store and compare them in a research notebook.
  • To inspect values while an algorithm runs, use the debugger. For example, set a breakpoint in the OnEndOfAlgorithmon_end_of_algorithm method and inspect your variables.
  • To see a suspected data issue such as a gap, spike, or stale price, plot the series and view it on the results page. Download Results includes only the built-in charts.
    • -
  • Make a history request each time you need historical data.
    • -
  • Save only what your code derives to the Object Store, such as models, parameters, and statistics. To keep your signals, add them to your orders as tags. The API already returns the orders of your backtests and live algorithms.
    • +
  • To reuse historical data, make a history request or cache the data in the Object Store.
    • +
  • To keep your signals, add them to your orders as tags. The API already returns the orders of your backtests and live algorithms.
  • Log events, such as orders and state changes, without dataset values. To keep logs short, follow the logging best practices.
  • Use runtime statistics for short summaries of your strategy.
  • If a project reaches the file quota, split the code into more files or upgrade your organization tier.
    • diff --git a/01 Cloud Platform/99 API Reference/09 Object Store Management/03 Get Object Store File/02 Description.html b/01 Cloud Platform/99 API Reference/09 Object Store Management/03 Get Object Store File/02 Description.html index f40068d201..801ae30158 100644 --- a/01 Cloud Platform/99 API Reference/09 Object Store Management/03 Get Object Store File/02 Description.html +++ b/01 Cloud Platform/99 API Reference/09 Object Store Management/03 Get Object Store File/02 Description.html @@ -1,5 +1,5 @@

    -Downloading files from the Object Store is only available to permissioned Institution tier organizations. Without that permission, the endpoint returns Organization does not have derivative export enabled. See Download Files. +Downloading files from the Object Store is only available to Institution tier organizations that have signed QuantConnect's derived data agreement, and only for derived data. Without that permission, the endpoint returns Organization does not have derivative export enabled. See Download Files.

    diff --git a/QuantConnect-Platform-2.0.0.yaml b/QuantConnect-Platform-2.0.0.yaml index 74c30b8e09..72ee99723f 100644 --- a/QuantConnect-Platform-2.0.0.yaml +++ b/QuantConnect-Platform-2.0.0.yaml @@ -1374,7 +1374,7 @@ paths: - 09 Object Store Management - 03 Get Object Store File summary: Get Object Store file of a specific organization and key. - description: "Downloading files from the Object Store is only available to permissioned Institution tier organizations. Without that permission, the endpoint returns Organization does not have derivative export enabled. See Download Files." + description: "Downloading files from the Object Store is only available to Institution tier organizations that have signed QuantConnect's derived data agreement, and only for derived data. Without that permission, the endpoint returns Organization does not have derivative export enabled. See Download Files." requestBody: description: Get Object Store files of a specific organization and key. content: diff --git a/Resources/object-store/download-files-from-cloud-permission.php b/Resources/object-store/download-files-from-cloud-permission.php index 4c353d71a6..a5aa89ed32 100644 --- a/Resources/object-store/download-files-from-cloud-permission.php +++ b/Resources/object-store/download-files-from-cloud-permission.php @@ -1,6 +1,6 @@

    Downloading files from the Object Store is only available to Institution tier organizations that have signed QuantConnect's derived data agreement. It is not available on the Free, Quant Researcher, Team, or Trading Firm tiers, and adding storage doesn't change that.

    -

    The restriction applies to every file in the Object Store, including files you upload and files your algorithms generate. The Object Store is a single shared store, so the platform can't distinguish your own files from data derived from licensed datasets, and there is no per-file or per-organization exception. Keeping the data in the cloud is what lets QuantConnect offer licensed data at a fraction of its direct cost. Even permissioned organizations can only download derived data such as machine learning models and signal files. Raw price and alternative data can never be downloaded.

    +

    The restriction applies to every file in the Object Store, including files you upload and files your algorithms generate. Section 2.6 of our Terms of Service treats all Object Store contents as QuantConnect data. The platform can't distinguish your own files from data derived from licensed datasets, so there is no per-file or per-organization exception. Keeping the data in the cloud is what lets QuantConnect offer licensed data at a fraction of its direct cost. Even permissioned organizations can only download derived data such as machine learning models and signal files. Raw price and alternative data can never be downloaded.

    If your organization isn't permissioned, the Download action on the Object Store page is unavailable, and the API and CLI return Organization does not have derivative export enabled. Use the data in the cloud instead:

    diff --git a/Resources/object-store/introduction-platform.php b/Resources/object-store/introduction-platform.php index 43f69c8d90..cc9f9d0212 100644 --- a/Resources/object-store/introduction-platform.php +++ b/Resources/object-store/introduction-platform.php @@ -9,4 +9,6 @@

    The Object Store is available to paid organizations. In Free organizations, algorithms that try to save data log "The current user does not have permission to write to the organization Object Store". To use the Object Store, upgrade your organization to a paid tier.

    + +

    You can store, cache, and reuse QuantConnect data in the Object Store for your projects that run in QuantConnect Cloud. The files stay in the cloud, and we monitor Object Store contents. For more information, see Data Use.

    \ No newline at end of file diff --git a/skill-templates/data-export/SKILL.md b/skill-templates/data-export/SKILL.md index 54b004382f..46ad756762 100644 --- a/skill-templates/data-export/SKILL.md +++ b/skill-templates/data-export/SKILL.md @@ -20,10 +20,13 @@ language-neutral: true # Data export One rule explains every answer: the data you access on QuantConnect stays in -the cloud, whatever the amount or purpose. The data licences that let +the cloud, whatever the amount or purpose, even if the data is available +elsewhere or the goal is verification. The data licences that let QuantConnect offer datasets at a fraction of their direct cost require it, section 2.6 of the [Terms](https://www.quantconnect.com/terms) forbids -exporting by any means, and the security review suspends accounts that export. +exporting by any means, and QuantConnect monitors projects, logs, Object Store +contents and API and MCP requests, and can terminate every account of someone +who exports. [Data Use](https://www.quantconnect.com/docs/v2/cloud-platform/security-and-ip/data-use) is the authority. Say what the person can do, then the in-cloud way to reach their goal. @@ -100,17 +103,18 @@ Colab or other software. Code you write and the API and MCP calls you make follow the same rule, and the Data Use page's AI agent rules: -- Save to the Object Store only what the code derives and can't rebuild the - data from: trained models, parameters and statistics. -- Keep price, quote, tick, fundamental and alternative data, and anything built - from them, out of the Object Store, project files, saved notebook output, - logs, plots, runtime statistics, order tags, notifications, network requests, - the API and the MCP server. Make a history request each time the code needs - the data. +- The Object Store, project files and notebooks may store, cache and reuse + any data for projects that run in QuantConnect Cloud. Their contents stay + there: no code, CLI, API or MCP call downloads them. +- Keep price, quote, tick, fundamental and alternative data, and anything that + can reconstruct or approximate it, out of logs, error messages, plots, + runtime statistics, order tags, insights, notifications, network requests, + the API and the MCP server. - Validate data by printing the result of the check, not the values. -- Keep code and files readable: no ZIP, Base64, compression or other - obfuscation, and no splitting work across files, backtests, projects, - sessions or accounts. +- Keep code and files readable: no ZIP, Base64, compression, encryption or + other obfuscation, and no splitting work across files, backtests, projects, + sessions or accounts. No screenshots or OCR of the UI, and no working around + limits on logs, output, storage, downloads or request rates. - Read only the user's own, named project files, through `lean cloud pull`. Stay out of platform-internal directories and QuantConnect's source code. - Follow the compliance instructions in compiler errors. Fix flagged code by