1. Introduction
Jint is an extension of Office365. Most of the data is stored on the client's Office365 tenant through the various Microsoft services.
However, the product has many features, some of which require the storage of certain elements in our databases. This document presents the details of this information.
2. Data stored by functionality
2.1. Unified Experience
The unified experience is the sidebar offered on all Jint sites. Customer settings for the unified experience are stored in our database. They are defined by the customer in the Jint configurator:
- The alert
- News and event search parameters
- Navigation links
- Application links
- Footer links
- The graphic theme
Unified experience features also require the collection of actions and preferences for each
user:
- Reading notifications
- Favorite applications
- Subscriptions to the news feeds of the My Subscriptions component
2.2. Site Engine
The Site Engine is the functionality for the client to save SharePoint sites as templates and then create new SharePoint sites from the templates.
The various templates registered by the customer are stored in our database. This means that no confidential data should be saved with a template, as it would then end up in our database.
2.3. Multilingualism
❗The Multilingualism feature is currently undergoing decommissioning from Jint since the beginning of 2023. We encourage you to use SharePoint Multilingual instead.
Jint adds a multilingualism feature to Modern SharePoint sites. Multilingual settings are stored in our database, capturing the correspondence between multiple sites in a language group and the relationships between pages.
2.4. Yammer Integration
It is possible to specify in the Jint configurator to replace SharePoint comments with Yammer comments on certain sites. The list of sites with Yammer comments is stored in our database.
2.5. NewsHub
The NewsHub allows displaying one or more information feeds created from external sources: Twitter, Facebook, YouTube, RSS, SharePoint...
We store the list of your favorite feeds to display them in your Digital Workplace.
3. Access to the Configurator
Access to the Jint Back Office requires authorization, which is stored by Jint.
4. Personal Data
We collect information about each user to record their preferences and measure the use of our services to improve our offering.
At Jint, the security and protection of our users' data are our top priority. To ensure the confidentiality of personal information while maintaining the efficiency of our services, we use an advanced method of user identifier anonymization through a hashing function.
4.1 Functioning of Anonymization via Hashing Function
User Identifiers and Use of Microsoft365
Users log in to Jint using their Microsoft365 accounts. The unique identifier for this account is an email address, which is sensitive information.
Anonymization Process of Identifiers
When a user logs in or registers on Jint using their Microsoft365 account, their identifier is processed by an advanced hashing function. This function converts the email address into a unique hash fingerprint, represented by a series of alphanumeric characters.
Data Security and Privacy Protection
The resulting hash fingerprint is stored in our database. It is important to note that this process is unidirectional, meaning it is impossible to retrieve the original email address from the stored hash fingerprint. Thus, no personally identifiable information is recorded in our systems, preserving user privacy.
4.2 Preferences
- Reading notifications
- Favorite applications
- Subscriptions to news feeds in the "My Subscriptions" component
- Teams channels
4.3 Usage Statistics
Jint collects usage statistics for its services. These data are crucial to understand customer usage and improve our offering.
Analyzed actions include:
- Pages and sites visited with jint.coponents, including user numbers and adoption of intranets created with Jint
- Use of Jint features to identify the most important ones and analyze the impact of our changes
- Performance of pages with jint.coponents
Comments
0 comments
Please sign in to leave a comment.