Rhinobird ties generations, credits, and History to the account you use at Login / Sign up. Losing access—wrong Google profile, expired password, or an old work email—feels urgent when a campaign deadline looms. This article explains how to sign in again on the English UI, how to avoid creating a duplicate empty account, and when support must help you recover the original profile.
Open Login / Sign up the right way
From any tool page, use Login / Sign up in the product chrome. The international site offers:
- Continue with Google — Uses your Google identity; pick the same Google account you used for past Generate runs.
- Continue with Email — Uses email and password credentials registered to Rhinobird.
After success, open History to confirm prior runs appear. If the list is empty but you expected assets, you are likely on a different identity—sign out and retry with the other method or email.
Recover email-and-password access
- Confirm which email address receipts and Rhinobird messages use—that is probably your login.
- Restore mailbox access with your email provider before blaming Rhinobird.
- Return to Login / Sign up, choose Continue with Email, and use any on-screen password reset or recovery link.
- Complete sign-in in the same browser profile where you will generate, so session cookies stay consistent.
If no reset link appears in the UI you see, do not invent steps—contact support with the registered email so staff can guide verified recovery.
Recover Google-based access
Google sign-in fails when you pick a personal Gmail while the team previously used a Workspace account, or when browser profiles swap. Sign out of Rhinobird, click Continue with Google, and explicitly choose the account that owns payment history. If Google itself is locked, fix Google recovery first; Rhinobird cannot override Google authentication.
Avoid duplicate accounts
Creating a fresh login because the old one “does not work” splits credits and History. Before you register anew, try both Google and email paths, incognito with only one extension disabled, and another browser. Duplicate accounts slow support investigations and may violate one-account-per-user expectations in Service Agreement.
Session issues that look like password loss
Sometimes you are still signed in but the UI froze—refresh once or open History directly. Corporate SSO is not described here; if your company wraps browsers with special policies, test a standard Chrome or Edge profile. Clear site data only for Rhinobird if support asks; avoid wiping all cookies unless necessary.
When support must intervene
Escalate when you cannot access the registered email, Google account is permanently lost, you suspect unauthorized access, or login errors persist after verified credentials. Contact 13378452864 or support@rhinobird.ai. Provide the email on file, approximate last successful sign-in, and screenshots without sharing passwords in email bodies. Privacy handling is covered in Privacy Policy; company details appear on About Us.
After you regain access
Verify credit balance and recent History entries before large batch Generate runs. Update team documentation with the canonical login method—Google vs email—so the next handoff does not repeat the same lockout. Store recovery codes for Google and email in your team password manager, not in chat logs.
Most login problems are wrong-account selection, not platform data loss. Match the identity that originally generated, then use support for verified recovery when mailboxes or Google profiles are gone.