Acceptable Use PolicyLeraLink Team

Acceptable Use Policy

The rules for what may be published, sent and done on LeraLink, and what happens when they are broken.

Last updated: 12 November 2026

1. About this policy

LeraLink is a multilingual knowledge publishing platform 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. Company Information gives our full details. In this policy "we" and "us" mean SSStudio, or a successor entity to which SSStudio assigns its agreements with notice.

This policy sets out in detail the conduct rules of section 8 of the Terms of Service, and applies to everyone who uses LeraLink. For organisations that run an installation, it forms part of the Customer Agreement. Where this policy and those documents differ, the Customer Agreement prevails for customers and the Terms of Service prevail for everyone else, except where this policy is stricter about illegal content.

How we decide on reports and what you can do if you disagree with a decision is set out in the Content Moderation Policy.

2. Who this policy applies to

This policy applies to everyone who uses LeraLink, in any role:

RoleWho this is
CustomerAn organisation or person that has agreed to run an installation (its own knowledge site on a LeraLink address or its own domain).
Installation owner and administratorA person who manages an installation: its people, roles, settings, domains, newsletters and AI settings.
AuthorA person who writes, translates, cites, reviews, edits or publishes Pieces in an installation, including editors and reviewers in editorial review.
MemberA person with an account who has joined an installation, for example to comment, annotate, follow, register for an event or receive a newsletter.
ReaderAnyone who reads a public page of an installation, with or without an account.
API and integration userAnyone who reaches LeraLink by automated means, including scripts, feeds, integrations and any programming interface we make available.

A customer is responsible for the use of its installation by the people it admits, as set out in section 6.

3. Prohibited content

You must not publish, upload, store, translate, send or link to the following through LeraLink. This applies to every kind of content: text, images, audio, video, data, files, comments, annotations, profiles, newsletters, event pages and messages.

3.1 Illegal content

Content that is illegal under the law of the European Union or of the Netherlands, or under the law of the EU Member State where it is made available to readers, is not allowed. Under the Digital Services Act (Regulation (EU) 2022/2065, art. 3(h)), illegal content is any information that, in itself or in relation to an activity, does not comply with EU law or the law of a Member State.

The categories below are examples. They are not a complete list.

3.2 Child sexual abuse material

Child sexual abuse material is never allowed, in any form, including drawn, generated or altered images and text that sexualises children. We have zero tolerance:

  • We remove or disable access to it as soon as we become aware of it.
  • We terminate the accounts involved and, where a customer is involved, may suspend the installation.
  • We report it to the Dutch hotline (Expertisebureau Online Kindermisbruik) and to the police, and preserve what the law allows or requires us to preserve for the investigation.
  • We do not forward it to anyone else, including the person who reported it.

3.3 Terrorist content

Content that incites, solicits, threatens or instructs on the commission of terrorist offences, or that glorifies them, within the meaning of Regulation (EU) 2021/784 on terrorist content online and Directive (EU) 2017/541, is not allowed.

Material shown for educational, journalistic, artistic or research purposes, or to prevent or counter terrorism, is assessed in that context, as Regulation (EU) 2021/784 requires. Context must be clear from the publication itself.

3.4 Incitement and threats

Content that incites violence against a person or group, that threatens a person, or that calls for or organises criminal acts is not allowed. This includes threats under article 285 of the Dutch Criminal Code (Wetboek van Strafrecht).

3.5 Unlawful hate speech

Content that is unlawful hate speech is not allowed. This includes public incitement to hatred, discrimination or violence, and insulting a group of people, on the grounds of race, religion or belief, sex, sexual orientation, disability or another protected characteristic, within the meaning of articles 137c to 137e of the Dutch Criminal Code and Council Framework Decision 2008/913/JHA.

Reporting on, quoting, analysing or criticising such speech for research, journalism, education or public debate is not in itself prohibited. The way it is presented must make that purpose clear.

3.6 Defamation

Content that unlawfully harms a person's honour or reputation is not allowed. This includes defamation and slander within the meaning of articles 261 and 262 of the Dutch Criminal Code, and statements that are unlawful under civil law (article 6:162 of the Dutch Civil Code). Accurate reporting and well-founded criticism, including of public figures and institutions, is not defamation.

3.7 Infringement of intellectual property

Content that infringes copyright, related rights, database rights, trademarks or other intellectual property is not allowed. Use that the law permits, such as quotation (article 15a of the Dutch Copyright Act, Auteurswet) or use with the rights holder's licence, is allowed. Authors are responsible for recording the rights and sources of what they publish.

