Account data
The portal stores your email, display name, sign-in information and requests in its database. If you use Google sign-in, the site uses the Google account details needed to identify your account.
CheapOTP
Privacy
Information about data used by this website.
Session and interface choices
Cookies keep your sign-in session and chosen language. Your browser stores the theme and catalog width to remember your display choices.
How data is used
Account details support sign-in, your dashboard, and linking orders, wallet entries and support tickets to the correct user. The portal records IP addresses and basic security events to limit repeated sign-in attempts and review activity. Passwords are stored as hashes; admins do not need your password to help you.
USDT deposit history
The site stores your assigned deposit address, transaction hashes, USDT amounts, credit rates and wallet entries. Blockchain data is public; addresses and transactions can be looked up. The RPC service receives address/transaction queries to verify deposits. The site does not request customer seed phrases or private keys and stores no signing keys for deposit addresses.
Google, support email and providers
If you sign in with Google, the site uses the identity data needed to create or link your account and does not store Google tokens long term. When you rent a number, the selected provider receives the country and service; the site stores the number and OTP status returned for your order. If SMTP is configured, a copy of your ticket and email goes to the admin mailbox.
Retention, protection and contact
Sign-in sessions expire after eight hours. The local version does not yet have an automatic deletion schedule for accounts, orders and tickets; admins can view those records in the dashboard to provide support. Open a ticket to request review or correction of account information. Do not put secrets in support messages. Before public launch, the operator must publish its identity, retention periods and a workable data-request process.