Klaxoon

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: August 31, 2021

General information

Information provided by Klaxoon to Microsoft:

Information Response
App name Klaxoon
ID WA104382058
Office 365 clients supported Microsoft Teams
Partner company name Klaxoon
URL of partner website https://klaxoon.com
URL of Teams application info page https://klaxoon.com
URL of Privacy Policy https://klaxoon.com/legal
URL of Terms of Use https://static.klaxoon.com/website/pdf/eula.pdf

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

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?
zendesk domain name customer relationship management, help center

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?
We use the roster to personalize user response. eg: Hello {{givenName}}, thank you for your question! firstname, lastname, avatar, email and password (depending if delegated SSO or not). user account management

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?

access and error logs for debug purpose including : ip address,email Offline logs are encrypted and archived for one year. Online logs are kept one month

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.

Data is kept for the duration of the account activation. Data deletion and/or retrieval in flat format (pdf, xlsx, csv, images) or in Klaxoon format (.klx) is available at any time through the application itself. It is manual and under the responsibility of its owner, sole holder of the credentials to access it. Once the account is deactivated, user access is closed.

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?

No

Feedback

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

Identity information

This information has been provided by Klaxoon 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? No
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!