There isn’t really an out-of-the-box feature that implements this, but you do have a few options.
First of all, is there any particular reason why you would need to look at a field in the event, rather than at the general event timestamp? Doing the latter would make it easier to pick the right events.
If you’re using an RDBMS event store, you might just implement this as a DELETE query, erasing events that occurred more than 10 years ago.
Another option available for Axon is AxonIQ’s GDPR Module. It implements field-level encryption in event objects, with very fine grained control on what exactly gets encrypted using which key. The main use case of the GDPR Module is to enable cryptographic erasure: by throwing away a key, you can effectively delete certain fields in certain events, without having to change the stored event itself. Perhaps this could be useful in your case as well.