> 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/gallagher-security-site-data-policy.md). # Gallagher Security Site Data policy Understand how Gallagher Security collects, protects, accesses, and retains customer site data. ### Purpose Gallagher Security is a division of Gallagher Group. The below outlines how Gallagher Security will handle customer site data in accordance with the Gallagher Privacy Statement, freely available via our website [https://security.gallagher.com/privacy-statement](https://security.gallagher.com/Privacy-Statement) ### Site Data Gallagher Security may require site data in order to troubleshoot any issues. Types of data that may be collected may include: * Database backups(where possible, personal information should be anonymised on-site using the Gallagher Database Anonymiser Utility) * Application Error logs * Application Dump files * Activity Reports * Operating System logs Types of data that will not be collected: * Site recovery code * Non sanitised High Security files ### Data Collection Where possible, all data should be pre-encrypted on-site using AES-256 encryption with a strong password or complex passphrase. Site data may be collected/received by various methods: * Gallagher Security File Transfer Site * Customer’s own software delivery method (E.g OneDrive) * Via secure remote connection(such as TeamViewer) * As email attachments (preferably encrypted and signed using digital certificates) * In person or postal/courierdelivery of: Types of data that will not be collected: * Site recovery code * Non sanitised T1a site files * Type A ## Data Usage The site data will only be used for the purpose for which it was collected. ## Data Security All site data is held in a secure location on Gallagher Group’s internal network. Access to this location is only allocated to certain Gallagher staff on approval from the Technical Support Team Leader or Engineering Centre of Excellence Lead (see Data Accessibility, below). ## Data Accessibility The following Gallagher Security departments will have access to this secure location: o Technical Support o Security Engineering o Product Development (restricted to key personnel) All Gallagher Group staff are contractually bound to confidentiality. Gallagher Group policies are freely available to staff on our intranet. Gallagher staff receive periodic awareness training based on our Information Security Guidelines and our Privacy Guidelines. ## Data Storage Gallagher Security will store all collected site data for a period no longer than 6 months. At the end of 6 months the data will be securely deleted from the internal network automatically via a scheduled windows task. If specifically requested by the customer, their information can be deleted earlier. The deletion process includes: * Virtual machines on PCs * Encrypted archive files * Passwords in password safes * Database recovery codes * Other temporary files and notes All Gallagher Group staff are contractually bound to confidentiality. --- # 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/gallagher-security-site-data-policy.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.