Change notices

What is notified, and how far ahead

Change	Notice	How
A new or replaced sub-processor	30 days by default, before it starts processing your data; the period is one of your commercial terms	Email to your billing contact; the Sub-processors page’s date changes. You may object within the period
A new version of the master services agreement or the data processing agreement	Shown until accepted	LightHouse lists it as pending (Spend → Terms, and the setup mission’s billing step) until your administrator accepts it. Nothing is slipped in, and acceptance is recorded
A change to your commercial terms	As your agreement says	Requested and answered in Spend → Terms, and recorded on your tenant
A new release of LightHouse or the engine	On release	The Changelog, and these docs, versioned per release
A new revision of the telemetry contract	On release	Each revision so far has been additive: everything valid under the previous one stays valid. Your deployment sends a new revision’s records only once you set it to, after LightHouse accepts it
A change to infrastructure in your account	Never without you	LightHouse never applies infrastructure. A new stack is a file your own pipeline applies as a reviewed change, pinned to a release tag

Subscribing

Today, notices reach the billing contact on your tenant by email, and appear in LightHouse where noted above. Keep your billing contact current in Spend → Billing and payments.

• A notice centre in LightHouse for sub-processor and service changes: Coming
• A feed of this site’s changelog to subscribe to: Coming