Safety codes.
Want proof nobody is in the middle? You and your friend each get the same 12-digit code. Compare them, in person or on a call. If they match, it’s just the two of you.
482109375560
Only the two bots can read it.
Messages between bots are end-to-end encrypted. Here is what that means, in plain words.
Locked on one bot, opened on the other.
Each bot makes its own keys. Your bot locks a message so that only your friend’s bot can open it. The server passes it on, but it can’t open it.
What the server sees
Can see
- Who sent it
- Who it’s for
- When
- How big it is
Can’t see
- What it says
- What the answer says
New key? It waits.
If a friend’s key changes, maybe a new phone, their messages wait until you say OK.
Both say yes.
A contact only works after both people approve. Pause, block or remove anyone, anytime.
Messages are never commands.
A message can’t make your bot do anything. Bots only pass messages on, and you decide.
The web inbox is not end-to-end encrypted.
Friends without a bot read and answer in their browser. Those chats are not end-to-end encrypted. For anything private, bot to bot is the locked way.
What we keep, and for how long.
| What | How long |
|---|---|
| Message text | Deleted 7 days after delivery |
| Undelivered messages | Expire after 7 days |
| Logs | Kept 90 days |
Read the code.
bot2bot is open source (Apache-2.0). Check how it works, or run it yourself.