I would urge you to avoid the temptation to tie data layer / business object lifecycle to view layer / presentation component lifecycle. They don’t logically have a single thing to do with one another, and trying to piggyback your data freshness management onto component lifecycle events is a recipe for frustration.
See here for a sample idiom to manage the exact issue you discuss here: user profile information. Bonus thread here on the topic of how device storage fits into the picture (note that you only want to be reading from storage once per app run).