|
1 |
| -Rerun's analytics SDK. |
| 1 | +# Rerun's analytics SDK |
| 2 | + |
| 3 | +We use [PostHog](https://posthog.com/) to collect anonymous usage statistics. |
| 4 | + |
| 5 | +Usage data we do collect will be sent to and stored in servers within the EU. |
| 6 | + |
| 7 | +You can audit the actual data being sent out by inspecting the Rerun data directory directly. |
| 8 | +Find out its location by running `rerun analytics config`. |
| 9 | + |
| 10 | + |
| 11 | +### Opting out |
| 12 | +Run `rerun analytics disable` to opt out of all usage data collection. |
| 13 | + |
| 14 | +### What data is collected? |
| 15 | +The exact set of analytics events and parameters can be found here: <https://github.com/rerun-io/rerun/blob/main/crates/re_analytics/src/events.rs> |
| 16 | + |
| 17 | +- We collect high level events about the usage of the Rerun Viewer. For example: |
| 18 | + - The event 'Viewer Opened' helps us estimate how often Rerun is used. |
| 19 | + - The event 'Data Source Connected' helps us understand if users tend to use live |
| 20 | + data sources or recordings most, which helps us prioritize features. |
| 21 | +- We associate events with: |
| 22 | + - Metadata about the Rerun build (version, target platform, etc). |
| 23 | + - A persistent random id that is used to associate events from |
| 24 | + multiple sessions together. To regenerate it run `rerun analytics clear`. |
| 25 | +- We may associate these events with a hashed `application_id` and `recording_id`, |
| 26 | + so that we can understand if users are more likely to look at few applications often, |
| 27 | + or tend to use Rerun for many temporary scripts. Again, this helps us prioritize. |
| 28 | +- We may for instance add events that help us understand how well the auto-layout works. |
| 29 | + |
| 30 | +### What data is NOT collected? |
| 31 | +- No Personally Identifiable Information, such as user name or IP address, is collected. |
| 32 | + - This assumes you don't manually and explicitly associate your email with |
| 33 | + the analytics events using the analytics helper cli. |
| 34 | + (Don't do this, it's just meant for internal use for the Rerun team.) |
| 35 | +- No user data logged to Rerun is collected. |
| 36 | + - In some cases we collect secure hashes of user provided names (e.g. `application_id`), |
| 37 | + but take great care do this only when we have a clear understanding of why it's needed |
| 38 | + and it won't risk leaking anything potentially proprietary. |
| 39 | + |
| 40 | +### Why do we collect data? |
| 41 | +- To improve the Rerun open source library. |
0 commit comments