I'm a bit irritated about the information on https://docs.prefect.io/orchestration/faq/dataflow.html#gotchas-and-caveats , which claims to be an exhaustive list of data that might end up in the prefect database. It doesn't mention anything about the flow metadata like names of flows and tasks and their configuration like run_config, schedules or storage. So I assume this list isn't actually exhaustive?

Prefect was designed to allow users the ability to ensure both their code and their data never leaves their internal ecosystem. This guide will focus on how data moves between tasks and flows in the Prefect Cloud execution model, as well as call out any caveats that might result in data being exposed to Prefect Cloud.

All data being referenced here are the inputs and outputs of Prefect tasks.

It seems like flow and task metadata aren't considered 'data' for the purposes of that page. However, I agree that it can easily be misunderstood. Maybe if there was a FAQ topic

Code Handling in the Hybrid Model

, right next to the Data Handling topic, it would reduce confusion and better highlight the distinction between code and data.

Just opened a new issue for this: https://github.com/PrefectHQ/prefect/issues/4381

Thanks for the feedback @xyzy!