What a chief of staff reads for you, and what it leaves alone
Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. Everything useful it does starts with reading. It cannot follow up a deadline it has not seen or draft a reply to a thread it does not know about.
Which makes the edges of that reading the first thing worth being clear about. Not as a policy document, but as the plain answer to a question anybody sensible asks in the first minute: what is it looking at.
What it reads
Messages and todos provide the starting point.
Your messages, direct and group. The conversations you are part of. This is where commitments get made in a small company, so it is where most of the useful material is.
Your todos and their deadlines. What you have said you will do and when it is due, laid out on a calendar by due date. This is what lets it tell the difference between a busy week and a week where you have promised three things on the same day.
For data handling, model providers and retention, read the privacy policy. Conversation access and data retention are separate questions.
What it leaves alone
Conversations you are not a member of. Administrators cannot read other people’s private messages or groups they have not joined.
Permission to act. Reading a conversation does not authorize an AI reply to be sent; you decide which draft to send.
What it does with what it reads
Three things, and again the list is short because the limits are the point.
It may suggest. A suggested todo still needs a clear action, owner and deadline before the people involved can use it as a commitment.
It drafts. It writes the reply you were going to write, knowing the thread and knowing what you already said. Getting from an empty box to a decent draft is most of the work in a message, and it does that part.
It reminds. It follows up your todos and their deadlines, so the thing you agreed to on Tuesday is still in front of you on Friday rather than depending on your memory of a scrolled thread.
What it does not do with it
You choose which AI replies to send. AI replies are drafts you choose to send, signed in purple. Reminders you create for yourself can be scheduled, while reminders created by someone else require approval.
It does not decide. It can tell you that three deadlines land on Thursday. It cannot tell you which one to miss, because that depends on which customer is fragile this month and which colleague you promised last time. That is your judgement and it stays yours.
Keep the source and the draft distinct. A reply draft is something you review; sending it remains your decision.
Put those together and the shape is the same as the human job the name comes from. A chief of staff in a real company reads along, chases what was supposed to happen, prepares the material and writes the first version. They do not take your meetings or make your calls, and the reason is not modesty about their ability.
Why the boundary is what makes it usable
A company of ten has nobody whose job is to evaluate this. There is no security review, no procurement, no policy person. One person reads a page, forms a view in a few minutes, and either tries it or does not.
Under those conditions a long list of capabilities is not reassuring. Start with a concrete check: compare a draft against its source before choosing to send it.
That is four sentences. You can repeat them accurately after reading them once, which matters because the second person to use it in your company will hear about it from the first person rather than from a page like this one.
There is a second reason, which is about what people are willing to write. Every small company has conversations that are useful and uncomfortable: this is not working, I think we are wrong about the customer, I am struggling. Those happen somewhere. If the company’s own tool might be readable by the company, they move to a personal channel where nobody who could act on them will ever see them.
How to check it rather than take it on trust
Run a short evaluation in a test account or an environment the vendor has approved, using synthetic messages and harmless test records rather than customer or colleague conversations.
- Check whether an AI reply stays a draft until you approve it. Review scheduled reminders separately, since their sending rule may differ.
- Compare each proposed todo with a conversation you can access. Record whether the owner, action and date are supported by what was said.
- Read the draft before sending it. Check the recipient and the proposed next step against the conversation.
- Check the privacy policy for the handling and retention of account content and connection data.
Keep the results for an evaluation week before inviting colleagues. This can verify visible behavior in that account; it cannot replace a written data-flow explanation or production access tests for roles you do not control.
Where Opitor fits
Compare a draft with a conversation you can access before sending it. The role checklist helps you assess whether the next action is clear; the FAQ explains the current sending and access rules.
Updated 2026-11-10