3.8 Unlawful disclosure of personal data

You must not publish or send another person's personal data without a lawful basis. In particular:

  • Doxing is not allowed: collecting or sharing someone's personal data to intimidate them, or to cause or enable others to cause them serious harm (see article 285d of the Dutch Criminal Code).
  • Sharing images or recordings of a sexual nature of a person without their consent is not allowed.
  • Publishing special categories of personal data (such as health, religion, political opinion or sexual orientation) or criminal-law data about a person is allowed only where the GDPR (articles 9 and 10) and the Dutch GDPR Implementation Act (Uitvoeringswet AVG) permit it, for example for journalistic, academic, artistic or literary purposes within the limits of article 43 of that Act.

3.9 Malware and harmful files

Files or links that contain or deliver malware, ransomware, spyware, phishing pages, exploit code aimed at systems you are not authorised to test, or anything else designed to damage, take over or gain unauthorised access to a device or system are not allowed. Security research shared for defensive purposes is allowed where it does not provide a working attack on an unpatched system.

4. Prohibited conduct

You must not:

  1. Gain or attempt unauthorised access. Do not access, or try to access, accounts, installations, restricted Pieces, administration surfaces or data that you have not been given access to. Do not use another person's sign-in code, session or passkey.
  2. Test security outside the Coordinated Vulnerability Disclosure. Security testing is allowed only within the rules of our Coordinated Vulnerability Disclosure. Testing outside those rules, including denial-of-service testing, social engineering and testing other people's installations or data, is not allowed.
  3. Scrape or collect at scale. Do not collect content or personal data from LeraLink by automated means beyond what the installation's robots instructions and our rate limits allow, unless you have written permission. Search engines that follow those instructions are welcome. Text and data mining is subject to any reservation of rights stated in the licence or rights information of a work.
  4. Overload or disrupt the service. Do not send traffic or requests that place an unreasonable load on the service, interfere with other users, or bypass rate limits, caches or access controls.
  5. Circumvent AI policies or restrictions. Do not try to make content reach an AI model that the installation's AI policy, a restriction on a Piece, or a disabled feature keeps away from it. Do not try to change the instructions the platform gives to its AI services, or to make an AI service produce output it is designed not to produce. Do not remove or hide the label that marks AI output as machine-made.
  6. Send spam through newsletters or messages. The platform sends an installation's newsletter only to its members and subscribers. Members receive it by default and can switch it off at any time in their settings or with the link in every message; the platform adds a working unsubscribe link to every issue. Do not add people to a newsletter by any other means, and do not remove or hide the unsubscribe link. Do not use contact forms, invitations, comments or event pages to send unsolicited commercial messages.
  7. Impersonate others. Do not pretend to be another person or organisation, or suggest an affiliation, endorsement or authorship that does not exist. Do not claim a credit on a work you did not contribute to. Parody and satire are allowed where they are clearly recognisable as such.
  8. Misuse the report mechanism. Do not submit reports you know to be unfounded, submit reports in bulk to silence someone, or use reports to harass a person. See the Content Moderation Policy for how we deal with manifestly unfounded notices.
  9. Harass or intimidate. Do not engage in targeted, repeated conduct meant to intimidate, threaten or silence a person, including through comments, annotations, reviews or messages.
  10. Evade enforcement. Do not create new accounts or installations to continue conduct for which an account or installation was restricted.
  11. Break editorial confidentiality. Do not reveal the identity of reviewers in a blind review, or share manuscripts, reviews or editorial notes you received in confidence, unless the venue's rules or the law allow it.

5. Special rules for AI features

LeraLink offers a fixed set of AI-assisted features: translation, suggested search-engine (SEO) fields, a generated feature image, the search index, a description of the concepts and people that published text is about, and, where it is enabled for an installation, a composition assistant that makes proposals only. How these work is explained in How LeraLink Uses AI.

