Wide Ideas

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

General information

Information provided by Wide Ideas to Microsoft:

Information Response
App name Wide Ideas
ID WA200000819
Office 365 clients supported Microsoft Teams
Partner company name Wide Ideas
URL of partner website https://getwideideas.com
URL of Privacy Policy https://getwideideas.com/privacy-policy/
URL of Terms of Use https://pinpointprod.blob.core.windows.net/marketing/Partne...


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

How the app handles data

This information has been provided by Wide Ideas 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
Channel.Create delegated To create a channel in a Team. We store the channel ID for the created challenge. b0656c15-44aa-4aab-8956-bb97e3016535
Directory.Read.All delegated We use this to list users from customer directory N/A b0656c15-44aa-4aab-8956-bb97e3016535
Group.Read.All delegated We use this to read and sync teams from Microsoft Teams. We store Group ID of the team and members of the team. b0656c15-44aa-4aab-8956-bb97e3016535
TeamsAppInstallation.ReadWriteForTeam delegated This is used to install the app in Teams automatically We store information regarding in which team the app is installed b0656c15-44aa-4aab-8956-bb97e3016535
TeamsTab.Create delegated We use this to automatically create application (challenge/search ideas) tabs in channels created by Wide Ideas. N/A b0656c15-44aa-4aab-8956-bb97e3016535
User.Read delegated Used to authenticate users via SSO as well as sync user data We store name, email and user-id. b0656c15-44aa-4aab-8956-bb97e3016535

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?
Mailjet Email which is used for email notifications. email address To be able to send email notifications over activities

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?
In order to create users in our backend and give permissions to access content linked to the team. We store: Name - To shown the name of the user, Email address - To identify the user In order to manage permission to content in our backend

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?

We store name, email and IP number in our logs. The organisation can send an request to us as a supplier if they want any data to be deleted.

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.

Data storage: All customer data is stored in Microsoft Azure services. Users needs to be 2 factor authenticized via Azure AD. Role based access (RBAC) are in place. All access to Microsoft Azure is strictly made through encrypted connections. All data are encrypted at rest. All services are protected by Azure Security Center best practise.

We also have an Access Policy in place according to The principle of least privilege.

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?



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

Information from the Microsoft Cloud App Security catalog appears below.

View in a new tab


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

Identity information

This information has been provided by Wide Ideas 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? Yes
List the types of policies supported MFA
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


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