Airbyte stores its internal state and metadata in two databases. By default, Airbyte uses a Postgres database that it spins up as part of the Docker service described in the

docker-compose.yml

file:

airbyte/db

. You can also configure Airbyte to use a dedicated custom Postgres instance instead of the default one ([source](https://docs.airbyte.com/operator-guides/configuring-airbyte-db)). As for the data transferred by Airbyte connectors, it is purged from an Airbyte deployment once it is transferred from the source to the destination ([source](https://docs.airbyte.com/operator-guides/security)). If you want to access the metadata of each connection made in your workspace, you can look into the Airbyte's internal database where it stores state and configuration metadata ([source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1673982982062789)). Please note that accessing the internal database directly might not be recommended, and it's better to use Airbyte's API or UI for managing connections and their metadata.