> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/zh-tw/sep-2026/20260908.md).

# 關於更新 Cregis 標準用戶使用條款的通知

尊敬的Cregis用戶，

您好！我們將在 2026年9月12日 更新 **Cregis 的標準用戶使用條款**，屆時條款將自動更新，您無需進行任何手動操作。&#x20;

為幫助您提前瞭解相關內容，請前往Cregis 官網「資源 > 產品手冊 > [條款與細則](https://support.cregis.com/cregis-wallet-guide/zh-tw/terms_and_conditions/cregis-standard-terms-of-service)」先行查閱最新版本。如您對更新後的條款有任何疑問，歡迎隨時聯繫我們。

感謝您一直以來對 Cregis 的支持！

Cregis 團隊\
2026-09-08


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.cregis.com/announcement/zh-tw/sep-2026/20260908.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
