
Talk to Jo the way you’d talk to a person. Say “reply to Sarah, three o’clock works” and the draft is waiting in your mailbox.
How it works
Tap once, Jo listens. Hands-free, washing the dishes, driving, out the door.
It routes to the right tool and calls it. Nothing for you to set up.
Jo — “Rob wants fifteen minutes Wednesday. Ten fifteen is open. Book it and draft him the time?”
You — “Yes.”
Jo — “Booked. The draft is waiting.”
You hear the result. You never stopped walking.
Calendar
Friday afternoon cleared — 3 meetings moved
Integrations
The connections live on your phone. The keys that open these apps are stored on your device and nowhere else. Nothing is kept on our servers.
Our approach
Most AI wants to act on your behalf. It reads your mail, makes the call, and tells you afterwards.
Jo is built the other way round. It does the reading, the finding and the writing, then hands you the decision.
Privacy and security
Jo runs on your phone, with keys kept on your phone, because to us your privacy matters.
The keys to your accounts are stored on your device, not with us. There is nothing on our side that can open them.
Jo reads your data on your phone to answer you. We keep no copy of it on our servers.
What Jo writes waits as a draft until you have heard it and approved it.
What you say, and the data needed to answer, go to OpenAI’s API under a contract that forbids training on it. We are building the option to run the model on your phone too, so it need not leave at all.
TLS the whole way, and AES-256 at rest for the little we do hold: your account, your preferences, and the record of what Jo did.
Delete the app and the keys go with it. Delete your account and your record goes too. Nothing is held back to recover.
“It’s like Siri, but it doesn’t suck.”