flashcatcloud · GraceWalk · Jul 9, 2026 · Jul 9, 2026
diff --git a/docs.json b/docs.json
@@ -107,6 +107,8 @@
                 "pages": [
                   "zh/compliance/terms-of-service",
                   "zh/compliance/user-agreement",
+                  "zh/compliance/microsoft-teams-app-privacy-policy",
+                  "zh/compliance/microsoft-teams-app-terms-of-use",
                   "zh/compliance/service-sla",
                   "zh/compliance/data-security"
                 ]
@@ -1312,6 +1314,8 @@
                 "pages": [
                   "en/compliance/terms-of-service",
                   "en/compliance/user-agreement",
+                  "en/compliance/microsoft-teams-app-privacy-policy",
+                  "en/compliance/microsoft-teams-app-terms-of-use",
                   "en/compliance/service-sla",
                   "en/compliance/data-security"
                 ]

diff --git a/en/compliance/microsoft-teams-app-privacy-policy.mdx b/en/compliance/microsoft-teams-app-privacy-policy.mdx
@@ -0,0 +1,74 @@
+---
+title: "Flashduty Microsoft Teams app privacy policy"
+description: "Learn how the Flashduty Microsoft Teams app processes Teams-related data, why it is used, how it is stored, and how it is protected"
+---
+
+Last updated: 2026-07-09
+
+This policy explains how the Flashduty Microsoft Teams app (the "Teams app") processes data in Microsoft Teams scenarios. The Teams app sends Flashduty alert and incident notifications to Teams and lets you link a Teams user, team, or group chat, and take actions such as acknowledge, resolve, or snooze from incident cards.
+
+This policy applies to the Teams app. General data protection terms for Flashduty services are described in the [Data Protection Protocol](/en/compliance/data-security) and [User Agreement](/en/compliance/user-agreement).
+
+## Data processed
+
+To provide the Teams integration, the Teams app processes the following data only as needed:
+
+| Data type | Examples | Purpose |
+| --- | --- | --- |
+| Teams user information | Teams user ID, Microsoft Entra ID (AAD Object ID), user identifier in a conversation | Link a Teams user to a Flashduty user; verify the user taking an incident card action; send personal notifications or action feedback |
+| Teams team, channel, and group chat information | Team ID, team name, channel ID, conversation ID, group chat ID, group chat name entered by the user | Link a Teams team, channel, or group chat to a Flashduty instant messaging integration target; send incident cards to the intended conversation; update or reply to sent cards |
+| Teams conversation references | Bot Framework conversation reference, service URL, tenant information, activity ID | Allow the Teams app to send and update notifications after it is installed in a personal chat, team channel, or group chat |
+| Bot commands and interaction data | `help`, `linkUser`, `linkTeam`, and `linkChat` commands and parameters; Adaptive Card button actions | Understand the requested operation and generate linking cards, help cards, or incident action results |
+| Flashduty incident and alert card data | Incident title, severity, status, action type, card details, links | Display Flashduty notifications in Teams and return the action result after you click a card button |
+
+<Note>
+The Teams app does not read or store ordinary Teams chat content that is unrelated to Flashduty functionality. It processes only messages sent to the bot in personal chats, messages where the bot is mentioned in teams or group chats, installation and conversation reference data required for the app to work, and data needed to send or update Flashduty notifications.
+</Note>
+
+## Purposes of use
+
+The Teams app processes Teams-related data only for these purposes:
+
+- Link Teams users, teams, channels, or group chats to Flashduty instant messaging integration targets.
+- Send Flashduty alert and incident notifications to linked Teams personal chats, team channels, or group chats.
+- Update incident cards in Teams or reply with the result of an incident card action.
+- Verify the Teams user who performs a card action and provide next-step guidance when the user is not linked or the subscription is unavailable.
+- Retrieve the channel list or team details for a specified Team to support Teams integration setup.
+- Keep necessary service logs for security audit, troubleshooting, and service reliability improvements.
+
+## Storage
+
+The Teams app stores Bot Framework conversation references so it can later send or update notifications in installed Teams conversations. A conversation reference may include necessary fields provided by Microsoft Teams / Bot Framework, such as user, team, channel, group chat, tenant, and service URL information.
+
+When you complete linking in the Flashduty console, Flashduty stores the mapping between the Teams user, team, channel, or group chat and the Flashduty integration target. This mapping is used to deliver future incident notifications to the correct Teams target.
+
+The Teams app does not store ordinary chat messages as standalone long-term content. Incident, alert, and card data are business data in your Flashduty service. Their storage, deletion, and retention follow the applicable Flashduty agreements, product features, and your configuration.
+
+## Data sharing
+
+The Teams app uses Microsoft Teams, Microsoft Bot Framework, and related Microsoft services to receive bot messages, send Adaptive Cards, query Teams channel or team information, and update sent cards. Microsoft's processing of data in those services is governed by Microsoft's applicable terms and privacy statements.
+
+Flashduty does not sell or disclose Teams-related data to unrelated third parties except as needed to provide the Teams integration, comply with legal obligations, follow your authorization, or as otherwise provided in applicable agreements.
+
+## Data protection measures
+
+Flashduty uses reasonable technical and organizational measures to protect Teams-related data, including:
+
+- Transmitting data over secure protocols such as HTTPS.
+- Authenticating business API requests from the Flashduty backend to the Teams app.
+- Restricting access so only authorized personnel and services can access necessary data.
+- Managing service logs and operational data for troubleshooting, security audit, and reliability improvements.
+- Protecting customer data under the security measures described in the [Data Protection Protocol](/en/compliance/data-security).
+
+## Your controls
+
+You can control Teams app data and functionality in these ways:
+
+- Uninstall or remove the Flashduty app in Microsoft Teams.
+- Manage the Microsoft Teams instant messaging integration in the Flashduty console.
+- Contact Flashduty support to request access, correction, deletion, or export of data associated with your account.
+- If you are a Teams administrator, control app visibility, installation policies, and organization-level usage permissions in the Microsoft Teams admin center.
+
+## Contact us
+
+If you have questions about Teams app data processing, privacy protection, or data rights requests, contact Flashduty support at [support@flashcat.cloud](mailto:support@flashcat.cloud).
diff --git a/en/compliance/microsoft-teams-app-terms-of-use.mdx b/en/compliance/microsoft-teams-app-terms-of-use.mdx
@@ -0,0 +1,79 @@
+---
+title: "Flashduty Microsoft Teams app terms of use"
+description: "Learn the scope, account and subscription requirements, usage restrictions, and responsibility boundaries for the Flashduty Microsoft Teams app"
+---
+
+Last updated: 2026-07-09
+
+These terms apply to the Flashduty Microsoft Teams app (the "Teams app"). The Teams app is a Microsoft Teams integration for Flashduty services. It lets you receive Flashduty alert and incident notifications in Teams, link Teams users or conversations, and take incident response actions from notification cards.
+
+These terms supplement the [Terms of Service](/en/compliance/terms-of-service) and [User Agreement](/en/compliance/user-agreement). If these terms conflict with a separate written agreement between you and Flashduty, the separate written agreement controls.
+
+## Scope
+
+The Teams app supports these scenarios:
+
+- Receive Flashduty alert and incident notifications in Teams personal chats, team channels, or group chats.
+- Use bot commands such as `help`, `linkUser`, `linkTeam`, and `linkChat` to view help and complete linking flows.
+- Acknowledge, resolve, snooze, or perform custom actions configured in Flashduty from Teams Adaptive Cards.
+- Send, update, or reply to incident notification cards from the Flashduty backend through the Teams app.
+- Retrieve necessary Teams team and channel information to support integration setup.
+
+## Requirements
+
+Before using the Teams app, you need:
+
+- A valid Flashduty account.
+- The required Flashduty plan, subscription, or entitlement for the features you use.
+- The necessary alert source, incident notification, and Microsoft Teams instant messaging integration configuration in Flashduty.
+- Permission from your Microsoft Teams organization administrator to install and use the Teams app.
+- Compliance with the applicable rules of Microsoft Teams, Microsoft 365, Microsoft Bot Framework, and your organization.
+
+<Note>
+If the Flashduty account is not linked, the subscription is unavailable, or Teams admin policies restrict app usage, some or all Teams app features may not work.
+</Note>
+
+## Your responsibilities
+
+You are responsible for:
+
+- Ensuring that you have permission to install and use the Teams app in the target Teams organization, team, channel, or group chat.
+- Ensuring that receiving Flashduty alert and incident notifications in Teams does not violate your organization's security, compliance, or data processing requirements.
+- Properly managing your Flashduty account, Teams account, administrator permissions, integration IDs, and linking configuration.
+- Confirming that incident actions taken from Teams cards are within your role, authorization, and internal process.
+- Avoiding unrelated sensitive personal information, secrets, passwords, or confidential content in bot commands, card fields, or integration configuration.
+- Removing Teams app installations or Flashduty integration configurations that are no longer needed.
+
+## Usage restrictions
+
+You must not use the Teams app to:
+
+- Send illegal, infringing, fraudulent, malicious, harassing, spam, or otherwise improper content.
+- Bypass access controls or security restrictions in Flashduty, Microsoft Teams, or your organization.
+- Read, forward, disclose, or process another person's Teams information, Flashduty incident data, or business data without authorization.
+- Interfere with the normal operation of the Teams app, Flashduty services, Microsoft services, or third-party systems.
+- Reverse engineer the Teams app, perform scanning attacks, abuse APIs, generate abusive automated traffic, or engage in other destructive behavior.
+
+If Flashduty reasonably determines that your usage creates security, compliance, abuse, or non-payment risk, Flashduty may restrict, suspend, or terminate Teams app-related services under the applicable agreements.
+
+## Third-party services
+
+The Teams app depends on Microsoft Teams, Microsoft Bot Framework, Microsoft 365, and related Microsoft services. When you use those Microsoft services, you must also comply with Microsoft's applicable terms, privacy statements, organization policies, and administrator configuration.
+
+Flashduty does not control Microsoft service availability, policy changes, client behavior, or review results. Installation failures, message delays, card rendering differences, or feature limitations caused by Microsoft services, organization policies, network conditions, or administrator configuration are not a breach of these terms by Flashduty.
+
+## Data and privacy
+
+For the scope, purposes, storage, and protection measures for Teams-related data processed by the Teams app, see the [Flashduty Microsoft Teams app privacy policy](/en/compliance/microsoft-teams-app-privacy-policy).
+
+Incident, alert, and card content are business data in your Flashduty service. You must ensure that this data is lawful, accurate, authorized, and managed according to your organization's visibility requirements.
+
+## Service changes and termination
+
+Flashduty may update, adjust, suspend, or terminate the Teams app due to product improvements, security requirements, Microsoft platform changes, laws and regulations, or business strategy changes. Flashduty will use reasonable efforts to notify you of material changes through documentation, in-product notices, email, or other means.
+
+You may uninstall the Teams app in Microsoft Teams or delete the related integration configuration in the Flashduty console at any time. After uninstalling or deleting the configuration, the related Teams target may no longer receive Flashduty notifications.
+
+## Support
+
+If you need help with installation, configuration, notification delivery, card interactions, or account linking, contact Flashduty support at [support@flashcat.cloud](mailto:support@flashcat.cloud).
diff --git a/en/on-call/integration/instant-messaging/microsoft-teams.mdx b/en/on-call/integration/instant-messaging/microsoft-teams.mdx
@@ -9,7 +9,28 @@ description: "By integrating the Microsoft Teams third-party app, you can receiv
 Microsoft Teams integration is currently in Beta stage. The following steps must be completed by a Microsoft Teams administrator.
 </Warning>
 
