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

Thirty-day advance notice of sub-processor changes

High severity High confidence Explicit document language Common · 289 of 352 platforms
Stay ahead of the changes
Track HubSpot and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF

This analysis describes what HubSpot'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)

The 30-day advance notice period, available only to customers who opt in, sets a defined minimum window for customers to assess or respond to sub-processor changes before they apply.

Consumer impact (what this means for users)

If you opt in to notifications, HubSpot must notify you at least 30 days before a sub-processor change takes effect.

How other platforms handle this

DeepL Medium

DeepL will inform Customer of the respective modification to the Service in a clear and comprehensible manner at least two (2) months in advance by means of a message by e-mail ("Change Notice").

Google Maps Medium

Google will provide at least 90 days' advance notice for materially adverse changes to any SLAs by: (i) sending an email to the Notification Email Address; (ii) posting a notice in the Admin Console; or (iii) posting a notice to the applicable SLA webpage.

Minecraft Medium

we'll inform you of the change before it takes effect, either by posting a notice on our website or by other reasonable means.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
If you opt-in to receive a notification, we will notify you at least 30 days prior to any such change taking effect.

Excerpt from HubSpot's Sub-Processors

Provision details

Document information
Document
HubSpot Sub-Processors
Entity
HubSpot
Document last updated
July 6, 2026
Tracking information
First tracked
July 6, 2026
Last verified
July 9, 2026
Record ID
CA-P-067092
Document ID
CA-D-00932
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
be1ee395d61eaf157e884c8abd16fb6f7764b8b8dffdb3704efbafbd67a0364d
Analysis generated
July 6, 2026 23:16 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: HubSpot
Document: HubSpot Sub-Processors
Record ID: CA-P-067092
Captured: 2026-07-06 23:16:08 UTC
SHA-256: be1ee395d61eaf15…
URL: https://conductatlas.com/platform/hubspot/hubspot-sub-processors/provision/CA-P-067092/thirty-day-advance-notice-of-sub-processor-changes/
Accessed: Aug. 18, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
High
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 HubSpot's Thirty-day advance notice of sub-processor changes clause do?

The 30-day advance notice period, available only to customers who opt in, sets a defined minimum window for customers to assess or respond to sub-processor changes before they apply.

How does this clause affect you?

If you opt in to notifications, HubSpot must notify you at least 30 days before a sub-processor change takes effect.

How many platforms have this type of clause?

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

Is ConductAtlas affiliated with HubSpot?

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