Telemetry

Bluebricks collects telemetry data about the usability of its bricks CLI and web application interface. In addition, Bluebricks collects general usage data from its platform. Telemetry collection is optional, and you may opt-out if you'd not like to share any information.

Why is telemetry collected?

Collecting telemetry about Bluebricks' usability and platform usage is essential for end users and customers, as it provides valuable insights that drive continuous improvement and innovation.

Telemetry enables Bluebricks to fully represent the diverse use cases of the entire user base and avoid capturing only the experiences of a limited subset of users.

This data helps us identify common pain points, understand which features are most valuable, and prioritize improvements that will benefit the majority of users.

By leveraging this information, we can make informed decisions that ensure Bluebricks continues to evolve in a way that enhances its relevance, performance, and overall user experience. Additionally, telemetry allows us to measure the impact of updates, confirming that our enhancements are delivering real value to our customers.

What is being collected?

We collect two segments of data; user-experience usability and platform performance and operation.

User Experience Usability

We track user behavioral activity, such as page views, scrolls, and clicks.

Additionally, we collect data about sessions, such as:

• Duration

• Continuity

• Geo-location

• Operation System

• Browser vendor and type

• Resolution

We do not collect private information about the user, including name, email, IP, etc. See Bluebricks Privacy for more information.

bricks Command Line

We collect behavioral activity such as command invokes, errors, and crashes outside of the web interface. We do not ship backlogs or collect private information about the runtime or the users.

Users can opt-out of command line telemetry by typing bricks telemetry disable command, and enable it by typing bricks telemetry enable.