Real Time Translator

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: June 25, 2021

General information

Information provided by Fairuse to Microsoft:

Information Response
App name Real Time Translator
ID WA200002171
Office 365 clients supported Microsoft Teams
Partner company name Fairuse
URL of partner website
URL of Teams application info page
URL of Privacy Policy
URL of Terms of Use


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

How the app handles data

This information has been provided by Fairuse 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
email delegated サービス利用者の E-Mail アドレスが収集されます。ユーザーを識別するための情報として使用します。 ユーザーがどのチャットルームに入室してそのチャットルームの中でどのような会話をしたかを保存します。ユーザーが後から会話履歴を参照するために必要になります。 c4e4c98c-f859-4682-89a5-48b66838c496
openid delegated 認証のために使用します。 ユーザーがどのチャットルームに入室してそのチャットルームの中でどのような会話をしたかを保存します。ユーザーが後から会話履歴を参照するために必要になります。 c4e4c98c-f859-4682-89a5-48b66838c496
profile delegated ユーザーの名前やユーザープリンシパル名をユーザー特定するために取得します。 ユーザーがどのチャットルームに入室してそのチャットルームの中でどのような会話をしたかを保存します。ユーザーが後から会話履歴を参照するために必要になります。 c4e4c98c-f859-4682-89a5-48b66838c496

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?
Cognitive Services No

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?

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? を参照してください。

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. を参照してください。

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?



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


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

Identity information

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

Does your app expose any web APIs? No
Does your app use preview APIs? No
Does your app use deprecated APIs? No


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