Acceptable Use Policy (AUP)

Acceptable Use Policy (AUP/AUPA)

1. Introduction and Scope

In short — this policy applies to everyone who uses OpsCentre, and it is your responsibility to read and understand it.

This Acceptable Use Policy (the "Policy" or "AUP") governs your use of the OpsCentre Community Management System and all related websites, applications, application programming interfaces, and services (together, the "Service") provided by OpsCentre, a sole trader operating from Ground Floor, Gallery Building, 65–69 Dublin Road, Belfast, BT2 7HG ("we", "us", "our", or "OpsCentre").

This Policy forms part of, and is incorporated by reference into, the OpsCentre Terms of Service (the "Terms"). Capitalised terms not defined in this Policy have the meaning given to them in the Terms. Where this Policy conflicts with the Terms, the Terms prevail, save that this Policy prevails on the specific subject of acceptable use.

This Policy applies to every Platform User, including every Community Director, and to everyone who accesses or uses the Service through a community. If you are a Community Director, you are responsible for ensuring that everyone who accesses the Service through your community complies with this Policy, and a breach of this Policy by any of your administrators, staff, or members is treated as a breach by you.

It is your responsibility to read and make sure you understand this Policy before you use the Service. If anything is unclear, please ask us before proceeding — we would rather answer a question first. To the extent permitted by law, and without affecting your rights as a consumer, we are not responsible for any loss arising from your failure to read, or your misunderstanding of, this Policy where it has been made available to you and you have had the opportunity to seek clarification.

We may update this Policy from time to time, including to reflect changes in law or regulatory guidance. Where changes are material, we will give notice in accordance with the Terms. Your continued use of the Service after a change takes effect constitutes acceptance of the revised Policy.

2. Definitions

In short — what the key words in this policy mean.

In this Policy, the following terms have the meanings set out below. Other capitalised terms are defined in the Terms.

In this Policy, "you" means, depending on the context, the Platform User or Community Director using the Service. Obligations expressed generally apply to all Platform Users; obligations concerning the operation of a community apply to Community Directors.

3. Our Independence from Third Parties

In short — OpsCentre is not connected to, or endorsed by, the games, platforms, or real services it can be used to model.

OpsCentre is an independent product. We are not affiliated with, endorsed by, sponsored by, or otherwise connected to any of the following, and nothing in the Service should be taken to imply any such relationship:

• Cfx.re, FiveM, Rockstar Games, or Take-Two Interactive;
• Roblox Corporation;
• Discord Inc.;
• any police service, ambulance service, fire and rescue service, military body, or other emergency service, government department, or public authority, in any jurisdiction.

OpsCentre is a tool for the administration of fictional roleplay communities. References within the Service to real-world organisations, ranks, procedures, doctrine, or terminology are provided to support realistic roleplay only. They do not represent, and must not be presented as, the official systems, records, or endorsement of any real organisation.

4. General Principles

In short — use OpsCentre lawfully and in good faith; the detailed rules follow.

You must use the Service lawfully, responsibly, and in good faith. In summary, and without limiting the detailed rules that follow, you must not use the Service:

• to do anything that is unlawful, or that facilitates unlawful activity;
• to create, share, or facilitate access to Illegal Content;
• to harm, harass, endanger, or exploit any person, and in particular any child;
• to store or process the genuine personal data of real, identifiable individuals except as expressly permitted by this Policy;
• to compromise the security, integrity, or availability of the Service or any connected system;
• to build, operate, or distribute any unofficial Integration with the Service;
• to infringe the rights of any third party, including intellectual property and privacy rights;
• to breach the terms of any third-party platform that you connect to, or use alongside, the Service;
• to misrepresent the Service as the official system of any real organisation, or to bring OpsCentre into disrepute.

The prohibitions in this Policy are illustrative, not exhaustive. Conduct that is clearly contrary to the general principles above may be treated as a breach even if it is not specifically listed.

5. Prohibited Content

In short — the content that is never allowed — starting with anything that harms children.

You must not create, upload, store, transmit, display, or otherwise make available through the Service any Content that falls within the categories below.

5.1 Child protection — absolute prohibitions

• any child sexual abuse material (CSAM), or any Content that sexualises a person under the age of 18, in any form, whether real, fictional, drawn, rendered, or generated by artificial intelligence. This prohibition is absolute and admits no exception;
• any Content or conduct that constitutes, depicts, promotes, or facilitates the sexual exploitation, grooming, or endangerment of a child;
• any Content that encourages, assists, or provides instruction in the abuse or exploitation of a child.

