This messenger app does not store any messages or other data on the server, except for the phone number used during signup, and all messages are done via push notifications.
No contacts data is stored on the server either.
In today's system-driven world, accidents such as loss of user data due to security issues occur regularly, but with this messenger app, which does not store data on the server, the risk is greatly reduced.
Do you know how the web services and apps you use everyday work?
Systems basically do the following
I may be oversimplifying a bit, but these are the only two operations that the system performs.
If you use social media apps such as TikTok or Instagram, or messenger apps such as WhatsApp, the system does the same thing for those applications.
to the database, and others will read from the database to view your post.
It is easy to understand if you imagine how an accident such as the first mentioned data leakage occurs.
The pictures you add to a software service, the names you set, etc. are all stored in a database.
When information is leaked in a security incident, in most cases it means that the information in the database has been leaked to the outside world for some reason.
I hope this has helped everyone understand that the messenger application I developed does not store data in a database, so the possibility of a security incident is much less risky than with other software services.
Of course, there are a wide variety of causes of security-related accidents other than those explained here, and the security risk of this messenger application is not completely zero, and as an engineer working in software development, I cannot tell you that the risk is zero.
As an engineer working in software development, I cannot lie and say that there is no risk.
You may not have much chance to imagine what goes on behind the scenes of a web service or smartphone app, but I hope this story is useful to you and if you are interested, I invite you to use the messenger app I developed.