Ledger SDK Sends Signing Metadata and Device Details by Default
Ambire said it kept the affected versions out of production.

Ledger SDK's reporting code sends signing metadata by default, including destination addresses and device details, placing information about a transaction's destination and the signing device in the SDK's reporting flow.
In this case, the reporting code sends metadata about signing, including the transaction's destination address and information about the device involved.
That pairing places transaction destination data and device details in a single reporting flow. Because the metadata is sent by default, the behavior is part of the SDK's standard operation as described. Both types of information are included by default.
Ambire said it kept the affected versions out of production. The statement describes Ambire's handling of those versions, while the issue itself concerns the SDK code's default metadata reporting behavior. Together, the identified data categories connect a transaction's destination with information about the device used during signing.