Trust
Security & trust
What MonitorSky can access, what it stores, who processes it, and what we do to protect it.
Last updated: November 14, 2026
Microsoft 365 requirements
- Senders sign in with a Microsoft 365 work account that has Microsoft 365 Business Basic or higher. In some organizations an IT admin has to approve MonitorSky first.
- Recipients do not need a license. They can use a personal or a work Microsoft Teams account.
- Free personal Teams account only? A free personal account cannot send campaigns. Contact us and we will help you migrate, typically within 2 to 4 business days depending on the number of contacts.
What MonitorSky can access in Microsoft 365
When you sign in, Microsoft shows a consent screen with four permissions. They are delegated permissions: MonitorSky acts only as you, inside your own account, and only with what you could do yourself in Microsoft Teams. These four are the only permissions MonitorSky asks for.
- Read and write user chat messages (Chat.ReadWrite): MonitorSky creates one-to-one chats with your contacts, sends the messages of your campaigns, reads the replies in those chats and syncs your contacts from your Teams chats.
- Send user chat messages (ChatMessage.Send): MonitorSky sends your campaign messages on your behalf.
- Sign in and read user profile (User.Read): signs you in and shows your name and email.
- Maintain access to data you have given it access to (offline_access): keeps you signed in without asking every time.
How to revoke access.
- Each user: remove MonitorSky at myapps.microsoft.com.
- A Microsoft admin: remove MonitorSky for the whole organization in Microsoft Entra (Enterprise applications).
Removing the permission at Microsoft stops MonitorSky from using it. Data already stored in MonitorSky stays until it is deleted as described in the Privacy Policy.
What we store and for how long
In short, as stated in our Privacy Policy (the policy is the full and binding statement):
- Your account details, contacts, groups, campaigns and messages: kept while your account is open. How long they are kept after you close your account, and how to have them deleted, is set out in the Privacy Policy (section 5, "How long we keep data").
- Encrypted nightly backups, with rolling retention (see the Privacy Policy).
- Error logs: 90 days, deleted automatically.
- Help-chat questions and answers: 90 days.
The policy lists every category, including the Microsoft sign-in tokens, with its period.
Where data lives and who processes it
Our servers and database are in the United States (New York). Encrypted backups are kept in Germany. These providers process data for us or are part of the service:
| Provider | What it does | Where |
|---|---|---|
| Hivelocity, Inc. | Server and database hosting | United States (New York) |
| IONOS SE | Encrypted nightly backups | Germany |
| Cloudflare, Inc. | DNS for monitorsky.cloud; proxy, TLS and DDoS protection for the website and app pages only (not the API, statistics or live-update service) | Global |
| STRATO AG | DNS only, for the live-update service address | Germany |
| Supabase, Inc. | Used by the live-update service: your MonitorSky user ID with the time each stream token was issued and expires, and technical error details | United States (N. Virginia) |
| Microsoft Corporation | Teams, Microsoft Graph and sign-in; also hosts the mailbox of our contact address | US and global |
| Anthropic, PBC | Help-chat answers | United States |
| Google LLC | Google Analytics 4, only after you accept cookies | US and global |
| Umami (self-hosted) | Cookie-free website statistics | United States (New York), on our own server |
For international transfers and your rights, see the Privacy Policy.
Security measures in place today
- Encrypted connections (HTTPS) for the app, the API and the statistics site, with Strict-Transport-Security (HSTS).
- Security headers on those sites: X-Content-Type-Options and Referrer-Policy everywhere, and the app limits where it can be embedded.
- The database is not reachable from the internet, and access to servers and the database is restricted to authorized personnel.
- Stored Microsoft access and refresh tokens, and app credentials, are encrypted at rest.
- Nightly database backups are encrypted, with rolling retention (see the Privacy Policy), and restoring from an encrypted backup has been tested.
This list only contains measures that are in place today. We update it when that changes.
Verified publisher and standards
Verified publisher on Microsoft Entra.
Microsoft has verified MonitorSky's publisher identity.
MonitorSky is implementing an information security management system (ISMS) with reference to ISO/IEC 27001:2022. MonitorSky is not certified.
Report a vulnerability
If you think you have found a security vulnerability in MonitorSky, please email [email protected] with a description and the steps to reproduce it. Please do not access data that is not yours, and do not publish details before we have had a chance to fix the problem.
The same contact is published in /.well-known/security.txt.