We treat any matter falling within this section with the utmost seriousness. Where we identify, or are credibly notified of, such Content, we will act immediately under Section 22 and, where the law requires or permits, will preserve relevant data and report it to the relevant authorities, which may include the National Crime Agency or an equivalent body.

5.2 Priority illegal content

You must not use the Service in connection with any Content or activity that amounts to "priority illegal content" under the Online Safety Act 2023 or is otherwise a criminal offence. This includes, without limitation, Content connected with:

• terrorism, or the encouragement, preparation, or facilitation of terrorism;
• the supply, offer to supply, or arrangement to supply controlled drugs or psychoactive substances;
• the unlawful supply, offer, or possession of firearms, weapons, or other prohibited articles;
• human trafficking, modern slavery, or facilitating unlawful immigration;
• fraud, financial crime, or the facilitation of either;
• the encouragement or assistance of suicide, or the encouragement of serious self-harm;
• threats to kill, harassment, stalking, or the coordination of harassment against any person;
• the sharing, or threat to share, intimate images of a person without their consent;
• the sending of communications that are false, threatening, or grossly offensive with intent to cause harm.

5.3 Harmful and abusive content

• Content that incites, threatens, glorifies, or facilitates violence or serious harm against any person or group;
• hate speech, or Content that harasses, bullies, demeans, or discriminates against any person or group on the basis of a protected characteristic, including race, ethnicity, nationality, religion, sex, gender reassignment, sexual orientation, disability, or age;
• Content that discloses, or threatens to disclose, the genuine private or identifying information of any real person without their consent (doxxing), including real names, home or work addresses, telephone numbers, financial details, or workplace information;
• Content designed to harass, intimidate, or stalk any person, whether a Member, a member of our staff, or any third party.

5.4 Malicious and infringing content

• Content that contains or distributes malware, viruses, worms, ransomware, or any other harmful code;
• Content that infringes the copyright, trade mark, database right, or other intellectual property rights of any third party;
• Content that you do not have the lawful right to upload, store, or share.

6. Use of Real Personal Data

In short — OpsCentre is for fictional roleplay records, not a real-world database about real people.

This is a defining rule of the Service. OpsCentre is a platform for managing fictional roleplay records about fictional characters. It is not a database for compiling, storing, or processing genuine information about real, identifiable people, and it must never be used as one.

6.1 The general prohibition

You must not use the Service to create, store, or process records that purport to be roleplay but in fact contain the genuine personal data of a real, identifiable individual. By way of example, and without limitation, you must not:

• record a real person's actual home address, telephone number, vehicle registration, financial details, or other real-world identifying information within a roleplay record;
• compile intelligence, criminal-record-style entries, surveillance logs, or "warning markers" about a real, identifiable person under the guise of in-character records;
• use the Service to harass, monitor, profile, or build a dossier on any real individual, whether a Member, a rival, a public figure, or any other person;
• upload genuine official documents (for example, real police, medical, or government records) belonging to or concerning any real person.

The test is one of substance, not labelling. Marking a record as "roleplay" or "in-character" does not make it acceptable if it in fact contains the genuine personal data of a real person used for a real-world purpose.

6.2 Permitted operational data

This rule does not prevent the limited, ordinary processing of personal data that is genuinely necessary to operate a community. The following are permitted, provided they are handled in accordance with the Terms, our Privacy Policy, and the Data Processing Addendum, and provided you have a lawful basis to process them:

• identifiers necessarily received when a Member authenticates, such as a Discord user ID, username, or avatar obtained through Discord OAuth, or the equivalent identifiers from another supported login provider;
• a Member's own contact details where they are held for the legitimate administration of a community, such as account management, communication, or moderation;
• records of a Member's own conduct on, or interaction with, a community where these are kept for legitimate moderation, safety, or administrative purposes.

The distinguishing principle is this: it is acceptable to process the real data necessary to run the community itself; it is never acceptable to use the Service as a covert real-world intelligence or surveillance system about real people.

6.3 Responsibilities as data controller

Where a Community Director processes the personal data of Members or other End Users through the Service, the Community Director acts as the data controller and we act as their data processor. The Community Director is responsible for ensuring there is a lawful basis for that processing, for providing any required privacy information to End Users, and for complying with applicable data protection law, including the UK GDPR and the Data Protection Act 2018, and, where relevant, the EU GDPR. The respective obligations are set out in the Data Processing Addendum.