When you use them:

  • No prohibited content. Do not use any AI feature to produce content that this policy prohibits, including through the instructions an installation writes for translation, images or SEO.
  • No identification of people from images. Do not use any feature to identify, recognise or profile a person from an image, a recording or their voice. LeraLink does not offer face recognition or biometric identification, and you must not try to make any feature do so.
  • No deceptive images of real people. Do not generate images that falsely show a real, identifiable person saying or doing something, or that could be mistaken for authentic documentation of a real event.
  • Review before you accept. AI output is a proposal until a person accepts it. Machine translations can be shown to readers before a person has reviewed them; they are then labelled 'AI translation · Not yet human-reviewed'. When you accept a translation, an SEO field or an image, you are responsible for it as if you had written or chosen it yourself.
  • Respect the installation's AI policy. An installation may have a stricter AI policy (for example, EU only or no external AI). Authors must not move content outside the installation to process it with models the policy excludes, and then bring the output back as if the policy had been followed.

Restricted Pieces are never sent to any AI model, whatever you do.

6. Customers and installation owners

6.1 Your responsibilities for your community

A customer decides who may join its installation, what they may do there and what is published. The customer must:

  1. Set and publish its own rules for its community where it needs more than this policy. Those rules may be stricter than this policy, but may not permit what this policy prohibits.
  2. Act on reports about content in its installation in a timely and careful way, and tell us without delay about content that is manifestly illegal or that threatens anyone's life or safety.
  3. Publish a privacy statement for its members and readers. The Installation Privacy Statement Template can be used for this.
  4. Have a lawful basis for the personal data it collects and publishes, including member lists, event registrations and newsletters.
  5. Have a lawful basis for the newsletters and publication emails it sends, and honour unsubscribe requests (the platform does this automatically).
  6. Grant administrative roles only to people who need them, remove them when no longer needed, and protect administrator access. We recommend that administrators use a passkey, and that installations require one where offered.
  7. Make sure that content uploaded by its people does not infringe the rights of others.
  8. Respond to our requests about content or conduct in its installation within the time we reasonably set.

6.2 Our role

We do not review content before it is published and we are not under a general obligation to monitor it. We act when we receive a notice or otherwise become aware of content or conduct that may break the law or this policy. We may act directly in any installation where the law requires it or where the matter is urgent, as described in the Content Moderation Policy.

7. Enforcement

We apply measures that are proportionate to the seriousness of the breach, its consequences, whether it was intentional, and whether it has happened before. A person decides each measure. The automatic safeguards against sign-up attacks described in the Content Moderation Policy can hold new memberships until a person approves them; they never remove content or close an account. Every measure that restricts content or an account comes with a statement of reasons, as the Content Moderation Policy describes.

StepMeasureWhen it is typically used
1Notice or warning, with a request to correctA first, minor breach, or a breach that the person can easily put right.
2Action on specific content: removal, disabling access, or restricting its visibility (for example to members only)Content that is illegal or breaks this policy.
3Restriction of features: for example the ability to comment, send newsletters, invite people or use AI featuresRepeated breaches, or misuse of a particular feature.
4Temporary suspension of an account or of an administrator's accessSerious or repeated breaches after a warning.
5Termination of an accountVery serious breaches, or repeated breaches after suspension.
6Suspension or termination of an installation, under the Customer AgreementA customer that does not address serious breaches in its installation, or that uses its installation for a prohibited purpose.

We may skip steps and act immediately where:

  • the content is child sexual abuse material or terrorist content;
  • there is a threat to anyone's life or safety;
  • an attack on the service or on other users is under way;
  • a court or competent authority orders it; or
  • waiting would cause serious harm that cannot be undone.

Before we suspend or terminate an installation, we give the customer notice and a reasonable opportunity to remedy the breach, unless one of the situations above applies. Where we suspend an installation, the customer keeps the right to export its data as described in the Data Export and Exit Policy, except for the content that is illegal.

8. How to report

What you want to reportWhere
Content you believe is illegalEmail legal@lera.link with the subject line Content report, as described in Report Content
Content or conduct that breaks this policyEmail legal@lera.link with the subject line Content report
A margin note in an installationSigned-in members: the report option next to it, which goes to the installation's team; or Report Content, which goes to us
A security vulnerabilitysecurity@lera.link, following the Coordinated Vulnerability Disclosure
An order or request from an authoritylegal@lera.link

A report about illegal content should include the exact web address of the content, an explanation of why you believe it is illegal, your name and email address, and a statement that you make the report in good faith. You do not need to give your name or email address when you report child sexual abuse material.

If someone's life or safety is in immediate danger, contact the emergency services (112 in the European Union) first.

9. Changes to this policy

We announce changes to this policy as set out in the Change Notification Policy. Earlier versions of this policy are available on request.

10. Contact

Questions about this policy and reports: legal@lera.link.