​

Why Does Activepieces need data?

As a self-hosted product, gathering usage metrics and insights can be difficult for us. However, these analytics are essential in helping us understand key behaviors and delivering a higher quality experience that meets your needs. To ensure we can continue to improve our product, we have decided to track certain basic behaviors and metrics that are vital for understanding the usage of Activepieces. We have implemented a minimal tracking plan and provide a detailed list of the metrics collected in a separate section.

​

What Does Activepieces Collect?

We value transparency in data collection and assure you that we do not collect any personal information. The full list of events is in the app itself: go to Platform → Infrastructure → Configurations and open See the events we track under Product analytics. Alongside them we count page views inside the app. Exact Code

​

Deployment setup

Licensed instances also send a daily snapshot of the shape of the deployment: how many app replicas and workers are running, their CPU / memory / disk sizes, their versions, worker configuration, the database / Redis / storage round-trips, the deployment settings shown on your diagnostics page (execution mode, storage location, sandbox memory limit, concurrency), and the release health check. It is the same information as Platform → Infrastructure → Health, and it carries no hostnames, no IP addresses, no storage endpoint, and nothing from your flows, your data or your connections. We use it to answer support questions without asking you to gather diagnostics, and to see which deployment shapes a release is about to affect before we ship it.

​

Opting out?

Go to Platform → Infrastructure → Configurations and switch Product analytics off. The setting is stored per platform, so an instance hosting several platforms controls each one separately. Deployment setup is a separate switch in the same place, and is on by default. Unlike product analytics it does not read AP_TELEMETRY_ENABLED — switch it off in the UI to stop the daily snapshot. AP_TELEMETRY_ENABLED=false still works as a starting value: each platform’s setting is created the first time it is read and takes the variable’s value, so a self-hosted instance with the variable set to false is opted out from the start and stays opted out through the upgrade. Once the setting exists, the toggle governs it and changing the variable has no further effect.