2. Use of the Application

Pulzen is a metric exporter designed to operate under a licensing system. The application is aimed at users who need to export metrics for analysis and monitoring. Our application focuses on improving the productivity of software development teams through different approaches, such as Satisfaction, Performance, Activity, Communication and Efficiency.

3. Data Storage and Management

3.1 Access Token

The application uses an access token to obtain metric information. This token is sensitive and is stored in environment variables configured by the customer in their hosting environment. Pulzen does not manage this token, except for the sole purpose of obtaining metric information.

3.2 Stored Information

The only information stored by the application are metrics and execution logs necessary for the operation of the platform. No other user information is stored.

3.3 Privacy and Security

Pulzen does not retain, store or access sensitive data beyond what is necessary for the operation of the application. All data remains in the end customer database.

3.4 Personal Data Protection

Pulzen meets the highest standards for the protection of sensitive information and is committed to safeguarding the personal data of users. The legal basis for data processing is the user's consent and contractual necessity.

3.5 Data Acquisition

Pulzen does not retain, store or access sensitive data beyond what is necessary for the operation of the application. All data remains in the end customer database.

3.5.1 Real-Time Data

Pulzen Gateway is designed to provide an efficient way to collect and process real-time data from a variety of sources. Real-time data is obtained through webhooks and API queries from integrated systems such as GitHub, BitBucket, GitLab and Azure DevOps. The information is sent in JSON format, analyzed to extract relevant metrics and stored in the database, maintaining an updated repository.

3.5.2 Historical Data

In addition to real-time data, Pulzen Gateway also manages historical data obtained exclusively through API queries to the same integrated platforms. Historical data is requested, assigned to a new object structure and stored in the database for long-term analysis and comparison with current data.

4. User Rights

As a user, you have the right to access your personal data stored by Pulzen. You can contact Pulzen via the email address indicated in section 9 of these Terms and Conditions.

5. User Responsibilities

The user is responsible for the correct configuration and protection of the environment variables containing the access token and any other configuration related to data security.

6. Security

6.1 Webhook Security

Data transmission from version control platforms such as GitHub, BitBucket, GitLab and Azure DevOps to Pulzen Gateway is protected by SSL verification and the use of secret tokens to authenticate webhook requests.

6.2 Security in Power BI

The integration with Power BI uses basic authentication, combining user credentials and Base64 coding to secure API requests.

6.3 Version Control API Security

Interactions with version control platforms' APIs are limited to read-only operations and use API keys to authenticate and authorize access, ensuring that only approved applications can retrieve information.