> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rns.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign In to Your RNS.ID Account

> Sign in to RNS.ID with your password, an email verification code, a connected social account, or a supported crypto wallet.

Use a method already connected to your RNS.ID account. Go to [rns.id/app](https://rns.id/app) and select **Sign in**.

## Sign in with email and password

1. Enter the email address connected to the account.
2. Enter the password.
3. Select **Sign in**.

If you forgot the password, use [Reset your password](/getting-started/reset-your-password). Do not create a second account just to bypass a sign-in problem; purchases and applications remain associated with the original account.

## Sign in with an email code

Select **Sign in with verification code**, enter the account email, and request a code. Enter the code received by email to complete sign-in. A code is time-limited; request a new one if the previous code has expired.

## Sign in with Google or Apple

Select the same provider you previously connected. Using a different provider or a different provider account may open another RNS.ID account instead of the one containing your services.

If an existing Apple account still uses an Apple Private Relay address, sign-in can pause at **Update your contact email**. You must verify a non-relay email address before continuing. This replaces the RNS.ID account email; it does not merge accounts. Follow [Apple Hide My Email and RNS.ID](/getting-started/apple-private-relay-email).

## Sign in with a crypto wallet

1. Select **Continue with Crypto Wallet**.
2. Choose the wallet and account previously connected to RNS.ID.
3. Review and sign the login message.

Wallet-prompt text can vary by wallet and network. The sign-in flow should request an off-chain signature rather than a token approval, asset transfer, or blockchain transaction. Sign only after starting from `rns.id` and confirming that the displayed purpose and address match. Do not treat a no-gas statement alone as proof that a prompt is safe, and do not share the resulting signature.

<Warning>
  Do not approve a token allowance, asset transfer, or blockchain transaction when you only intend to sign in. Cancel the request and review [Security and scam reporting](/support/security-and-scam-reporting) if the wallet prompt is unexpected.
</Warning>

## Location-based access restrictions

RNS.ID does not provide services in restricted countries or regions. The production sign-in page checks the location of the current connection before password, email-code, Google, Apple, wallet, and 2FA authentication. The applicable list is maintained dynamically and is not reproduced in this documentation.

If the product displays a restricted-location notice, changing the sign-in method does not bypass the restriction. Do not attempt to evade the control by changing networks or masking the connection location. [Contact RNS.ID Support](/support/contact-us) to ask what assistance or account-record access is permitted under the applicable restrictions.

## If sign-in fails

* Confirm that you are using the original email, Google account, Apple account, or wallet.
* Check spam or junk folders for email codes.
* Request a fresh code instead of repeatedly entering an expired one.
* Temporarily disable browser extensions that block the sign-in window, then retry in a current browser.
* For wallet sign-in, unlock the wallet and switch to the account already connected to RNS.ID.
* If a restricted-location notice appears, stop switching sign-in methods and follow the support route above.

For authenticator-based 2FA, five consecutive failed codes lock 2FA sign-in for 15 minutes and trigger a security-alert email. Stop retrying, set the authenticator device's date and time to automatic, and wait for the lock to end before entering the newest code. If the alert was not caused by you, change the account password and [contact support](/support/contact-us).

See [Troubleshooting](/support/troubleshooting) or [contact support](/support/contact-us) if you still cannot sign in.