myOKR

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

General information

Information provided by SOE Technologies to Microsoft:

Information Response
App name myOKR
ID WA200003308
Office 365 clients supported Microsoft Teams
Partner company name SOE Technologies
URL of partner website https://www.myokr.co
URL of Teams application info page https://www.myokr.co
URL of Privacy Policy https://www.myokr.co/privacy
URL of Terms of Use https://www.myokr.co/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 SOE Technologies 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.ReadWrite delegated Get user calendar details to create a 1:1 meeting in user calendar, update or delete created by myOKR platform and show free time slots We store created calendar id and joining URL in database for the meetings created in myOKR platform 5f5ab403-96ae-46a9-b78e-a06d60cc9e4e
User.Read delegated We use user azure object id to make user login into myOKR app using Microsoft authentication against the email user email and azure active object id 5f5ab403-96ae-46a9-b78e-a06d60cc9e4e
User.Read.All application Sync user information with myOKR platform and displays myOKR application analytics to admin based on various user cuts such as location, department & manager We store user id, name, email, department, title and manager information in the myOKR system 5f5ab403-96ae-46a9-b78e-a06d60cc9e4e
offline_access delegated Azure active directory id of user We use offline access to create recurring meetings in user calendar 5f5ab403-96ae-46a9-b78e-a06d60cc9e4e
openid delegated We use user azure object id to make user login into myOKR app using Microsoft authentication User active azure id is stored against the email 5f5ab403-96ae-46a9-b78e-a06d60cc9e4e

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?

Justification for accessing EUII? Is EUII stored in database(s)? Justification for storing EUII?
User Active Azure Directory ID is store against the email of the user to send proactive messages by the bot. Email, Name, Manager Information, Title, User Azure Active Directory ID This information is used in the myOKR application to build user account, allow manager to view their reportee details on platfrom, allow admin to view overall analytics and reports based on department, location and manager

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?

No OII or EUII appear in the applications telemetry or logs.

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.

Organization SPOC communicate to us for service closure and their data is deleted post 30 days after the intimation and rolled over from the database back-ups after additional 30 days.

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 SOE Technologies 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? 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!