Update dbt State data storage FAQ with metadata specs and hosting details#9349
Open
luna-bianca wants to merge 2 commits into
Open
Update dbt State data storage FAQ with metadata specs and hosting details#9349luna-bianca wants to merge 2 commits into
luna-bianca wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
luna-bianca
commented
Jun 8, 2026
|
|
||
| No actual data from your warehouse is transmitted. | ||
|
|
||
| The dbt State service runs in a single US multi-tenant (MT) instance and does _not_ make any live connections to your data warehouse. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). |
Contributor
Author
There was a problem hiding this comment.
@jtcohen6 Is it correct that we should link here?
Collaborator
There was a problem hiding this comment.
Suggested change
| The dbt State service runs in a single US multi-tenant (MT) instance and does _not_ make any live connections to your data warehouse. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). | |
| The dbt State service runs in a single US multi-tenant (MT) instance. The service never connects to your data warehouse. No actual data from your warehouse is transmitted. The only connection is to your running dbt process (CLI or platform) in order to exchange the metadata described above. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). |
Contributor
|
LGTM but defer to @jtcohen6 to confirm technical details |
jtcohen6
reviewed
Jun 23, 2026
| dbt State sends the following metadata to dbt Labs servers: | ||
|
|
||
| - **Last-modified timestamps** — used to determine whether upstream data has changed since the last run | ||
| - **SQL statement hashes** — SQL statements are hashed before transmission, so dbt Labs cannot see the contents; only hashes are stored and compared across runs to detect logic changes |
Collaborator
There was a problem hiding this comment.
Suggested change
| - **SQL statement hashes** — SQL statements are hashed before transmission, so dbt Labs cannot see the contents; only hashes are stored and compared across runs to detect logic changes | |
| - **SQL statement hashes** — SQL statements are processed to detect and classify changes, then hashed. Only the hash is persisted for future comparisons. |
|
|
||
| No actual data from your warehouse is transmitted. | ||
|
|
||
| The dbt State service runs in a single US multi-tenant (MT) instance and does _not_ make any live connections to your data warehouse. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). |
Collaborator
There was a problem hiding this comment.
Suggested change
| The dbt State service runs in a single US multi-tenant (MT) instance and does _not_ make any live connections to your data warehouse. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). | |
| The dbt State service runs in a single US multi-tenant (MT) instance. The service never connects to your data warehouse. No actual data from your warehouse is transmitted. The only connection is to your running dbt process (CLI or platform) in order to exchange the metadata described above. For data retention details, refer to the [dbt Labs privacy policy](https://www.getdbt.com/cloud/privacy-policy). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Closes https://dbtlabs.atlassian.net/browse/PRODDOCS-1104
Updates the dbt State "How is data stored?" FAQ to clarify what metadata is stored, data transmission behavior, and hosting details.
Changes:
Previews:
Checklist
🚀 Deployment available! Here are the direct links to the updated files: