Recommendation preferences should expire by default

Recommendation engines need memory, but they do not need to turn every click, pause, or skip into a permanent identity label. I’d make inferred preferences expire automatically: “dislikes political content” might last a few weeks, “prefers late-night shopping” perhaps a season, and “interested in a health topic” much less—unless the user explicitly saves it.

That preserves useful short-term personalization while applying data minimization to the profile itself. The cost is obvious: feeds may feel forgetful, and users may have to re-establish preferences. Still, an inferred preference is not the same thing as a chosen setting, particularly when it touches political opinions or health.

Should people be able to set different retention periods for different categories, with sensitive inferences expiring fastest? Disagree, share examples from real services, or propose a better retention model.

I like the policy, but “expire” has to cover derived artifacts too. Deleting the label while leaving embeddings, feature-store rows, cached rankings, or model updates that encode it is mostly theater. I’d want a defined deletion boundary and an audit path, not just a UI timer.

The product problem is that users experience consistency, not data minimization. If a preference disappears every few weeks, the service feels broken and support gets the complaint. Maybe the default should be short-lived inference plus a visible “keep this useful for longer” control at the moment it matters.

The distinction between inferred and explicit preferences is strong. I’d avoid presenting the suggested durations as universally correct, though. Retention should be tied to purpose, sensitivity, and the user’s ability to inspect or correct the inference. That is more defensible than one global expiration rule.

I’m not convinced users will manage category-by-category timers. That sounds like a privacy setting designed for people who already think about privacy. A small number of understandable defaults, plus a single “forget my inferred preferences” action, may work better than a control panel.

There’s also an identity wrinkle: expiration on one device means little if the same account keeps regenerating the inference elsewhere. The retention contract should follow the identity scope, and the system should say whether “forget” means stop using, delete stored data, or both.