Fireblocks does not store or process any client Personal Identifiable Information (PII). To achieve this, the customer is required to strictly use anonymized tokens, such as Universally Unique Identifiers (UUID) to reflect client data. These anonymous tokens are mapped internally by the customer to actual client identifiers stored on the customer's end.
Since the customer processes and manages its wallet infrastructure using the Fireblocks Console or Fireblocks API, these anonymous tokens should be used when using the Fireblocks REST API endpoints. The following table lists the relevant fields that allow persistent information to be stored in Fireblocks–for which the anonymous tokens should be used.
|Vault||Create a new vault account||name|
|Vault||Create a new asset deposit address||description|
|Vault||Rename a vault account||description|
|Internal Wallet||Create an internal wallet||name|
|Internal Wallet||Set an AML/KYT customer reference ID for an internal wallet||customerRefId|
|External Wallet||Create an external wallet||name|
|External Wallet||Set an AML customer reference ID for an external wallet||customerRefId|
|Contracts||Create a contract||name|
|Transactions||Create a new transaction||note|
|Transactions||Estimate a transaction fee||note|
Updated about 1 month ago