Trust, Safety & Integrity
The legal and governance infrastructure here was built before the feature set. A platform holding operational records needs it, and so do the communities that use one.
The Compliance Backbone
Each item below is available in the current build. Where hardening work is ongoing, the card says so.
Article 15 (access) and Article 17 (erasure) requests are handled through a structured case-management workflow. Statutory one-month deadlines are tracked automatically. Identity verification and Director sign-off on erasure are enforced.
Core workflow live. Object-storage hardening in progress — some attachment handling is still being strengthened.
Sensitive platform and operational actions — record access, searches, support sessions, staff bypasses — are written to dedicated audit trails. Selected evidentiary records carry database-level immutability controls (DB triggers); coverage is being expanded and verified across the remaining modules.
Reports involving CSAM, terrorism, credible threats, or court orders are automatically routed to the platform Trust, Safety & Integrity queue. Community Directors and staff cannot suppress, close, or redirect these reports — the pipeline is enforced at platform level.
Two parallel five-rung sanction ladders — one for platform users, one for communities. Each rung has documented authority, a mandatory cooling-off period, and a formal appeal window. No one is removed or suspended without a documented trail.
Consequential actions are gated by the role registry — only the correct authority can take them. A Director break-glass mechanism exists for genuine emergencies; every invocation is logged with a mandatory reason (minimum 50 characters), timestamped and irrevocable.
A live breach register (Article 33/34 notification timelines tracked), data retention schedule, sub-processor register, ICO correspondence log, and DPIA register — each maintained as a structured record in the platform.
A first-party "Report a Problem" tool surfaces in every community. Reports are routed into the mandatory escalation pipeline for triage, with full audit trail. The platform is structured for OSA obligations — regulated services can meet their transparency requirements.
A minimum age of 13 is required to hold a platform account, in line with UK data protection law (GDPR Article 8 and UK GDPR equivalent). Subscriptions require an age declaration of 18 or over. The age gate is enforced during mandatory onboarding — before ordinary platform access — and again at the subscribe flow.
Every tenant-scoped query filters on the community's own tenant ID, and automated cross-tenant test suites run on every merge. Independent security reviews (May–July 2026) found no cross-tenant data leak.
Application-level scoping is the live isolation layer. Database-level row-level security is deployed as a staged backstop and is still being hardened before it is enforced independently of the application.
The User Model
The platform has two distinct account types with separate rights, obligations, and data-protection roles.
Anyone who creates an account on OpsCentre via Discord OAuth. A Platform User can join communities and participate in roleplay. They have no billing relationship with OpsCentre, but they hold a platform account with the full protections of the Privacy Policy and Terms of Service.
The individual who creates and runs a community on OpsCentre. The Director holds the subscription, bears responsibility for acceptable use within their community, and has access to community configuration, member management, and the full compliance toolkit.
Platform-Staff Accountability
Trust runs in both directions. These are the governance rules that apply to OpsCentre staff when handling a community.
Platform-staff access runs through recorded support sessions — which staff member, which community, when, and under which session type. Record access and searches performed inside RMS and LEDS during a session are written to those modules' audit trails.
Support sessions auto-expire after one hour, so access does not persist indefinitely. Platform Management can extend a running session; every extension is recorded — who extended it, and when.
Routine support access starts with your community: staff can only open a community-requested session against an open request raised by your own admins, and sessions are visible to the community by default. A narrow, Director-of-OpsCentre- authorised exception exists for safeguarding and legal investigations where advance visibility would defeat the purpose; it is logged at platform level.
Your admins can cancel an open support-access request at any time before it is actioned, and can ask platform Management to end a running session. Any consequential action taken by platform staff is subject to the same appeal and review process as any other sanction.
The compliance backbone is backed by legal documents that set out the rights and obligations of every party. All are publicly available and in plain language.
Contact the Data Protection team at [email protected]. We respond without undue delay and at the latest within one month (UK GDPR Art. 12). For Trust, Safety & Integrity matters, use [email protected].