Where does Chrome store the URLs for web apps (desktop shortcuts that open in a ...

I am using Windows 10 (21H2) and I have a semi-old chrome shortcut for a site, that I set up to open in a new window (so that it works like an app - create shortcut -> open in new window). Problem is, it doesn't work anymore - at least not since a chrome update a while ago. Instead of fussing around to figure out why it doesn't work, I just want to create the shortcut again, to not overcomplicate things. I have backups going back several years, so this shouldn't be hard to figure out. Shouldn't.

Problem is, I can't figure out where chrome stores the URLs for these shortcuts/web apps. The shortcut is a shortcut to "C:\Program Files\Google\Chrome\Application\chrome_proxy.exe" --profile-directory=Default --app-id=XXX, the XXX being what looks like some kind of GUID.

To understand how this all works, I've created another "web app" to see how things change. I've already seen this question but Chrome doesn't seem to be creating an extension with a matching string, as suggested in the answer. I've looked all around Google, and I can't seem to find anything there. I've analyzed the web app creation process with Process Monitor, and while I've found where it places Icons in the file system and uninstall information in the registry, I still have no clue where it stores the URL.

So where does Chrome store these URLs?

So, one and a half years later, I finally found the answer to this question:

The URLs are stored in the profile folder, in Sync Data\LevelDB. On Windows, that would be %LOCALAPPDATA%\Google\Chrome\User Data\Default\Sync Data\LevelDB. You're looking for the files that end in .ldb. These are key-value stores, according to this site. It can be opened in a text file, even though it's kind of hard to read through - but you will find the app names and the URLs in there. The search tool of the text editor or the findstr command on Windows (I believe the Linux equivalent is grep) will be your best friend.

Thanks to @Arctiic, since his comment helped me narrow down the haystack quite a bit.