Timeneye

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

General information

Information provided by DM Digital SRL to Microsoft:

Information Response
App name Timeneye
ID WA200001950
Office 365 clients supported Microsoft Teams
Partner company name DM Digital SRL
URL of partner website https://www.dmdigital.it
URL of Privacy Policy https://www.timeneye.com/privacy-policy
URL of Terms of Use https://www.timeneye.com/terms-and-conditions

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 DM Digital SRL 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.Read delegated Event Start/End DateTime, Event Subject, Event ID, Event Web URI. Generate suggestions based on calendar events. Event Start/End DateTime, Event Subject, Event ID, Event Web URI. Being able to link a generated suggestion to the relevant calendar event. 56412014-bafe-474e-95b4-ebfea106a167
Calendars.Read.Shared delegated Event Start/End DateTime, Event Subject, Event ID, Event Web URI. We use this information to generate suggestions based on calendar events. Event Start/End DateTime, Event Subject, Event ID, Event Web URI. We use this information to link a generated suggestion to the relevant calendar event. 56412014-bafe-474e-95b4-ebfea106a167
Directory.Read.All delegated User's groups' ids. We use this information to check the groups the user is member of so that we may sync his groups' planners. User's groups' ids. We use this information to check the groups the user is member of so that we may sync his groups' planners. 56412014-bafe-474e-95b4-ebfea106a167
Group.Read.All delegated Group Name, Group ID. We use those information while syncing the planner projects. Group Name, Group ID. 56412014-bafe-474e-95b4-ebfea106a167
Tasks.Read delegated task list name, task list ID. We use this information while syncing the planner projects. task list name, task list ID. We use this information while syncing the planner projects. 56412014-bafe-474e-95b4-ebfea106a167
User.Read delegated email, name. We use this information to log in the user/create the user account email, name. We use this information to log in the user/create the user account 56412014-bafe-474e-95b4-ebfea106a167
User.ReadBasic.All delegated user name, email. We use this information so the user can import other users from Planner/Microsoft to our service. user name, email. Basic informations required to create a new user in our service. 56412014-bafe-474e-95b4-ebfea106a167
email delegated email. We use this information to log in the user/create the user account email. We use this information to log in the user/create the user account 56412014-bafe-474e-95b4-ebfea106a167
offline_access delegated Permission required to sync the planner/calendar while the user is not online. Permission required to sync the planner/calendar while the user is not online. 56412014-bafe-474e-95b4-ebfea106a167
openid delegated id_token. Logging in the user through Microsoft SSO id_token. Logging in the user through Microsoft SSO. 56412014-bafe-474e-95b4-ebfea106a167
profile delegated email, name. We use this information to log in the user/create the user account email, name.We use this information to log in the user/create the user account 56412014-bafe-474e-95b4-ebfea106a167

Data access using other Microsoft APIs

Apps and add-ins built on Microsoft 365 may use additional Microsoft APIs other than Microsoft Graph to collect or process organizational identifiable information (OII). List any Microsoft APIs other than Microsoft Graph this app uses.

API Is OII collected? What OII is Collected? Justification for collecting OII? Is OII stored? Justification for storing OII?
Outlook calendar API No

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?

User name and email, Company Billing details. When the account/user is deleted the information is removed.

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 pass sensible information to our partner systems except for user's email for support, ticketing and billing purposes. The information is deleted upon the account deletion on our system.

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 DM Digital SRL 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? 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? 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? No
Does your app use deprecated APIs? Yes

Feedback

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