Data and permissions policy & Organisation-level settings

Data and permissions policy 

In order for the Pigeonhole Live app to work within your Webex meeting we use the following permissions and data:

• App Display Context
• App Theme
• Meeting Details:
• Meeting ID
• Conference ID
• User Details (if PII is enabled)
• Webex User’s Display name
• Webex User’s Email
• Webex User ID

We only store the following permissions and data:

• Meeting ID
• Conference ID 
• Webex User’s Display name  (if PII is enabled)
• Webex User’s Email  (if PII is enabled)

Note: When PII is disabled, we only store derived values for User ID, that serve as an anonymous identifier for each attendee. 

Collection of Personally Identifiable Information (PII)

If collection of Personally Identifiable Information (PII) is enabled for embedded apps, meeting attendees will be automatically signed in on Pigeonhole Live with their Webex name and email. If collection of PII is disabled by your Webex admin, all meeting attendees will be anonymous.

Webex Admins can manage PII policies from the Webex Control Hub.

Organisation-level settings and permissions

Webex Account admins will need to enable the Pigeonhole Live app for your organisation accounts following the instructions here. Once enabled, Pigeonhole Live will appear in the app list in your Webex Meetings. 

Account admins are also recommended to whitelist the following domains to ensure that the Pigeonhole Live app for works without any disruptions during your Webex meetings: 

• login.pigeonholelive.com       
• static.pigeonholelive.com      
• dashboard.pigeonholelive.com
• pigeonhole.at                  
• static.pigeonhole.at           
• static-cloudfront.pigeonhole.at
• api.pigeonhole.at                      
• help.pigeonholelive.com
• webex.pigeonholelive.com