The term telemetry refers to the collection of certain usage data to help improve the quality of a piece of software. Dendron uses telemetry primarily for collecting usage data.
This page describes the overall telemetry approach for Dendron, what kind of data is collected and how to opt-out of data collection.
Why does Dendron collect metrics?
Telemetry helps us better understand how many users are using our products and how often they are using our products. Unlike many telemetry services, our telemetry implementation is intentionally limited in scope.
We use telemetry to answer the following questions:
- how many people are actively using Dendron?
- how performant is Dendron over time and how do new changes impact performance?
- what features are most useful for users?
What is not collected
Dendron will never collect data inside your notes. We believe that your personal knowledge is for your eyes alone.
What is collected
The below is a collection of common fields that are collected
|string||Currently installed version of the product (e.g. |
|string||Currently installed version of the IDE (e.g. |
|string||The specific IDE in question(e.g. |
|string||Client's operating system architecture (e.g. |
|string||Client's operating system (e.g. |
|string||Client's node version (e.g. |
|string||Random, non-identifiable signature UUID (e.g. |
|string||When the request was made|
When is data collected?
Data is collected in scenarios that are described below.
When Dendron initializes, we collect data about on initialization time. This helps us measure the performance impact of changes that run before startup as well as improvements to our indexing performance over time.
|number||Number of seconds for startup|
|number||Number of notes across all vaults (rounded to the nearest 10 notes)|
|number||Number of vaults in workspace|
|boolean||Check whether caching is disabled|
When Dendron is first installed or upgraded, we collect information about both previous and current versions. This helps us plan deprecation policies.
|string||Previous version of Dendron|
When lookup is performed, Dendron collects profiling information for different phases of lookup. This helps us measure the performance impact of optimizations and features we add to lookup.
- Lookup Show: when lookup is presented
- Lookup Update: when lookup items are updated
- Lookup Accept: when a result from lookup is accepted
|string||What kind of lookup ("schema" or "note")|
|boolean||Did an error happen during this phase?|
|string||What initiated the lookup? ("onValueChange", "updatePickerBehavior:journal", etc )|
|boolean||Was a new note created during this phase?|
When telemetry is disabled or enabled, we collect information about the event to let us get an estimate of the number of untracked clients
How to opt out of data collection
You can disable telemetry from Dendron either on a per-workspace level or globally. To disable on a workspace level, set noTelemetry to
To disable telemetry across all workspaces, you can run the Disable Telemetry command.
Why not have opt-in telemetry?
The goal of telemetry is to make data driven decisions about features and use cases that can make the most difference to our users.
One way we could collect data is to conduct surveys but traditionally, these had very low participation and are also biased towards users that are already active in our community. Having telemetry allows us to collect feedback from our larger user base and avoids this bias.
Opt-in telemetry, at best, gives us a narrow and biased set of users. At this point, we are back to make decisions based on limited data. Opt-out telemetry that is limited in scope is the tradeoff we made in terms of preserving user privacy while still gathering meaningful data that can help improve the product.