Most apps ask for a lot before they let you in: an email address, a password, a password you must confirm, a recovery question, a birthday. SecXChat asks for two things — your phone number, and a one-time code sent to it. That is the whole signup. There is no password to invent, remember, or forget, and no email address involved at any step.
It starts with the download. Get the app from the official download page and install it; it is about 63.8 MB and runs on Android 6.0 and newer. Open it, and the first thing it asks for is your phone number. Enter it in international format — the country code first, then the number — and double-check it before you continue, because the code that proves the number is yours is about to be sent to exactly that number.
Within a moment, a six-digit code arrives by SMS. It is valid for five minutes, so enter it promptly. Type the six digits into the app and you are in — the code matches, the number is confirmed as yours, and the account exists. Then add your name, the one people call you, and you are done. From download to first chat is a few minutes, and most of that is the download itself.
There is a reason the signup is this short. A password is a burden that falls on you and a risk that falls on the app: passwords are forgotten, reused across services, guessed, and leaked in breaches that have nothing to do with you. By not having one at all, SecXChat removes the most common way accounts are taken over. There is nothing to phish, nothing to reset, and nothing to leak. The one-time code is the key, and it works once and then dies — five minutes later it is useless to anyone, including you.
That short life is also why the code deserves care. The code is the proof that a number is yours, so it should be treated like a key: never share it with anyone, in any chat, for any reason. No genuine message from SecXChat will ever ask you to send your code back. If someone messages you claiming to be support, or a friend, or the app itself, and asks for the code that just arrived on your phone — that is the attack. The code is for the app's box on your screen, and nowhere else.
If the code does not arrive, do not panic, and do not request a dozen codes at once. First check the number you entered — one wrong digit sends the code to a stranger's phone, or to no phone at all. Then wait a minute and tap Resend. Codes expire after five minutes, and for safety there is a limit on how many codes one number can request in an hour — if you hit it, wait and try again. On a weak signal the message can also be slow; moving to a spot with better reception is often all it takes.
Once you are in, your account is your number. Lose the phone, and the same number signs you back in on the new one — and if chat backup was switched on, your history comes back with it. Change your number one day, and you will need to set the account up around the new one, so keep the number you sign up with as stable as you can. It is the only identifier the app has for you, which is precisely why it is asked for so carefully and why nothing else is.
Reinstalling the app, or moving to a new phone, works the same way: install SecXChat, enter the same number, and type the new one-time code that arrives. Your account is waiting behind that number, and if chat backup was on, your history is offered back during setup — the same code, the same number, the same account.
That is the trade SecXChat makes, and it is a deliberate one: less information from you, more responsibility carried by the app. No email to sell, no password to leak, no profile to build from data you never meant to give. Just a number, a code that lives for five minutes, and your name. The rest is messaging.
