Your vendor gave you notice.You just didn’t get it.
The contract you signed points at documents you did not negotiate: a data processing addendum, a subprocessor list, a security page. Most of them live on the vendor’s website. In many agreements, updating that page is the notice, so your window to object can open and close without anyone sending you a thing.
Marrowick will give Customerthirty (30)ten (10) days’ prior written notice before engaging any new Subprocessor. Noticewill be sent to the administrative contact on filemay be given by updating the Subprocessor List published at marrowick.example/subprocessors.
Material. The published notice period fell from thirty days to ten, and notice moved from an email to a page you would have to check. Whether that binds you depends on what you signed.
Illustration. Marrowick Cloud is invented, as is the clause.
A contract is a set of pointers
You negotiated the first document. The rest arrived by reference, and they are the ones that move.
Master Services Agreement
Data Processing Addendum
Subprocessor List
Technical and Organizational Measures
Security overview
Every step down is a document you are bound by and do not control. The last one is a web page with an edit button, and nobody on your side is watching it.
Marrowick publishes no version history for three of those five documents. Each hairline is a copy the vendor never kept, and an unbroken run of them is how you show what a document said on the day you relied on it.
It starts with the contract you signed
The clause at the top of this page looks like your window to object just shrank. Read against the agreement you actually signed, it didn’t. Hand it that agreement: it reads the references out of the document, fetches what each one points at right now, and shows where the live version has drifted from your paper.
MSA_Marrowick_2025-11-14.pdf
4 live documents, fetched just now
Drift since you signed
DPA §4.1 — Subprocessor notice
affects your rightsMarrowick will give Customer thirty (30) ten (10) days’ prior written notice before engaging any new Subprocessor.
Your MSA §8.3 fixes thirty days. Their change does not bind you — but it binds anyone signing their current paper, and you would not know either way without both documents side by side.
Preview, with the same invented vendor.
What arrives when something moves
Most of the time you will never open the product. So the alert carries the whole thing: what changed, what it does to your rights rather than to everyone’s, and the deadline it just started.
Marrowick Cloud added a subprocessor outside your transfer list
- Ostravine Mail, processing in Singapore, added to the subprocessor list on 11 Sep.
- Singapore is not in your Annex I. Your MSA §8.3 gives you thirty days to object.
- 11 Oct 2026 to object
Preview, with the same invented vendor.
What it will do
- It runs the clock for you
- A new subprocessor opens a window to object, and that window is set by your agreement rather than by the vendor's current one. It works out when the window opened, when it closes, and tells you before it does.
- It separates the material from the noise
- A single crawl turns up thousands of clause-level differences, and nearly all of them are reformatting, renumbering, or a lawyer moving a comma. You hear about the ones that move a number, a deadline, a liability cap, or a right you were relying on.
- It keeps the receipt
- Every version is stored hashed and timestamped. When an auditor or your own customer asks what a vendor had committed to last March, you can show them the page as it stood that day.
The whole week, in one view
Deadlines first, changes second, and only the few that are worth a person’s time.
Design preview, with invented vendors.