Privacy
SmsVeo

What registration without an identity document means here

SmsVeo’s current registration form requests a name, email address, password and password confirmation. It does not include an identity-document upload. This is the precise scope of the document-free registration described on this site; it is not a promise that every operation collects no information or that a target platform will waive its own checks.

KYC is commonly short for know your customer. The phrase covers identity checks in different contexts, so a general no-KYC label needs a stated scope. Check the service’s confirmed registration and order conditions instead of interpreting the absence of one field as a guarantee about all account processing.

Account data

Registration requests your name, email and password. Account, payment and support actions use the account service; if it is unavailable, these operations cannot be completed.

Requests from the account area carry your session credentials. Do not share the device or session while a number or message is displayed.

Keep the session and screenshots private too

Protect the account that contains your messages and sign out on shared devices. Avoid displaying an OTP during a screen share. A screenshot of a private inbox becomes public information if you post it. Mask codes and personal details when asking for support.

Keep the code for the service screen you opened yourself. Someone who contacts you and knows a name or order reference is not entitled to the code. To describe a reception problem, provide the activation state, request time, service and country instead of publishing the message or handing over account credentials.

Crypto payment does not itself provide anonymity

The payment method and the service’s data handling are separate issues. Bitcoin.org explains that Bitcoin transactions are public and can be traced through addresses and transaction history. Paying in crypto therefore does not establish that an order, account or message is anonymous. Other assets have their own transaction systems; do not generalise one network’s details to every asset.

A top-up starts from 20 USD and is separate from buying an activation. Read the asset, network, destination and amount in the actual invoice instructions, then follow its account status. An outgoing transfer is not proof of a credited balance. Never disclose a wallet’s recovery phrase or private keys in a support conversation.

How information is used

Where the account service is available, account details support registration, authentication and account management. Order and transaction records support delivery, billing, payment verification and support. Messages are used for the reception requested in the order.

Session cookies

When sign-in is available, a session cookie supports access to private pages. Keep the session private on shared devices and sign out after use.

Service providers

Depending on the deployed service, hosting and database providers handle site records, SMS providers allocate numbers and route messages, and payment infrastructure verifies blockchain transactions. Support and email providers may handle requests. Only the information needed for each function should be shared.

Data retention and requests

Retention depends on the account’s operation, order tracking, support needs, disputes and applicable obligations. Message content should be removed or minimised when it is no longer needed for reception or support, subject to those obligations.

Use the contact email to request access, correction or deletion of your data, or to ask about applicable privacy rights. Identify the account and request without sending a password or OTP. Identity may need to be verified before disclosing or changing private records.