Openwake · evidence pack

Snowflake

https://www.snowflake.com · record 613 · read 2026-10-13 · rules/v1 · generated 2026-10-23 04:13 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-10-13213895ee6ffda357…seq 53170
dpahttps://www.snowflake.com/legal/data-processing-addendum2026-10-13383eb30780141243…seq 53171
Ledger proof for this record.
seq 53392 · key 2f898a895f05b7a0 · 2026-10-13T05:19:29.134Z
hash 720c230c553643e46fc2d3a6633b7e14a6a4ebdd020fd746041b29fab446d63a
prev 9d18df1795781f55db0564025cc0114501d758d65699fad2a45c2459b36a3d4b
payload 487f172c68fe7cc4467dc26ac7e3f8bf21f577d56859776fcffd9da47fd2f728
signature WgScN7BUESqDXOTkD+0IAPGZ/G6mDdc/lojFjxfVGifSy+Ymwa+XDUm48Nji5FJMs9TO1d6qIxF3Z1jJkAVvBw==
anchored 2026-10-13 at head seq 53553 29b831e17d49be9d0c48e24c727cfa82ce9b500faacabb488dae167a42404d31
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.