7. Protection of Children and Minimum Age

In short — no under-13s, and extra care where a community includes teenagers.

The Service is not intended for, and must not be made available to, any person under the age of 13. A Community Director must not knowingly permit any individual under the age of 13 to access or use the Service through their community, whether as an Administrator, Member, or End User. If you become aware that a person under 13 is using the Service, you must remove their access without delay and notify us through the Escalation Report.

Where a community admits Members who are between 13 and 18 years of age, the Community Director is responsible for ensuring that the community is operated in a manner appropriate to the presence of young people, that any required parental consents are obtained where the law requires them, and that no Content or conduct prohibited by Section 5 is directed at or involves those Members.

We reserve the right to suspend or terminate any community that we reasonably believe is permitting the use of the Service by children under 13, or that is failing to safeguard young people who use it.

Where we have reason to suspect that the name or date of birth held for an account is inaccurate, the TSI Team may require the account holder to re-verify that information before continuing to use the Service. A record is kept of both the information previously held and the information re-submitted. Where we establish that an account holder is under the age of 13, we will block the account's access and erase the personal data held on the account, retaining only irreversible keyed cryptographic hashes of the account's sign-in identifiers, used solely to prevent the same person from regaining access; no readable personal data is retained for that purpose. This processing is explained further in our Privacy Policy.

8. Online Safety and the Online Safety Act 2023

In short — we both have duties to keep illegal and harmful content off the platform.

We take our responsibilities under the Online Safety Act 2023 (the "OSA") and related online safety law seriously, and we expect every community to support us in meeting them. This section sets out how those responsibilities are shared.

8.1 Our commitments

We operate the Service in a manner intended to identify, mitigate, and manage the risk of the Service being used to share Illegal Content or content that is harmful to children. This includes maintaining clear terms of use, providing accessible reporting tools, removing Illegal Content where we become aware of it, and keeping appropriate records of our safety measures.

8.2 Your obligations

As a Community Director operating a community on the Service, you must:

• not use the Service to generate, share, or facilitate Illegal Content or content harmful to children;
• operate your community in a way that does not create a foreseeable risk of such content arising, having regard to the nature of your community and its membership;
• act promptly to remove or restrict such content within your community where it arises, and report it to us through the Escalation Report;
• co-operate with any reasonable request we make in connection with our online safety duties, including requests for information necessary for a risk assessment or a regulatory response;
• ensure that your own use of the Service complies with any online safety obligations that apply to you in your own right.

8.3 Regulatory co-operation

We may be required to provide information to, or take action at the direction of, Ofcom or another regulator or authority. Where this affects your community, we will act proportionately and, where lawful and practicable, will keep you informed. You must not obstruct our compliance with a legal or regulatory obligation.

9. No Unofficial Integrations, Addons, or Connections

In short — only we build connections to OpsCentre — you can suggest ideas, but not build your own.

OpsCentre is a closed platform. To protect the security and integrity of the Service and the data held within it, we are the only party permitted to build, publish, or operate Integrations with the Service. This is a deliberate security measure.

9.1 What is prohibited

You must not, and must not permit or assist any third party to:

• build, develop, publish, distribute, sell, or operate any unofficial Integration with the Service, including any addon, plugin, extension, bridge, bot, script, or connector that connects to, calls, extends, or interoperates with the Service or its APIs;
• reverse engineer, probe, or analyse the Service, its APIs, its data structures, or its internal interfaces in order to create or enable any such Integration;
• access the Service, or any API we provide, by automated means other than through functionality we expressly provide and authorise for that purpose;
• represent, advertise, or imply that any third-party product, tool, or service is compatible with, certified for, endorsed by, or connected to OpsCentre.

9.2 Official integrations

From time to time we may build and offer our own official Integrations, including integrations with FiveM and other platforms. Where we do, they are provided and supported by us, subject to the Terms, and are the only Integrations permitted to operate with the Service. The existence of an official Integration does not entitle you or any third party to build your own.

9.3 Suggesting an integration

We welcome suggestions. If you would find an Integration useful, you are encouraged to propose it to us through our support channels or the Escalation Report. We will consider proposals on their merits. Proposing an Integration does not give you any right to build it yourself, and we are under no obligation to develop any Integration that is suggested.

