Storybook collects completely anonymous data to help us improve user experience. Participation in this anonymous program is optional, and you may opt-out if you'd not like to share any information.
Why is telemetry collected?
Hundreds of thousands of developers use Storybook daily to build, test, and document components. Storybook is framework agnostic and integrates with the front-end ecosystem:
- Libraries such as Styled-Components, Tailwind, Redux
- Design tools such as Figma, Sketch, Zeplin and InVision
- Workflow tools such as Notion, Confluence, and Jira
In the past, our improvement process relied on manually gathering feedback. But with a growing userbase and the need to support a wide variety of integrations, we need a more accurate method for gauging Storybook usage and pain points.
These telemetry data help us (the maintainers) to prioritize the highest impact projects. That allows us to keep up with trends in the front-end ecosystem and verify that our community's hard work achieves the intended result.
What is being collected?
We collect general usage details, including command invocation, Storybook version, addons, and the view layer.
Specifically, we track the following information in our telemetry events:
- Timestamp of the occurrence.
- Command invoked (e.g.,
- Storybook unique identifier: One-way hash generated during Storybook installation process.
- One way hash of the IP address where the event occurred for spam detection.
- Story count.
- Storybook version.
- Storybook metadata:
- Supported view layers (e.g., React, Vue, Angular, Svelte).
- Builder (e.g., Webpack4, Webpack5, Vite).
- Meta framework (e.g., Next, Gatsby, CRA).
- Addons (e.g., Essentials, Accessibility).
- Feature flags (e.g.,
- Package manager information (e.g.,
- Monorepo information (e.g., NX, Turborepo).
- Whether the command was invoked on CI or not.
Access to the raw data is highly controlled, limited to select members of Storybook's core team who maintain the telemetry. We cannot identify individual users from the dataset: it is anonymized and untraceable back to the user.
What about sensitive information?
We take your privacy and our security very seriously. We perform additional steps to ensure that secure data (e.g., environment variables or other forms of sensitive data) do not make their way into our analytics. You can view all the information we collect by setting the
1 to print out the information gathered. For example:
Will generate the following output:
Will this data be shared?
The data we collect is anonymous, not traceable to the source, and only meaningful in aggregate form. No data we collect is personally identifiable. In the future, we plan to share relevant data with the community through public dashboards (or similar data representation formats).
How to opt-out
You may opt-out of the telemetry by setting Storybook's configuration element
true, using the
--disable-telemetry flag, or setting the environment variable
1. For example:
bootevent that contains no metadata at all (simply used to ensure the telemetry is working). It is sent prior to evaluating your
main.js, so it is unaffected by the
disableTelemetryoption. If you want to ensure that event is not sent, be sure to use the
Crash reports (disabled by default)
In addition to general usage telemetry, you may also choose to share crash reports. Storybook will then sanitize the error object (removing all user paths) and append it to the telemetry event. To enable crash reporting, you can set the
enableCrashReports configuration element to
true, using the
--enable-crash-reports flag, or set the
STORYBOOK_ENABLE_CRASH_REPORTS environment variable to
1. For example:
Generates the following item in the telemetry event: