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

General information

Information provided by Binary Geek Limited to Microsoft:

Information Response
App name Weekly10
ID WA200001441
Office 365 clients supported Microsoft Teams
Partner company name Binary Geek Limited
URL of partner website https://www.weekly10.com
URL of Teams application info page https://www.weekly10.com/integrations/microsoft-teams/
URL of Privacy Policy https://www.weekly10.com/terms/privacy
URL of Terms of Use https://www.weekly10.com/terms/customer


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

How the app handles data

This information has been provided by Binary Geek Limited 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
Directory.Read.All application Synchronisation of users from Azure AD into Weekly10 (optional) User identity data: User Principal Name, Email, First Name, Last Name and Manager. 2cc7f3cd-05e3-4ebb-b9f9-d92f1bcda7fb
Calendars.ReadWrite application Checking of employee availability and automated booking of meetings (optional). Employee availability times (not details) and when a meeting is booked the reference to that meeting. This data is used to understand if an employee is out of office for a seamless employee experience and to book meetings for 1:1s or Performance Reviews. 494610b2-b490-4f54-8384-312d6f9b4869
User.Read delegated Verification of user for SSO purposes on the Azure AD. No additional data is retained apart from token information. 6fd1421e-89e8-4a8b-bd01-9397656a50d5

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?
We only access the Teams User ID of the individual. This means that the bot can respond in a specific way to that user. No

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?

Organisation Name and User Names in the event of a reported bug or issue. Logs are stored in this format for up to 30 days and then 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.

All data residing in Weekly10 can be controlled by specified administrators. When changing policies in Weekly10 this directly impacts the data in Microsoft Azure (where client data resides).

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!

Identity information

This information has been provided by Binary Geek Limited 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,

- 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? No


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