Terms & Conditions / Policy Change Monitoring (v1)
When Did Your Vendor Last Change Its Terms?
Terms change without a version number. A processor adds a subprocessor, a platform rewrites its acceptable use policy, a supplier trims the service credit, and the notice either never arrives or arrives as "we have updated our terms." ChangeTower watches every agreement and policy page you are bound by, reads each change, and tells your team which clause moved and what it now says. Every check stores a dated snapshot, so "what did these terms say when we signed" always has an answer.
✓ No credit card · First monitor live in 5 minutes
Every page here is under a monitor. ChangeTower checks it on the schedule you set, stores a dated snapshot on every check, and summarizes what changed in plain language.
This is the screenshot ChangeTower stored on that check: the page exactly as a visitor saw it, kept alongside the HTML and never edited afterwards.
Detection is content-level. ChangeTower reads the words and the HTML. The screenshot is kept as the visual record of the page, not compared against anything.
Every agreement you are bound by and every policy page you publish, in one place. Open a row to see which clause moved and the page exactly as it looked that day.
Tell it which clauses matter. It archives the rest.
A terms page changes for a hundred reasons, and most of them are a reformatted heading or a new office address. Describe what you actually care about in plain language, and only those changes reach anyone.
Written in your words, not in selectors.
You do not have to know which part of the page holds the liability cap. Write the rule the way you would say it to a colleague: liability, indemnity, termination, fees, data processing, subprocessors. Every change is read and classified against it before anything is sent, and the ones that do not match are still captured and archived, they just stay out of the channel.
Two of these three changes never reached the channel. All three are in the archive.
Vendor terms, supplier agreements, your own policies. Each in its folder.
Monitors are organized into folders that mirror how the work is actually split: by vendor, by entity, by client. Your monitors grow with the vendor list without turning into a pile.
Sorted the way your team is.
Legal owns the vendor terms, procurement owns the supplier agreements, and whoever ships the website owns your own policy pages. Folders keep the sources grouped by who acts on them, and each folder's alerts go to that team's channel: a subprocessor addition reaches privacy, a fee schedule reaches procurement.
Vendor terms, supplier agreements and your own policy pages, each in its own folder. Outsourced legal teams keep one per client, with the archives kept apart.
"When did that clause change?" is a lookup now, not an investigation.
Snapshots are stored on every check, whether the page changed or not. The agreements you operate under become a record you can open to any date.
The version history your contract file wishes it had.
Online terms are amended by republishing a page. There is no version number, no redline and often no notice worth the name. A dated snapshot of every check is what turns "we believe the cap was 12 months when we signed" into something you can put in front of the vendor.
Everything that happens after a clause changes.
One vendor rewriting its terms, followed from the first alert to the record you take into the renewal call.
Did Northgate ever tell us what actually changed in their new terms? Renewal call is Thursday and I would like to know before we sign.
Every monitored page captured on the 03:00 check.
AI summary: The liability cap fell from 12 months of fees to 3 months, and the notice period for future changes shortened from 30 days to 14 days. Effective 01 Aug 2026.
Routed to the channel your team already works in. Email, Microsoft Teams and webhooks carry the same alert.
Northgate Cloud revised its Terms of Service, effective 01 Aug 2026. The limitation of liability cap fell from 12 months of fees paid to 3 months, and the notice period for future changes shortened from 30 days to 14 days.
9. Limitation of liability. Northgate total liability under this agreement is capped at the fees paid by the customer in the preceding 3 months.
14. Changes to these Terms. Northgate will notify customers at least 14 days before any material change takes effect. Continued use after that date constitutes acceptance.
| Term | Value |
|---|---|
| Liability cap | 3 months of fees |
| Notice of change | 14 days |
| Governing law | Delaware |
The screenshot stored on that check: the page exactly as a visitor saw it, kept with its HTML.
Every day in between has a snapshot too, changed or not. That is what lets you answer what the terms said on the day you signed.
Every version of this vendor's terms since you signed, page by page and dated, ready for the renewal call or the file.
Reading a vendor's terms in a tab? Put them under watch from right there.
Vendor review does not happen in a dashboard. It happens in a legal hub, three clicks from a pricing page, at the end of a security questionnaire. The ChangeTower browser extension turns the page you are reading into a monitor.
From open tab to watched agreement, in one click.
You are working through a new vendor's legal hub before signing. Click the icon, say which clauses you want to hear about in plain language, and the page joins the rest of your monitors with its first snapshot stored on the next check.
These terms govern access to the Tessellate platform and to any services ordered under an order form referencing them.
11. Termination. Either party may terminate this agreement on 30 days written notice. Fees paid in advance are not refundable.
16. Data retention. Customer data is deleted within 60 days of termination unless a longer period is required by law.
The data processing agreement and the acceptable use policy form part of these terms and are published separately.
Tessellate may update these terms by publishing a revised version to this page. The version number and the date above change with it.
Found during the vendor review, monitored before the tab closes. The agreement joins your monitors, archived from its next check.
Plus an in-app activity stream: everything recently captured, and everything that changed, in one place.
Purpose-built for the pages your obligations actually live on.
An agreement is rarely one document any more. It is a terms page, a policy that page incorporates by reference, a schedule of fees, and a list of subprocessors, each republished on its own schedule. Check frequency is set per page to match.
Vendor Terms of Service
The master terms most software and platform relationships actually run on, watched clause by clause.
dailyData Processing Agreements
Processing terms, transfer mechanisms and the annexes they point at.
dailySubprocessor Lists
Additions, removals and location changes on the lists your DPA obliges you to review.
dailyPrivacy & Cookie Policies
What a vendor says it collects, why, and how long it keeps it.
dailyFee Schedules & Pricing Terms
Rate cards, assessments and pass-through charges published outside the contract itself.
dailyService Levels & Support Terms
Commitments, credit caps, claim windows and support hours, all amendable by republishing a page.
weeklyAcceptable Use & Platform Policies
The rules your product has to keep meeting to stay on someone else's platform.
weeklySupplier & Reseller Terms
Terms of supply, partner program rules and channel agreements across the supplier list.
weeklyYour Own Policy Pages
Your published terms, privacy policy and cookie notice, checked after every deploy and CMS edit.
hourly – dailyWhere legal and procurement teams put ChangeTower to work.
Renewal and renegotiation, with the record in hand
Walk into the renewal knowing every change the vendor made since you signed, in order, with the dates. A liability cap that quietly halved and a notice period that shrank are leverage, but only if you can show when they moved.
Subprocessor and DPA changes into the privacy review
Your DPA gives you a window to object to a new subprocessor, and it starts whether or not the notification email reached the right inbox. The addition reaches privacy the morning it appears on the list.
Your own policy pages, verified after every deploy
A template change drops the cookie preferences link. A deploy republishes the effective date on terms nobody edited. Watch your own published policies and hear about it the next morning, not from a complaint.
What the terms said on the day you signed
Online terms are amended by replacing a page, so the version you agreed to can simply stop existing. A timestamped snapshot of every check is the record that answers the question later, exported as a PDF or spreadsheet report.
For terms and policy monitoring, here's what we recommend turning on.
These are the capabilities legal and procurement teams lean on hardest.
AI Monitoring
Alert rules in your own words: "liability, indemnity, termination and fees, not formatting." Every change summarized in plain language.
Explore →Selective Monitoring
Watch just the clause, the fee table or the subprocessor list, and ignore the marketing banner and cookie bar around it.
Explore →Content Monitoring
Track the exact wording that carries the obligation: caps, notice periods, effective dates and clause numbers, at the content and HTML level.
Explore →Scheduled Checks
Set frequency per page: daily across the vendor list, weekly on the quiet ones, and as often as every 5 minutes on a page you are actively watching.
Explore →Bulk Setup
Import the whole vendor list in one pass. Every terms, DPA and subprocessor page in the register goes under monitoring in an afternoon.
Explore →Password-Protected Pages
Plenty of terms only exist inside a customer portal or a partner dashboard. Those pages can be monitored too, with credentials stored securely.
Explore →Questions legal and procurement teams ask first.
What exactly is a snapshot?
A dated capture of a page: the rendered page and the HTML behind it, stored every time a scheduled check runs, whether the page changed or not. Each one carries a precise timestamp and stays retrievable. That is what turns "I am fairly sure the cap used to be 12 months" into a record you can open and send.
Is this only for software vendors?
No. Software terms are the most common starting point, but teams watch the same way across suppliers and logistics partners, payment and banking providers, marketplaces and platforms whose policies their product depends on, resellers and channel partners, insurers and landlords, and their own published policies. If the terms live on a page reachable by a URL, a monitor can watch them.
Our vendors email us when their terms change. Where does this fit?
Those emails go to whoever signed up, which is often one person who has since changed roles, and they arrive when the vendor decides a change is worth announcing. Plenty of edits never generate one. ChangeTower watches the page itself, so you see every change on your own schedule, you decide what counts as material rather than the vendor deciding for you, and you keep a dated record of the wording either way. Most teams keep the emails and let your monitors be the thing they actually rely on.
Will I drown in alerts?
No, and that is the point of the AI layer. Describe what matters in plain language, such as "alert me when a liability, indemnity, termination, fee or data processing clause changes, ignore formatting and contact details", and every change is read and classified before anything reaches a channel. The rest is archived without an alert, so the record stays complete while the channel stays quiet.
How often are the pages checked?
As often as each page needs. Check frequency is set per monitor, so the terms of a vendor you are mid-negotiation with can be checked far more often than a supplier policy that moves once a year. Tune the cadence any time: many teams turn it up around a renewal or a migration, then back down afterwards.
Can it watch terms that sit behind a login?
Yes. A monitor can sign in before it checks a page, with the credentials stored securely, so terms and rate cards that only exist inside a customer portal, a partner dashboard or a member area are captured and archived the same way public pages are.
Can different alerts go to different teams?
Yes. Alerts route by folder: vendor terms to the legal channel, fee schedules to procurement, subprocessor lists to whoever owns privacy. Slack, Microsoft Teams, email and webhooks carry the same alert, so each team gets changes where they already work, and the in-app activity stream keeps the whole picture in one place.
Can you tell us when something disappears, not just when it changes?
Yes, and on policy pages it is often the sharper signal. Tell ChangeTower which elements or terms should be present, and it alerts you when one goes missing from a monitored page: a cookie preferences link dropped by a template change, a required disclosure removed from your own privacy policy, a clause quietly deleted rather than rewritten.
Stop finding out about clause changes at renewal.
Put every agreement and policy page you are bound by under a monitor, and have a dated record of the wording from this point forward. First monitor live in under five minutes.