Thanks for the quick response. It makes sense why one synchronization is one session, for sanity’s sake. Could one cookie be used to describe each individual sync session whereas an additional cookie be placed in persistent storage, i.e. cached on disk, to describe the device identity? I’m looking at Firefox as an example. My identity is synchronized at least once during every browsing session, and yet the device lists a single (UUID? don’t remember the terminology…) for that connection. I think Plex does something similar in their access lists.