Anonymous Telemetry

To help the Kedro Project maintainers improve the software, Kedro can capture anonymised telemetry. This data is collected with the sole purpose of improving Kedro by understanding feature usage. Importantly, we do not store personal information about you or sensitive data from your project, and this process is never utilized for marketing or promotional purposes. Participation in this program is optional, and Kedro will continue working as normal if you opt-out.

The Kedro Project’s telemetry has been reviewed and approved under the Telemetry Data Collection and Usage Policy of LF Projects, LLC.

Kedro collects anonymous telemetry through the Kedro-Telemetry plugin, which will prompt you for your consent the first time.

Collected data fields:

  • Unique user identifier(UUID): The UUID is a randomly generated anonymous identifier, stored within an OS-specific configuration folder for Kedro, named ‘telemetry.conf’. If a UUID does not already exist, the telemetry plugin generates a new one, stores it, and then uses this UUID in subsequent telemetry events.

  • CLI Command (Masked Arguments): The command used, with sensitive arguments masked for privacy. Example Input: kedro run --pipeline=ds --env=test What we receive: kedro run --pipeline ***** --env *****

  • Hashed Package Name: An anonymized identifier of the project.

  • Kedro Project Version: The version of Kedro being used.

  • Kedro-Telemetry Version: The version of the Kedro-Telemetry plugin.

  • Python Version: The version of Python in use.

  • Operating System: The operating system on which Kedro is running.

  • Tools Selected and Example Pipeline: The tools chosen and example pipeline inclusion during the kedro new command execution, if applicable.

  • Number of Datasets, Nodes, and Pipelines: Quantitative data about the project structure.

For technical information on how the telemetry collection works, you can browse the source code of kedro-telemetry.