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

Twenty-Eight-Day Sub-Processor Objection Window

Medium severity Medium confidence Explicit document language Unique · 0 of 352 platforms
Stay ahead of the changes
Track Snowflake and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

Customers with an executed DPA may object to a newly added third-party sub-processor by emailing privacy@snowflake.com within twenty-eight days of Snowflake's notice, with the resolution of such objections governed by the terms of the individual DPA.

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes the procedural mechanism and deadline for exercising sub-processor objection rights, with the practical effect of any objection depending entirely on the contractual language in each customer's individual DPA rather than a uniform procedure.

Interpretive note: The practical effect of an objection depends on the language of each customer's individual DPA, which varies by contract and is not published in this document.

Consumer impact (what this means for users)

This provision requires customers to submit sub-processor objections within twenty-eight days of notice, and the document states that objection handling is determined by the individual DPA, meaning the available remedies vary by customer contract.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Opt Out of Arbitration
    Within 28 days
    Send a written objection to privacy@snowflake.com within twenty-eight days of receiving Snowflake's notice of a new sub-processor, identifying the specific sub-processor and the basis for the objection. Refer to your DPA for the resolution procedure applicable to your account.

Cross-platform context

See how other platforms handle Twenty-Eight-Day Sub-Processor Objection Window and similar clauses.

Compare across platforms →
▸ View Original Clause Language DOCUMENT RECORD
"
If you are a current Snowflake customer, with a fully executed data processing agreement ("DPA") in place with Snowflake, you may notify us of an objection to Snowflake's use of a new Third-Party Sub-processor used to process your Customer Data by sending such objection to privacy@snowflake.com 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. Objections shall be handled as described in your DPA.

Excerpt from Snowflake's Sub-Processors

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

(1) REGULATORY LANDSCAPE: GDPR Article 28(2) requires that controller-processor agreements include provisions giving the controller the ability to object to sub-processor changes.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    File a complaint →

Provision details

Document information
Document
Snowflake Sub-Processors
Entity
Snowflake
Document last updated
July 6, 2026
Tracking information
First tracked
July 6, 2026
Last verified
July 9, 2026
Record ID
CA-P-015685
Document ID
CA-D-00936
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
78a6e16dd3159fc2d602a3ee1c68e30dd1fd4b2c775842c21d2702f594f4f363
Analysis generated
July 6, 2026 23:26 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Snowflake
Document: Snowflake Sub-Processors
Record ID: CA-P-015685
Captured: 2026-07-06 23:26:12 UTC
SHA-256: 78a6e16dd3159fc2…
URL: https://conductatlas.com/platform/snowflake/snowflake-sub-processors/provision/CA-P-015685/twenty-eight-day-sub-processor-objection-window/
Accessed: Aug. 12, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Get the 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.

Frequently Asked Questions

What does Snowflake's Twenty-Eight-Day Sub-Processor Objection Window clause do?

This provision establishes the procedural mechanism and deadline for exercising sub-processor objection rights, with the practical effect of any objection depending entirely on the contractual language in each customer's individual DPA rather than a uniform procedure.

How does this clause affect you?

This provision requires customers to submit sub-processor objections within twenty-eight days of notice, and the document states that objection handling is determined by the individual DPA, meaning the available remedies vary by customer contract.

Is ConductAtlas affiliated with Snowflake?

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