> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library.md).

# Gallagher Policies library

Access Gallagher policies and supporting process documentation.

Browse policy summaries and their authoritative sources.

<table><thead><tr><th width="211.999755859375">Policy</th><th width="411">Description</th><th>Link</th></tr></thead><tbody><tr><td>CarePlan terms and conditions</td><td>CarePlan eligibility, renewal, service levels, and warranty terms</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/careplan-terms-and-conditions.md">View policy</a></td></tr><tr><td>Software Licence and Maintenance terms and conditions</td><td>Command Centre software licensing and maintenance terms</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/software-licence-and-maintenance-terms-and-conditions.md">View policy</a></td></tr><tr><td>Warranty and Returns Policy</td><td>Product warranty coverage and returns policy</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/warranty-and-returns-policy.md">View policy</a></td></tr><tr><td>Key Device Policy</td><td>Key-device licensing, removal alarms, replacement, and return requirements</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/key-device-policy.md">View policy</a></td></tr><tr><td>Contractor Conduct Policy</td><td>Conduct standards for contractors, suppliers, and Channel Partners</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/contractor-conduct-policy.md">View policy</a></td></tr><tr><td>Gallagher Security Site Data Policy</td><td>Collection, protection, access, and retention of customer site data</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/gallagher-security-site-data-policy.md">View policy</a></td></tr><tr><td>Mobile Connect SDK Support and Release Policy</td><td>SDK releases, support versions, compatibility, upgrades, and pre-release support</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/mobile-connect-sdk-support-and-release-policy.md">View policy</a></td></tr><tr><td>Software Development Lifecycle and Data Protection</td><td>Software development lifecycle and data-protection approach</td><td><a href="/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library/software-development-lifecycle-and-data-protection.md">View policy</a></td></tr></tbody></table>


---

# 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.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/gallagher-policies-library.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.