Openwake · evidence pack

Snowflake

https://www.snowflake.com · record 253 · read 2026-09-06 · rules/v1 · generated 2026-09-06 04:05 UTC

Facts

Trains on customer data
unclear
“• operate, audit and improve our Sites, products and services, which includes training our machine learning and artificial intelligence models;”
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.30
Opt-out mechanism
You may opt out of receiving promotional emails from us by following the instructions in those emails or by accessing the Snowflake Preference Center (https://info.snowflake.com/2024-Preference-center).
“You may opt out of receiving promotional emails from us by following the instructions in those emails or by accessing the Snowflake Preference Center (https://info.snowflake.com/2024-Preference-center).”
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.50
AI features
present
“We may use artificial intelligence, machine learning, or other automated processing to assist us in carrying out the purposes listed below.”
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.55
Model providers named
none named
No supporting text found in the documents read.
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.20
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://www.snowflake.com/privacy-policy/ · confidence 0.20
Subprocessor notice
28 days
“Snowflake shall provide such notification both to (i) email addresses that have subscribed for notifications on the Sub-processor Site, and (ii) email addresses designated by Customer as ‘privacy notices’ recipients within Service, at least twenty-eight (28) days in advance of allowing the new Sub-processor to Process Customer Personal Data (the “Objection Period”).”

Subprocessors (0)

NameCategoryLocationQuoted from
None listed.

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://www.snowflake.com/privacy-policy/2026-09-06b80342b0ae8f88a7…seq 471
dpahttps://www.snowflake.com/legal/data-processing-addendum2026-09-0661e08b7abe924fa5…seq 472
Ledger proof for this record.
seq 524 · key 2f898a895f05b7a0 · 2026-09-06T01:40:52.462Z
hash ab74244dd8bd0e99e33750584077bcc6763de3d809092da998f7ad258cf8e03c
prev c4d7602075f89dc9ed77feabe53b87ea6484af502934d12130c45bb2f6f1c73e
payload 98e28abdf726568b15f199cbcc129c6fba01b8796ab17d25e133f222a959fc20
signature yrQ4XqXcU8URc9KU+BxK+kirTiabJzalN2D4ldplgUTCzn3HLMUs6UwSCda7jNNGK5/bEXcqfFz+Nk+NI8ClAA==
anchored 2026-09-06 at head seq 564 231a9dea0f93915bd7110e6786e00908325db3031635ace53c1023f850e0c49c
Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.