Calendar Pro

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: September 2, 2021

General information

Information provided by Witivio to Microsoft:

Information Response
App name Calendar Pro
ID WA200002152
Office 365 clients supported Microsoft Teams
Partner company name Witivio
URL of partner website https://www.witivio.com
URL of Privacy Policy https://www.teams-pro.com/en/privacy-policy/
URL of Terms of Use https://www.teams-pro.com/en/terms-of-use/

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 Witivio 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
User.Read delegated The data is used The data is used to display the information in the UI fb507a6d-2eaa-4f1f-b43a-140f388c4445
User.ReadBasic.All delegated The data is used The data is used to list people for enabling people picker fb507a6d-2eaa-4f1f-b43a-140f388c4445
email delegated The email is used The email is used to identify the user in the UI fb507a6d-2eaa-4f1f-b43a-140f388c4445
offline_access delegated The data is used Offline access is used to enable SSO with Microsoft Teams fb507a6d-2eaa-4f1f-b43a-140f388c4445
openid delegated Authentication OpenID is used for authentication with Microsoft Teams fb507a6d-2eaa-4f1f-b43a-140f388c4445
profile delegated The data is used Profile is used to enable SSO with Microsoft Teams fb507a6d-2eaa-4f1f-b43a-140f388c4445

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?

The telemetry contains the UPN and the AAD ID for diagnostics. Only PROD/Run administrators has access to the production telemetry. The logs are stored for 90 days and can be deleted on request by email at dpo@witivio.com

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.

Witivio only uses Microsoft Azure components, deployed in the north Europe region. We use application insight and Cosmos DB for data analytics and storage. Witivio use MFA for all users, including admins. Admins have a user account (for workstation) and a privileged account for accessing Azure ressources.

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!

Identity information

This information has been provided by Witivio 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? 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? ,
- OAuth2 Implicit Flow, unless required for a SPA
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!