Pexip One for Outlook

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: July 27, 2021

General information

Information provided by PexipAS to Microsoft:

Information Response
App name Pexip One for Outlook
ID WA200003137
Office 365 clients supported Outlook 2013 or later on Windows, Outlook 2016 or later on Mac, Outlook on the web
Partner company name PexipAS
URL of partner website https://www.pexip.com
URL of Privacy Policy https://www.pexip.com/privacy
URL of Terms of Use https://www.pexip.com/terms

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 PexipAS 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
Calendars.Read delegated Event data for users is used to schedule meetings on the platform and track changes to meeting metadata We store meeting titles, start and end times (all encrypted). These are used to give metadata to meetings on Pexip One 69609b5a-e416-4d72-b10b-8903e84780c3

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?
https://help.pexip.com/service/subprocessors.htm https://help.pexip.com/service/subprocessors.htm https://help.pexip.com/service/subprocessors.htm

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?

Exchange user IDs are stored to index and correlate user data. These are held until the user signs out of the app. Personal data relating to a user's Pexip One account is held for up to 6 months following the duration of the service contract. Meeting metadata is held for 3 months. Audio/video stream data is not held, and neither are meeting chat messages

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 only process/store such organisational data as is needed to conduct video sessions and provide infrastructure.

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 PexipAS 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? 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!