About
We built the memory Teams forgot.
Presify started with a green dot and a nagging question: was that person actually around today, or did we just catch them online?
Anyone who runs a remote or offshore team has lived this. Teams shows you a green dot in the moment, then forgets it the instant it changes. No yesterday, no last week, no pattern. So you end up guessing, or asking around in a way that makes good people feel watched.
We also knew what we did not want this to become. The market is full of tools that read messages, log keystrokes, and screenshot desktops, then hand a manager a productivity score. That is not insight, it is surveillance, and it quietly corrodes the trust that remote work runs on. We took the opposite bet: read the one signal Teams already publishes, presence, and nothing else. No message content, no files, no keystrokes, nothing installed on anyone’s machine.
That single constraint shaped the whole product. Presify turns presence into history you can actually use: when a team is reachable, how online time is trending, where time zones overlap, and the occasional pattern worth a second look. It is the difference between a hunch about how someone has been doing and a chart the two of you can look at together.
What we hold ourselves to
Read-only or not at all
Presify holds five read-only Microsoft permissions and zero write permissions. It cannot send a message, change a setting, or touch a mailbox in your tenant. By construction, not by policy.
Minimum data, maximum signal
We collect presence status changes and the basic directory information needed to label and scope people. Never email, chats, calls, files, or calendar content. If a feature would need more, the default answer is no.
Evidence, not verdicts
Every anomaly flag shows exactly how it was computed, and every report carries the same line: presence data is a starting point for a conversation, never a sole basis for action against a person.
Boring on purpose
Tenant isolation enforced in the database, encryption everywhere, least-privilege access, and an append-only audit trail you can export. The unglamorous parts are the product.
How we operate
- Where your data lives
- US-based AWS infrastructure, exclusively. Retention is bounded by your plan, and deletion tools are built in.
- When we answer
- Support runs Monday through Friday, 9am to 5pm US Eastern, through our contact form. Service health is public at /status, incidents included.
- What we promise in writing
- Our Terms, Privacy Policy, and Data Processing Agreement say the same things these pages do. The documentation lists every permission and what it is for.