Metadata fields in Snowflake¶
The data contained in metadata fields may be processed outside of your Snowflake Region. It is your responsibility to ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data is entered into any metadata field when using the Snowflake Service.
When creating an object in Snowflake, metadata fields may be captured. The most common metadata fields are:
Object definitions, such as a policy, an external function, or a view definition.
Object properties, such as an object name or an object comment.
Attention
For objects defined through SQL, metadata fields are usually populated by any fields entered as part of CREATE <object>, and ALTER <object>, or method call statements for a given object. Creating or manipulating objects in other languages, such as Python, may also populate metadata fields based on the object’s definitions and properties.
When using these commands, ensure that no personal data (other than for a User object), sensitive data, export-controlled data, or other regulated data populates any metadata fields.
In addition to the above fields, the following table sets forth additional potential metadata fields in the Snowflake Service. Metadata is “Usage Data” as defined in our Terms of Service or other agreement between you and Snowflake covering use of the Snowflake Service.
Snowflake updates this table regularly as new features and services are added. If you have questions about how Snowflake tracks data or about sensitive information in the actual query text please contact Snowflake Support.
Additional Metadata |
Query literals |
|
|---|---|---|
Snowflake Native App manifest file |
||
Snowpark Container Services specification file |
||
Listing information, manifest file, and profiles |
||
Custom instructions for Snowflake Copilot |
||
Generic error messages from ML functions |
||
Semantic models |