CheckoryCheckory
Clause 12.4 live URL versus last year's emailed PDF, posted AUP SLA and price list, no face

How to Review a Unilateral Online-Policy Update Right

Review a posted-URL policy update: list what the page can rewrite, demand a named inbox, calendar continued use, then hunt a walk-right with a refund.

9 min readArticle
💡

Key takeaway in 30 seconds

How to review a unilateral online-policy update right is a posted-URL hunt: list what the page can rewrite, demand a named inbox, calendar the continued-use clock, and hunt a material-change walk-right with a prepaid refund. Last year's click-Accept does not close the file. Then freeze the old page, object in writing, or ask to walk.

The vendor mailed Slack, not the notices inbox, and says a posted URL plus continued use rewrites the Acceptable Use Policy, the SLA, and a then-current add-on list. The twelve-day hunt: list every incorporated URL, demand a named inbox, calendar the continued-use clock, and hunt a walk-right with a refund — not last year's click-Accept.

In September 2026, Nell — Ops at a 17-person UK SaaS — has Finance's yes on a £3,200-a-month session-replay vendor. Clause 12.4 lets the vendor update Policies by posting a URL and treats continued use as acceptance. No named inbox, no walk-right, no prepaid refund. The AE mailed Slack on 13 September: trust.vendor.com/legal changes on 1 October. The live AUP now forbids “automated extraction” — Support's nightly CSV. Legal says last year's click-Accept closed the file. Nell has twelve days of pressure, and the hidden risk is a login on 2 October.

Disclaimer: Checkory provides AI support, not legal advice. Consult a qualified lawyer for binding decisions.

What does posting rewrite — AUP, SLA, processing terms, or a price list?

List every live URL the packet — the signed files you will perform under — incorporates, and write what each page may rewrite. A posted update is not one tweak. Do list each URL. Do not treat last year's PDF as current.

Freeze the MSA — the master services agreement —, the order form, and every schedule that points at a live page. Circle AUP wording, SLA credits and window, DPA — data processing agreement — processing, and add-on price. PageCrawl treats data-use, new restrictions, and SLA credit math as review items. FTC Tech-at-FTC (13 February 2024) is other-paper colour for a quiet data-use rewrite — not a finding on Nell's CSV. If the fight is whether “automated extraction” should catch a Support export, that is an AUP-substance hunt.

For example, Nell now has four rewrites: an export ban, sole-remedy credits, a calendar-month SLA window, and a then-current add-on list. Do pin today's live page before 1 October overwrites it.

Four posted-URL rewrites: AUP, SLA credits, processing terms, add-on list
Four posted-URL rewrites: AUP, SLA credits, processing terms, add-on list

Typical mistake

Treating last year's click-Accept as the pause. That click closed last year's words.

Posted-URL paper versus a complete update path

CheckNell's paper (silent)Complete path
What the URL may rewriteAUP + SLA + then-current listEach incorporated URL listed
Who was toldAE Slack onlyNamed inbox or role
Continued useAcceptance after 1 OctoberClock calendared; use defined
Walk-right + refundSilent; Q4 prepaid sitsExit + prepaid refund
NOM headingTreated as a shieldDoes not stop a posted URL

Which inbox has to be told — a named address or a buried changelog?

Circle whether the paper names an inbox or a role for policy updates. An AE Slack ping and a Trust Centre changelog are not that inbox. Do write the named address or “inbox: none — AE Slack only.” Do not assume anyone had a duty to refresh the URL.

Ninth Circuit Stover v Experian Holdings, 978 F.3d 1082 (2020), repeating Douglas (2007), is US other-paper: parties have no duty to refresh terms periodically. A later website visit does not bind someone who was never told the words had moved.

In practice, even a mass email is fact-specific. Dentons on Ireland-Gordy (29 April 2026) notes a subject line, a bold link, a dated effective date, and stated continued-use assent — and still said mass email is not enough in every case. Nell's Slack thread is thinner. Ironclad: posting plus continued use frequently fails without adequate notice. If the fight is whether a formal email was deemed received, that is the notices-clause hunt — then leave.

Named inbox versus AE Slack and a buried changelog, inbox none
Named inbox versus AE Slack and a buried changelog, inbox none

When to treat continued use as deemed acceptance?

Write the effective date and what the paper calls use — any login, any API call, any nightly CSV. Continued use after that date is the vendor's clock, not a shrug. Do calendar 1 October. Do not keep clicking around “just to check” if the plan is to object.

Do not write that Nell is already bound or already free. TOSLawyer (8 July 2026) is vendor-side colour: continued-use assent is the weaker path for material changes. A later click-Accept is a fresh decision, not a cleanup of last year. If you have no MSA yet and the fight is the first website Accept, that is a first-time Accept checklist — a different hunt.

