Should deleting visible history also delete the personalization behind it?

I ran into a UX question while building a personalized app and I’m curious how other people would handle it. The app compares repeat check-ins over time, so previous results are useful as a baseline for future ones. The problem is that I originally used the same data for both the user’s visible History screen and the personalization behind future comparisons. So if someone deletes an old result because they just don’t want it in their history anymore, the app also loses part of the context it was using to understand future check-ins. That feels a little off to me. Technically, it would be easy to separate visible history from the underlying personalization state, but then the UX gets more complicated. If a user deletes something from their history, what should they reasonably expect? Should the app forget that interaction entirely, or is it acceptable to remove the visible record while keeping some derived personalization from it? I’m leaning toward making the distinction explicit rather than treating “delete” as one universal action, but I’m not sure what expectation feels most natural from the user’s side. Curious how others would approach this, especially in products that become more personalized over time.