1. Introduction

Jint for Teams is a Jint application that allows you to create custom dashboards directly within Microsoft Teams. Its goal is to centralize essential information, business tools, and communication to improve productivity and the digital experience of employees within their everyday workspace, Microsoft Teams.

Like other Jint products, Jint for Teams integrates with Microsoft 365. The majority of source data resides in the customer’s Microsoft 365 tenant. This document clarifies what Jint for Teams stores and what it does not.

2. What Jint for Teams Does NOT Store (Data Resides in Microsoft 365)

The protection and confidentiality of your data are paramount. Jint for Teams is designed to display information from your Microsoft 365 environment without duplicating the storage of sensitive content.

Jint for Teams does not store the following personal data, which remains in your Microsoft 365 tenant:

• Email content (displayed via the My Emails widget)
• Meeting details (displayed via the My Meetings widget)
• Task content (displayed via the My Tasks widget)
• Detailed profile information (displayed via My Profile, Employee Directory, Organization Chart)
• File content (displayed via the My Files widget)

This information is simply aggregated and displayed in the Teams interface through Jint for Teams for convenience. Jint for Teams never stores sensitive information.

3. What Jint for Teams Stores (Configuration and Preferences)

To enable the creation and customization of dashboards, Jint for Teams stores the following information:

• Dashboard Structure and Configuration:
  • Dashboard names
  • Which widgets are included in a dashboard and their layout
  • Specific widget settings: data sources (e.g., SharePoint sites for News, external feeds for News Hub), targeting options, specific content (for Focus), display settings (for Newcomers, Anniversaries), displayed apps (for My Apps), iFrame configuration, etc.
  • Audience targeting settings for dashboards
  • Company-defined key links (Application widget, Navigation widget)
• User Preferences and Customization:
  • Quick links added by the user
  • Personalized list of favorite applications (My Apps favorites)

This configuration and preference data is tied to the user or target audience to ensure the correct dashboard with the appropriate options is displayed for the right person. Jint for Teams relies on IDs wherever possible to avoid storing confidential names.

• Data Not Stored in Your Tenant – Jint for Teams Articles (if used):
  These articles are not stored in your tenant but in a Jint database. Currently, this data is not encrypted. These are not SharePoint articles but a different category of articles.

4. Access to Dashboards and Configuration

Access to create, edit, and view Jint for Teams dashboards in Teams is managed through specific roles (e.g., Contributor, Jint for Teams Administrator, Dashboard Manager). To identify users or groups with these extended permissions (beyond simple viewing), Jint for Teams stores their Microsoft identifiers (user ID or Azure AD group ID). Role assignment is managed through the Jint for Teams rights management screen, accessible to Jint for Teams administrators.

5. Anonymization of Usage Data (For Usage Monitoring)

If data is collected to monitor overall Jint for Teams usage (to improve the service), Jint applies an advanced anonymization method:

• User Identifiers: The user’s unique Microsoft 365 ID is processed using a one-way hashing function.
• Anonymized Storage: Only the hash value is stored to link usage actions to an anonymous user. It is not possible to retrieve the original identifier from the hash.
• Purpose: These anonymized data points are used solely to understand overall usage, identify popular features, and improve the service—without ever storing the user’s raw personal identifier in usage logs.