Official connections only
Telegram connects through the official Telegram Business connected-bot API and Instagram through Meta’s official interfaces, and since we never ask for your account password there’s nothing on our side to keep.
Security and trust
Nobody here gets a master key
Signing in proves who you are. It doesn’t prove that this conversation is yours, that the channel is still connected, or that the protected part is open — those get asked again, each at the moment it matters. Agents answer the same questions you do.
Separated by owner
Conversations, contacts, and payments live in your own space, and the check that keeps them there runs in the database itself, a layer below the interface.
Messages kept as they arrived
A message holds the text, the timestamp, and the edit trail exactly as the platform issued them. An edit becomes another entry rather than a correction to the old one, and a deletion is recorded the same way. The thread you read is the thread that happened.
A code for sensitive content
A six-digit code arrives in WhatsApp and lives 5 minutes. The access it opens lasts 15 minutes and covers one conversation.
We stay inside the platforms’ rules
Where a platform allows an outbound message only inside a window, or only through an approved template, that’s the rule the product lives by. A send the platform would reject is turned down here first, and the rule gets named.
Answers point back at the messages
Anything the assistant tells you points back to the messages it read, and you can open them and check the claim yourself.
You set how far an agent goes
Advise, prepare, and act are named rungs, and you choose the one an agent stands on. A risky step waits for your yes. The conversation comes back to you the second you ask for it.
How access works inside
Least privilege at every boundary, agents included
The app, the agent runtime, the protected-content service, and the database each hold their own keys, and none of them can reach past its own job.
- An agent never outranks its person
An agent borrows the rights of the person it belongs to and loses them the moment that person does. A conversation you can’t open stays closed to it too.
- A separate service for protected content
Sensitive content is unlocked by a service with its own keys and its own rights in the database. The rest of the product never receives them. A bug in the app therefore can’t turn into an open door on the protected side.
- What a delivery log is allowed to hold
Delivery records hold a status and a short reason. Message bodies, codes, and keys don’t reach them.
Questions
What people ask about security
- Do you read my conversations?
- No. Content stays inside your own space, and the sensitive part sits behind a short-lived code on top of that.
- Can an agent send something I never approved?
- No. It works inside the rules and permissions you handed it, and any step that reaches another person can be held until you say go.
- Why is a WhatsApp code needed?
- So that one stolen session isn’t enough. The code proves the person opening the conversation is the one holding the phone. Whoever walked off with your open tab doesn’t have it.
- What if I lose access to WhatsApp?
- Everyday work with your conversations carries on. Only the content that needs code confirmation stays shut, and only until the number is back with you.
- Is any data passed on to others?
- Conversations are never sold and never handed over for advertising. The outside parties here are the platforms themselves and the payment side when you pay.