Something broken, something wrong, something worrying: all of it is worth telling us. Textly has no analytics collecting crashes in the background, which means a report from you is genuinely how we find out.
Write to [SUPPORT EMAIL] with:
Screenshots help enormously, but please blur personal message content first.
First, inside the app: mark the message as spam. That correction improves detection on your device immediately.
Then, if you are willing, send us the message pattern: the wording and the link domain, with your own details removed. Fraud campaigns run against thousands of people at once, and one report sharpens the filter for everyone.
If money was involved, contact your bank first and report it to your national fraud authority. That matters more than telling us.
A legitimate message in Spam, or an extracted appointment with the wrong time. Move it back or correct it in place. Textly learns locally from that.
Tell us as well if it keeps happening with the same sender. A repeated false positive is a bug in the model, not in your usage.
If you believe you have found a vulnerability, or anything that contradicts our claim that nothing leaves your device, write to [SECURITY EMAIL] and please give us a reasonable window to fix it before publishing.
We do not currently run a paid bug bounty. We do take these reports seriously, respond to every one, and credit researchers who want to be named.
We cannot read your conversations and we would rather keep it that way. When a report needs message content (a scam wording, for example), remove everything that identifies you or the people you talk to.
Names, phone numbers, addresses, account details and anything a stranger could use to identify someone.
The sender type, the wording, the link domain and the time. That is what makes a report useful.
We will never ask for a password, a code or a login token. Not in support, not ever. Any message that does is not from us.
[SUPPORT EMAIL]
Typical response within [X] business days.
[SECURITY EMAIL]
Vulnerability reports and privacy concerns.
Keep reading