> For the complete documentation index, see [llms.txt](https://docs.scaleconnect.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleconnect.com.au/scaleconnect-docs/trust-centre/trust-centre.md). # Trust Centre ScaleConnect handles sensitive financial data on behalf of mortgage brokers and their clients. This section covers how we protect that data, how we verify the accuracy of our financial model, and the regulatory environment we operate in. *** ## Data Integrity Our simulation engine was independently audited and certified by the world's #1 ranked model auditing firm. Every code change is regression-tested against the certified baseline before it reaches production. [Read more →](/scaleconnect-docs/trust-centre/data-integrity.md) *** ## Data Security All data is encrypted in transit and at rest, hosted in AWS Sydney, and protected by role-based access controls. Third-party services are vetted for SOC 2 and PCI DSS compliance. [Read more →](/scaleconnect-docs/trust-centre/data-security.md) *** ## Policy & Compliance ScaleConnect operates within the Australian financial services regulatory environment. We support brokers' compliance obligations — we don't replace them. [Read more →](/scaleconnect-docs/trust-centre/policy-and-compliance.md) *** ## Limitations & Disclaimers ScaleConnect does not provide financial advice, credit advice, or investment recommendations. Simulation outputs are modelling tools, not predictions. [Read more →](/scaleconnect-docs/trust-centre/limitations-and-disclaimers.md) --- # 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://docs.scaleconnect.com.au/scaleconnect-docs/trust-centre/trust-centre.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.