What we expect from a chat
We're used to messages being sent instantly. You type, hit send, and a second later the double tick appears. It doesn't matter if the other person is asleep, has no signal, or their phone is off. The message 'sends' anyway. We've accepted that as normal.
But there's a question almost nobody asks: if the other person isn't connected, where is your message in the meantime? The answer is simple: on a server. A company has it stored on their machines, waiting for the recipient to connect to deliver it. Meanwhile, the message is there. On a hard drive that isn't yours. In a data center you don't control. Under privacy policies that can change tomorrow.
The invisible price of immediacy
That immediacy has a price you don't see. For a message to 'send' when the other person isn't connected, someone needs to store it somewhere. That someone is the company's server. And that server, by storing your message, also records who sent it, who it's addressed to, at what time, and from where. Even if the message is encrypted, that data — the metadata — is recorded.
In other words: the convenience of your message 'sending' instantly is exactly what allows someone to know who you talk to. It's not a side effect. It's the mechanism.
And there's something else. Many services assure that your messages are encrypted on their servers and that they don't read them. That's probably true. But the encrypted message and the keys to decrypt it are stored in the same infrastructure. Today the company's policy says those keys aren't used. Tomorrow the policy can change. An employee with sufficient access could use them. A cyberattack could obtain both at once. A court order could demand it. It's not that anyone is doing it. It's that the architecture makes it possible. And when a door exists, the question isn't whether someone will open it, but when.
Why Solo2 is different
In Solo2 there's no server storing your messages. When you write something and the other person isn't connected, the message stays on your device. It doesn't go anywhere. Nobody stores it. It waits on your phone or computer until the other person connects and both devices can talk directly.
That means sometimes there's a wait. It could be a second, an hour, or until the next day. It depends on when the other person opens Solo2. It's exactly like a phone call: if the other person doesn't answer, there's no conversation. Not because something is broken, but because that's how direct conversations work.
The wait is the guarantee
Think of it this way: if your message sent instantly even though the other person wasn't connected, it would mean there's a server receiving and storing it for you. And if there's a server storing your messages, then someone has your data. It's one or the other.
The wait you sometimes experience in Solo2 isn't an inconvenience. It's proof that nobody else has your message. It's the visible sign that the conversation is truly direct, truly private, truly yours. When you see your message waiting, you can be sure of one thing: it's only on your device and nowhere else in the world.
Like a call, not a mailbox
Most messaging apps work like a mailbox: you leave the message in a slot and someone picks it up when they can. Solo2 works like a phone call: you both have to be there for a conversation to happen. The difference is that when you finally connect, the conversation is absolutely private. Nobody listens. Nobody records. Nobody knows it existed.
That small moment of waiting is the price of real privacy. And for many people, it's a price worth paying.