Fellow

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: May 21, 2021

General information

Information provided by Fellow Insights Inc to Microsoft:

Information Response
App name Fellow
ID WA200002576
Office 365 clients supported Microsoft Teams
Partner company name Fellow Insights Inc
URL of partner website https://fellow.app
URL of Privacy Policy https://fellow.app/privacy-policy/
URL of Terms of Use https://fellow.app/terms-of-use/

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 Fellow Insights Inc 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 both Fellow connects with user's calendars to provide them the ability to take notes on the data. Fellow stores all event data for the user's primary calendar. Attachments are not stored. This is used within Fellow to provide a calendar-based note taking experience. f6671df0-1909-428c-91f7-1c42df04d3e4
Channel.ReadBasic.All delegated We collect the names of channels that a user is a member of in order to show them a list of channels that they can send notes to. We cache the names and IDs of channels that a user is a member of, in order to allow users to send notes from Fellow to the specified channel. f6671df0-1909-428c-91f7-1c42df04d3e4
Directory.Read.All application This data is only collected if an admin install is done for the whole organization. We use the directory data to sync a list of users and automatically provision accounts. If and only if an org-wide install is performed by the admin from within workspace settings inside Fellow, admins have the option to enable automatic sync of all users from Azure AD into Fellow (automatic provisioning). In this case, we store user information such as ID, Name, Email, and Manager, and Group memberships (for team-management capabilities). f6671df0-1909-428c-91f7-1c42df04d3e4
Group.Read.All application This data is only collected if an admin install is done for the whole organization. We use the directory data to sync a list of users and automatically provision accounts. If and only if an org-wide install is performed by the admin from within workspace settings inside Fellow, admins have the option to enable automatic sync of all users from Azure AD into Fellow (automatic provisioning). In this case, we store user information such as ID, Name, Email, and Manager, and Group memberships (for team-management capabilities). f6671df0-1909-428c-91f7-1c42df04d3e4
People.Read delegated User's contacts are collected, in specific contact displayNames and email addresses. This is used within Fellow to provide a list of users to invite to invite to a note / share a note with. User's contacts are collected, in specific contact displayNames and email addresses. This is used within Fellow to provide a list of users to invite to invite to a note / share a note with. f6671df0-1909-428c-91f7-1c42df04d3e4
People.Read.All application This data is only collected if an admin install is done for the whole organization. User's contacts are collected, in specific contact displayNames and email addresses. This is used within Fellow to provide a list of users to invite to invite to a note / share a note with. If and only if an org-wide install is performed by the admin from within workspace settings inside Fellow, admins have the option to enable automatic sync of all users from Azure AD into Fellow (automatic provisioning). In this case user's contacts are collected, in specific contact displayNames and email addresses. This is used within Fellow to provide a list of users to invite to invite to a note / share a note with. f6671df0-1909-428c-91f7-1c42df04d3e4
Team.ReadBasic.All delegated A list of teams the user is a part of is collected. This is used within fellow for the purposes of allowing the user to sent notes from Fellow to a team. We cache the names and IDs of teams that a user is a member of, in order to allow users to send notes from Fellow to the specified teams channel. f6671df0-1909-428c-91f7-1c42df04d3e4
User.Read delegated Basic user information is collected. User name, email, job title. This information is used within Fellow to create user accounts and company accounts. Basic user information is stored. User name, email, job title. This information is used within Fellow to maintain user accounts and company accounts. f6671df0-1909-428c-91f7-1c42df04d3e4
User.Read.All application This data is only collected if an admin install is done for the whole organization. We use the directory data to sync a list of users and automatically provision accounts. If and only if an org-wide install is performed by the admin from within workspace settings inside Fellow, admins have the option to enable automatic sync of all users from Azure AD into Fellow (automatic provisioning). In this case, we store user information such as ID, Name, Email, and Manager, and Group memberships (for team-management capabilities). f6671df0-1909-428c-91f7-1c42df04d3e4
offline_access delegated The user's refresh token to maintain access to data gathered through other scopes. The user's refresh token is stored in the database. This is used within Fellow to sync events in the background for the calendar-based note taking experience as well as notifications for note taking on scheduled events. f6671df0-1909-428c-91f7-1c42df04d3e4

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?

No EUII is accessed.

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?

Fellow stores information provided directly by the user, including personal data. Fellow also stores some information from third party systems, such as OAuth data, Calendar data, and PII such as name & email. We retain all data indefinitely, for as long necessary and legally permissible for the purpose for which it was collected. We securely delete this information at an earlier date upon receipt of a request by users. Log data is retained for 30 days.

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.

All data transfers occur over secured APIs to our backend systems. Fellow employs many controls to ensure the Security and Confidentiality of its systems, according to the SOC 2 framework as defined by AICPA. Fellow's controls undergo an annual audit to ensure continued compliance. A SOC 2 report can be shared upon request and NDA.

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!

Information from the Microsoft Cloud App Security catalog appears below.

View in a new tab

Feedback

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

Identity information

This information has been provided by Fellow Insights Inc 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? ,

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