10. Compliance with Third-Party Platforms

In short — follow the rules of Cfx/FiveM, Discord, and Roblox when you use them with OpsCentre.

You may use the Service alongside third-party platforms. Where you do, you are responsible for ensuring that your use of the Service, and any officially provided Integration you choose to enable, is operated in compliance with that platform's terms. In particular:

10.1 Cfx.re and FiveM

Where you connect your FiveM server to the Service, whether through an official Integration we provide or otherwise, you are responsible for ensuring that your FiveM server and its configuration comply with the Cfx.re Terms of Service, the FiveM Platform Server List Rules, and all related Cfx.re policies, including any rules governing paid assets and monetisation. Our provision of an official FiveM Integration does not make us responsible for your server's compliance with Cfx.re's rules.

10.2 Discord

• comply with the Discord Terms of Service, Developer Terms of Service, and Developer Policy;
• not use the Service to scrape Discord, to store Discord data beyond what is necessary for an authorised integration to function, or to facilitate any use of Discord that Discord prohibits;
• ensure that any Discord connection you enable through the Service is properly authorised and configured.

10.3 Roblox

If you use the Service to administer a Roblox community, you must comply with the Roblox Terms of Use, Community Standards, and all related Roblox policies, paying particular attention to the rules protecting younger users. Consistent with Section 7, you must not use the Service to process the personal data of any Roblox user under the age of 13.

10.4 Our right to act on third-party compliance

Where we are made aware of, or otherwise identify, a breach by you of a third-party platform's terms, we reserve the right to investigate, to collect and preserve relevant evidence, and to lodge a report or case with that platform. We do this to maintain good relations and co-operation with the platforms our customers rely on. Such a breach may also constitute a breach of this Policy and result in enforcement action under Section 22.

11. Prohibited Conduct

In short — don't attack the Service's security, misuse accounts, or abuse the platform.

11.1 Security and integrity

• probe, scan, or test the vulnerability of the Service or any connected system, except as expressly permitted under the responsible disclosure terms in Section 20;
• breach, disable, circumvent, or interfere with any security, authentication, or access-control mechanism;
• access, or attempt to access, any account, data, or part of the Service that you are not authorised to access, including the data of another community;
• exploit, manipulate, or bypass the multi-tenant boundaries of the Service in order to view or affect another community's data;
• introduce any malware, or any code or mechanism intended to disrupt, degrade, or gain unauthorised access to the Service.

11.2 Access and accounts

• share your account credentials with any unauthorised person, or permit any unauthorised person to use your access;
• create an account on behalf of another person without their consent, or impersonate any person or organisation;
• create or use an account to evade a suspension, termination, blacklist, or other enforcement action;
• transfer or sell your account or community except as permitted by the Terms.
• have multiple accounts without express permission from us.

11.3 Misuse of the Service

• copy, reverse engineer, decompile, or disassemble any part of the Service, except to the extent this restriction is prohibited by applicable law;
• scrape, harvest, or systematically extract data from the Service except through functionality we expressly provide for that purpose;
• resell, sublicense, or commercially exploit the Service or access to it, except as expressly permitted by the Terms;
• use the Service to build, train, or benchmark a competing product or service.

12. Account Security

In short — keep your account secure — you're responsible for what happens under it.

You are responsible for the security of your account and for all activity that takes place under it. You must:

• keep your account credentials confidential and secure, and not share them with any unauthorised person;
• use any authentication or security features we make available, and follow good security practice;
• where you are a Community Director, ensure that each Administrator you authorise maintains the security of their own access;
• notify us without undue delay if you become aware of any unauthorised access to, or compromise of, your account, including through the Escalation Report.

To protect account security and to detect misuse of the Service, including attempts to evade enforcement action, each sign-in records the IP address and device (user-agent) information used, together with automated security indicators computed on our own systems — for example, whether the connection appears to originate from an anonymising service such as a VPN or the Tor network, from datacenter address space, or from a shared or rapidly changing address. These checks are carried out entirely on our own infrastructure; your IP address is not sent to any third-party service for this purpose. This information is visible only to a restricted group of senior Trust, Safety and Integrity staff and the Platform Director, and is explained further in our Privacy Policy.

We are not responsible for losses arising from your failure to keep your account secure, including misuse of the Service by a person who gains access through compromised or shared credentials.

13. Fair and Reasonable Use

In short — use the Service reasonably and don't overload or abuse it.

