OpsPocket security

Last updated: 10 November 2026

OpsPocket holds SSH keys and runs commands on your servers, so it's built so that you don't have to trust us with them. This page says how, in plain words, for you and for your company's security team. What data goes where is in the privacy policy. A one-page summary to share is at opspocket.app/security-overview.pdf.

The short version

What we can and can't see

Your server addresses, user names, keys, passwords, commands, files, terminal output and agent chats never reach Mt7. There is no OpsPocket account and no OpsPocket cloud that holds them.

Only three things ever reach a server of ours, and none of them carries your server data:

The Assistant talks to the AI provider you choose, with your own key, and asks before it first sends anything. The agent chat runs the AI CLI that is already signed in on your server, under your account there.

On your phone

On the connection

Changes to your servers

Every connection, visible

For security and compliance teams

Report a vulnerability

If you find a security problem in OpsPocket, opspocket.app or opspocket.mt7.io, email developer@mt7.in with "Security" in the subject. Please include what you found and how to reproduce it, and give us a reasonable time to fix it before telling others. We answer within 2 working days, keep you updated, and credit you in the release notes if you'd like. We treat reports made in good faith as help.

Our contact details for researchers are also at opspocket.app/.well-known/security.txt.

Limits

No app can be perfectly secure. Keep your phone's own screen lock on and its system up to date. If we learn of a problem that puts your data at risk, we'll fix it, say so in the app's release notes, and tell the authorities where the law requires it.