Qualified

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: May 5, 2021

General information

Information provided by Qualified to Microsoft:

Information Response
App name Qualified
ID WA200002720
Office 365 clients supported Microsoft Teams
Partner company name Qualified
URL of partner website https://www.qualified.com
URL of Teams application info page https://www.qualified.com/university-guide/microsoft-teams-...
URL of Privacy Policy https://www.qualified.com/legal/privacy
URL of Terms of Use https://www.qualified.com/legal/terms-of-service

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 Qualified 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.

Permission Type of permission (Delegated/ Application) Is data collected? Justification for collecting it? Is data stored? Justification for storing it? Azure AD App ID
Channel.ReadBasic.All application Allows us to select channel to notify email address, tenant id, oauth refresh token 2c951ed5-c5c6-493f-9b02-4b42e3ba536c
Team.ReadBasic.All application Allows us to find all channels from all teams, to allow us to select channels to notify email address, tenant id, oauth refresh token 2c951ed5-c5c6-493f-9b02-4b42e3ba536c

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 API Yes Tenant ID, Team ID's, Channel ID's Tenant ID: To determine service_url for bot framework api calls; Team ID's + Channel ID's: to determine which teams/channels our bot has been added to Tenant ID, Team ID's, Channel ID's Tenant ID: To determine service_url for bot framework api calls; Team ID's + Channel ID's: to determine which teams/channels our bot has been added to

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.

All non-Microsoft services OII is transferred to What OII is transferred? Justification for transferring OII?
Heroku, Sentry, Papertrail Name, Email address, IP These systems host and monitor our production service

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?

No EUII is accessed.

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?

Email address, IP. Data is retained as long as customer contracts with us

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.

We have the ability to delete and adjust retention with our vendors

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 Qualified 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? Yes
Does your app use MSAL (Microsoft Authentication Library) for authentication? No
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? No
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!