You must use the Service fairly and reasonably, and in a way that does not impair its operation for us or for other communities. In particular, you must not:

• place an excessive or disproportionate load on the Service, its infrastructure, or its supporting systems;
• make automated or high-volume requests beyond any limits we set, or circumvent any rate limit, quota, or technical restriction;
• use the Service in a way that degrades performance, availability, or stability for other communities;
• use the Service for any purpose other than the legitimate administration of a community.

Where we operate usage tiers or capacity limits, you must use the Service within the tier or limit applicable to your community, and must upgrade where your usage requires it. We may take enforcement or operational action where use is unfair, excessive, or abusive.

14. Your Content and Your Responsibilities

In short — you own and are responsible for your content; we just host it.

As between you and us, you and your Members own the Content you and they create through the Service. We do not claim ownership of your Content. You grant us only the limited rights necessary to host, store, process, transmit, back up, and display that Content for the purpose of providing the Service, and to comply with our legal and regulatory obligations.

You are responsible for your Content and, where you are a Community Director, for the conduct of your community. This includes ensuring that your Content is lawful, that you hold all rights necessary to use it, that it does not breach this Policy, and that it does not infringe the rights of any third party. We act as a host and processor of your Content; we are not its author and do not endorse it.

15. Content Moderation, Monitoring, and Removal

In short — we can remove content and, when investigating, access a community without notice.

15.1 Removal and restriction of Content

Separately from any action we may take against an account under Section 22, we may remove, disable, restrict, or render inaccessible any Content that we reasonably believe breaches this Policy, is unlawful, is harmful to any person, or exposes us or any third party to legal or reputational risk. We may do so with or without notice, depending on the circumstances and the seriousness of the matter.

15.2 Monitoring

We are not obliged to monitor Content or activity on the Service, and we do not pre-screen all Content. However, we reserve the right to monitor, review, and investigate Content and activity where we reasonably consider it necessary, including to operate the Service, to investigate a suspected breach, to protect any person, or to comply with our legal and regulatory obligations. We are not liable for Content that we have not reviewed, and the fact that we have the ability to monitor does not create a duty to do so.

15.3 Investigatory access

So that we can properly investigate suspected breaches of this Policy or the Terms, and protect users and the Service, we may access a community's data and systems within the Service without prior notice to that community. We will use this capability only for the legitimate purposes of investigating a suspected breach, protecting any person from harm, maintaining the security or integrity of the Service, or complying with a legal or regulatory obligation. Our lawful basis for this processing, and the safeguards that apply to it, are set out in our Privacy Policy and Data Processing Addendum.

16. Brand and Impersonation

In short — don't misuse our name or pretend to be us.

You must not misuse our name, branding, logos, or identity. In particular, you must not:

• impersonate OpsCentre, or hold yourself out as us or as authorised to act on our behalf;
• use our name, logo, or branding except as we expressly permit;
• operate, or assist in operating, any service that imitates OpsCentre or is presented so as to be confused with it;
• make any false or misleading statement about your relationship with OpsCentre.

17. Feedback

In short — if you suggest an idea, we can use it freely.

We welcome feedback, ideas, and suggestions, including suggestions for new features or Integrations. If you provide us with any feedback or suggestion, you agree that we may use it freely, for any purpose, without restriction and without any obligation to you. You do not acquire any right in the Service, or any right to payment or acknowledgement, by providing feedback or suggesting an idea, including where we later develop something similar.

18. Sanctions and Export Control

In short — don't use the Service in breach of sanctions or export laws.

You must not use the Service in breach of any applicable sanctions, export control, or trade restriction laws, and you must not access or use the Service from, or on behalf of any person or entity in, a territory or for a purpose that such laws prohibit. You confirm that you are not subject to any such restriction that would make your use of the Service unlawful.

19. Anti-Spam and Communications

In short — don't use the Service's messaging to spam or send unlawful messages.

Where the Service allows you or your Members to send messages, notifications, or other communications, you must not use that functionality to send unsolicited bulk communications, spam, phishing, or fraudulent messages, or any communication that is unlawful or breaches this Policy. You are responsible for ensuring that any communications you send through the Service comply with applicable law, including data protection and electronic-communications law.

20. Responsible Disclosure of Security Issues

In short — if you find a security flaw, report it responsibly and we won't pursue you for good-faith research.

