Effective Date

What is an effective date?

An effective date is the day a contract, or a new version of it, starts to apply. Before that day, the old rules govern. From that day on, the new ones do.

In vendor documents you will see it at the top of the page, as "Effective date," "Effective as of" or "Effective starting." It appears on terms of service, privacy policies, data processing agreements and pricing pages.

When a vendor sends a notice of changes, the effective date is the most important line in it. It is your deadline to read, object or leave.

What it looks like in a vendor's terms

A typical clause reads like this:

These Terms are effective as of March 1. Updated Terms take effect on the date stated at the top of the revised version, or, if no date is stated, when we post them. If you use the services after the effective date, the updated Terms apply to you.

• "Effective as of March 1": the date this version starts to bind you.
• "The date stated at the top": the vendor can set a future date for a new version.
• "When we post them": with no date given, the change applies right away.
• "After the effective date": your use after that day is treated as accepting the new version. See continued use as acceptance.

The AWS Customer Agreement says modified terms take effect "upon posting or, if we notify you by email, as stated in the email message."

Future dates and preview versions

Many vendors publish a new version before it applies. The page shows a future effective date, and the old version stays in force until then. This gap is your notice period.

Real examples:

• X posted its update on September 9, 2026, and said the new terms take effect on October 9, 2026.
• The Atlassian Customer Agreement is marked "Effective starting: October 1, 2026."
• The SurveyMonkey AI terms show "Updated: November 3, 2025" and "Effective date: December 27, 2025," almost eight weeks apart.

During the gap, two versions can exist at once: the current one and the upcoming one. Read the upcoming one, because that is the one you will be held to.

Some contracts also add a second layer. A change may be published with one date but only apply to you at your next renewal. See right to reject changes.

A real change we caught

Venpo flagged a case where SurveyMonkey changed its AI providers on a page still dated November 2025. In September 2026 its subprocessor list added AWS Bedrock and Anthropic and dropped Azure OpenAI. The date at the top did not move, but the content did. It shows why you cannot judge whether a page changed from its date alone.

Why it matters to you

The effective date sets your deadline. If a new version raises prices, widens data use or adds an arbitration clause, the effective date is when it bites. Any right to object or cancel usually has to be used before then, or within a short window after the notice.

It also tells you which version applies to a past event. If there is a billing dispute or a data incident, the terms in force on that date usually control. That is why saving old versions matters. See terms of service version history.

What to check

• The effective date of each new version, and whether it is in the future.
• Whether the date on the page is an effective date or only a "last updated" date.
• Whether changes apply to you on the effective date or only at your next renewal.
• Any deadline to object or cancel, counted from the notice or the effective date.
• Whether the new version claims to apply to events before its effective date.

Last updated date

A last updated date is the date a vendor shows to say when it last edited a page. It is not the same as an effective date, and it is not always a reliable sign of when something changed.

The two dates answer different questions. "Last updated" says when the text was edited. "Effective" says when the rules start to apply. They can differ by weeks, as the SurveyMonkey AI terms above show.

Two things can make a last updated date misleading:

• The page changed but the date did not move.
• The date moved but only a typo or link changed.

Some pages show only one of the two dates. The AWS agreement shows "Last Updated," while the Atlassian Customer Agreement shows only an effective date. Law firm Morgan Lewis advises website owners to add a date stamp showing when their terms were last updated. Treat the date as a hint, then compare the text itself.

How Venpo helps

Dates on legal pages can lag behind the text. Venpo checks the content of your vendors' public legal pages, not just their dates, and emails you a plain-English alert when the text changes, with what changed and why it matters. Each vendor gets a change history, so you can see which version applied when.