-## 1. Install and Update App
+<Note>
+To learn how the Teams app handles Teams users, teams, channels, group chats, and incident card data, see the [Flashduty Microsoft Teams app privacy policy](/en/compliance/microsoft-teams-app-privacy-policy) and [Flashduty Microsoft Teams app terms of use](/en/compliance/microsoft-teams-app-terms-of-use).
+</Note>
+
+## 1. Data and permissions
+
+The Flashduty Teams app processes Teams data only as needed to send alert notifications, complete linking configuration, and handle incident card actions.
+
+| Data or capability | How it is used |
+| --- | --- |
+| Teams user ID and Microsoft Entra ID (AAD Object ID) | Link a Teams user to a Flashduty user; verify the user taking an incident card action; send personal notifications or action feedback |
+| Team ID, team name, and channel ID | Link a Teams team or channel; send alert and incident notifications to the selected Teams channel; retrieve the team details and channel list for a specified Team |
+| Group chat ID and chat name entered by the user | Link a Teams group chat; send alert and incident notifications to the selected group chat |
+| Conversation ID, activity ID, and Bot Framework conversation reference | Send, update, or reply to Teams notification cards after the app is installed |
+| Bot commands and card actions | Handle `help`, `linkUser`, `linkTeam`, and `linkChat` commands, as well as acknowledge, resolve, snooze, and custom action buttons |
+| Flashduty alert and incident card data | Show alert or incident details in Teams and sync card action results back to Flashduty |
+
+The Flashduty Teams app does not read ordinary Teams chat content that is unrelated to Flashduty functionality. It processes only messages sent to the bot in personal chats, messages where the bot is mentioned in teams or group chats, card button actions, installation and conversation reference data required for the app to work, and data needed to send or update Flashduty notifications.
+
+The current app package does not request Microsoft Graph permissions for reading organization-wide chat content. If a future version introduces new Teams permissions or data processing scenarios, Flashduty will update this documentation and the related privacy notice.
+
+## 2. Install and update app
 
 <Steps>
 <Step title="Download App">
