Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Last updated by the developer on: November 6, 2026
General information
Information provided by SOV17 LLC to Microsoft:
| Information | Response |
|---|---|
| App name | Acknowledged |
| ID | WA200013064 |
| Office 365 clients supported | Microsoft Teams |
| Partner company name | SOV17 LLC |
| Company's website | https://acknowledged.app |
| App's Terms of Use | https://acknowledged.app/terms |
| Core functionality of the app | Read confirmations for Teams channel posts. A member posts a must-read announcement from the message box, and people confirm in one click. Acknowledged reminds those who haven't, in a private chat. Only the sender sees who has acknowledged, and can export that list as a CSV file. Works in standard, private and shared channels, including channel meetings. |
| Company headquarter location | Armenia |
| App info page | https://acknowledged.app/help/ |
| What is the hosting environment or service model used to run your app? | Paas |
| Which hosting cloud providers does the app use? | GCP, Azure |
| Is AI functionality part of the app's features or workflows? | No |
| Online Service interfaces | Bot Framework Connector REST API (smba.trafficmanager.net, smba.infra.gcc.teams.microsoft.com): messages, channel members. Azure Bot Service webhook: https://api.acknowledged.app/api/messages. Teams message extension, task module, Adaptive Cards and the Teams JavaScript library. Entra ID token endpoint (login.microsoftonline.com) through MSAL. Bot Framework signing keys (login.botframework.com). No calls to Microsoft Graph, Exchange Online/EWS or SharePoint Online. |
Questions
Questions or updates to any of the information you see here? Contact us!
How the app handles data
This information has been provided by SOV17 LLC about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.
| Information | Response |
|---|---|
| Does the app or underlying infrastructure process any data relating to a Microsoft customer or their device? | Yes |
| What data is processed by your app? | Organization: tenant ID and plan, team and channel IDs. People: display names, Teams user IDs, Entra object IDs, each member's home tenant ID. Content: announcement title, message and due date, plus acknowledgement, reminder and opt-out times. Paid plans: the purchaser's Entra object ID and Paddle IDs. Email addresses and UPNs in the Teams member list are dropped, never stored. |
| Does the app support TLS 1.2 or higher? | Yes |
| Does the app or underlying infrastructure store any Microsoft customer data? | Yes |
| What data is stored in your databases? | Organizations: tenant ID, plan, Paddle IDs. Installations: team and channel IDs, who installed. Announcements: title, message, due date, author. Recipients: name, Teams user ID, Entra object ID, home tenant ID, state, times. Monthly usage counts. Drafts with the member list (up to 24 hours). Membership checks (up to 1 hour). Product events with no personal fields. Billing webhook receipts. |
| If underlying infastructure processes or stores Microsoft customer data, where is this data geographically stored? | United States of America |
| Do you have an established data rentention and disposal process? | Yes |
| How long is data retained after account termination? | Less than 60days |
| Do you have an established data access management process? | Yes |
| Do you transfer customer data or customer content to third parties or sub-processors? | Yes |
| Do you have data sharing agreements in place with any third party service you share Microsoft customer data with? | Yes |
Questions
Questions or updates to any of the information you see here? Contact us!
This information has been provided by Acknowledged about the security practices this app employs.
| Information | Response |
|---|---|
| Do you perform annual penetration testing on the app? | No |
| Does the app have a documented disaster recovery plan, including a backup and restore strategy? | Yes |
| Does your environment use traditional anti-malware protection or application controls? | ApplicationControls |
| Do you have an established process for indentifying and risk ranking security vulnerabilities? | Yes |
| Do you have a policy that governs your service level agreement (SLA) for applying patches? | Yes |
| Do you carry out patch management activities according to your patching policy SLAs? | No |
| Does your enviroment have any unsupported operating systems or software? | No |
| Do you conduct quarterly vulnerability scanning on your app and the infastructure that supports it? | No |
| Do you have a firewall installed on your external network boundary? | Yes |
| Do you have an established change management process used to review and approve change requests before they are deployed to production? | Yes |
| Is an additional person reviewing and approving all code change requests submitted to production by the original developer? | No |
| Do secure coding practices take into account common vulnerability classes such as OWASP Top 10? | Yes |
| Multifactor Authentication (MFA) enabled for: | CodeRepositories, DNSManagement, Credential |
| Do you have an established process for provisioning, modification, and deletion of employee accounts? | No |
| Do you have Intrusion Detection and Prevention (IDPS) software deployed at the perimeter of the network boundary supporting your app? | No |
| Do you have event logging set up on all system components supporting your app? | Yes |
| Are all logs reviewed on a regular cadence by human or automated tooling to detect potential security events? | Yes |
| When a security event is detected are alerts automatically sent to an employee for triage? | Yes |
| Do you have a formal information security risk management process established? | Yes |
| Do you have a formal security incident response process documented and established? | Yes |
| Do you report app or service data breaches to supervisory authorities and individuals affected by the breach within 72 hours of detection? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
This information has been provided by SOV17 LLC regarding the compliance standards their app requires and the certifications they have achieved.
| Information | Response |
|---|---|
| Does the app comply with the Health Insurance Portability and Accounting Act (HIPAA)? | N/A |
| Does the app comply with Health Information Trust Alliance, Common Security Framework (HITRUST CSF)? | No |
| Has the organization achieved a Service Organization Controls (SOC 1) Certification? | No |
| Has the organization achieved a Service Organization Controls (SOC 2) Certification? | No |
| Has the organization achieved a Service Organization Controls (SOC 3) Certification? | No |
| Do you carry out annual PCI DSS assessments against the app and its supporting environment? | N/A |
| Is the app International Organization for Standardization (ISO 27001) certified? | No |
| Does the app comply with International Organization for Standardization (ISO 27018)? | No |
| Does the app comply with International Organization for Standardization (ISO 27017)? | No |
| Does the app comply with International Organization for Standardization (ISO 27002)? | No |
| Is the app Federal Risk and Authorization Management Program (FedRAMP) compliant? | No |
| Does the app comply with Family Educational Rights and Privacy Act (FERPA)? | N/A |
| Does the app comply with Children's Online Privacy Protection Act (COPPA)? | N/A |
| Does the app comply with Sarbanes-Oxley Act (SOX)? | N/A |
| Does the app comply with NIST 800-171? | No |
| Has the app been Cloud Security Alliance (CSA Star) certified? | No |
Questions
Questions or updates to any of the information you see here? Contact us!
This information has been provided by SOV17 LLC about the privacy posture of their app.
| Information | Response |
|---|---|
| Do you have GDPR or other privacy or data protection requirements or obligations (such as CCPA)? | Yes |
| Does the app have an external-facing privacy notice that describes how it collects, uses, shares, and stores customer data? | Yes |
| Privacy Policy URL | https://acknowledged.app/privacy |
| Does the app perform automated decision making, including profiling that could have a legal effect or similar impact? | No |
| Does the app process customer data for a secondary purpose not described in the privacy notice (i.e. marketing, analytics)? | No |
| Do you process special categories of sensitive data (i.e. racial or ethnic origin, political opinion, religious or philosophical beliefs, genetic or biometric data, health data) or categories of data subject to breach notification laws? | No |
| Does the app collect or process data from minors (i.e., individuals under the age of 16)? | No |
| Does the app have capabilities to delete an individual's personal data upon request? | Yes |
| Does the app have capabilities to restrict or limit the processing of an individual's personal data upon request? | No |
| Does the app provide individuals the ability to correct or update their personal data? | Yes |
| Are regular data security and privacy reviews performed (for example, Data Protection Impact Assessments or privacy risk assessments) to identify risks related to the processing of personal data for the app? | Yes |
Questions
Questions or updates to any of the information you see here? Contact us!
| Information | Response |
|---|---|
| Does your application integrate with Microsoft identity platform (Microsoft Entra ID) for single-sign on, API access, etc.? | Yes |
| Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? | No |
| Does your app use the latest version of MSAL (Microsoft Authentication Library) or Microsoft Identity Web for authentication? | No |
| Does your app support Conditional Access policies? | No |
| If your app does not use one of the above libraries, what authentication library or libraries does it use? | MSAL Node 5.6.0, through the Microsoft Teams SDK 2.1. |
| Does your app support Continuous Access Evaluation (CAE) | N/A |
| Does your app store any credentials in code? | No |
| Apps and add-ins for Microsoft 365 might use additional Microsoft APIs outside of Microsoft Graph. Does your app or add-in use additional Microsoft APIs? | Yes |
Data access using Microsoft Graph
Graph Permission Permission Type Justification Microsoft Entra App ID ChannelMember.Read.Group rsc Lets the bot read, through the Bot Framework roster API, the member list of the shared and private channels where Acknowledged is added. Without it the shared-channel roster is refused, so Status could not list who is pending and no reminders could be sent. Acknowledged makes no Microsoft Graph calls. a94529e7-540c-4b2a-a354-cf78d80b0b33
This application does not have Additional APIs.
Questions
Questions or updates to any of the information you see here? Contact us!