Sensei Labs Conductor

Publisher Attestation: The information on this page is based on a self-assessment report provided by the app developer on the security, compliance, and data handling practices followed by this app. Microsoft makes no guarantees regarding the accuracy of the information.

Last updated by the developer on: January 5, 2021

General information

Information provided by Sensei Labs Inc. to Microsoft:

Information Response
App name Sensei Labs Conductor
ID WA200001951
Office 365 clients supported Microsoft Teams
Partner company name Sensei Labs Inc.
URL of partner website https://www.senseilabs.com
URL of Privacy Policy https://www.senseilabs.com/conductor/conductor-privacy-poli...
URL of Terms of Use https://www.senseilabs.com/conductor/msft-teams-terms-condi...

Feedback

Questions or updates to any of the information you see here? Contact us!

How the app handles data

This information has been provided by Sensei Labs Inc. about how this app collects and stores organizational data and the control that your organization will have over the data the app collects.

Data access using Microsoft Graph

List any Microsoft Graph permissions this app requires.

This application does not use Microsoft Graph.

Data access using other Microsoft APIs

Apps and add-ins built on Microsoft 365 may use additional Microsoft APIs other than Microsoft Graph to collect or process organizational identifiable information (OII). List any Microsoft APIs other than Microsoft Graph this app uses.

API Is OII collected? What OII is Collected? Justification for collecting OII? Is OII stored? Justification for storing OII?
bot framework Yes Teams instance ID to map Teams instance to instance of our application associated with the organization Teams instance ID to map Teams instance to instance of our application associated with the organization

Non-Microsoft services used

If the app transfers or shares organizational data with non-Microsoft service, list the non-Microsoft service the app uses, what data is transferred, and include a justification for why the app needs to transfer this information.

Non-Microsoft services are not used.

Data access via bots

If this app contains a bot or a messaging extension, it can access end-user identifiable information (EUII): the roster (first name, last name, display name, email address) of any team member in a team or chat it's added to. Does this app make use of this capability?

Justification for accessing EUII? Is EUII stored in database(s)? Justification for storing EUII?
to properly address the person during bot conversations. In order to map the user in Teams to their user in our application Teams identifier, name, email address to map Teams user to user in our platform

Telemetry data

Does any organizational identifiable information (OII) or end-user identifiable information (EUII) appear in this application's telemetry or logs? If yes, describe what data is stored and what are the retention and removal policies?

Teams team membership. Association between customer's Teams instance and their Conductor instance. Data retained as long as they are a Conductor customer. Removal when customer's Conductor instance is decommissioned, or on request

Organizational controls for data stored by partner

Describe how organization's administrators can control their information in partner systems? e.g. deletion, retention, auditing, archiving, end-user policy, etc.

N/A

Human review of organizational information

Are humans involved in reviewing or analyzing any organizational identifiable information (OII) data that is collected or stored by this app?

Yes

Feedback

Questions or updates to any of the information you see here? Contact us!

Information from the Microsoft Cloud App Security catalog appears below.

View in a new tab

Feedback

Questions or updates to any of the information you see here? Contact us!

Identity information

This information has been provided by Sensei Labs Inc. about how this app handles authentication, authorization, application registration best practices, and other Identity criteria.

Information Response
Do you integrate with Microsoft Identify Platform (Azure AD)? Yes
Have you reviewed and complied with all applicable best practices outlined in the Microsoft identity platform integration checklist? No
Does your app use MSAL (Microsoft Authentication Library) for authentication? Yes
Does your app support Conditional Access policies? No
Does your app request least privilege permissions for your scenario? Yes
Does your app's statically registered permissions accurately reflect the permissions your app will request dynamically and incrementally? Yes
Does your app support multi-tenancy? Yes
Does your app have a confidential client? Yes
Do you own all of the redirect Unified Resource Identifier (URI) registered for your app? Yes
For your app, what do you avoid using? - Wildcard redirect URIs,
- OAuth2 Implicit Flow, unless required for a SPA
- Resource Owner Password Credential (ROPC) flow
Does your app expose any web APIs? Yes
Does your permission model only allow calls to succeed if the client app receives the proper consent? Yes
Does your app use preview APIs? No
Does your app use deprecated APIs? No

Feedback

Questions or updates to any of the information you see here? Contact us!