Change Notification Policy
How and when SSStudio tells customers and users about changes to LeraLink's documents, suppliers, features and service.
Last updated: 12 November 2026
1. About this policy
This policy is provided by SSStudio, The Hague, the Netherlands, trading as LeraLink, registered with the Dutch Chamber of Commerce (KvK) under number 98779885, VAT identification number (BTW-ID) NL005352396B67. Postal address on request: legal@lera.link. It sets out how much notice we give before a change, through which channels, and what you can do if you do not agree with a change. It applies to customers that run an installation and, where stated, to every person with a LeraLink account.
Where the Customer Agreement, the Data Processing Agreement or the Service Level Agreement sets a longer notice period or a stronger right, that document prevails.
2. Notice periods
| What changes | Notice | Your options |
|---|---|---|
| Terms of Service, Privacy Statement, Customer Agreement, Data Processing Agreement, Service Level Agreement and the other documents in the Legal project, where the change affects your rights or obligations | At least 30 days before the change takes effect | Object, or end the agreement or close your account before the change takes effect (section 5). |
| The same documents, where the change is required by law, by an order of an authority, or to address a security risk | As much notice as the situation allows; this can mean that the change takes effect immediately | We explain why the change could not wait. Your right to end the agreement remains. |
| The same documents, where the change does not affect anyone's rights (for example a correction of a typing error, a new contact address, clearer wording with the same meaning) | Published with a new date; no advance notice | None needed. |
| Subprocessors (new or replaced) | At least 30 days before the subprocessor starts processing personal data | Object under the Data Processing Agreement (section 4). |
| Material reduction of a paid feature | At least 30 days | End the agreement before the change takes effect, with a refund of fees paid in advance for the period after termination. |
| AI providers and models in the default chains, where a new provider receives personal data | At least 30 days, as a subprocessor change | Object under the Data Processing Agreement, or ask for a stricter AI policy for the installation. |
| The definition of an installation AI policy (Standard, EU only, Open models only, No external AI), where the change reduces the protection it gives | At least 30 days | Object, ask for another AI policy, or end the agreement. |
| A change that only increases protection (for example a stricter AI rule, a shorter retention period, a stronger security measure) | Announced when it takes effect | None needed. |
| Fees | As the Customer Agreement sets out (clause 13.6): from the start of a renewal, with written notice before it | Give notice that you will not renew. |
| Planned maintenance with expected downtime or read-only time | At least 48 hours | Plan around it. |
| Emergency maintenance | As soon as possible, at the latest when it starts | We explain the reason afterwards. |
| Security incidents and personal data breaches | As set out in Incident Response and Notification and in the Data Processing Agreement | As set out in those documents. |
3. Channels
| Channel | Used for |
|---|---|
| Email to installation owners | Every change that requires advance notice and affects customers, and planned maintenance. Sent to the owners of each installation and to the contact addresses in the Customer Agreement. |
| Account holders | Changes to the Terms of Service or the Privacy Statement that affect people's rights: announced in the Updates project on hub.lera.link and in a notice on LeraLink's sites. |
| Announcements in the Updates project on hub.lera.link | Every change that requires advance notice, including the Policy Change Notice and the Subprocessor Change Notice, and planned maintenance. |
| Release Notes in Updates | New, changed and removed features. |
| A notice on LeraLink's sites | Planned maintenance and read-only periods, shown in advance and while they last. |
| status.lera.link | Incidents affecting availability of the platform. |
| Previous versions | Every previous version of every legal document is kept unchanged and is available on request. |
Emails about changes are service messages. They are sent to all affected installation owners, including those who have switched off newsletters.
4. Subprocessor changes
We keep the current list of subprocessors in Subprocessors and Recipients. When we intend to add or replace a subprocessor:
- We publish a Subprocessor Change Notice in Updates → Announcements and email installation owners and the privacy contact named in the Order Form at least 30 days before the subprocessor starts processing personal data. The notice says who the subprocessor is, what it will do, which personal data it will process, where, and with which transfer safeguard.
- A customer may object on reasonable grounds related to data protection within that 30-day period, by writing to privacy@lera.link.
- Within 14 days we try to find a solution with the customer, for example by not using the subprocessor for that installation, a stricter AI policy, or switching off the AI feature concerned. If no solution is possible or acceptable, the customer may end the affected service as the Data Processing Agreement provides, without a fee for early termination and with a refund of fees paid in advance for the period after termination.
In an emergency, where a subprocessor must be replaced at short notice because it can no longer provide its service securely or lawfully, we may make the change with shorter notice. We then tell customers as soon as possible why, and the right to object applies from that moment.
5. If you do not agree with a change
- Customers may end the Customer Agreement before a change that materially and adversely affects them takes effect, as the Customer Agreement sets out (clause 20.2). Fees paid in advance for the period after termination are refunded. A change to the Customer Agreement, the Service Level Agreement, the Acceptable Use Policy or the Terms of Service that is adverse to a customer applies to a running subscription term only from its next renewal, unless it is required by law, by a court or an authority, or to address a security risk (clause 20.3). The Data Export and Exit Policy applies.
- Account holders may close their account before the change takes effect with Delete my account everywhere. They can first download their data with Download my data.
- If you continue to use LeraLink after a change takes effect, the new version applies to you from that date. A change does not apply to events that took place before it took effect.
6. What counts as material
A change is material, and needs 30 days' notice, if it:
- reduces a right, a protection or a commitment in a legal document, or adds an obligation for customers or users;
- changes where personal data is stored, or which parties receive it;
- changes the purposes for which we process personal data, or our legal basis for it;
- reduces an AI policy's protection, or allows AI to do something it did not do before;
- removes or materially reduces a paid feature, or reduces a service level; or
- shortens the notice periods, export rights or retrieval periods in the Data Export and Exit Policy.
A change of fees follows the Customer Agreement (clause 13.6).
A change is not material if it only corrects an error, clarifies wording without changing the meaning, updates contact details or company registration details, or increases protection. When in doubt, we treat a change as material.
7. Versions and the archive
- Every legal document states the date on which it was last updated.
- When a change alters the meaning of a document, the notice says what changed and why.
- Every previous version is kept unchanged, with the period in which it was in force, and is available on request.
- When a person creates an account, we record which version of the Terms of Service and the Privacy Statement they accepted, and when. A later version is not asked for again; it applies as section 5 describes.
8. Successor entity
SSStudio may transfer its agreements to a successor entity, for example a private limited company (BV) set up by its owner. We will give at least 30 days' notice of such a transfer, by email and in Announcements, and the transfer does not reduce anyone's rights. A customer with a reasonable objection to the successor may end its agreement as the Customer Agreement sets out (clause 1.2).
9. Contact
Questions about changes: legal@lera.link. Objections to subprocessors: privacy@lera.link.