Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
The document lists Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107) as an optional third-party sub-processor for R2 cloud storage in connection with the Egress Cost Optimizer feature, operating across all Snowflake-managed ECO cache regions as described in Snowflake's Documentation.
This analysis describes what Snowflake's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision discloses that customers enabling the Egress Cost Optimizer feature may have Customer Data processed and stored by Cloudflare in Snowflake-managed cache regions, expanding the sub-processor footprint beyond the primary cloud infrastructure providers.
Interpretive note: The specific geographic regions in which Cloudflare ECO cache operates are described in external Snowflake Documentation rather than in this page, limiting full assessment of transfer scope from this document alone.
This provision establishes that Customer Data may be stored in Cloudflare R2 cloud storage if the Egress Cost Optimizer feature is enabled, with Cloudflare operating across all Snowflake-managed ECO cache regions as described in external documentation.
Cross-platform context
See how other platforms handle Cloudflare Optional Sub-Processor for Egress Cost Optimizer and similar clauses.
Compare across platforms →Monitoring
Snowflake has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Cloudflare R2 cloud storage for optional use in connection with Snowflake's Egress Cost Optimizer feature See Documentation * SCCs Cloudflare Sub-processorsExcerpt from Snowflake's Sub-Processors
(1) REGULATORY LANDSCAPE: Engagement of Cloudflare as a sub-processor for data storage engages GDPR Article 28 obligations and requires that Cloudflare processing is covered by adequate contractual protections. SCCs are the stated transfer mechanism. The specific cache regions operated by Cloudflare for ECO are described in external documentation rather than this page, which may affect the completeness of customers' transfer impact assessments. (2) GOVERNANCE EXPOSURE: Low to Medium. Cloudflare was added as a sub-processor on April 11, 2025 per the Updates Summary. Customers who enabled the Egress Cost Optimizer feature prior to that date should confirm that their sub-processor records and DPA notifications reflect this addition. Customers who have not enabled the feature are not subject to Cloudflare processing under these terms. (3) JURISDICTION FLAGS: EU and UK customers should assess the specific Cloudflare cache regions used by the ECO feature and confirm that SCCs cover all applicable data flows to those regions. Cloudflare's global network may include cache locations in jurisdictions requiring individual transfer impact assessments. (4) CONTRACT AND VENDOR IMPLICATIONS: Customers with DPAs that enumerate permitted sub-processors or limit sub-processor additions to specific categories should review whether Cloudflare's addition as a storage sub-processor requires a DPA amendment or amendment notice under their specific contract terms. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should review Snowflake's Documentation referenced in the table to identify all ECO cache regions where Cloudflare may process Customer Data and incorporate those regions into transfer impact assessments. The optional nature of this sub-processor engagement means that compliance obligations are triggered only if the Egress Cost Optimizer feature is activated.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision discloses that customers enabling the Egress Cost Optimizer feature may have Customer Data processed and stored by Cloudflare in Snowflake-managed cache regions, expanding the sub-processor footprint beyond the primary cloud infrastructure providers.
This provision establishes that Customer Data may be stored in Cloudflare R2 cloud storage if the Egress Cost Optimizer feature is enabled, with Cloudflare operating across all Snowflake-managed ECO cache regions as described in external documentation.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Snowflake.