Perhaps you should check what Chrome version they are using, there is a known issues with Chrome 79 that it is causing data loss for WebViews. Apparently it migrates profile data to a new location, but due to poorly written tests they didn't realise that they also needed to move localstorage, indexeddb, etc. After the update the data is still in the old location, but Chrome looks in the new one and hence assumes there is no data. I imagine at that point most apps would assume that it's a new users and create new data. Here is the issue on the Chromium bug tracker, it's caused a fair bit of drama for obvious reasons. They appear to be taking it seriously, but it's a bit of an awkward situation because anyone who has experienced this problem now has 2 sets of conflicting data. So it's not clear which data to preserve.
I believe they halted the rollout on Friday so it won't be affecting all users, but the estimate is around 10% got the update... All a bit of a mess really.