What do you mean by "utilise anonymised data for troubleshooting"? Anonymised data can be used for research, but troubleshooting requires specific information.
The data in question looks like this I redacted addresses and transaction ids:
"[<DATEANDTIME>] [ERROR] Order failed with error: insufficient funds, main.ExchangeSession{OrderID:"b0a06943af3df054", Status:"EXCHANGING", FromCurrency:(*cryptoManager.LtcHandler)(0xc0002aa000), ToCurrency:(*cryptoManager.EthHandler)(0xc000134a20), FromCurrencySign:"LTC", ToCurrencySign:"ETH", FromCurrencyID:2, ToCurrencyID:4, FeeRate:1, SendAmount:0.0013312683123676756, ReceiveAmount:0.035, ToAddress:"<REDACTED>", FromAddress:"<REDACTED>", RefundAddress:"<REDACTED>", ToTransactions:[]cryptoManager.CryptoTransaction{}, FromTransaction:cryptoManager.CryptoTransaction{Txid:"<REDACTED>", Confirmations:1, Amount:0.35, Explorers:[]*cryptoManager.CryptoTransactionExplorer{(*cryptoManager.CryptoTransactionExplorer)(0x7ff7f819b180)}}, ToConfirmations:12, FromConfirmations:1, ExchangeRate:<REDACTED>, ErrorMessage:"", ExpirationTime:<REDACTED>, CollectionTime:-1}"
As shown, when an error occurs, the system logs the relevant transaction state, including the error and technical details, without exposing personally identifiable information (such as IP addresses). This allows for effective debugging while maintaining user privacy.
So basically, the system says record xxx has malfunctioned - here are the anonymized details. Your support rep then goes to the database to research the record, where he/she has access to all PII (including IP addresses)?
Unless you provide column level restrictions on your database, you cannot say the data is anonymized any more than any other system - understand? Again, I would completely do away with that "technobabble", as without KYC anyone running this script is breaking US law. Take resources you would spend on that, and remove all custody through smart contracts - IMO that is the winner feature!