We welcome the good-faith efforts of security researchers to help keep the Service safe. If you discover a security vulnerability, we ask that you disclose it to us responsibly, and we will not pursue enforcement action against you for good-faith research that complies with this Section.

Good-faith research means that you:

• act solely to identify and report a vulnerability, and not to exploit it for any other purpose;
• do not access, modify, delete, or exfiltrate any data belonging to us or to any other community beyond the minimum necessary to demonstrate the vulnerability;
• do not degrade, disrupt, or deny service to others, and do not use automated or high-volume testing that would do so;
• give us a reasonable opportunity to investigate and remediate before disclosing the issue to anyone else, and do not disclose it publicly without our agreement;
• comply with all applicable law at all times.

To report a vulnerability, contact us at [email protected]. Conduct that goes beyond good-faith research — including accessing other communities' data without need, or attempting to extract or sell data — is not protected by this Section and is a serious breach of this Policy.

21. Reporting and the Mandatory Escalation Report

In short — use the in-app report tool to tell us about serious or illegal content.

We provide a built-in reporting mechanism within the community administration area of the Service, known as the Mandatory Escalation Report. It is the primary route by which Administrators must report breaches of this Policy and online safety concerns to us.

21.1 When you must submit an Escalation Report

You must submit an Escalation Report without undue delay where you become aware of:

• any Illegal Content, or any content that is harmful to children, within your community or elsewhere on the Service;
• any breach, or suspected breach, of Section 5 (prohibited content), Section 6 (real personal data), or Section 7 (children) of this Policy;
• any matter that you are required to report under the Online Safety Act 2023 or other applicable law;
• any use of the Service by a person under the age of 13.

21.2 Other reporting routes

You may also report breaches by email to [email protected] or [email protected], and security vulnerabilities to [email protected]. Where the matter is urgent and concerns a risk to a person's safety, you should also contact the appropriate emergency services or authorities directly.

21.3 How we handle reports

The TSI Team assesses and acts on reports in accordance with this Policy and the Terms. We may not always be able to update you on the outcome of a report concerning another community, but we will act on credible reports, and we will preserve and, where required, disclose relevant data to the authorities.

22. Enforcement

In short — what we can do if the rules are broken — from a warning up to removal and reporting to the authorities.

22.1 Grounds for enforcement

We may take enforcement action where we reasonably consider it appropriate. The grounds on which we may act include, but are not limited to:

• to protect users, or any other person, from harm;
• to prevent, limit, or remove Illegal Content or content harmful to children;
• to protect the security, integrity, or availability of the Service;
• to comply with the law, or with a regulator, court, or authority;
• to protect the rights, property, or safety of OpsCentre, our customers, or any third party;
• to protect the reputation and integrity of the platform, including our relationships with the third-party platforms our customers rely on;
• to address any breach, or suspected breach, of this Policy or the Terms.

Enforcement action is at our discretion. We will normally act proportionately to the seriousness of the matter, but we are not required to apply the steps below in sequence, and we may take whatever action we reasonably consider appropriate in the circumstances.

22.2 Levels at which we may act

We may take enforcement action at any of the following levels, individually or in combination:

• Individual — against a specific Platform User, Administrator, or Member;
• Module — by restricting or disabling a specific Module within a community, such as the Records Management System, where that Module is being misused, while leaving the rest of the community operational;
• Community — against a community as a whole.

Because a Community Director is responsible for the conduct of their Administrators and Members, serious conduct by an individual (for example, conduct falling within Section 5.1) may, where we consider it appropriate, result in enforcement action against the wider community as well as the individual.

22.3 The sanctions ladder

Our standard graduated sanctions, administered by the TSI Team, are:

Module restriction (Section 22.2) may be applied on its own or alongside any tier above, as a proportionate response to the misuse of a particular Module.

22.4 Authority to act

Verbal and Written warnings may be issued by TSI Team staff. Final Written warnings, suspensions, and terminations require authorisation at TSI Team management level or above. Where a relevant role is unfilled, authority defaults upward, ultimately to the Platform Director. Certain actions are reserved to the Platform Director, as set out below.

22.5 Aggregation

We may treat a series of minor breaches cumulatively. Repeated low-level breaches, taken together, may be treated as a more serious matter and escalated accordingly.

22.6 Summary action

