Notice of Changes to Terms
A notice of changes is the email or posted message a vendor uses to tell you its terms, privacy policy or other legal documents are changing, and when the new version starts to apply.
What is a notice of changes to terms?
A notice of changes is the message a vendor sends, or the banner it posts, to say its legal terms are about to change or already have. It often arrives as an email titled "We've updated our terms" or "Updates to our Terms of Service."
The notice itself is not the change. It points to a new version of a document, such as the terms of service, the privacy policy or the data processing agreement (DPA), the contract that covers how the vendor handles personal data for you.
Many vendor contracts let the vendor change its terms on its own. That right comes from a unilateral amendment clause. The notice is how the vendor tells you it is using that right.
Notice matters for a legal reason too. A changed contract is, in basic contract law, a new offer. As the American Bar Association's Business Law Today explains, a proposed change generally needs notice and your agreement before it binds you. How much notice is enough depends on the facts and on the court.
What it looks like in a vendor's terms
A typical clause reads like this:
We may update these Terms from time to time. If a change is material, we will notify you at least 30 days before it takes effect, by email to the account owner or by a notice in the product. Other changes take effect when we post them. If you keep using the service after the effective date, you accept the updated Terms.
- "From time to time": the vendor keeps the right to change the terms whenever it chooses.
- "If a change is material": only changes the vendor treats as important get advance notice. See material change.
- "At least 30 days": the notice period, your window to read and react before the new terms apply.
- "By email or a notice in the product": the channel. Email to one person on your account may be all you get.
- "Take effect when we post them": for smaller changes, there may be no advance notice at all.
- "If you keep using the service": the vendor treats continued use as acceptance.
The AWS Customer Agreement lets AWS change the agreement by posting a new version and adds that "It is your responsibility to check the AWS Site regularly."
How much warning vendors give
There is no single standard. The notice period is set mostly by the vendor's own contract, and it can differ for different kinds of change. Here are real examples from vendor documents as of October 2026.
- No advance notice: under the AWS Customer Agreement, general changes take effect when posted, or as stated in an email if AWS emails you.
- 30 days: the GitHub Terms of Service promise notice of material changes, such as price increases, at least 30 days before they take effect.
- 30 days, with a catch: the Atlassian Customer Agreement says Atlassian must use "commercially reasonable efforts" to post changes 30 days ahead. That is a promise to try, not a guarantee.
- Different periods for different topics: the same AWS agreement gives 30 days' notice for fee increases, 90 days for adverse changes to a service level agreement, and 12 months before discontinuing material functionality of a service.
Many vendors land on 30 days for material changes. X, for example, posted its 2026 update on September 9 with an effective date of October 9, 2026.
Email notice vs posting on the website
Vendors give notice in two main ways. They email the address on your account, or they post the new version on their website, sometimes with a banner or an in-app message.
Email is better for you because someone actually receives it. Posting alone puts the burden on you to go looking. Courts have pushed back on posting-only notice in some cases. In Douglas v. U.S. District Court (9th Cir. 2007), a phone customer was not bound by revised terms that the provider had only posted on its website. The court said customers have no duty to keep checking a website for changes.
That case involved a consumer, and the law varies by state and by facts. It does not mean every posted change fails. It does mean the way a vendor gives notice can affect whether a change binds you.
Email notice has its own weak spot. It usually goes to one address, such as the account owner or billing contact. If that person left, or the email lands in a shared inbox nobody reads, you got notice on paper but not in practice.
A real change we caught
Venpo flagged that Meta dropped the 30-day notice from its WhatsApp Business terms in September 2026. Meta used to give 30 days' written notice before ending the agreement, and can now end it "at any time for any reason upon notice to you." The rewrite also deleted the promise "we will notify you before we make a Change," and using the platform after an update now counts as accepting it. You see changes like these only by comparing the old and new versions of the terms.
Why it matters to you
A notice of changes is often the only warning you get before your deal with a vendor shifts. The new terms can touch three things you care about.
- Money: price increases, new fees and stricter refund rules often arrive through a terms update. See price change notice.
- Data: a privacy policy or DPA update can widen how the vendor uses your data, for example for AI training or advertising.
- Your obligations to your own customers: if you promised customers how their data is handled, a vendor change can put you out of line with your own promises.
The notice period is also your only window to act. Once the effective date passes, your options shrink. Some contracts let you object or cancel, but only within a set time after the notice.
Data changes carry an extra point. In a February 2024 blog post, FTC staff warned that a company that starts using data more freely and tells people only through a "surreptitious, retroactive amendment" to its terms or privacy policy may be acting unfairly or deceptively. That is staff guidance, not a rule, but it shows why the timing and clarity of notice matter.
What to do when you get a "We've updated our terms" email
- Find the effective date. That is your deadline to decide.
- Find out what changed. Look for a summary, a change log or a comparison. If there is none, compare the old and new text with a redline.
- Check the changes that touch money, data, liability and how disputes are handled, such as a new arbitration clause.
- Check your own contract for options: a right to object, a right to cancel, or changes that only apply at renewal. See right to reject changes.
- If a change matters, write to the vendor before the effective date and keep a copy of what you sent.
- Save a copy of both versions, so you can show later what you agreed to and when. See terms of service version history.
What to check
- How much notice the vendor promises, and whether that promise covers all changes or only material ones.
- Whether the notice period is a firm promise or only "reasonable efforts."
- Which channel counts as notice: email, a posted page, or an in-app message.
- Which email address receives legal notices, and whether a person still reads it.
- Whether you can reject a change or cancel and get a refund for prepaid time.
- For a negotiated contract, ask for written notice of any change at least 30 days ahead, sent to a named contact.
Notices clause
A notices clause is the part of a contract that says how each side must send formal messages to the other, and when a message counts as delivered. It decides where a notice of changes has to go.
The AWS Customer Agreement is a clear example. AWS may give notice by posting on its website or by emailing the address on your account. A posted notice counts from the moment it is posted. An email counts when it is sent. The agreement also says it is your job to keep your email address current.
Notices to the vendor often follow stricter rules. In the same AWS agreement, notices to AWS go by fax, personal delivery, courier or registered mail. The Atlassian Customer Agreement sends notices to the billing or technical contact you gave, and says email is not enough for some notices, such as certain termination notices from you.
So check two things. Who on your side receives notices, and how you must send yours. A cancellation or objection sent the wrong way may not count.
How Venpo helps
Notices go to one inbox, and some changes come with no notice at all. Venpo watches your vendors' terms, privacy policies, DPAs and other public legal pages and emails you a plain-English alert when one changes, with what changed and why it matters. Each vendor also gets a change history, so you can see every version you were held to.
Frequently asked questions
Can a vendor change its terms without telling you?
Many contracts let the vendor post changes without an email, and some changes take effect on posting. Whether that binds you depends on the contract, the facts and the court, since some US courts have refused to enforce changes the customer never had notice of.
How much notice do SaaS vendors have to give before changing terms?
For business contracts in the US, the notice period is mostly whatever the vendor's own contract promises. You will see anything from no advance notice to 30 or 90 days, depending on the vendor and the type of change.
Do I need to reply to a "We've updated our terms" email?
Usually no reply is needed. Many vendors' terms treat continued use as acceptance, though courts do not always agree. Reply only if you want to object, ask a question or use a right to cancel, and do it before the effective date.
What if the notice went to someone who left the company?
The vendor may still treat the email as valid notice. Keep the account owner, billing and legal contact addresses current, and route them to a shared inbox someone checks.
Is a notice of changes the same as a contract amendment?
No. A notice tells you the vendor changed its standard terms on its own. A contract amendment is a change both sides sign.
Related terms
Sources
- AWS Customer Agreement
- GitHub Terms of Service
- Atlassian Customer Agreement
- X Privacy Center: Updates to our Terms of Service (2026)
- US Court of Appeals for the Ninth Circuit: Douglas v. U.S. District Court (July 2007)
- ABA Business Law Today: Online contracts (May 2016)
- FTC Technology Blog: AI (and other) Companies: Quietly Changing Your Terms of Service Could Be Unfair or Deceptive (Feb 13, 2024)
Last reviewed