If this is still happening merchants with app development resources probably want to capture the cart data on the frontend and try to pipe it to an external datastore.
As it's possible if even something like this is correct the [FILTERED] text is permanent in the data and shopify can't recover the original info for some reason.
A quick redundancy may be add a hidden contact form that submits the users identifiable metrics and the cart data at the time of checkout. Assuming this [FILTERED] issue does not extend to the contact form system, if it does that method is moot.
The tricky bit of course is correlating that external data to the correct orders based on that externa data.
If the customer isn't logged in you have to assume any extra referring data you pass in a cart attribute might also get clobbered breaking a attempts matching things together for that redundant data.
Some off the shelf possibilities for merchants without development resources.
Usemechanic might be able to facilitate this as long as you can correlate an order to the draft-order which should be easy if you require customers accounts to checkout. guest checkouts will be tricker to work out.
Repurpose something like the following to log the data and not create a new checkout:
https://tasks.mechanic.dev/create-a-draft-order-from-the-cart
Another possibility is any apps that might allow cart tracking/sharing etc where you can view the cart contents for a customer account at some point regardless of successful checkout. If so then in any emails you send to the customer you can prefill some of the possible correct answers to lower friction on the customer side.
An interim goal for all of the above approaches should be that any emails you send to the customer about missing product info you can prefill some possible best guess to lower friction on the customer side.
