The Data Collection section needs clarifications

[iensu]

The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications.

This section should be improved:

• It is not clear what exact data Microsoft gathers and for what exact purpose the data points are gathered.
• While it does say that you can disable telemetry, the text just points to the repository in general. The documentation is long and it is not even clear if the instructions are in the README or elsewhere in the repository.
• There is a disableTelemetry option, but it's not clarified if this applies to all telemetry or to the telemetry intended for Microsoft purposes.

Lastly, it would be fantastic if the telemetry sent to MS would be opt-in, rather than opt-out.

[MSNev]

Ok, finally have a response that I'll try and articulate here.

• The disclaimer that we have already is the generic disclaimer used across Microsoft and as such this will be kept as the disclaimer here, rather than creating a specific one for this SDK.

To try and answer the specific questions.

It is not clear what exact data Microsoft gathers and for what exact purpose the data points are gathered.

• This is hard to provide the "exact data" because it depends on the site using the SDK, as it is up to the site owner to provide the details. It should be noted that this data is NOT collector for Microsoft usage, it is collected and sent to Microsoft servers on-behalf of the "site" (application/page using the SDK), ALL of the current data sent by the SDK is available to the owner of the instrumentation key (within the portal)

While it does say that you can disable telemetry, the text just points to the repository in general. The documentation is long and it is not even clear if the instructions are in the README or elsewhere in the repository.

• Understand, we will look to make it easier to discover

There is a disableTelemetry option, but it's not clarified if this applies to all telemetry or to the telemetry intended for Microsoft purposes.

• When this configuration is used ALL telemetry is disabled, as this blocks all event from being batched / sent. And as mentioned above there is no specific telemetry intended for Microsoft purposes, this SDK is used to facilitate application owners (site / page) to collect telemetry for their own usage.
• While there are AI Internal messages these are sent to the storage used by the instrumentation key and (may) be used to assist for debugging purposes as to why the system may or may not be doing what is expected. ie. They are intended to facilitate that there is some sort of AI Sdk Issue which may be stopping the SDK from functioning as expected.

Lastly, it would be fantastic if the telemetry sent to MS would be opt-in, rather than opt-out.

• Just restating again, this is under the control of the site that is using the SDK and what they want to collect for their usage.
• It is the hosting application (site / page) responsibility to determine whether
  • The SDK is initialized and should start collecting and sending application telemetry as configured
  • Whether the end-user has opted in or out of any telemetry collection (ie. user opted-out, then don't initialize the SDK or set the disabledTelemetry configuration)
  • Whether the end-user has opted in or out of reading / setting any cookies, we have configuration and accessors to enable enabling / disabling cookie usage (passed in during initialization) and since v3.x we now support the same via just dynamically updating the configuration after initialization.