Provision record
Snowflake · Snowflake Sub-Processors · View original document ↗

Objection period may differ per individual DPA

Common · 290 of 343 platforms
Stay ahead of the changes
Track Snowflake and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

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

How other platforms handle this

OpenAI

We may assign our rights or obligations under these Terms to any affiliate, subsidiary, or successor in interest of any business associated with our Services.

Credit Karma

You may not assign your rights under the Agreement, by operation of law or otherwise, without our consent.

Teladoc

Teladoc Health may assign, transfer, or delegate any of its rights and obligations hereunder without your consent.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
within twenty-eight (28) days after Snowflake's notice of such new Third-Party Sub-processor, or such other period of time as set forth in your DPA.

Excerpt from Snowflake's Sub-Processors

Provision details

Document information
Document
Snowflake Sub-Processors
Entity
Snowflake
Date stated by the document
March 6, 2026
As printed in Snowflake’s text (version CA-V-007631), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
July 6, 2026
Text quoted from version
CA-V-006917, captured Sept. 12, 2026
Record ID
CA-P-069654
Document ID
CA-D-000936
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-006917)
d51735989fab5f85ed25b096a0433cf8a9be25d9b04bc1593f2032eaa305ee8c
Analysis generated
July 6, 2026 23:26 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006917, captured Sept. 12, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007631, captured Oct. 16, 2026; this clause has not been re-checked against it.
Citation Record
Entity: Snowflake
Document: Snowflake Sub-Processors
Record ID: CA-P-069654
Version: CA-V-006917
Captured: 2026-09-12 01:21:23 UTC
SHA-256: d51735989fab5f85…
URL: https://conductatlas.com/platform/snowflake/snowflake-sub-processors/provision/CA-P-069654/objection-period-may-differ-per-individual-dpa/
Accessed: Nov. 3, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Snowflake's Objection period may differ per individual DPA clause do?

The clause states: “within twenty-eight (28) days after Snowflake's notice of such new Third-Party Sub-processor, or such other period of time as set forth in your DPA.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 290 platforms. See the full comparison.

Is ConductAtlas affiliated with Snowflake?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Snowflake.