How Chat Works
Every message you send is locked in your browser before it goes anywhere. iMegha's job is simple: tell the other person "you have a new message." The actual message? That stays in your cloud. iMegha never sees it.
Sending a Message
You message a colleague about a case
You need to discuss a confidential case with a colleague. You open iMChat, type your message, and hit send. Here's what happens behind the scenes — all in a split second:
You type a message
Write your message in the iMChat window, just like any other chat app.
Browser locks the message
Before the message leaves your device, your browser scrambles it into unreadable text.
Stored in your cloud
The locked message is saved in your own private cloud — not on iMegha's servers.
Recipient gets notified
The platform sends a heads-up: "You have a new message." That's all it sees.
They read the message
Their browser fetches the locked message from your cloud, unlocks it, and displays it.
The message content travels directly between your cloud and the recipient's browser. iMegha is just the doorbell — it rings, but it never opens the letter.
What iMegha Sees vs. What You See
Here's the same message from two perspectives. On the left is what you and your colleague see. On the right is what iMegha's servers see.
What you see
"The client showed improvement this week. Blood pressure is down to 130/85 and responding well to the new medication. Can we discuss adjusting the dosage at Thursday's meeting?"
Clear, readable text -- exactly what was typed.
What iMegha sees
a]#kx8$mQ!vR2&nL9@pW3*fY7^bK0+dH5~jT4%cZ6(eA1)sU8_gM2|oI 7<qX3>rN5/wB9,hE6.yF0:lP4;uJ8=tV1?kG3!zD7#aC2$xS6%mO9^
Meaningless scrambled data. No way to reconstruct the original.
The server cannot leak what it cannot read
Even if someone broke into iMegha's servers, they would find nothing useful -- no messages, no names, no patient data. The platform genuinely does not have access to your conversations.
Why This Matters for Sensitive Conversations
Most chat services store your messages on their servers -- readable by their employees, vulnerable to breaches, and subject to government requests. iMChat is different because your messages are never on a third-party server in the first place.
Healthcare
Patient information never sits on a third-party server. Discuss cases with colleagues knowing the data stays in your cloud.
Legal
Attorney-client privilege stays privileged. Confidential case discussions never pass through a platform that could be subpoenaed.
Personal
Your private conversations are truly private. No company employee can read them. No data breach can expose them.
Group Conversations
Group chats work the same way, with one small addition: when you create a group, iMegha generates a shared lock that all members can use. Each member gets their own personal copy of this lock, wrapped so only they can open it.
The result: everyone in the group can read the messages, but no one outside the group can -- including iMegha. When someone is removed from the group, their copy of the lock is revoked and a new one is created for the remaining members.
How group messages flow
You type a message and your browser locks it with the group's shared lock.
The locked message is stored in your cloud.
iMegha notifies every group member: "New message in the group."
Each member's browser fetches the locked message from your cloud, unlocks it with their copy of the group lock, and displays it.
Messages stay in the sender's cloud
In a group with five people, when you send a message, it's stored once -- in your cloud. The other four members read it directly from your cloud. No copies are made anywhere else.
How iMChat Compares
Traditional chat services
- Messages stored on the company's servers
- Company employees may have access
- Server breach exposes all conversations
- Subject to government data requests
- You trust the provider to keep things private
iMChat
- Messages stored in your own cloud
- No one at iMegha can read them
- Platform breach exposes nothing readable
- Data requests go to you, not us
- Privacy is enforced by math, not policy
Want the full technical details? Algorithms, key exchange, and protocol specifics are in the Technical Whitepaper.