For serious breaches, we may suspend or terminate access immediately and without prior warning, bypassing the sanctions ladder. Serious breaches include, but are not limited to, those listed in Section 22.7, deliberate attempts to breach the security of the Service or access another community's data, building or operating an unofficial Integration, and any conduct that exposes us, our customers, or any third party to serious legal or safety risk.

22.7 Mandatory action — illegal content and child safety

Illegal Content of any description, and any breach of the child-protection prohibitions in Section 5.1, may result in immediate termination of access. In these cases we will, where the law requires or permits, preserve relevant data and report the matter to the police, the National Crime Agency, or another relevant authority. Matters falling within this Section are not subject to the sanctions ladder, the appeal process, or any consideration of reinstatement.

22.8 Blacklisting

In addition to the sanctions above, we operate a blacklist. Blacklisting permanently bans an individual from accessing any OpsCentre service, including by creating or using any future account. Blacklisting may be issued only by the Platform Director, and may be applied under the grounds in Section 22.1, including for any reason we reasonably consider appropriate to protect users, the Service, or the platform.

22.9 Interim suspension pending investigation

Where we are investigating a suspected breach, we may suspend or restrict access on an interim basis as a holding measure, before deciding what, if any, further action to take. An interim suspension is precautionary and is not a finding of breach.

22.10 Warning expiry and rescission

Warnings do not necessarily remain in force indefinitely. A warning may expire, or be rescinded, at the discretion of our management, having regard to your subsequent conduct. We are not obliged to rescind any warning.

22.11 Notification

Where we take enforcement action against you, we will notify you through an in-app notification, and, where appropriate, by email from the TSI Team. Our notification will tell you the type of action taken, the issue that gave rise to it, and a brief explanation. We are not obliged to disclose the source of a report, or the means by which a breach was detected or identified. Enforcement notices identify the issuing member of staff by their role title rather than by personal name. Where we ask you to acknowledge a notice, we record evidence of that acknowledgement, including the time and the IP address and device (user-agent) information used.

22.12 Evidence and reporting

We may preserve relevant data and logs as evidence of a breach. Where the law requires it, or where we reasonably consider it necessary to protect any person or to comply with a regulatory obligation, we may disclose that evidence to the police, a regulator, or another authority, and, in the case of a breach of a third-party platform's terms, to that platform.

22.13 Appeals

You have no contractual right of appeal. However, as a matter of discretion, we operate an appeal process through which you may ask us to review an enforcement decision. Whether we consider an appeal, and the outcome of any appeal, is at our sole discretion and is final. The appeal process is not available for matters falling within Section 22.7.

22.14 Reinstatement

Whether access is ever reinstated following suspension, termination, or blacklisting is at the sole discretion of the Platform Director. We are under no obligation to reinstate access, and reinstatement will not be considered for matters falling within Section 22.7.

22.15 No liability for good-faith enforcement

We are not liable for any loss you suffer as a result of enforcement action taken in good faith under this Policy, including action taken on the basis of a credible report that later proves to be mistaken, or loss of access to Content or functionality during a suspension or investigation.

23. Service Availability, Module Control, and Changes

In short — we can change or pause features for operational reasons — separate from any enforcement.

Separately from enforcement, and for operational reasons, we may from time to time restrict, disable, modify, or withdraw the Service, any Module, or any feature, including for maintenance, updates, security, technical necessity, or the ongoing development of the Service. Action taken for these operational reasons is not enforcement action and does not imply any breach on your part.

Some features may be provided on a trial, beta, or evolving basis. Such features are provided as they are, may change or be withdrawn, and should not be relied upon as permanent. We will act reasonably to limit disruption, but we do not guarantee uninterrupted availability of the Service or any particular Module or feature, except as expressly set out in the Terms.

24. Survival and General

In short — the serious rules keep applying even after you stop using the Service.

We may suspend or restrict access to the Service, in whole or in part, where we reasonably consider it necessary to investigate a suspected breach of this Policy, to protect the Service or any person, or to comply with a legal or regulatory obligation.

Any provision of this Policy that by its nature should survive termination — including those concerning Illegal Content, child protection, real personal data, blacklisting, our rights of enforcement, and our right to report to the authorities — will continue to apply after your use of the Service ends. This Policy is governed by the law of England and Wales, in accordance with the Terms.

25. How to Contact Us

In short — where and how to reach us.

If you have any questions about this Policy, or about what is and is not permitted on the Service, please contact us before acting if you are unsure. We would always rather answer a question than take enforcement action.

End of Acceptable Use Policy