> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/logger-card-client-user-manual/copyright.md). # Copyright The contents of this document are copyright of ICU Scandinavia AB or its subsidiaries. All Rights Reserved.You may view, print, copy and distribute information from this document provided that:(a) the information is used internally (by you or any third party to whom you distribute it) only for informational, non-commercial purposes; (b) no fee may be charged for distribution of any information to any third party; (c) any and all copyright or other proprietary notices that appear herein, together with this legal notice, must appear on all copies that you make or distribute; and(d) no material may be modified, edited or taken out of context such that its use creates a false or misleading statement or impression of the document. Modifications to the contents of this document are explicitly prohibited. **Trademarks** ICU Boomerang™, ICU ROQS™ and ICU System™ are all trademark of ICU Scandinavia AB. ICU Scandinavia™ is also a trademark. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. --- # 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://help.boomerang3.com/logger-card-client-user-manual/copyright.md?ask=&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.