> For the complete documentation index, see [llms.txt](https://docs.bsure.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsure.io/technical-description/dataflow-and-visibility.md). # Dataflow and visibility This table describes how data flows between the parties: Bsure, Customer and Microsoft.
From To Content
Customer Bsure Count of billed users, Usage metrics*, Operational logs
Microsoft Bsure Customer name, Customer country, Subscription name, Count of billed users
Bsure Customer Runtimes and metadata such as list prices and windows versions +
\*Usage Metrics : We monitor unique users accessing the different Bsure Insights pages and how fast they load. This data is aggregated and anonymized before sent to Bsure. All collected data is stored securely and anonymized, retained only for as long as necessary to fulfil the stated purposes, and is not disclosed to third parties except where required by law, pursuant to a valid legal basis, or with explicit user consent. --- # 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.bsure.io/technical-description/dataflow-and-visibility.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.