[Bug] Synchronization error from the "upstash" database

### 📦 Deployment Method

Vercel

### 📌 Version

last

### 💻 Operating System

Windows, macOS, iOS

### 📌 System Version

11

### 🌐 Browser

Chrome, Edge, Safari, Firefox, Other

### 📌 Browser Version

last

### 🐛 Bug Description

I'm encountering a problem with syncing data from the "upstash" database. I've configured the "upstash" database on my main computer, including settings for font size, model configuration, predefined Mask lists, and options to hide certain elements or change languages. When I set up the same "upstash" database on my second computer, chat history and access codes sync properly, but the settings like font size, model configuration, predefined Mask lists, and others don't sync. This forces me to reconfigure everything manually.

### 📷 Recurrence Steps

_No response_

### 🚦 Expected Behavior

Ideally, there should be a button to update settings that differ from the backup database or to update with the latest data from the computer.

### 📝 Additional Information

Additionally, after configuring various settings and expecting that pressing the sync button would update the "upstash" database, it turns out that all previous settings were reset. I suspect that data may have been pulled from upstash, causing the settings to be overwritten. Therefore, there should be a check for differences between user data and upstash data before syncing. If there are differences in user configurations, those might be the updates the user wants to apply to the upstash database. Thus, there should be a custom update button for the database.

Additionally, there are areas that need improvement regarding password login. I noticed that when I use a password to log in, no data synchronization occurs, which shouldn't be the case. It should be as simple as using a password, and everything should sync automatically. I'm not sure what your original approach was, but users shouldn't have to set additional configurations. It would mean that each time a different computer is used, users would need to set up the password, database, and all settings again. This goes against the principle that once you have a password, it should be easy to access without requiring further configuration after a successful login.

Currently, I use only the "upstash" database setup, which synchronizes the password anyway. This creates a conflict in my mind—why is a password needed when using just the "upstash" database setup suffices? The password gets synced and configured in the settings immediately. I understand you might have your reasons for doing it this way, but I hope you will improve the initial points I mentioned above.