Copyright © 2026 Authors retain the copyright of this article. This article is an open access article distributed under the Creative Commons Attribution License which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

@article{192399,
        author = {Ronit Sarkar and Athava Vilas Shelke and Manish Mahimkar and Sahilkumar Basude and Rajni Ratnaparkhi},
        title = {Secure connect},
        journal = {International Journal of Innovative Research in Technology},
        year = {2026},
        volume = {12},
        number = {9},
        pages = {1344-1347},
        issn = {2349-6002},
        url = {https://ijirt.org/article?manuscript=192399},
        abstract = {These days, with all the cyber attacks and data leaks popping up everywhere, plus worries about who is watching our online stuff, its pretty clear we need better ways to keep communications private. I mean, secure digital privacy just feels essential now, especially in messaging.
This project I worked on for my final year engineering is called SecureConnect. Its a web app for secure messaging that uses end to end encryption, and it has this credit system where you top up as you go. Unlike those usual apps that make you subscribe or give away your data for free tiers, here you buy credits just for what you use, like chats or calls. That gives people more say in how they spend, which I think makes sense for folks who do not message a ton, or for small businesses and stuff.
You know, sectors like healthcare or finance could really use something like this for those quick secure talks without committing to big plans. Freelancers too, probably.
On the tech side, we built the front end with React.js to make the interface easy to use on the web. For the backend, its serverless with AWS Lambda and API Gateway, which handles the processing without needing constant servers. Data gets stored encrypted in DynamoDB, including user info and credits. Authentication is through AWS Cognito, so logins stay secure.
The encryption part draws from the Signal Protocol, using things like libsodium or the WebCrypto API to keep messages private, just between the people involved. No one else can peek. Billing works by subtracting credits for each thing you do, say per message sent or minute on a call, all managed in cloud functions.
We followed agile methods to build it modularly, with ongoing deployments. It seems solid for scalability.
Sometimes I wonder if the pay per use is the best fit, some apps do freemium and it works, but others say it protects privacy more this way.},
        keywords = {Pay per use model, Encryption, Security.},
        month = {February},
        }