Financial data and privacy

This page supplements the AnyPath Privacy Policy for the AnyPath-operated BSC settlement rail.

Data used for settlement

AnyPath processes settlement account identifiers, financial-party references, deposit addresses, transaction hashes, block-finality and token-transfer evidence, payout destinations, amounts, status transitions, reconciliation evidence, risk decisions, and security audit events. A passkey public key, credential identifier, signature counter, backup state, and lifecycle status are stored; biometric data and private keys remain on your authenticator and are not received by AnyPath.

Public-chain visibility

BSC addresses, amounts, token transfers, and transaction hashes are public blockchain data. Copy and explorer actions in the Console link only to allowlisted BscScan URLs, but opening an external explorer is still a visit to a third party.

Retention and deletion

Eligible profile data is deleted or anonymized after account deletion. Immutable financial and security evidence is retained when required for ledger integrity, reconciliation, fraud prevention, dispute handling, tax, sanctions, or other legal obligations. Retained movements use a pseudonymous financial-party reference after identity anonymization where possible. Pseudonymous records are not anonymous or non-personal data when they can still be linked to a person.

Access and export

Billing views and CSV exports are scoped to the authenticated account or authorized administrator role. Exports use an immutable financial-movement projection and a fixed snapshot boundary so later activity is not silently mixed into the same export.