@@ -39,7 +60,7 @@ Wait a few minutes, organization members can find this app in +Apps → **Built
 </Step>
 </Steps>
 
-### Update App
+### Update app
 
 <Warning>
 If your installed app version is lower than 1.0.3, please follow the process below to update.
@@ -65,7 +86,7 @@ Wait for the app version to update in the client (may take tens of minutes).
 </Step>
 </Steps>
 
-## 2. Link Team
+## 3. Link team
 
 <Steps>
 <Step title="Find App">
@@ -95,7 +116,7 @@ In the Team, @Flashduty and send command `linkTeam {ID}`, then click **Link Now*
 </Step>
 </Steps>
 
-## 3. Link Chat
+## 4. Link chat
 
 <Steps>
 <Step title="Find App">
@@ -121,9 +142,9 @@ In the Chat, @Flashduty and send command `linkChat {ID} {ChatName}`, then click
 </Step>
 </Steps>
 
-## 4. Notification Card Actions
+## 5. Notification card actions
 
-When incident notifications are pushed to Microsoft Teams, the notification cards support the following interactive actions, allowing you to respond to incidents directly in Teams without switching to the Flashduty console:
+When incident notifications are pushed to Microsoft Teams, the notification cards may include the following interactive actions. The available buttons depend on the Flashduty card you receive and the backend configuration:
 
 - **Acknowledge**: Mark that you have started handling the incident
 - **Resolve**: Mark the incident as resolved and close it
@@ -134,7 +155,7 @@ When incident notifications are pushed to Microsoft Teams, the notification card
 War room functionality is not currently supported for Microsoft Teams. If you need to use the war room feature, consider using Slack, Feishu/Lark, Dingtalk, or WeCom integration instead.
 </Note>
 
-## 5. Link User
+## 6. Link user
 
 <Steps>
 <Step title="Find App">
@@ -160,7 +181,7 @@ Copy and send command `linkUser {}` to the chat, then click **Link Now**.
 </Step>
 </Steps>
 
-## 6. FAQ
+## 7. FAQ
 
 <AccordionGroup>
 <Accordion title="Team or individual not receiving messages?">