Data Recovery Request: Account deletion bug caused by silent merge (Recovery Email

[wang3cu-collab]

Description of the Issue
I am reporting a critical account logic bug that led to the loss of 3 months of research data. I am currently stuck in an infinite 404/Login loop.

How the bug happened

1. I have a primary Google account. My QQ email is set as the "Recovery Email" for this Google account.
2. Due to persistent captcha issues, I tried to test a "new" account using my QQ email.
3. The system silently merged the QQ login with my existing Google User ID (likely due to the recovery email relationship) without any notification.
4. Thinking it was a separate temporary account, I deleted the account while logged in via QQ.
5. This action unexpectedly deleted my primary Google account's data as well.

Current "Zombie" State
Now, when I try to log in via Google:

• It says "You are logging back into lmarena".
• It immediately redirects to a 404 page.
• After refreshing, the UI shows I am logged in, but I cannot accept the Terms of Service (it keeps saying "Failed").
• This proves the database record is in a "corrupted/half-deleted" state but the User ID still exists.

Why this is urgent
This account contains 3 months of my intellectual work, ideas, and critical chat history. Losing this is devastating to me. Since the system returns a 404 instead of "Account Not Found," I believe the data might still be recoverable in the backend (e.g., in a "soft delete" state).

Request
I hope the developers check the database logs for this conflict. I am the legitimate owner of both emails and can provide any proof needed.

Primary Google Email:wang****@gmail.com
Recovery QQ Email:3308******@qq.com
Approx. Deletion Time:[Dec 25th,UTC 07:00]

Please help me recover my life's work. Thank you.

[wang3cu-collab]

Critical Evidence of UX Misleading: I was absolutely certain I was deleting a separate, empty account because the system's UI explicitly signaled so:

Onboarding Triggered: Upon logging in with the QQ email, the system forced me into a new user onboarding flow, asking me to "Enter your name". This is a massive logic bug: a "new user" flow should never be linked to an existing 3-month-old ID.

Identifier Confusion: The UI displayed the QQ email address in the bottom-left corner, reinforcing the illusion of a separate identity.

I acted based on these explicit UI cues. I had no way of knowing that a "delete" command initiated from a "newly created" profile would wipe the data of my primary Google account.

[wang3cu-collab]