PolyBuzz Chats Missing After Sign-In? Check the Account First

If your PolyBuzz chats appear missing immediately after sign-in, verify the account before deleting anything. An empty history is an observation, not proof that the original conversations were erased. It may also mean you opened a different account or conversation.

The PolyBuzz Privacy Policy describes Google, Apple and email registration. That makes the original sign-in route relevant to a missing-history investigation. This guide does not promise that two sign-in methods merge, that a guest session transfers automatically or that a deleted conversation can be recovered.

Preserve the last working session

If one device still shows the conversation, leave that session intact while checking the other device. Avoid reinstalling the app, clearing all storage or signing out everywhere as your first experiment. Those actions can remove clues or access that may be useful to support.

Write down the visible account identifier, sign-in method you remember, device and approximate date of the last successful access. Keep sensitive identifiers in your own record; do not publish them in a public help thread. You generally need the fact that two identifiers differ, not a public copy of both.

Reconstruct the sign-in path

Consider a fictional example. Alex used one Google account in a browser last month, but the phone now opens with another Google account selected. The name on the phone may look familiar while its PolyBuzz identity differs. That is an account-matching problem until evidence shows otherwise.

Check these items in order:

1. Which account identifier is visible in the working session, if available?
2. Did you originally choose email, Apple or Google?
3. Which identity did the current provider account chooser select?
4. Was the older session a registered account or a guest session?
5. Is the history empty everywhere, or only on one device or in one conversation view?

Google’s linked-apps guidance explains how to review connections from a Google account. That can help you confirm which Google identity is associated with an app. It does not establish that Google can restore PolyBuzz’s conversation history or that removing a connection fixes the problem.

Compare observations without assuming a merge

Make a short two-column record: “working session” and “missing session.” Note the platform, sign-in route, visible identifier and whether any other conversations or purchases appear. A purchase receipt can be a clue to the original identity, but avoid sharing payment details unnecessarily.

If the identifiers differ, do not create more accounts to see what happens. Return to the original sign-in route if you can do so safely, or ask official support how to identify the intended account. Do not assume identical display names or email-looking text guarantee that two login paths resolve to one account.

If the identifiers match but the history differs, record the affected conversation, time and exact symptom. “The chat list is empty on mobile, while one conversation remains visible in the browser” is more useful than “everything disappeared.” Avoid restarting or deleting the surviving conversation as a test.

Ask support a question it can investigate

Provide the platform and version, approximate last access, original sign-in method, whether another session still works and a redacted account identifier through the official support route. Ask whether the issue concerns account matching, synchronization or a removed conversation.

No support volunteer needs your password or a one-time authentication code. Keep the working session and your small evidence record until you receive an answer. If support confirms that data is unavailable, distinguish that confirmed outcome from the earlier uncertainty; repeated destructive cleanup will not supply missing evidence.