COMPLIANCE & RISK ASSESSMENT GUIDE
UK Online Safety Act: A Practical Compliance Guide & Risk Assessment Template for Chat Website Owners
If your website has live chat or private messaging that people in the UK can use, it is almost certainly a user-to-user service under the UK Online Safety Act 2023 (OSA), regulated by Ofcom.
Small website owners tend to fall into one of two traps. Some panic and assume the law means every site must buy expensive age-check software or ban children outright. Others ignore it completely because they think it only applies to Facebook, TikTok and porn sites. Neither is right.
What Ofcom actually expects from a small chat site is mostly process and paperwork: a written risk assessment, clear rules, a way for users to report problems, and someone who actually acts on those reports quickly. If children are likely to use your site, you also need to protect them from harmful content and from grooming. Age-check software is only required in specific situations, which this guide spells out.
This guide covers what the Act asks of a small chat site, when age checks really are required (and when they are not), how World of Chat Messenger (woc-messenger) can support your safety measures, and how to fill in each section of our Risk Assessment Template.
This is a practical guide, not legal advice. It reflects the Act and Ofcom’s published codes and guidance as of November 2026. Links to the Ofcom sources are at the bottom.
📥 Download the Risk Assessment Template
A clean, ready-to-fill template with the Children’s Access Assessment, the 17 kinds of priority illegal content Ofcom asks you to assess, and prompts in every row.
1. What the Online Safety Act Is Actually Asking For
Once you understand the shape of the law, filling in the paperwork becomes common sense. For a chat site, the Act boils down to two sets of duties:
- Illegal content duties (apply to every user-to-user service, in force since March 2025): You must assess how your chat could be used for illegal activity and take proportionate steps to reduce it, then remove illegal content quickly when you become aware of it. For chat, the big risks are grooming and child sexual abuse material (CSAM), intimate image abuse, harassment and threats, hate, fraud and scams, plus drugs, weapons, terrorism and the other priority offences.
- Children’s safety duties (apply only if children are likely to access your service, in force since July 2025): If under-18s are likely to use your chat, you must assess the risk of them encountering content that is harmful to children and take proportionate steps to protect them. The most serious category, which Ofcom calls “primary priority content”, is pornography, and content encouraging suicide, self-harm or eating disorders. The next tier, “priority content”, includes bullying, abusive or hateful content, serious violence and dangerous challenges.
Why chat widgets are in scope:
A blog with static articles isn’t a user-to-user service. Once you add a chat where visitors can send messages or photos to each other, your site becomes one, and you (the site owner, because you control who can use the chat) are the “provider” with the legal duties. Anyone who has run a chat room knows that if it’s left unmoderated with open photo uploads, someone will eventually post porn, send unsolicited explicit photos, spam scam links or harass people. The Act asks you to write down how you prevent and handle that, and then actually do it.
What every small chat site needs as a baseline. Ofcom’s illegal content codes have a short set of measures that apply even to small, low-risk services:
- A written illegal content risk assessment, kept on file.
- A named person accountable for online safety compliance. This goes in your internal records and doesn’t have to be published on your site (see the note below).
- A content moderation function, meaning someone who reviews reported content and takes illegal content down swiftly.
- An easy way for users to report content and make complaints, and a process for acting on them.
- Clear terms of service explaining how you protect users.
The named person, and your personal safety:
Anyone who has run a chat site knows that banned users can hold grudges. Some go looking for the owner’s real name, address or social media and make threats, and this happens far more often than people outside the industry realise. The good news is that Ofcom’s “named person” measure is about internal accountability: it’s a name in your risk assessment and records, so Ofcom knows who is responsible if it ever contacts you. It is not a requirement to publish your name on your website.
Practical steps: use a role-based contact on your site (e.g. safety@yoursite.co.uk), not a personal email or phone number. Moderate under a site username, not your real name. Don’t publish your home address; if you run the site as a business and other laws require a business address, a registered office or virtual office address is the usual answer. Keep your real details in the assessment itself and share them with Ofcom or the police if asked. If a banned user threatens you, keep the messages and report it to the police (threats and harassment are offences in their own right), and log it in your risk assessment as evidence of the harassment risk on your site.
Larger services, and services that assess themselves as medium or high risk for particular harms, get extra recommended measures on top. For example, a service at high risk of grooming is expected to apply safety defaults for child accounts so strangers can’t freely message them or find them.
A note on CSAM reporting: since 7 April 2026, UK-based user-to-user services must report detected child sexual exploitation and abuse content to the National Crime Agency (NCA) through its industry reporting portal. Non-UK providers must report UK-linked content.
2. Children, Age Checks & Pornography: What the Law Really Requires
This is where most guides (including our own earlier version) get it wrong, so it’s worth being precise.
You do not have to ban children
Nothing in the Act requires a chat site to ban under-18s. Running an adults-only community is a perfectly reasonable business choice, but it’s a choice, not a legal requirement. If children use your site, the law asks you to protect them, not to exclude them.
You do not automatically need age-check software
Ofcom does not expect every website to run “highly effective age assurance” (photo-ID checks, facial age estimation, credit-card checks and so on). In practice it is mainly porn sites and large platforms that have rolled it out. Under Ofcom’s Protection of Children Codes, highly effective age assurance is recommended in these situations:
- Your service exists mainly to host porn or other primary priority content (or priority content). In that case, age checks should block children from the whole service.
- Your terms of service allow porn, or another kind of primary priority content (suicide, self-harm or eating-disorder content). Age checks should then stop children from seeing it.
- You ban that content but it isn’t technically feasible for you to take it down. Ofcom says only a very limited set of services are in this position.
- You allow a kind of priority content you’re medium or high risk for, or you push content to users through a recommender feed, in which case age checks are used to filter what children see.
- You publish your own pornographic content (as opposed to users posting it). This falls under Part 5 of the Act, which has required highly effective age assurance since January 2025.
If your chat bans pornography and self-harm/suicide/eating-disorder content in its rules, and you actually moderate and remove it quickly, none of these apply, and Ofcom’s codes do not ask you to install age-check software. What they do ask, if children are likely to use the site, is that you protect them through your rules, moderation, reporting and complaints, and, where your risk assessment calls for it, measures such as stopping strangers from contacting children.
That’s also why age verification costs (see our breakdown of UK Online Safety Act Age Verification Costs) are not a cost most small chat sites need to carry.
The Children’s Access Assessment (Section 35): get the logic right
Every user-to-user service must carry out a children’s access assessment and keep a written record of it. It asks two questions:
- Is it possible for children to access the service? The Act says you can only answer “no” if you use age verification or age estimation so that children are not normally able to get in. A “this site is 18+” line in your terms or a tick-box asking users to confirm their age does not count. So without age checks, the honest answer is “yes, children could access it”, and you move on to question 2.
- Is the “child user condition” met? That means a significant number of children actually use the service, or it’s the kind of service likely to attract a significant number of children. “Significant” can be a small number relative to your total users, and the answer must be based on evidence of who actually uses your site, not who you intend to use it.
How we think about it on World of Chat
World of Chat is an 18+ site, and that’s part of the culture rather than just a line in the terms. Most adults genuinely don’t want children in the same chat space, so when an under-18 turns up our users tend to report them quickly, and we remove them.
Will children still get into the chat rooms sometimes? Yes, there’s no point pretending otherwise on any open chat site. In our experience they usually get bored and move on, and the community and moderators catch the rest. That’s the honest picture we use for our assessment: children are an occasional visitor we deal with, not a group that uses the site in any real numbers.
This is how to think about your own site. Don’t ask “could a child ever get in?” (on an open chat the answer is always yes). Ask “what does the evidence show about who is actually using it?” Look at how many users you remove or get reports about for appearing underage, what your moderators see day to day, and whether that is growing. Bear in mind the legal test is a significant number of children, not a majority. If you find under-18s are a regular, noticeable part of your chat, don’t keep relying on an 18+ rule. Treat your site as likely to be accessed by children, do the children’s risk assessment, and think seriously about how to keep them safe there.
If the child user condition is not met, your service is not treated as likely to be accessed by children and the children’s safety duties don’t apply, though the illegal content duties still do. You must repeat the access assessment at least once a year, and sooner if you make a significant change or see evidence of more children using the site. If you skip the assessment altogether, the Act treats your service as likely to be accessed by children.
If the condition is met, or you honestly can’t rule it out, that is not a disaster. You complete a children’s risk assessment and put proportionate protections in place. For a chat site that bans porn and self-harm content, that mostly means things you should be doing anyway: clear rules, swift moderation, easy reporting, and protecting child users from contact by strangers if your grooming risk is high.
Choosing your path
- An adult or niche hobby community with no real evidence of children using it: your access assessment may reasonably conclude the child user condition is not met. Base it on evidence (your audience, what moderators see, reports, sign-up data), not just your “18+” rule, and re-check it every year.
- A general or open “chat to strangers” site, or one with guest access that anyone arriving from Google can use: be realistic. It’s hard to show children don’t use a general chat service in significant numbers. The safer course is to assume they might, do the children’s risk assessment, and focus on keeping porn and other harmful content out and on preventing grooming.
- Either way: you can still choose to make your chat 18+, remove users who appear to be under 18, and tell users to report anyone who seems underage. That’s a sensible safeguard, but it doesn’t replace the assessments.
💡 Pro Tip: Guest Chat vs. Logged-In Members Only
In your WordPress admin settings for woc-messenger, you can allow Guest Users or restrict chat to Logged-In WordPress Members Only. Switching guest chat off cuts down on drive-by trolls and spammers, and on visitors wandering in from search engines, and gives you better evidence about who your users are. Registration on its own is not age assurance, but it’s a meaningful risk reduction worth recording in your assessment.
3. How World of Chat Messenger Supports Your Safety Measures
Your risk assessment needs to say what technical and moderation controls you have. World of Chat Messenger (woc-messenger) gives you a set of built-in tools you can cite. They support your compliance; they don’t achieve it on their own. Ofcom still expects you (or your moderators) to review reports and act on them quickly.
| Safety Feature | How It Works & How It Helps |
|---|---|
| Server-Side Explicit Photo Scanner & Blur Cover | When a user sends a photo in chat, it is checked by a scanner on our server before display. If a photo looks sexually explicit, it is automatically covered with a blur and a warning overlay, so viewers aren’t shown it unless they choose to uncover it. Site owners can toggle scanning in settings. Automated scanning isn’t perfect and blurring isn’t age assurance, so treat it as one layer alongside a no-porn rule and moderation, not a guarantee. |
| 1-Click Abuse Reporting with 15-Message Context | Every user has a Report button. When someone reports a user or a message/photo, the system packages the report with the surrounding 15 messages of conversation context and sends it to your WordPress Chat Monitor. This directly supports Ofcom’s baseline expectation of an easy reporting route and a moderation function that can act on it. |
| Discreet 1-Click User Blocking | Any user can instantly block another user from messaging them. User blocking is one of the measures in Ofcom’s codes (formally recommended for larger and higher-risk services) and is a practical defence against harassment, stalking and unwanted sexual contact. |
| Multi-Layer Bans (Account, Guest ID & IP Address) | WordPress administrators (and any moderators you appoint) can ban users for 1 hour, 24 hours, 7 days, or permanently. Registered users are banned by account; guests are banned by both their persistent Guest ID and their IP address, so refreshing the browser doesn’t get around a ban. |
| Rolling 90-Day Auto-Delete | Messages, shared photos and activity logs are kept for 90 days so you can investigate reports, and are then automatically and permanently deleted, so your site doesn’t become a long-term archive of harmful content. If you report child abuse content to the NCA, the law requires you to keep the related evidence for 1 year, so save it before the auto-delete removes it (see the NCA reporting section of this guide). |
| Rate Limiting & Duplicate-Message Spam Filters | Built-in rate limits and duplicate-message filters make it much harder for bots to flood your chat with scam links, phishing URLs or other junk. |
| Multi-Tenant Site Isolation | Your website’s chat is isolated from every other website using our software. Users on other websites can’t see your users, search your profiles, or message into your site, which keeps your risk assessment about your own community. |
4. How to Report Child Sexual Abuse Content to the NCA
The National Crime Agency (NCA) is the UK’s national law-enforcement agency for serious and organised crime, including online child sexual abuse. Under section 66 of the Online Safety Act, since 7 April 2026 UK-based user-to-user services must report child sexual exploitation and abuse (CSEA) content they find on their service to the NCA. That covers child sexual abuse images or videos, links to them, and grooming. Non-UK services only need to report content with a UK link (for example, a UK victim or offender). The duty applies whatever the size of your site.
You don’t have to go looking for this content. The duty is to report it when you become aware of it, for example through a user report or something a moderator sees, and it hasn’t already been reported.
Step 1: Register on the NCA portal (when you first need to report)
- Reports go through the NCA’s CSEA Industry Reporting Portal (CSEA-IRP). The regulations say you must register before you submit your first report. You don’t have to register in advance, and if you never have anything to report, you never need to register. Registrations are only processed Monday to Friday during working hours, so some owners choose to register early to avoid a delay, but that’s optional.
- The first person to register becomes your Organisation Administrator. You’ll need your name, work email and phone number; your site’s name and web address; your country (and company number if you have one); a contact email; your address; and an emergency contact the NCA can reach.
- You verify your email, submit, and the NCA’s Child Sexual Exploitation Referral Bureau approves or rejects the application by email. The NCA’s step-by-step registration guide is linked in the sources below.
Step 2: When you find something
- Don’t forward, download or share the content beyond what the report needs, and don’t confront the user.
- Remove it from public view and ban the account (account, Guest ID and IP).
- Preserve the evidence before the 90-day auto-delete removes it (see below).
- File the report on the portal. The regulations set the speed by priority: immediately if a child’s life or safety is at immediate risk, as soon as reasonably practicable if serious harm may happen soon, and without undue delay otherwise. If you think a child is at real risk right now, mark the report Priority 1. You usually won’t know where the child or the user is, but the NCA can trace IP addresses and pass it to the right police force. Your job is to get the information to them quickly and accurately.
- Keep the reference number the portal gives you, and answer any follow-up request from the NCA within 7 days.
What goes in a report
The regulations list the information to include where you have it. You’re not expected to invent data you don’t collect:
- Your name, email and phone number as the person reporting.
- The content itself, how and where it was found, and when it was uploaded.
- Technical details such as the uploader’s IP address, the page URL and any image data.
- What you know about the account: username, email, profile URL, and registration and login IP addresses from the previous three months.
- A priority level and a declaration that you’ve provided everything available. If you learn more later, you file a supplementary report.
Keeping the evidence: the 90-day auto-delete
Once you’ve made a report, the regulations require you to keep the reported content, the information you submitted and the relevant user data (including chat logs from the two weeks before the content was shared) for 1 year, and the report reference number for 5 years. World of Chat Messenger’s rolling 90-day auto-delete would otherwise remove this, so as soon as you identify reportable content, export or save the report bundle and the related chat history somewhere secure and access-restricted. Don’t let the auto-delete clear it.
5. Step-by-Step: How to Fill Out Each Section of the Template
Ofcom requires your assessment to be “suitable and sufficient”, meaning it reflects your site, your features and your evidence. Don’t copy another site’s completed assessment. You don’t send it to Ofcom; you complete it, date it, keep it on file, and produce it if Ofcom asks.
Header & Top Details
- Website Name: your site’s name and domain.
- Date Completed & Next Review Date: the date you complete it, and a review date no more than 12 months later. Ofcom recommends reviewing the illegal content risk assessment at least annually, and the Act requires you to redo the children’s access assessment at least every year. You also need to reassess before any significant change to your chat (for example, turning on photo sharing or opening chat to guests).
- Named Responsible Person: Ofcom’s codes recommend that every service names an individual accountable for online safety. This is an internal record, so use your real name and role here. It does not need to appear on your website. Publicly you can stay as a site username with a role-based contact email, which matters on chat sites where banned users sometimes try to track down and threaten the owner (see the note in section 1).
Section 1: About Our Website and Chat Service
Describe what your site actually is and what the chat can do. Be specific: a members-only chat on a classic car forum has a very different risk profile from an open stranger-chat site with photo sharing. The features you list here (private messaging, photo sharing, guest access, user profiles) are exactly the “risk factors” Ofcom’s Risk Profiles ask you to consider.
Example of what to write in Section 1:
“Website topic: [MySite.co.uk] is an independent UK hobby website for [topic, e.g. retro gaming / local sports fans]. We use the World of Chat Messenger plugin so visitors can chat about [topic].
Who uses it: [Logged-in members and guests / Logged-in members only]. We have around [e.g. 50–200] monthly chat users.
What users can do: [Public chat / private messages / photo sharing on or off].
Our approach: Our rules prohibit illegal content, pornography, harassment and scams. Reports are reviewed by [me / our moderators] [daily] and rule-breakers are removed.”
Section 2: Children’s Access Assessment
Work through the two Section 35 questions honestly and write down your evidence. This is a record of your reasoning, not a magic formula that gets you out of the children’s duties.
- Can children access the service? Unless you use age verification or age estimation that genuinely stops children getting in, write “Yes”. An 18+ rule or self-declaration doesn’t change this answer.
- Do a significant number of children actually use it? Give your evidence: your audience, what moderators and reports show, sign-up data, any users removed for appearing to be under 18.
- Is it likely to attract a significant number of children? Consider your topic, design and how people find the chat (for example, open guest chat reachable from search engines).
- Your age policy (if you have one): if you’ve chosen to run an 18+ community, say so and explain how you handle users who appear to be underage. Present it as a safeguard, not as proof that children can’t get in.
- Your conclusion: either “The child user condition is not met, so our service is not likely to be accessed by children. We will reassess within 12 months, or sooner if we see evidence of children using it,” or “Our service is likely to be accessed by children, so we have completed a children’s risk assessment and apply the protections set out below.”
Section 3: Protecting Children from Harmful Content (if children are likely to access the site)
If you concluded children are likely to access your chat, record how you protect them. For most chat sites this means:
- Your rules ban primary priority content (pornography; content encouraging suicide, self-harm or eating disorders). Keeping these banned, and removing them swiftly, is what keeps you outside the situations where Ofcom’s codes recommend age-check software.
- How harmful content is found and removed: user reports with 15-message context, your Chat Monitor, how often you check it, and how quickly you act.
- Explicit photos: the server-side scanner blurs likely-explicit photos as an extra layer. Or, if you’ve turned photo sharing off, say so.
- Bullying and abuse (priority content): blocking, reporting and bans.
- Grooming: how you stop adults using the chat to target children, such as monitoring reports of sexualised or age-related messages, removing offenders, and, if your risk is high, limiting who can privately message accounts you believe belong to children.
Section 4: The 17 Kinds of Priority Illegal Content
Ofcom asks you to assess each of the 17 kinds of priority illegal content separately, plus any other illegal content likely on your service (such as cyberflashing). For each, give a risk level of Negligible, Low, Medium or High, based on how likely it is on your site and how severe the impact would be, then note your evidence and mitigations.
Rate honestly, not optimistically. Don’t write “Negligible” in every box. Ofcom knows that harassment, abuse and scams are everyday problems in live chat, while terrorism or human trafficking are far rarer on a hobby site. Here’s how to approach the rows:
- Child sexual exploitation and abuse (grooming and CSAM): Ofcom’s Risk Profiles flag direct messaging, the ability to contact strangers, image sharing and anonymous or guest users as key risk factors for grooming, and a chat service will have several of these. Don’t rate it Negligible just because your rules say 18+. What to write: your relevant features; how grooming would be noticed (reports with context, moderators watching for sexualised or age-related talk); blocking; bans; photo scanning; and your process for removing CSAM, preserving evidence and reporting it to the NCA (or IWF and police).
- Intimate image abuse and extreme pornography: Relevant wherever users can send photos. Note whether photo sharing is on, the scanner and blur, reporting, blocking and bans. Also consider cyberflashing (sending unsolicited sexual images), a non-priority offence you should still cover.
- Harassment, stalking, threats and abuse, and hate: Often Low or Medium for an active chat. These are the most common real-world problems. Point to blocking, reporting, bans and how quickly you act.
- Fraud and financial offences: Scam, phishing and romance-fraud messages are common in open chats. Point to rate limits, duplicate-message filters, rules against solicitation, reporting and bans.
- Encouraging or assisting suicide: Note that your chat has no algorithmic feed, rules forbid it, moderators remove it, and you signpost users in distress to support (e.g. Samaritans on 116 123).
- Controlling or coercive behaviour and sexual exploitation of adults: Usually Low for a hobby site, but think about private messaging. Note blocking, reporting, and bans for solicitation or exploitation.
- The rest: terrorism; drugs and psychoactive substances; firearms, knives and other weapons; human trafficking; unlawful immigration; proceeds of crime; foreign interference; animal cruelty: For most small community sites these will be Negligible or Low. Briefly say why (e.g. “no marketplace or payment features”, “small community about [topic]”), that it’s banned by your rules, and that it would be removed, banned and referred to police if seen.
Section 5 & Section 6: What You Already Do & Honest Weak Points
In Section 5, confirm where your rules and terms are published and who moderates (you alone, or you plus volunteer moderators), and how often reports are checked. A moderation function that actually reviews reports and removes illegal content swiftly is one of Ofcom’s baseline expectations for every service.
In Section 6 (Weak Points), be candid. Ofcom’s guidance expects you to think about where your controls could fail. Good examples:
- Harmful text chat is mainly caught through reports and moderators, so it depends on someone checking regularly.
- Grooming can look like ordinary friendly conversation at first.
- You don’t use age verification, so you can’t be certain no under-18s are present.
- Automated photo scanning can miss images or flag innocent ones.
- A determined banned user could come back via a VPN.
Writing these down, along with what you do about them, shows that you’ve genuinely thought about how your chat works rather than ticking boxes.
Section 7: Responsibility, Serious Cases & Review
Fill in the responsible person and completion date. Keep the commitment that child sexual abuse content is removed immediately, the evidence preserved for at least a year, and the content reported to the NCA (see the NCA reporting section of this guide). If you have registered on the NCA portal, note the date. Save the finished document, and set a calendar reminder for your review.
Ready to Complete Your Assessment?
Download the template, replace the bracketed prompts with your own site’s details and evidence, and keep it in your site records.
Sources
- Online Safety Act 2023, section 35: Children’s access assessments
- Online Safety Act 2023, section 36: Duties about children’s access assessments
- Ofcom: Quick guide to illegal content risk assessments
- Ofcom: Illegal content codes of practice
- Ofcom: Content moderation, technical feasibility and age assurance
- Ofcom: Duty to report CSEA content
- The Online Safety (CSEA Content Reporting by Regulated User-to-User Service Providers) Regulations 2026
- NCA: How to register your organisation for the CSEA Industry Reporting Portal
- Ofcom: Online safety toolkit for services
