Sooner or later, every app needs a human. A message that will not send, a backup that will not restore, a code that never arrived, a setting that does not do what it says — the moment you need help, the question is where to find it and what to say so the answer comes quickly. For SecXChat, the answer is simple: email support at support@secxchat.com, any time, from any email account.
Before you write, try the two checks that solve the most problems on their own. First, make sure you are on the latest version — download it from the official SecXChat download page and install it over your current app, because many small problems are already fixed in the newest build, and support will ask you to update first anyway. Second, check the FAQ page on the website: it answers the common questions — signup and codes, backup and restore, view-once media, screenshot alerts, calls, statuses and the rest — in plain words, and it may already have your answer. If neither helps, write to support; that is what the address is for.
A good support message has four parts, and writing them takes two minutes. First, what happened: one or two sentences describing the problem as you saw it — "my backup has been stuck at the same point for an hour", "my code never arrived", "the app closes when I open a video". Second, what you expected: "I expected the backup to finish", "I expected a code within a minute". The gap between what happened and what you expected is the problem, and naming both halves makes it visible. Third, what your screen showed: the exact words of any error message, and what you were doing just before it happened — which screen you were on, what you tapped, whether you were on Wi-Fi or mobile data. Fourth, your app version, if you know it: it is on the download page for the newest release, and it tells support exactly which build you are running.
There are two things never to put in a support email. The first is your one-time code. Support will never ask for it, no genuine message from SecXChat will ever ask you to send it back, and a code sent by email is a code anyone reading that email could use. If someone claiming to be support asks for your code, stop — that is not support, and you should block and report them. The second is anything you would not want a stranger to read: passwords, bank details, private photos. Support needs to know what went wrong, not who you are beyond your account; describe the problem, not your life.
What happens after you send it? Support reads your message and writes back to the same email address, so use an inbox you actually check, and keep an eye on it after you write. If the problem needs a fix in the app, it goes to the people who build it, with your description attached — which is why the details matter: a vague report ("the app is broken") can take days to untangle, while a precise one ("backup stuck at the same point for an hour, on version 3.0.5, on Wi-Fi") can point straight at the cause. If you do not hear back, reply to your own message rather than starting a new one, so the thread stays together and nobody has to ask you the same questions twice.
Asking for help is not a failure — it is how an app gets better. Every support message is also a report about the app itself: if ten people write about the same screen, that screen gets fixed. So write clearly, include the four parts, leave out the code and the private details, and send it. The people on the other end are the same people who build the app you use every day, and the fastest way to help them help you is a short, honest message about exactly what you saw.
While you wait for a reply, there are two things worth doing. First, keep using the app normally unless the problem stops you — a support answer often asks you to try something, and it is easier to try it while the problem is still fresh in your mind than a week later when you have forgotten what went wrong. Second, if the problem is urgent — you cannot sign in, your chats will not restore, a code never arrives — say so plainly in your first message, so support can see at a glance that it needs attention now rather than later. A clear subject and an honest first line do more than a long message ever will. And when the answer comes, write back and say whether it worked: a closed loop helps the next person with the same problem, because the fix that worked for you is the fix support will offer them next time.
