isLucid

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 9, 2021

General information

Information provided by UAB Lucid Agreements to Microsoft:

Information Response
App name isLucid
ID WA200002385
Office 365 clients supported Microsoft Teams
Partner company name UAB Lucid Agreements
URL of partner website https://islucid.com
URL of Teams application info page https://islucid.com
URL of Privacy Policy https://islucid.com/privacy-policy/
URL of Terms of Use https://islucid.com/eula/

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 UAB Lucid Agreements 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
Calls.AccessMedia.All both With a user specific consent for each call separately (initiated transcription) it access audio stream. Audio stream is forwarded to a transcription service so users would get further functionality. App stores in a separated containers on Azure (blob storage and Cosmos DB for each client separately) transcription and related meta information. This is required to provide further access of a meeting information for the user, who used the application and was in the specific meeting. 98b70422-b0b2-41bf-8673-60d85f5d38c7
Calls.JoinGroupCall.All both With a user specific consent for each call separately (initiated transcription) it access audio stream. Audio stream is forwarded to a transcription service so users would get further functionality. App stores in a separated containers on Azure (blob storage and Cosmos DB for each client separately) transcription and related meta information. This is required to provide further access of a meeting information for the user, who used the application and was in the specific meeting. 98b70422-b0b2-41bf-8673-60d85f5d38c7
Group.ReadWrite.All both When user uses integration with Microsoft Planner to create tasks from call and automatically store in MS Planner, isLucid collects for that user available groups, plans, assignees. Without this permission user wouldn't be able to create task from the transcription using isLucid Task title, task creator, task timestamp, task description is stored so users could get access to the history of tasks, made from a specific meeting. 98b70422-b0b2-41bf-8673-60d85f5d38c7
OnlineMeetings.Read.All both Application collects meeting titles so users later (when meeting is finished) could find previous transcripts and tasks easier. Meeting title, timestamp of the meeting, meeting organizer 98b70422-b0b2-41bf-8673-60d85f5d38c7
Tasks.ReadWrite both When user uses integration with Microsoft Planner to create tasks from call and automatically store in MS Planner, isLucid collects for that user available groups, plans, assignees. Without this permission user wouldn't be able to create task from the transcription using isLucid Task title, task creator, task timestamp, task description is stored so users could get access to the history of tasks, made from a specific meeting. 98b70422-b0b2-41bf-8673-60d85f5d38c7
User.ReadWrite.All both When user uses integration with Microsoft Planner to create tasks from call and automatically store in MS Planner, isLucid collects for that user available groups, plans, assignees. Without this permission user wouldn't be able to create task from the transcription using isLucid Task title, task creator, task timestamp, task description is stored so users could get access to the history of tasks, made from a specific meeting. 98b70422-b0b2-41bf-8673-60d85f5d38c7
openid both User ID, tenant ID collected to provide Azure Active Directory login functionality for our users User ID, tenant ID for further rights management 98b70422-b0b2-41bf-8673-60d85f5d38c7

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?
hubspot.com Name, Surname, Email and Phone number of newly registered users We are using Hubspot CRM for maintaining sales related information

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?
Bot is enabling sending of Audio stream to the transcription service. To provide readable transcription we need to associate audio with users (speakers). Without providing such info transcripts are useless Name, surname, status if it's a guest account or a Microsoft one Bot is enabling sending of Audio stream to the transcription service. To provide readable transcription we need to associate audio with users (speakers). Meeting participants information is also relevant to enable users see, who were attending the meeting.

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?

Users while using our service are generating transcripts. In transcripts meeting participants (names, surnames) presented. Potentially anything can be mentioned during the call. We store this data for users as long as they are using our services. Once client ends using us, within 30 days we destroy all associated data.

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 do not control any data on our clients when client purchases isLucid as a hosted solution. For SaaS solution we enable users to cancel using our services and then we delete Cosmos DB isntance, associated with the partner. We are in process of sending information to compliance API too

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 UAB Lucid Agreements 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? 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,
- OAuth2 Implicit Flow, unless required for a SPA
- Resource Owner Password Credential (ROPC) flow
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? Yes
Does your app use deprecated APIs? Yes

Feedback

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