# Dataflow and visibility

This table describes how data flows between the parties: Bsure, Customer and Microsoft.

<table data-header-hidden><thead><tr><th width="117.18182373046875">From </th><th width="114.0909423828125">To </th><th>Content </th></tr></thead><tbody><tr><td>Customer </td><td>Bsure </td><td>Count of billed users, Usage metrics*, Operational logs </td></tr><tr><td>Microsoft </td><td>Bsure </td><td>Customer name, Customer country, Subscription name, Count of billed users </td></tr><tr><td>Bsure </td><td>Customer </td><td>Runtimes and metadata such as list prices and windows versions + </td></tr></tbody></table>

\*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.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bsure.io/technical-description/dataflow-and-visibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.