Protect your account and recognize verification requests
Use the correct sign-in route and keep identity, payment and support requests separate.
On this page
Use a device and email account you control. Open Rentari from its known address rather than an unexpected message link.
Review sign-in protection
Check Account settings for the available password and two-step verification controls. Keep your verified contact details current.
Handle codes privately
Enter a one-time code only in the sign-in or verification flow you started. Support does not need your password or sign-in code in a message.
Distinguish verification purposes
Account sign-in, screening identity and payment-provider business verification are different processes. Read which request you are completing and use its secure form.
Respond to suspicious access
If you can still sign in, change the relevant credentials and review your account details. Contact support with the account email, time and suspicious activity; contact the payment provider about an unauthorized bank or card event.
Check the result
- You can identify the correct verification flow and report suspicious activity without exposing credentials.
FAQs
Is a new-device code proof of a breach?
Not by itself. A new browser or cleared cookies can require verification. If you did not start the sign-in, do not share the code and review your account security.
Where can I read about data handling?
Use Rentari’s current Privacy Policy and Terms linked on the site. This guide does not substitute for those policies or promise a particular certification.
Why is payment-provider KYC different from account sign-in?
Payment-provider verification checks the collecting person or business and the information needed for payment access. Sign-in verification checks access to your Rentari account. Complete the specific secure flow requested; neither should be substituted for the other.