Continued-use clock, silent walk-right, and prepaid refund path
Continued-use clock, silent walk-right, and prepaid refund path

Twelve-day posted-policy hunt

1

Freeze the packet and the live URLs

MSA + order form + every URL schedule. Paste the posted-policy sentence. Save today's live page.

2

List what posting may rewrite

AUP, SLA credits, DPA processing, then-current add-on price. Four rewrites, not one tweak.

3

Name who was actually told

Circle a named inbox or role. Else write “inbox: none — AE Slack only.”

4

Calendar the continued-use clock

Write the effective date and what counts as use. Do not decide anyone is already bound.

5

Hunt a walk-right and a prepaid refund

Circle exit + refund. Else write “walk-right: silent” and ask before the date.

6

Pick freeze, notice-plus-exit, or walk

Pin the old URL, object in writing, or treat the date as a commercial go/no-go.

What does a silent material-change walk-right do to the prepaid refund?

Hunt a terminate-for-material-change, a reject-and-exit, and a prepaid refund. Renewal months away is not that right. Do circle the walk-right or write “walk-right: silent.” Do not treat Q4 fees already paid as gone.

The ABA SaaS note (2021) is US practitioner structure: if they can change the paper unilaterally, insist on a no-charge exit where the change hits what you bought. Law Insider specimens show a named trigger and a notice period — not a verdict on Nell.

CMA GOV.UK Writing a fair contract (22 July 2026) is trader–consumer structure — not Nell's B2B paper. A blank-cheque variation is unlikely to be fair there if paired with no genuine exit. Do not write that clause 12.4 is void. ReviewMyContract (2026): ask in writing for a penalty-free terminate if you reject. If the number is a named annual uplift on the order form, that is an order-form uplift hunt — then leave.

Why does a no-oral-modification heading not stop a posted URL?

A no-oral-modification clause polices informal changes — Slack, email, a course of dealing — by demanding signed writing. A posted-URL sentence treats use as the variation. Do not treat a NOM heading as a shield against a URL.

If the fight is Slack as price, a named variation role, or “in writing” versus “signed,” that is the signed-variation hunt. This hunt stops here: they posted a URL and started a continued-use clock. Do not retell Rock Advertising on this page.

How do you choose freeze, notice-plus-exit, or walk?

Spend the twelve days on one of three moves: freeze the old page, send a written objection that asks for a walk-right, or treat 1 October as a commercial go/no-go. Do pick a path. Do not send every URL to counsel — a qualified lawyer — with no packet.

Workflow: list posted URLs → named inbox notice → continued-use clock → walk-right + refund → not a NOM → freeze / notice+exit / walk. Freeze: pin the old URL — Webtingle is ops colour for a dated pin — do not click Accept “to be helpful.” Notice+exit: write to notices and the AE, name the deltas, ask for a pull or a signed variation with a walk-right plus prepaid refund, and state you do not accept by silence. Walk: if they refuse, treat 1 October as a commercial go/no-go.

Success bar: fill a one-page log — packet → live URLs → what posting can rewrite → named inbox or AE-only → continued-use clock → walk-right + refund or silence → freeze / notice+exit / walk — and point to one sentence that pauses “we already accepted last year.” Verify that a NOM heading does not stop a posted URL. Do not decide whether continued use already bound you. Escalate a prepaid-quarter fight to counsel.

Pause sentence

On Nell's paper the pause is “inbox: none — AE Slack only” plus “walk-right: silent.”

Flag posted-URL wording on the same file

A first-pass — the first machine pass that extracts clauses before a human reads every page — can highlight posted, URL, continued use, and material change. A High flag — a machine highlight on this file — still needs a human.

Start document analysis

Frequently asked questions

Does clicking Accept later count?
Treat a later click as a fresh decision, not a cleanup of last year.
Can they raise price via a posted list?
Circle whether a then-current add-on list is incorporated by URL. A named annual uplift on the order form is a different hunt.
How is this different from no-oral-modification?
A posted-policy update bypasses signed writing — that is this hunt. Slack-as-variation is a different guide.
Is a Trust Centre changelog notice?
Write “inbox: none” unless the paper names an inbox or role. A changelog is not directed notice.
Does last year's Accept close this file?
No. This is a mid-term posted update on a deal you already signed.
What if the AE mailed Slack instead of notices?
Write “inbox: none — AE Slack only.” Deemed receipt of a formal email is a different hunt.

What to do next

Sources

Related guides

Updated: September 13, 2026