Who operates JAT Messenger?
JAT Messenger is an independent Bangladesh-built messaging project by Jahangir Alam Talukder. Contact: jahangirtalukder07cse@gmail.com.
Information we process
When you sign in with Google, the service receives a verified Google account identifier, email address and display name. It creates an internal account ID, a unique public JAT ID, optional username, contact requests, messages, account sessions, blocks and call signaling/history. It may process request metadata to detect abuse.
How we use information
To authenticate users, support contacts, route one-to-one messages and calls, prevent unauthorized access and abuse, and operate or improve the pilot.
Storage and service providers
Cloudflare Workers, D1 and Durable Objects are planned to process account records, messages, and signaling. Google handles account sign-in. Audio is sent between browsers using WebRTC when a direct connection works; this pilot does not record calls or store call audio.
Encryption and limitations
Connections should use HTTPS/WSS in production; WebRTC media is encrypted in transit. Stored messages are not end-to-end encrypted in this MVP. Service operators with authorized administrative access to the database may be able to access stored messages. Browser-closed call notification is not guaranteed.
Cookies and retention
We use an HttpOnly login cookie and a temporary one-time Google sign-in nonce. Account records and conversations are retained until deletion or a later policy change; future retention limits must be defined and documented before public launch.
Account deletion
Use Profile > Delete my account while signed in. The D1 schema uses cascading deletion of the account and associated messages, contacts and sessions. Deletion does not remove records already copied to a recipient's separate service or backups immediately.
Contact
For privacy questions, email jahangirtalukder07cse@gmail.com.