Telemetry Policy
Evergrowth Telemetry Policy
Effective Date: 2026-01-01
This Telemetry Policy applies to all Evergrowth software products and Business Central extensions, including DimLogic, 1099 Per-Line, EGLogger, and any future AppSource offerings.
This Telemetry Policy is provided for informational and transparency purposes only. In the event of any conflict, the Evergrowth Privacy Policy governs the collection and use of data.
Privacy is not just a promise - it’s an implementation detail.
Executive Summary
Evergrowth software products collect a limited set of technical telemetry to help ensure reliability, diagnose errors, and improve product usability. This telemetry consists solely of system and operational metadata (such as timing, error summaries, and feature usage patterns) and does not include personally identifiable information, user identities, or business transaction data. Where telemetry is generated by Evergrowth, it is intentionally scoped to a single runtime session and is not used to track users across sessions. Additional telemetry generated by Microsoft Business Central is governed by Microsoft’s own platform and privacy controls. All telemetry is processed within Microsoft Azure using industry-standard security practices and is accessible only to authorized Evergrowth personnel.
Overview
This policy is intended to explain the telemetry that is gathered and provide clarity to users and decision makers regarding the collection of telemetry data by software produced by 1319988 Alberta Ltd. o/a Evergrowth Consulting. In all cases, telemetry data is collected under the Evergrowth Privacy Policy located at:
Data Collection Mechanisms
Unless specifically stated otherwise, all data, analytics and telemetry that is gathered by Evergrowth Software is transmitted, stored in, consumed by and parsed using Microsoft Azure Application Insights. Some of the data that is emitted by Business Central is controlled entirely by Microsoft, and outside the control of the developer. Other data that is within the developer’s control is confirmed to contain no Personally Identifiable Information, and where possible contains no transaction data of any kind other than metadata about the transaction. (i.e. the time the transaction took to execute, the usage patterns from users, or should an error occur the nature of the error.)
Access
Care is taken to ensure that only authorized personnel employed by Evergrowth Consulting have access to this information in accordance with Microsoft’s published best-practice recommendations for Azure security.
Data Collected (Sample)
Acknowledging that the developer does not have full control over the emission of telemetry data, the following non-exhaustive fields and information represent what is being collected, and by which party. Where the party is Evergrowth Consulting, a reason will be provided:
| Field | Data Type | Collecting Party (Microsoft / Evergrowth / Both) | Reason |
|---|---|---|---|
| timestamp (UTC) | Date / time | Microsoft | |
| message | text | Both | summary of emission reason |
| severityLevel | integer | Both | classification of urgency |
| itemType | text | Microsoft | |
| alCallerAppId | guid | Microsoft | used to identify the developer’s application |
| alCallerAppName | text | Microsoft | used to identify the developer’s application |
| alCallerAppVersion | text | Microsoft | used to identify the developer’s application |
| alCallerAppPublisher | text | Microsoft | used to identify the developer’s application |
| alContext | text | Microsoft | used to identify the location in the code where the emission occurred |
| alCorrelationId | guid | Evergrowth | used to aggregate data across a single runtime session and is not used by Evergrowth Consulting for cross-session tracking or user identification |
| alDataClassification | text | Microsoft | SystemMetadata is the only classification allowed by Microsoft to be emitted |
| alError | text | Evergrowth | when an error occurs, a summary of the error will show; example: Attempted to evaluate a document type of: "Custom" |
| alObjectId | integer | Microsoft | used to identify where in the code the emission occurred |
| alObjectName | text | Microsoft | used to identify where in the code the emission occurred |
| alObjectType | text | Microsoft | used to identify where in the code the emission occurred |
| clientType | text | Microsoft | |
| companyName | text | Microsoft | used to isolate where in the database the emission occurred |
| component | text | Microsoft | |
| componentVersion | text | Microsoft | version number of Business Central |
| eventId | text | Evergrowth | used to classify and aggregate similar events; example: al.Error.Internal |
| extensionId | guid | Both | used to identify the module |
| extensionName | text | Both | used to identify the module |
| extensionPublisher | text | Microsoft | used to identify the module (Evergrowth Consulting) |
| extensionVersion | text | Both | used to identify the module |
| telemetrySchemaVersion | text | Microsoft | used to identify the data package structure |
| operationName | text | Microsoft | |
| operation_Id | guid | Microsoft | |
| operation_ParentId | guid | Microsoft | |
| operation_SyntheticSource | text | Microsoft | |
| session_Id | guid | Microsoft | |
| application_Version | guid | Microsoft | |
| client_Type | text | Microsoft | |
| client_Model | text | Microsoft | |
| client_OS | text | Microsoft | |
| client_IP | text | Microsoft | blocked |
| cloud_RoleName | text | Microsoft | |
| cloud_RoleInstance | text | Microsoft | |
| appId | guid | Microsoft | refers to Azure Application Insights |
| appName | text | Microsoft | refers to Azure Application Insights |
| iKey | guid | Microsoft | |
| sdkVersion | text | Microsoft | |
| itemId | guid | Microsoft | |
| itemCount | integer | Microsoft | |
| _ResourceId | text | Microsoft |
This table is provided as a representative example of telemetry fields observed at the time of publication. Field presence, naming, or availability may vary based on Microsoft platform changes, tenant configuration, or regulatory requirements.
Evergrowth believes that privacy policies should be clear, technically accurate, and understandable to both technical and non-technical readers. This document is intentionally detailed to support that goal.