OpenThoughts Governance Pack
Open, transparent and responsible by design.
This page brings the OpenThoughts governance policies together in one consistent, customer-facing format. Each policy is written to support openness, shared learning, resident protection, member trust and clear accountability.
Approved and implemented: 04 May 2026UK EnglishFounder-led independent platform
Clear rules
Each policy explains what members, contributors, suppliers and advertisers can expect from OpenThoughts.
Open accountability
We publish how decisions are made, how concerns are reviewed and how the platform protects trust.
Safe sharing
Shared learning is encouraged, but not at the cost of personal data, confidentiality, safety or fairness.
Policy 01Acceptable Use Policy
Acceptable Use Policy
Clear rules for safe, lawful and constructive use of the OpenThoughts platform
OpenThoughts
Version 1.0
OpenThoughts Acceptable Use Policy
Document owner: OpenThoughts Founder / Platform Owner Applies to: members, prospective members, visitors, contributors, moderators, suppliers, advertisers and anyone using OpenThoughts Recommended status: standalone public policy, incorporated by reference into the Terms of Use, membership rules, upload rules and supplier/advertiser terms Review cycle: at least annually, and sooner after significant incidents, legal changes or platform changes Important note: this document is a practical governance policy and website wording draft. It is not legal advice.
1. Recommended decision
OpenThoughts should adopt a standalone public Acceptable Use Policy as a launch-critical control. The rules should not be hidden only inside the Terms. They should be visible at sign-up, on forum pages, on upload pages, in supplier and advertiser areas, in the footer and beside the Report this function.
This is the best solution for the site’s ambition because OpenThoughts is built on trust, shared resources, professional conversation and open-source thinking for the social housing sector. That model only works if members know what is welcome, what is not allowed, and what OpenThoughts can do when the platform is misused.
The policy should be strong but still sound like OpenThoughts:
open, generous and practical;
clear about resident and member safety;
firm on privacy, copyright, confidentiality and commercial misuse;
fair in how moderation and account actions are handled;
easy to point to when removing content, restricting accounts or responding to reports.
2. Plain-English policy position
OpenThoughts is built for constructive sharing, learning and collaboration. Use it generously, lawfully and respectfully.
Do not use OpenThoughts to scrape data, spam people, harass others, upload unlawful or confidential material, share resident-identifiable information, harvest supplier leads, impersonate someone else, upload malware, advertise without permission, misuse logos or commercially exploit resources shared by the community.
OpenThoughts may remove content, restrict features, reject uploads, suspend accounts, end membership, refuse advertising, terminate supplier access or take other reasonable action where these rules are breached.
3. Scope
This policy applies to all use of OpenThoughts, including:
public pages, member areas, forums, groups, comments, replies and direct engagement features;
resource uploads, templates, guides, images, presentations, documents, AI-assisted content and adapted materials;
supplier directories, supplier profiles, advertising pages, sponsored content and commercial listings;
contact forms, membership forms, event forms, newsletter forms and enquiry routes;
the Report this function and any complaint, appeal, takedown or moderation process;
use by members, prospective members, guests, suppliers, advertisers, moderators, administrators and platform partners.
4. Core acceptable use principles
| Principle | What it means |
|---|---|
| Be lawful | Do not post, upload, share or encourage anything unlawful, fraudulent, malicious, defamatory, discriminatory, harassing, infringing or unsafe. |
| Be respectful | Discuss issues, services, learning and systems. Do not use OpenThoughts for personal attacks, intimidation, pile-ons, harassment or targeted negativity. |
| Protect residents | Do not upload or post resident-identifiable information, live cases, safeguarding concerns, complaints, repair records, ASB case details or health/vulnerability information. |
| Protect employers and partners | Do not upload confidential employer documents, internal reports, unpublished data, contracts, screenshots or restricted policies unless you have permission to share them. |
| Respect intellectual property | Only upload material you own, created, are authorised to share, or can lawfully licence under the relevant OpenThoughts licence terms. |
| Respect the community model | Shared resources are for sector learning and non-commercial collaboration unless expressly stated otherwise. Do not package, resell, scrape or exploit community content. |
| Be transparent | Declare AI-assisted content, sponsored content, conflicts of interest, supplier interests and any relevant limitation in the material you share. |
| Use the right route | Use Report this for concerns. Use employer emergency, safeguarding, repairs, complaints, ASB or risk escalation routes for urgent or case-specific matters. |
5. Prohibited uses
The following uses are not allowed. This list is not exhaustive. OpenThoughts may act where behaviour undermines the purpose, safety, legality or reputation of the platform.
| Prohibited use | Rule |
|---|---|
| Scraping, harvesting or automated extraction | Do not scrape, crawl, copy, export, mine or harvest member information, email addresses, supplier data, forum posts, resource libraries or content at scale without written permission. |
| Spam or nuisance activity | Do not post repetitive promotional messages, bulk messages, irrelevant links, clickbait, phishing content, misleading offers or unsolicited direct marketing. |
| Harassment, bullying or intimidation | Do not abuse, threaten, shame, humiliate, stalk, target, pile on, discriminate against or repeatedly contact someone who has asked not to be contacted. |
| Unlawful uploads | Do not upload material that is illegal, infringing, fraudulent, malicious, defamatory, discriminatory, obscene, extremist, hateful or otherwise unlawful. |
| Confidential documents | Do not upload confidential employer, supplier, resident, partner, board, procurement, legal, contract, HR, safeguarding, casework or investigation documents without authority. |
| Resident-identifiable information | Do not post names, addresses, photos, voice notes, case references, repair histories, vulnerabilities, health information, tenancy details or any combination of details that could identify a resident or household. |
| Supplier lead harvesting | Do not use OpenThoughts to harvest member data, build sales lists, bypass advertising rules, scrape sector contacts, send unsolicited sales messages or pressure members into procurement conversations. |
| Impersonation or false authority | Do not pretend to be another person, organisation, moderator, supplier, resident group, employer, regulator, professional body or OpenThoughts representative. |
| Malware, security misuse or harmful files | Do not upload viruses, scripts, executable files, macros, spyware, tracking files, ransomware, corrupted files or anything designed to interfere with systems or data. |
| Unauthorised advertising | Do not advertise, promote, sponsor, recruit, sell or solicit commercially unless the relevant advertising or supplier route has been approved by OpenThoughts. |
| Misuse of logos and branding | Do not use logos, employer branding, supplier branding, accreditation marks, regulator marks or OpenThoughts branding in a way that suggests endorsement, approval or partnership without permission. |
| Commercial exploitation of shared resources | Do not copy, repackage, resell, train commercial products on, place behind a paywall, or commercially exploit shared OpenThoughts resources unless the licence and creator expressly allow it. |
| Misleading AI or generated media | Do not upload undeclared AI-generated content, deepfakes, misleading images, fabricated evidence, hallucinated legal advice, fake case studies or untested AI outputs presented as fact. |
| Defamation and reputational risk | Do not post unverified allegations, name individual staff members negatively, accuse organisations of unlawful behaviour without public evidence, or turn learning discussions into attacks. |
| Urgent risk or case management misuse | Do not use OpenThoughts as an emergency, safeguarding, legal, complaints, repairs, ASB, domestic abuse, homelessness or case-management route. |
| Circumventing controls | Do not try to bypass moderation, upload limits, file restrictions, membership checks, security controls, rate limits, payment controls or account restrictions. |
6. Resource upload rules
Because the resource library is central to OpenThoughts, upload rules should be strict, clear and enforced consistently.
Members, suppliers and contributors must not upload resources unless they can confirm that the content is lawful, safe, shareable and suitable for the platform.
Upload rules:
only upload resources you created, own, are authorised to share, or can lawfully licence for reuse under the relevant OpenThoughts terms;
do not upload documents containing personal data, resident data, live case details, confidential employer information or commercially sensitive information;
remove hidden metadata where appropriate, including author names, tracked comments, internal file paths and embedded personal information;
do not upload executable files, macros, scripts, password-protected files, infected files or files designed to evade scanning;
do not upload branded or adapted documents unless you have the right to share them and the branding does not mislead others about endorsement or approval;
first uploads, sensitive categories and branded resources may be held for moderation before publication;
OpenThoughts may remove, quarantine, edit labels, restrict reuse wording, ask for proof of permission or reject uploads where risk is identified.
7. Forum and group posting rules
Forum and group pages should encourage practical learning while preventing harm, legal risk and misuse.
Members should:
discuss themes, learning, processes, policy, practice and improvement ideas, not identifiable residents or named staff members;
avoid posting urgent safeguarding concerns, domestic abuse risks, ASB case details, homelessness cases, fire safety emergencies, damp and mould live cases, repairs casework or health/vulnerability information;
avoid asking other members to share confidential policies, restricted documents, procurement details, personal data or internal screenshots;
not use groups to sell, solicit leads, promote services, recruit members to paid activity or redirect users to commercial offers unless approved;
use neutral, professional wording and challenge ideas and processes, not people;
report concerns using the Report this route rather than escalating arguments in public threads.
8. Supplier, advertiser and commercial-use rules
Suppliers and advertisers may be part of the OpenThoughts ecosystem, but commercial activity must be transparent and controlled.
| Area | Policy position |
|---|---|
| Allowed with approval | Paid advertising, supplier directory listings, sponsored content, approved webinars, approved resource sponsorship and clear commercial profiles. |
| Not allowed | Cold messaging members, harvesting leads, scraping member lists, disguising adverts as peer advice, presenting paid placement as endorsement, or pressuring members into procurement conversations. |
| Required wording | Supplier presence on OpenThoughts does not mean endorsement, recommendation, procurement approval, due diligence completion or fitness for purpose. |
| Member protection | Members and organisations must carry out their own procurement, due diligence, conflict, value-for-money and compliance checks. |
| Enforcement | Supplier or advertiser misuse may lead to content removal, loss of advertising privileges, account restriction, non-renewal or termination. |
9. Membership and identity rules
Members must:
provide accurate registration information and not misrepresent their identity, organisation, role or authority;
use only approved membership routes and not bypass verification checks;
not share accounts, transfer access, sell access, invite unauthorised people into member-only areas or use another person’s login;
keep login details secure and notify OpenThoughts if they suspect unauthorised access;
accept that OpenThoughts may reject, suspend or close accounts where identity cannot be verified or where access is being misused.
Housing-sector member access may be limited to approved and verified housing association, local authority, ALMO or relevant professional email addresses, depending on the membership rules in force.
10. Content standards
OpenThoughts may remove, edit labels on, restrict, demote or review content that falls below the following standards.
Content should:
be accurate to the best of the contributor’s knowledge, or clearly labelled as an opinion, draft, example, AI-assisted output, learning prompt or discussion starter;
not present unverified legal, safeguarding, medical, financial, procurement or professional advice as fact;
use inclusive, professional and accessible language;
not be deliberately misleading, manipulated, fabricated or presented without relevant context;
include attribution where required and not remove attribution from another creator’s work;
not include tracking links, hidden advertising, hidden affiliate arrangements or undisclosed commercial interests.
11. “Do not post” quick list
This quick list should be placed near upload and forum-posting screens:
do not post resident names, addresses, photos or case details;
do not post confidential employer documents or internal screenshots;
do not post urgent safeguarding, emergency, ASB, repairs, homelessness or domestic abuse concerns;
do not post unverified allegations about people or organisations;
do not post material you do not own or have permission to share;
do not post supplier adverts or sales messages unless approved;
do not post malware, scripts, executable files or password-protected files without approval;
do not post AI-generated content without saying it has been AI-generated or AI-assisted;
do not post logos or branding in a way that suggests endorsement without permission.
12. Upload and posting declaration wording
OpenThoughts should require members to confirm the following before uploading resources or posting in higher-risk areas.
| Context | Recommended checkbox wording |
|---|---|
| General posting checkbox | I confirm this post follows the OpenThoughts Acceptable Use Policy and does not include resident-identifiable information, confidential documents, urgent safeguarding concerns, unlawful material, harassment, spam or unauthorised advertising. |
| Resource upload checkbox | I confirm I own this resource, created it, have permission to share it, or am otherwise entitled to upload it. I confirm it does not contain resident data, confidential information, malware, hidden personal data or material that breaches copyright or another person’s rights. |
| AI declaration checkbox | I confirm whether this content was AI-generated or AI-assisted and have checked it before sharing. I will not present AI-generated legal, professional or factual material as verified advice unless it has been properly checked. |
| Commercial interest checkbox | I confirm whether I have any supplier, advertiser, paid, sponsored or commercial interest connected to this post, resource or recommendation. |
| Sensitive group checkbox | I understand OpenThoughts is not an emergency, safeguarding, complaints, repairs, ASB, domestic abuse, homelessness, legal or case-management route and I will follow my organisation’s procedure for live or urgent matters. |
13. Moderation and enforcement
OpenThoughts should reserve the right to act proportionately, quickly and consistently. The action taken should depend on risk, seriousness, intent, repeat behaviour and potential harm.
| Risk level | Possible response |
|---|---|
| Low-level concern | Edit label, add context note, ask the member to amend, move to a better category, warn member, or temporarily hide while clarified. |
| Moderate concern | Remove content, restrict posting, place future uploads into moderation, require evidence of permission, issue formal warning, or limit access to specific areas. |
| Serious concern | Suspend account, remove content immediately, block uploads, terminate membership, end supplier listing, refuse renewal, preserve evidence, or escalate under relevant legal/privacy/safeguarding processes. |
| Repeated misuse | Apply escalating restrictions, suspend or close account, block supplier access, refuse future membership or advertising, and record the decision in the internal moderation register. |
| Urgent or high-risk material | Remove or hide immediately where needed to reduce harm, preserve evidence, and direct the person to the correct emergency, safeguarding, employer or statutory route where appropriate. |
14. Report this route
Every member-generated page should include a visible report route. Members should be encouraged to report concerns rather than arguing publicly or copying sensitive information into new posts.
The Report this function should allow people to report:
personal data or resident-identifiable information;
copyright, attribution or licence concerns;
abusive, discriminatory or harassing content;
confidential information or employer documents;
spam, supplier misuse, lead harvesting or unauthorised advertising;
broken attribution, misleading use of logos or false endorsement;
accessibility issues or unusable content;
urgent-risk content so OpenThoughts can remove or redirect it, while making clear the platform is not the emergency response route.
15. Complaints and appeals
Members, suppliers and contributors should have a fair way to challenge moderation decisions, content removals, upload rejections, membership restrictions or advertising decisions. The Complaints and Appeals Policy should apply.
OpenThoughts should look at genuine concerns properly, but does not need to enter circular arguments about obvious breaches or repeated misuse.
Recommended stages:
Initial review: review by OpenThoughts or the moderator responsible for the decision.
Escalated review: review by the platform owner or a separate reviewer where reasonably possible.
Final platform decision: decision recorded with reasons. OpenThoughts may refuse repeated appeals that raise no new information.
16. Public website wording
The following wording can be used on the public policy page.
Page title
Acceptable Use Policy
Opening wording
OpenThoughts is a place for constructive sharing, learning and collaboration across the housing sector. To keep it useful, safe and fair, everyone using the platform must follow these acceptable use rules.
Main rule
Use OpenThoughts lawfully, respectfully and transparently. Do not use it to scrape data, spam people, harass others, upload unlawful or confidential material, share resident-identifiable information, harvest leads, impersonate others, upload malware, advertise without permission, misuse logos or commercially exploit shared resources.
Platform action
We may remove content, restrict features, suspend accounts, end membership, reject uploads, refuse advertising or take other reasonable action where these rules are breached.
Community wording
OpenThoughts works because members help protect the space. If you see something that looks wrong, use the Report this function rather than copying, reposting or escalating the concern publicly.
17. Where this policy should appear
| Location | How to use it |
|---|---|
| Website footer | Link to the Acceptable Use Policy alongside Terms, Privacy Policy, Cookie Policy, Accessibility Statement, Complaints and Appeals, Copyright and Takedown, and Report this. |
| Membership sign-up | Add a checkbox confirming the applicant agrees to follow the Acceptable Use Policy. |
| Forum posting pages | Add a short reminder with a link to the policy and “do not post” warnings. |
| Resource upload pages | Add a mandatory upload declaration, prohibited file/data warning and link to file upload controls. |
| Supplier directory and advert pages | Add commercial use, no lead harvesting, no endorsement and advertising rules. |
| Group pages | Add additional warnings for ASB, Domestic Abuse, Supported Housing, Fire Safety, Damp and Mould, Safeguarding, Complaints, Legal/Policy and other higher-risk topics. |
| Terms of Use | Incorporate by reference and state that breach may lead to moderation or account action. |
| Moderator guidance | Use as the rulebook for content removal and account decisions. |
18. Internal register and evidence requirements
OpenThoughts should keep a simple internal Acceptable Use enforcement register. This helps demonstrate consistency, identify repeat misuse and evidence decisions if challenged.
| Field | Purpose |
|---|---|
| Reference number | Unique moderation or incident reference. |
| Date reported | Date and time concern was reported or identified. |
| Reported by | Member, visitor, moderator, supplier, admin, automated tool or external party. |
| Content / account involved | URL, resource title, post title, member name or supplier listing. |
| Concern type | Personal data, copyright, harassment, spam, confidential information, supplier misuse, malware, defamation, urgent risk or other. |
| Risk rating | Low, medium, high or urgent. |
| Action taken | No action, edit, warning, hide, remove, suspend, terminate, escalate, DPA route or legal review. |
| Decision rationale | Brief reason for decision. |
| Member notified | Yes/no, date and method. |
| Appeal status | No appeal, pending, upheld, partly upheld, not upheld or final. |
| Learning action | Policy update, wording change, plugin control, training, upload restriction, category warning or other improvement. |
19. Recommended implementation plan
| Timing | Action |
|---|---|
| Before launch | Publish the Acceptable Use Policy; add sign-up checkbox; add upload declarations; configure report categories; train moderators; add footer link. |
| At launch | Display forum and upload warnings; route supplier activity through approved advertising paths; activate first-upload moderation and report logging. |
| First 30 days | Review any reports, upload problems, supplier behaviours and member queries; refine wording where confusion appears. |
| First 90 days | Review enforcement consistency; update Terms cross-references; check whether additional controls are needed for high-risk groups or file types. |
| Ongoing | Annual policy review and immediate review after serious incidents, legal changes, platform changes or repeated misuse patterns. |
20. Launch checklist
☐ Publish public Acceptable Use Policy page.
☐ Add footer link to the policy.
☐ Add sign-up agreement checkbox.
☐ Add upload declaration checkbox.
☐ Add AI declaration checkbox where relevant.
☐ Add commercial interest declaration where relevant.
☐ Add “do not post resident data” reminder to upload and forum pages.
☐ Add Report this button to member-generated content.
☐ Create moderation register.
☐ Train moderators and administrators on enforcement thresholds.
☐ Cross-reference policy in Terms, Supplier / Advertiser Terms, File Upload Controls, AI Usage Policy, Copyright and Takedown Process, Complaints and Appeals Policy and Safeguarding / Urgent Risk wording.
☐ Review after launch incidents or within 90 days of go-live.
21. Final decision wording
OpenThoughts should publish a standalone Acceptable Use Policy and treat it as enforceable platform rules. This is the best solution because the site will rely on member-generated discussion, resource uploads, supplier participation, advertising, AI-assisted content, Creative Commons sharing and trusted professional exchange.
The policy should protect the open-source ethos without making the platform feel closed or overly corporate. It should say clearly: share generously, challenge constructively, credit properly, protect residents, respect confidentiality, do not commercially exploit the community, and use the right route for urgent or sensitive matters.
This gives OpenThoughts a fair and transparent basis for removing content, refusing uploads, limiting supplier misuse, closing accounts and protecting the resource library that gives the platform its value.
Policy 02Moderation Policy
Moderation Policy
Full strengthened policy and implementation decision
| Decision summary: OpenThoughts should adopt a standalone public Moderation Policy, cross-referenced in the Terms, Acceptable Use Policy, Report This function, File Upload Risk Controls, AI Usage Policy, Defamation and Reputational Risk Policy, Safeguarding and Do Not Post Urgent Risk Policy, Supplier/Advertiser Terms and Complaints and Appeals Policy. The policy should be practical, operational and firm: it should protect open sector learning while making clear that OpenThoughts may remove, hide, edit, restrict, suspend or permanently remove accounts where content or behaviour creates legal, safety, confidentiality, data protection, copyright, reputational, supplier misuse or community risk. |
|---|
| Document control | Details |
|---|---|
| Owner | OpenThoughts founder / platform owner |
| Applies to | Members, contributors, forum users, suppliers, advertisers, administrators, moderators and visitors where they interact with member-generated or supplier-generated content |
| Recommended status | Public policy page plus internal operating procedure |
| Review cycle | Every 6 months during launch year, then annually or sooner after a serious incident, legal change or platform change |
| Version | Version 1.0 - approved and implemented |
| Date | 04 May 2026 |
Important note: This policy explains how OpenThoughts manages moderation, safety and platform standards. It is published for transparency and should be read alongside the wider OpenThoughts governance pack.
1. Purpose of this policy
OpenThoughts exists to support open, practical and generous knowledge-sharing across the social housing and local authority housing arena. The value of the platform depends on people being able to share ideas, resources, reflections, questions and learning safely. This policy turns the existing “respect and removal” approach into an operational moderation framework.
protect members, residents, organisations, suppliers, advertisers and the platform;
keep discussions focused on learning, practice improvement and lawful sharing;
prevent the platform being used for abuse, spam, scraping, harassment, unlawful uploads, confidential disclosure, resident-identifiable data, supplier lead harvesting or reputational attacks;
provide a clear route for reports, decisions, appeals and repeat-breach action;
support legal and regulatory accountability, including data protection, copyright, defamation, safeguarding-style risk and online safety considerations.
2. Best decision for OpenThoughts
2.1 Recommended position
The best solution for OpenThoughts is to publish a clear standalone Moderation Policy and use it as the operating basis for all user-generated, supplier-generated and advertiser-generated content. It should not be hidden inside long Terms only. Members need to understand the rules before they post, upload, comment, advertise or report content.
Standalone public page: Publish as “Moderation Policy” under the Nitty Gritty / Trust / Safety area.
Short notices at the point of risk: Add short moderation notices on forum posting pages, upload pages, supplier profile submissions, advert booking pages and group pages.
Report-driven safety model: Use the “Report this” function on every member-generated page so members help identify risk.
Human oversight: Use human review for reported, sensitive, branded, personal-data, safeguarding-style, reputational, legal, copyright, advertiser and supplier misuse concerns.
Clear enforcement ladder: Use warnings, content edits, temporary restrictions, suspension and permanent removal depending on risk, intent and repetition.
Evidence retention: Keep proportionate records of reports, decisions, edits, removals, appeals and repeat misuse.
No endless arguments: Allow fair appeals but do not enter circular disputes about obvious breaches, bad-faith complaints or attempts to relitigate final decisions.
2.2 Why this is the best fit
OpenThoughts is not a generic social media site. It is a professional learning and resource-sharing platform for housing people.
The platform’s strength is open thinking, but that creates risk where people upload files, talk about sensitive themes or discuss organisations.
A visible, fair and firm moderation policy strengthens trust without killing the open-source ethos.
It gives the founder and administrators a defensible basis for action when content needs to be removed quickly.
It supports supplier neutrality by preventing advertisers from using the platform as an unmoderated sales or lead-harvesting route.
It supports data protection by making it clear that resident-identifiable, confidential and employer-sensitive information must not be posted.
3. Scope
| Area | Covered by moderation policy |
|---|---|
| Member profiles | Names, job roles, biography text, profile images, links, badges and claims of affiliation. |
| Forums and comments | Discussion threads, replies, group conversations, direct replies, polls and Q&A posts. |
| Resource library | Uploaded templates, policies, guidance, slides, toolkits, images, spreadsheets, screenshots and adapted documents. |
| Groups | All specialist groups, including ASB, Domestic Abuse, Supported Housing, Fire Safety, Damp and Mould, Repairs, Building Safety, Customer Voice, Complaints and Service Recovery. |
| Supplier and advertiser content | Supplier profiles, adverts, sponsored posts, case studies, downloads, promotional claims and contact forms. |
| AI-generated content | AI-assisted posts, summaries, templates, images, media or tools uploaded by members or suppliers. |
| Events and learning areas | Event comments, speaker materials, workshop resources and feedback spaces. |
| Messages or contact features | Any platform-provided messaging, enquiry or collaboration features, if enabled. |
| Reports and complaints | Reports submitted by members, copyright holders, suppliers, advertisers, organisations or third parties. |
4. Moderation principles
Open thinking, not unsafe posting: The platform encourages challenge, debate and practical learning, but not unlawful, unsafe, abusive or confidential disclosure.
Discuss issues, not attack people: Posts should focus on learning, process, practice, evidence and ideas rather than personal attacks or unverified allegations.
Residents first: Do not post live cases, urgent risks, resident-identifiable information or details that could identify a household.
Professional honesty: Members should declare AI-generated or AI-assisted work, copyright status, adaptations and supplier interests where relevant.
Proportionate action: Moderation action should match the risk, severity, urgency, intent and history of the issue.
Fairness and consistency: Similar cases should be handled in similar ways, with room for context where required.
Document decisions: Moderation should be recorded so OpenThoughts can show what happened and why.
No circular disputes: OpenThoughts will consider genuine concerns properly but will not engage in repeated arguments about clear breaches or final decisions.
5. What gets removed immediately
OpenThoughts should remove, hide or restrict the following content immediately where it is identified. In high-risk cases, removal should take place before a full investigation is complete.
| Immediate removal category | Examples | Likely action |
|---|---|---|
| Resident-identifiable personal data | Names, addresses, phone numbers, case references, photos, repair logs, medical details, domestic abuse details, safeguarding details or screenshots that identify a resident or household. | Hide or remove immediately. Log as personal data incident. Consider breach assessment. Notify uploader. |
| Urgent safeguarding, emergency or live risk posts | Posts asking the platform to deal with a live safeguarding concern, domestic abuse risk, ASB threat, homelessness emergency, fire risk, damp and mould health emergency or welfare concern. | Hide identifying details. Signpost to organisational procedures and emergency routes. Log and review. |
| Confidential employer or third-party documents | Internal reports, Board papers, procurement documents, unpublished policies, staff investigation material, legal advice, commercially sensitive data. | Remove or quarantine. Ask uploader to confirm rights. Escalate if necessary. |
| Copyright/IP breach risk | Templates, images, logos, paid materials, consultancy documents, training packs or third-party resources uploaded without permission. | Temporarily remove or restrict pending review. Follow IP takedown process. |
| Defamatory or reckless allegations | Unverified allegations of unlawful conduct, corruption, fraud, discrimination, negligence or misconduct by named people or organisations. | Hide and review. May edit, remove or require evidence and responsible framing. |
| Abuse, harassment or discriminatory content | Threats, bullying, hate, slurs, targeted harassment, repeated hostile behaviour, doxxing or intimidation. | Remove immediately. Warning, suspension or permanent removal depending on severity. |
| Malware, executables or unsafe files | Executable files, scripts, macro-enabled files, suspicious links, password-protected files without approval. | Block or remove. Security review. Suspend account if malicious. |
| Spam, scams or unauthorised advertising | Lead harvesting, mass messaging, irrelevant sales posts, fake offers, phishing, supplier promotion outside approved routes. | Remove. Warn or suspend. Supplier contract action where applicable. |
| Deepfakes or misleading generated media | AI-generated images, audio or video used to mislead, impersonate, shame or fabricate evidence. | Remove immediately. Suspend or remove account for serious misuse. |
| Illegal content or credible criminal risk | Content that appears to facilitate crime, threats, fraud, child sexual exploitation or abuse, terrorism or other serious unlawful activity. | Remove or restrict. Preserve evidence. Escalate under legal/safety procedure where appropriate. |
6. What may be edited, labelled, hidden or restricted
Not every moderation concern requires deletion. Where risk can be managed safely, OpenThoughts may edit, label, hide, restrict, add context, request changes or move content to a more suitable area.
| Moderation option | When to use | Examples |
|---|---|---|
| Edit minor issue | A small correction would fix the problem without changing the substance. | Remove accidental email address, correct typo in attribution, remove employer-sensitive line. |
| Add label or note | Transparency is needed but content can remain. | “AI-assisted”, “member-submitted”, “sponsored”, “adapted from”, “awaiting attribution correction”. |
| Hide pending review | Risk needs review but immediate permanent removal would be premature. | Copyright complaint, reputational complaint, branded document, questionable supplier claim. |
| Move content | The content is acceptable but posted in the wrong place. | Supplier promotion posted in a discussion group moved to supplier area or removed pending advert approval. |
| Request member amendment | The post has value but needs safer wording. | Remove organisation name, anonymise scenario, reframe allegation as learning question. |
| Restrict visibility | The resource may be suitable for a smaller verified group only. | Sensitive professional template that should only be visible to verified housing members. |
| Close comments | The content is acceptable but discussion has become circular or hostile. | Repeated argument after moderator warning. |
7. Member-generated content rules
Do not upload or post resident-identifiable information, live case details or personal data unless it has been lawfully anonymised and there is a clear right to share it.
Do not post confidential employer documents, internal reports, Board papers, legal advice, procurement materials or commercially sensitive information without permission.
Do not name individual staff members negatively or invite pile-ons against individuals.
Do not make unverified allegations about organisations or people.
Do not upload resources unless you own them, created them, have permission to share them or can lawfully license them under the applicable OpenThoughts sharing terms.
Do not use the platform to harvest leads, scrape member data or commercially exploit shared resources outside the permitted licence.
Do not impersonate another person, organisation, supplier, regulator, professional body or employer.
Do not use logos, badges, images or organisational names in a way that falsely implies endorsement, partnership or approval.
Declare AI-generated or AI-assisted content where relevant and check it before sharing.
Use plain, fair, professional language and focus on issues, processes, learning and improvement.
8. Supplier and advertiser moderation
Supplier and advertiser content requires additional moderation because OpenThoughts must remain procurement-neutral and avoid any impression that supplier presence equals endorsement, recommendation, due diligence approval or fitness for purpose.
| Supplier / advertiser issue | Moderation response |
|---|---|
| Unauthorised advertising in member discussions | Remove post, warn supplier/member, direct to approved advert route. |
| Supplier lead harvesting or scraping | Suspend access pending review; consider permanent removal and contract termination. |
| Misleading claims of endorsement | Remove or amend wording; require corrected copy; record breach. |
| Unverified performance claims | Request evidence, add caveat or remove claim. |
| Use of member details for unsolicited sales | Investigate as supplier misuse; restrict account; escalate under supplier terms. |
| Sponsored content not clearly labelled | Hide until labelled and approved. |
| Supplier complaint about member criticism | Review for fairness, evidence, defamation and tone. Do not remove fair, evidence-based discussion simply because it is inconvenient. |
| Repeat supplier breach | Suspend or terminate supplier access; remove directory listing or advert; record reason. |
9. Personal data in content
If content appears to contain personal data, OpenThoughts should treat it as a priority moderation issue. User-generated content can itself be personal data, and moderation activities may involve processing account data, content data, reports and decision records. The platform should follow its Data Protection Policy, Breach Response Procedure and DPIA decisions.
Hide or remove content containing resident-identifiable information as soon as reasonably possible.
Record what was found, where it was found, who reported it, when action was taken and what action was taken.
Assess whether the issue is a personal data breach and whether ICO or individual notification may be required.
Do not repost the content in moderation discussions or emails unless necessary and secure.
Where possible, preserve a secure evidence copy with restricted access if needed for investigation.
Tell the uploader what went wrong and how to avoid repetition.
Apply account restrictions where the upload was reckless, repeated or deliberate.
10. Safeguarding-style and urgent risk content
OpenThoughts is not an emergency, safeguarding, complaints, repair, ASB, domestic abuse, case management, legal or risk escalation route. Moderation should not attempt to manage live cases through the platform.
Remove or hide resident-identifiable details from urgent risk posts.
Reply with the approved “do not post urgent risk” wording and direct the member to their employer’s safeguarding, emergency, ASB, complaints, repairs or risk procedure.
Where content indicates an immediate threat to life or serious harm, follow the internal escalation procedure and seek appropriate advice.
Record the moderation action and outcome.
Consider warning or restricting users who repeatedly post live case details after being told not to.
11. Reporting content
Every member-generated page should include a visible “Report this” route. Reports should feed into a central moderation inbox or dashboard and be triaged according to risk.
| Report category | Examples | Target first action |
|---|---|---|
| Personal data | Resident name, address, case details, staff personal data, phone number. | Same day where possible; urgent if high risk. |
| Copyright or attribution | Unlicensed resource, missing creator, wrong licence, misuse of logo. | Within 2 working days; faster if credible rights issue. |
| Abusive content | Harassment, hate, bullying, intimidation. | Same day where possible. |
| Confidential information | Internal employer document, Board paper, legal advice, procurement file. | Same day where possible. |
| Spam or supplier misuse | Lead harvesting, sales spam, scraping, misleading advert. | Within 2 working days; immediate for scams. |
| Broken attribution | Creator not named, wrong source, missing Creative Commons wording. | Within 5 working days. |
| Accessibility issue | Unreadable file, missing alt text, inaccessible PDF, poor contrast. | Within 5 working days or added to improvement log. |
| Safeguarding or urgent risk | Live case, risk of harm, emergency or vulnerability issue. | Urgent triage; signpost away from platform. |
| Defamation/reputation risk | Unverified allegation, personal attack, naming staff negatively. | Same day where possible. |
12. What happens after a report
A report is received through the “Report this” form, email route or admin flag.
The report is logged with date, time, URL, content type, reporter category and risk category.
A moderator carries out initial triage and decides whether content should remain visible, be hidden, be restricted or be removed immediately.
The moderator reviews the content against this policy, the Acceptable Use Policy, Terms, data protection policies, copyright/takedown process, safeguarding warning and supplier/advertiser terms as relevant.
Where needed, the moderator asks the uploader, rights holder, supplier or complainant for more information.
A decision is recorded with the reason and action taken.
The uploader and reporter may be notified where appropriate, proportionate and safe.
The matter may be escalated to the founder/platform owner, legal adviser, data protection lead or supplier contract owner where risk is high.
Repeat issues are added to the member, supplier or advertiser conduct history.
Appeal rights are offered where the decision allows appeal.
13. Decision categories
| Decision | Meaning |
|---|---|
| No action | The content does not breach policy or the report is not substantiated. |
| Monitor | The content remains live but is watched because risk may develop. |
| Informal guidance | Member receives advice about safer wording, anonymisation or posting expectations. |
| Edit agreed | Content is amended by the member or moderator to remove a minor issue. |
| Moderator edit | OpenThoughts edits limited content to remove immediate risk, such as accidental personal data or broken attribution. |
| Label added | AI-assisted, sponsored, member-submitted, adapted, attribution pending or similar transparency label is added. |
| Hide pending review | Content is temporarily unavailable while checks take place. |
| Remove content | Content is deleted or permanently unpublished. |
| Restrict account | Account functions are limited, such as upload rights or posting rights. |
| Temporary suspension | Account access is paused while the matter is investigated or as a sanction. |
| Permanent removal | Membership, supplier access or advertiser access is terminated. |
| External escalation | Matter is referred for legal, data protection, security, safeguarding-style or law enforcement advice where appropriate. |
14. Appeals
Moderation decisions should usually be appealable where content is removed, an account is restricted, a member is suspended, a supplier listing is removed or an advertiser is sanctioned. Appeals should be handled under the Complaints and Appeals Policy.
Appeals must explain what decision is being challenged and why the member, supplier or advertiser believes it was wrong.
Appeals should normally be submitted within 10 working days of the decision notice.
A different reviewer should consider the appeal where practical.
OpenThoughts may uphold, vary or overturn the original decision.
OpenThoughts may refuse repeated appeals that raise no new information or attempt to reopen a final decision.
Immediate safety, personal data, copyright, safeguarding-style, malware, abuse or legal risk removals may remain in place while an appeal is considered.
15. Account restrictions, suspension and permanent removal
| Action | When it may apply | Examples |
|---|---|---|
| Warning | Low-level or first-time breach where risk is limited and the member is likely to learn. | Minor attribution omission, accidental promotional post, poor wording. |
| Upload rights restricted | Risk relates to resources or files. | Repeated upload declaration errors, branded resources without permission, unsafe file types. |
| Posting rights restricted | Risk relates to forums or comments. | Repeated hostile posting, circular arguments, repeated naming of individuals. |
| Temporary suspension | Serious issue, investigation needed or repeated breach after warning. | Potential confidential document upload, abusive content, supplier misuse. |
| Permanent removal | Severe, deliberate, repeated or unsafe behaviour. | Malware, doxxing, deliberate resident data upload, impersonation, harassment, lead harvesting, repeated unlawful uploads. |
| Supplier/advertiser contract termination | Commercial partner breaches platform rules or trust requirements. | False endorsement claims, scraping, spam, misuse of member data, repeated misleading adverts. |
16. Evidence retention
Moderation records should be retained proportionately so that OpenThoughts can evidence fair process, support appeals, manage repeat misuse and respond to legal, data protection, copyright or supplier issues. Records should not be kept for longer than necessary and should be managed under the Records Retention Schedule.
| Record type | Suggested retention | Notes |
|---|---|---|
| Routine content report with no action | 12 months | Useful for trend monitoring and repeat bad-faith reporting. |
| Content removed for low-level breach | 24 months | Retain decision, link, reason and notice sent. |
| Personal data incident moderation record | As per breach procedure, normally 6 years for significant incidents | Coordinate with breach log and data protection register. |
| Copyright/IP takedown record | 6 years after closure | Retain complaint, evidence, decision and correspondence. |
| Supplier/advertiser breach record | Contract term plus 6 years | Coordinate with supplier terms and contract records. |
| Suspension or permanent removal decision | 6 years after account closure | Retain enough to defend decision and prevent re-registration misuse. |
| Appeal record | 6 years after final outcome | Retain appeal, review, outcome and rationale. |
| Malware/security incident | 6 years or in line with cyber incident procedure | Coordinate with security logs and breach response. |
17. Moderation register
OpenThoughts should maintain an internal moderation register. The register does not need to be public, but it should be complete enough to evidence consistency and learning.
| Field | Purpose |
|---|---|
| Report ID | Unique reference for each moderation matter. |
| Date and time reported | Supports response-time tracking. |
| Reporter category | Member, supplier, advertiser, third party, admin, automated alert. |
| Content URL or location | Where the content appeared. |
| Content type | Forum post, resource upload, supplier profile, advert, comment, profile, message. |
| Risk category | Personal data, copyright, abuse, confidential info, spam, safeguarding, defamation, accessibility, supplier misuse. |
| Initial risk rating | Low, medium, high, urgent. |
| Immediate action | No action, hidden, removed, restricted, escalated. |
| Decision and rationale | Why the final decision was reached. |
| Member/supplier notified | Date and method of notification. |
| Appeal offered / received | Appeal status and outcome. |
| Repeat breach flag | Links to member or supplier history. |
| Learning action | Policy, system, wording or training improvement. |
18. Internal workflow
| Stage | Action | Owner |
|---|---|---|
| 1. Intake | Receive report through Report This, email, admin flag or automated alert. | Moderator / administrator |
| 2. Triage | Classify risk and decide whether immediate hiding/removal is needed. | Moderator |
| 3. Secure evidence | Capture enough evidence proportionately; restrict access for high-risk content. | Moderator / platform owner |
| 4. Apply policy | Review against relevant policies and terms. | Moderator |
| 5. Escalate if required | Refer legal, data protection, security, supplier or urgent risk matters. | Platform owner |
| 6. Decide | No action, edit, label, hide, remove, restrict, suspend or terminate. | Moderator / platform owner |
| 7. Notify | Notify uploader, reporter, supplier or advertiser where appropriate. | Moderator |
| 8. Record | Update moderation register and related logs. | Moderator |
| 9. Appeal | Handle appeal under Complaints and Appeals Policy. | Appeal reviewer |
| 10. Learn | Update guidance, checkboxes, training, filters or page wording. | Platform owner |
19. Website-ready public wording
19.1 Short page introduction
OpenThoughts is here for open, useful and generous thinking across housing. To keep that space safe, fair and trusted, we moderate content where needed. We do not remove content simply because someone disagrees with it. We may remove, hide, edit, label or restrict content where it creates legal, safety, confidentiality, copyright, personal data, reputational, supplier misuse or community risk.
19.2 Forum posting notice
Before posting, please check: no resident-identifiable information, no live cases, no urgent safeguarding or emergency concerns, no confidential employer documents, no personal attacks, no unverified allegations and no supplier promotion unless it is in an approved supplier area. Discuss learning, practice and process - not personal attacks.
19.3 Upload notice
Only upload resources you own, created or have permission to share. Do not upload resident data, confidential employer documents, live case information, password-protected files, unsafe files or materials that cannot be shared under the OpenThoughts licence and upload terms. First uploads and sensitive categories may be moderated before publication.
19.4 Report wording
Use “Report this” if you see personal data, copyright concerns, abusive content, confidential information, spam or supplier misuse, broken attribution, accessibility issues, urgent risk content, defamatory wording or anything else that may put people or the platform at risk.
19.5 Removal wording
We may remove content immediately where we believe it creates risk. This includes personal data, confidential information, unlawful uploads, abusive content, malware, urgent risk details, misleading supplier claims, unverified allegations or content that may expose OpenThoughts, members, residents, organisations or suppliers to legal or reputational harm.
19.6 No circular arguments wording
We will look at genuine concerns properly. We will explain our decision where appropriate. We will not enter into circular arguments about obvious breaches, repeated points already answered or attempts to relitigate final decisions without new information.
20. Member notification templates
| Scenario | Suggested wording |
|---|---|
| Content hidden pending review | We have temporarily hidden your content while we review a moderation concern. This does not mean a final decision has been made. We will consider the issue against our Moderation Policy and contact you if we need more information. |
| Personal data removed | We have removed or edited your content because it appeared to include personal data or information that could identify a resident, household, staff member or case. OpenThoughts must not be used to share live case details or resident-identifiable information. |
| Copyright concern | We have restricted access to your resource while we review a copyright, licence or attribution concern. Please provide evidence that you own the material, have permission to share it or can licence it under the applicable OpenThoughts terms. |
| Defamation/reputation concern | We have hidden or edited content because it may create reputational or legal risk. Please reframe the issue around learning, process and evidence, without personal attacks or unverified allegations. |
| Supplier misuse | We have removed promotional content because supplier activity must take place only through approved advertising or supplier routes. OpenThoughts is a learning platform, not an unrestricted sales channel. |
| Warning | This is a moderation warning. Further breaches may lead to restricted access, suspension or removal. Please review the Moderation Policy and Acceptable Use Policy before posting again. |
| Suspension | Your account has been temporarily suspended while we review serious or repeated moderation concerns. We will confirm the outcome and any appeal route when the review is complete. |
21. Moderator checklist
Have I classified the report correctly?
Does the content include personal data or resident-identifiable information?
Does it include confidential employer, supplier or third-party information?
Does it raise safeguarding-style, emergency or live risk concerns?
Does it raise copyright, attribution, licence or logo misuse concerns?
Does it include harassment, discrimination, abuse, threats or personal attacks?
Does it make an allegation about a person or organisation that needs evidence or reframing?
Is the content supplier promotion or lead harvesting outside approved routes?
Is immediate hiding or removal required before review?
Have I recorded the evidence, decision and rationale?
Does the member, reporter, supplier or advertiser need to be notified?
Is this a repeat issue that should affect account status?
Is an appeal available?
Is there any learning for platform wording, forms, upload controls, filters or guidance?
22. Moderator decision matrix
| Risk level | Description | Default action | Examples |
|---|---|---|---|
| Low | Minor issue, no immediate harm, likely accidental. | Guide, edit, label or request amendment. | Missing attribution, wrong group, unclear AI declaration. |
| Medium | Policy breach or avoidable risk, but not urgent or severe. | Hide or edit; warn; record. | Supplier promo in discussion, mild personal criticism, branded template needing permission check. |
| High | Likely legal, safety, data, confidentiality, reputational or serious community risk. | Hide/remove immediately; escalate; consider restriction. | Resident data, confidential report, serious allegation, harassment, copyright complaint. |
| Urgent | Potential immediate harm, serious illegality, security threat or very sensitive personal data. | Remove/restrict immediately; preserve evidence; escalate to platform owner and relevant procedure. | Malware, doxxing, live safeguarding detail, credible threat, CSEA concern. |
23. Interaction with other OpenThoughts policies
| Policy / process | How it connects |
|---|---|
| Terms and Conditions | Moderation powers and member agreement should be built into Terms. |
| Acceptable Use Policy | Defines prohibited behaviour that moderators enforce. |
| Report This Function Policy | Creates the reporting route that triggers moderation. |
| File Upload Risk Controls | Defines upload-specific moderation checks and file restrictions. |
| Creative Commons Licence Decision | Sets licence expectations for shared resources. |
| Copyright, Attribution and Takedown Requests | Handles IP complaints and attribution corrections. |
| AI Usage Policy | Defines declaration and safety rules for AI-generated content. |
| Defamation and Reputational Risk Policy | Supports handling of allegations, personal attacks and organisation criticism. |
| Safeguarding and Do Not Post Urgent Risk Policy | Supports removal/signposting of live cases and urgent risk content. |
| Breach Response Procedure | Used where moderation identifies a personal data breach or security incident. |
| Data Processor Register / DPIA | Ensures moderation tools and workflows are privacy assessed. |
| Supplier / Advertiser Terms | Controls supplier misuse, adverts and lead harvesting. |
| Complaints and Appeals Policy | Handles challenges to moderation decisions. |
| Governance Page | Explains publicly how moderation is run and how decisions are made. |
24. Compliance and guidance notes
OpenThoughts should take advice on whether any parts of the platform are in scope of the UK Online Safety Act, particularly if it allows user-to-user posting, forums, comments, messaging, file-sharing or public interaction. OpenThoughts should also document privacy risks connected with moderation, because moderation may involve processing personal data in posts, reports, account histories and decision records.
Ofcom guidance explains that the Online Safety Act creates duties for certain online services, including user-to-user services, around illegal content and safety systems.
The ICO explains that personal data breaches must be reported to the ICO within 72 hours where required, and that individuals must be informed without undue delay where a breach is likely to result in high risk to rights and freedoms.
ICO security guidance expects organisations to process personal data using appropriate technical and organisational measures.
OpenThoughts should review these duties during DPIA screening, before launch and whenever the platform adds new features such as private messaging, automated moderation, supplier directories or wider public access.
25. Implementation checklist
| Action | Priority | Status |
|---|---|---|
| Publish standalone Moderation Policy page. | Launch critical | Not started |
| Add short posting notice to forum pages. | Launch critical | Not started |
| Add upload moderation notice and upload declaration. | Launch critical | Not started |
| Add “Report this” route on member-generated pages. | Launch critical | Not started |
| Set up moderation inbox/dashboard and register. | Launch critical | Not started |
| Define first-upload moderation queue. | Launch critical | Not started |
| Define sensitive-category review rules. | Launch critical | Not started |
| Create member warning, removal, suspension and appeal templates. | High | Not started |
| Train administrators/moderators on personal data, urgent risk, copyright, defamation and supplier misuse triage. | High | Not started |
| Link policy to Terms, Acceptable Use, Report This, File Upload, AI, Copyright, Supplier Terms and Complaints/Appeals pages. | High | Not started |
| Complete DPIA screening for forums, uploads, moderation and supplier/member interaction. | High | Not started |
| Review Online Safety Act scope and Ofcom guidance before launch. | High | Not started |
| Review moderation metrics monthly during launch period. | Medium | Not started |
| Run six-month policy review after launch. | Medium | Not started |
26. Final recommended decision
OpenThoughts should adopt this Moderation Policy as a launch-critical control. The platform’s ambition is to be open, generous and useful, but openness without operational moderation would expose residents, members, employers, suppliers and the founder-owned platform to avoidable risk. The right balance is not heavy-handed censorship. The right balance is clear expectations, visible reporting, proportionate intervention, proper records, fair appeals and firm action against unsafe, unlawful, abusive, confidential, misleading or commercially exploitative behaviour.
Recommended final wording for the policy decision:
OpenThoughts will protect open sector learning by moderating content where needed. We welcome challenge, discussion and different views, but we will remove or restrict content that puts residents, members, organisations, suppliers, advertisers or the platform at risk. We will look at genuine concerns properly. We will not enter into circular arguments about obvious breaches.
Appendix A - Internal moderation record template
| Field | Entry |
|---|---|
| Report ID | |
| Date/time reported | |
| Reporter name/contact if provided | |
| Reporter category | |
| Content URL/location | |
| Content type | |
| Reported issue | |
| Risk category | |
| Risk level | |
| Immediate action taken | |
| Evidence captured and secure location | |
| Uploader/member/supplier | |
| Policy sections applied | |
| Decision | |
| Rationale | |
| Notification sent | |
| Appeal offered | |
| Appeal outcome | |
| Repeat breach flag | |
| Learning/action required | |
| Closed date |
Appendix B - Sources and reference points
Reference points used when strengthening this policy include:
Ofcom guidance for providers of online services about how to comply with Online Safety Act duties, including illegal content and user-to-user service considerations.
Ofcom March 2026 online safety industry bulletin on duties to report detected and unreported child sexual exploitation and abuse content where applicable.
ICO guidance on personal data breaches, including the 72-hour reporting expectation where notification is required.
ICO guidance on data security and appropriate technical and organisational measures under UK GDPR.
OpenThoughts internal policy suite: Acceptable Use, Report This, File Upload Risk Controls, AI Usage, Copyright Takedown, Defamation/Reputation Risk, Safeguarding and Do Not Post Urgent Risk, Supplier/Advertiser Terms, Procurement Neutrality, DPIA Screening, Data Processor Register and Complaints and Appeals.
Policy 03Report This Function Policy
Report This Function Policy and Implementation Decision
A full and strengthened policy for member reporting, content safety, platform trust and rapid issue triage
| Field | Detail |
|---|---|
| Document owner | OpenThoughts Founder / Platform Owner |
| Applies to | All member-generated pages, forum posts, groups, comments, uploads, resources, supplier areas, adverts and public-facing interaction routes |
| Recommended status | Adopt before launch as a mandatory platform safety control |
| Version | 1.0 |
| Review cycle | Every 6 months for the first year, then annually or after a significant incident |
| Language | UK English |
Decision summary: OpenThoughts should introduce a visible, consistent and easy-to-use “Report this” function on every member-generated page. This should not be treated as a minor website feature. It should be a core part of the platform safety system, helping members flag risk early and giving OpenThoughts a clear record of what was reported, when, by whom and how it was resolved.
1. Purpose of this policy
This policy sets out the decision, rules and operating process for the OpenThoughts “Report this” function. It is designed to help members report concerns about content, uploads, behaviour or technical barriers in a clear and structured way. It supports the wider OpenThoughts ethos: open-source thinking, professional generosity, transparency, safety, fair challenge and responsible collaboration across the housing sector.
2. Recommended decision for OpenThoughts
The best solution is to build “Report this” into the platform from the start and to place it wherever members can read, upload, comment, discuss, advertise or interact. OpenThoughts should not rely on members finding a generic contact page, emailing informally or raising concerns in public comments. A visible reporting route creates trust, protects members, reduces legal and safeguarding risk, supports accessibility and makes moderation evidence-led.
3. Scope
This policy applies to all areas of OpenThoughts where a concern could arise, including forums, groups, comments, member profiles, resource libraries, uploaded files, images, supplier profiles, adverts, sponsored content, event listings, newsletters, AI-assisted material, shared templates and any future collaborative tools.
4. Core principle
Members become part of the safety system. Reporting should feel simple, fair and constructive. It should not be framed as punishment or policing. It should be framed as shared stewardship: protecting residents, members, employers, suppliers, originators, accessibility, copyright, data protection and the integrity of the platform.
5. Formal policy position
| Policy decision | OpenThoughts position |
|---|---|
| Default position | Every member-generated page should include a clear “Report this” route. |
| Visibility | The function should be visible without needing to scroll to the site footer. It should appear near the content it relates to. |
| Categories | The report form should use structured categories so issues can be triaged quickly. |
| Fairness | Reported content should be reviewed before action wherever possible, except where temporary removal is needed to reduce immediate risk. |
| Evidence | Every report should create a record in an internal report register. |
| Tone | The process should be calm, factual and proportionate. OpenThoughts will not enter into circular arguments about obvious breaches. |
6. Report categories
| Report type | What it covers |
|---|---|
| Personal data | Content appears to include personal data, resident details, names, addresses, contact details, reference numbers, case histories, identifiable circumstances, images or other information that could identify a person. |
| Copyright or IP issue | Content may have been uploaded without permission, copied from another source, incorrectly licensed, adapted without rights, or may use logos, images, templates or documents that the uploader is not entitled to share. |
| Abusive, discriminatory or harmful content | Content may be abusive, bullying, harassing, discriminatory, hateful, intimidating, threatening, sexually inappropriate or otherwise inconsistent with the OpenThoughts conduct standards. |
| Confidential information | Content appears to include confidential employer material, internal documents, unpublished strategies, commercial information, tender material, legal advice, HR information, operational security details or restricted housing-sector information. |
| Spam, promotion or supplier misuse | Content appears to be spam, repeated self-promotion, inappropriate selling, lead harvesting, unsolicited sales contact, procurement pressure, undeclared sponsored content or misuse of the supplier/advertiser space. |
| Broken or missing attribution | Content may need corrected author details, licence wording, source acknowledgement, Creative Commons attribution, original creator recognition or clearer adaptation wording. |
| Accessibility issue | Content, documents, images, videos, forms or pages are difficult to access, not screen-reader friendly, missing alternative text, poorly structured, colour-dependent, not keyboard accessible or otherwise presenting an accessibility barrier. |
| Urgent risk or safeguarding concern | Content appears to include a live safeguarding, domestic abuse, ASB, health, safety, homelessness, repair emergency or other urgent risk concern. OpenThoughts is not an emergency or case-management route, but moderators need to remove personal details and direct the poster to the proper organisational route. |
| Defamation or reputational risk | Content makes unverified allegations, names individual staff members negatively, accuses an organisation of unlawful behaviour without public evidence, or creates avoidable legal or reputational risk. |
| Other concern | A catch-all route for issues not covered above, with a free-text explanation field. |
7. Where the “Report this” function should appear
| Location | Required placement |
|---|---|
| Forum posts and comments | Report link beside each post and comment. |
| Group pages | Report link for the group description, pinned content and each discussion thread. |
| Resource library items | Report link on the resource landing page and beside each downloadable file. |
| Uploaded templates and documents | Report link near download button and licence/attribution information. |
| Member profiles | Report link where profile misuse, impersonation or inappropriate content may be an issue. |
| Supplier directory | Report link on supplier listing cards and profile pages. |
| Advert pages and sponsored content | Report link on advert landing pages and sponsored articles. |
| Event listings | Report link where a listing is inaccurate, misleading, inaccessible or inappropriate. |
| Search results | Where technically possible, include “Report” on individual result cards or provide report route from the result destination page. |
| Footer and help area | A general “Report a concern” page should also exist for members who cannot find the content-specific report button. |
8. Website-ready wording
8.1 Button wording
Report this
Report a concern
Report content
Report an issue with this resource
8.2 Short notice near the button
Suggested wording: Use “Report this” to tell us about personal data, copyright concerns, abusive content, confidential information, spam or supplier misuse, broken attribution or accessibility issues. Reports help keep OpenThoughts safe, fair and useful for the housing sector.
8.3 Full report page wording
Suggested wording: OpenThoughts is built on shared trust. If you see something that looks wrong, risky, inaccessible, incorrectly attributed or not suitable for the platform, please report it. We will review genuine concerns properly and take proportionate action. Reporting does not automatically mean content will be removed, but it does mean the concern will be recorded and considered.
8.4 Urgent risk wording
Suggested wording: Do not use OpenThoughts to report emergencies, safeguarding concerns, live resident cases, repairs, ASB, domestic abuse, homelessness or health and safety risks. Follow your own organisation’s emergency, safeguarding, complaints, repairs, ASB, domestic abuse or risk escalation procedure. If you believe content on OpenThoughts includes live personal or urgent risk information, report it so it can be reviewed and, where needed, removed or anonymised.
9. Report form fields
| Field | Requirement |
|---|---|
| Reporter name | Auto-populated for logged-in members where possible. |
| Reporter email | Auto-populated where possible and used only for follow-up about the report. |
| Content URL | Auto-captured from the page where the report button was clicked. |
| Content type | Forum post, comment, resource, upload, supplier profile, advert, member profile, event listing, group page or other. |
| Report category | Dropdown with the categories listed in this policy. |
| Free-text explanation | What is the concern? What should we look at? Keep this factual. |
| Urgency | Low, medium, high, immediate review needed. |
| Evidence upload | Optional screenshots or evidence, with a warning not to upload further personal, confidential or sensitive material unless necessary. |
| Attribution correction details | For attribution reports: original creator, correct source, licence, link and proposed wording. |
| Copyright/IP confirmation | For IP reports: confirmation that the reporter is the rights-holder or is authorised to act, or is raising a good-faith concern. |
| Accessibility details | Device, browser, assistive technology if relevant, page/resource affected and the barrier experienced. |
| Confirmation checkbox | “I confirm this report is made in good faith and is as accurate as I can make it.” |
10. Triage workflow
| Stage | Action |
|---|---|
| 1. Report received | System creates an internal report reference and sends an acknowledgement where appropriate. |
| 2. Initial risk screen | Moderator checks whether there is immediate risk: personal data, safeguarding-style information, confidential material, abusive content, serious copyright risk, defamation or security concern. |
| 3. Temporary action | Content may be temporarily hidden, restricted, anonymised or locked while reviewed if leaving it live creates risk. |
| 4. Review | OpenThoughts reviews the content, report details, relevant policies and any evidence. |
| 5. Decision | Decision may include no action, correction, attribution edit, warning, content edit, temporary removal, permanent removal, account restriction, supplier action or escalation. |
| 6. Communication | Reporter and, where appropriate, the content originator are informed of the outcome in clear and proportionate terms. |
| 7. Record keeping | Outcome, evidence, decision reason and learning are logged in the internal report register. |
| 8. Pattern review | Repeated reports, repeat misuse or emerging risks are reviewed to improve platform controls. |
11. Response times
| Type | Target response |
|---|---|
| Immediate or high risk | Initial review as soon as reasonably possible. Examples: personal data, safeguarding-style details, confidential documents, serious abuse, threats, credible legal risk or security concern. |
| Standard reports | Acknowledge within 3 working days where a response is needed. Aim to complete review within 10 working days. |
| Complex IP, data protection or legal-risk reports | Acknowledge within 3 working days. Provide an update if review will take longer than 10 working days. |
| Accessibility reports | Acknowledge within 5 working days where contact details are provided. Fix immediately where simple; otherwise add to the accessibility improvement log. |
| Appeals or disputed outcomes | Handled through the Complaints and Appeals Policy where the reporter or originator disagrees with the decision. |
12. Action matrix
| Concern | Likely action |
|---|---|
| Personal data | Hide immediately if identifiable or risky; remove, redact or anonymise; notify uploader; consider data breach procedure if personal data has been exposed. |
| Copyright/IP | Temporarily remove where credible; request evidence; correct attribution where appropriate; restore only if rights are clear. |
| Abuse/discrimination | Remove or edit if breach is clear; warn member; restrict account for serious or repeated issues. |
| Confidential information | Hide immediately if credible; contact uploader; do not republish unless permission and suitability are clear. |
| Spam/supplier misuse | Remove promotional misuse; warn supplier/member; apply advertiser terms; restrict repeat offenders. |
| Broken attribution | Correct attribution promptly where evidence is clear; record the correction. |
| Accessibility issue | Fix page/resource if possible; provide alternative format where reasonable; log wider improvement. |
| Urgent risk/casework | Remove personal details; remind poster OpenThoughts is not a case route; signpost to organisational procedure. |
| Defamation/reputational risk | Hide or edit while reviewed; require factual framing; remove unverified allegations or negative naming of individuals. |
13. Internal report register
OpenThoughts should maintain an internal register for all meaningful reports. This does not need to be public, but it should be structured enough to evidence fair decision-making, learning and accountability.
| Register field | Purpose |
|---|---|
| Report reference | Unique ID for the report. |
| Date received | Date and time report was submitted. |
| Reporter details | Name, member ID and contact details where available. |
| Content URL | Direct link to the reported content. |
| Category | Report category selected. |
| Initial risk rating | Low, medium, high, urgent. |
| Temporary action | Whether content was hidden, locked, removed or left live. |
| Policy references | Relevant policies considered. |
| Outcome | No action, edit, attribution correction, removal, warning, restriction, escalation. |
| Decision reason | Brief explanation. |
| Date closed | Closure date. |
| Learning | System, wording, moderation or training improvement needed. |
| Appeal status | Whether appealed and outcome. |
14. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Platform Owner / Founder | Owns the policy, makes final decisions on high-risk cases, approves serious account or supplier action and ensures learning is acted on. |
| Moderator / Administrator | Reviews reports, takes proportionate action, records decisions and escalates high-risk issues. |
| Members | Report concerns in good faith, avoid public pile-ons and do not use reporting to harass, silence fair challenge or pursue personal disputes. |
| Uploaders / Originators | Only upload material they are entitled to share, respond constructively to concerns and correct errors where needed. |
| Suppliers / Advertisers | Comply with advertiser terms, avoid misuse of member information and respond quickly to complaints involving their content or behaviour. |
| Technical provider | Ensures the report function works, captures necessary metadata, preserves evidence and supports accessibility. |
15. Misuse of the report function
OpenThoughts should welcome good-faith reporting but protect the platform from misuse. The report function must not be used to harass other members, suppress fair professional debate, retaliate against challenge, create circular arguments, submit knowingly false complaints or repeatedly re-open decisions without new evidence.
| Misuse type | Response |
|---|---|
| Good-faith error | Explain the outcome and close the report. |
| Repeated unfounded reports | Warn the member and provide guidance on appropriate use. |
| Harassing or retaliatory reports | Restrict use of the report function or take conduct action. |
| False or malicious report | Apply member conduct sanctions, including suspension or removal where serious. |
| Supplier misuse | Apply supplier/advertiser terms, including removal of adverts or account restrictions. |
16. Technical and accessibility requirements
| Requirement | Detail |
|---|---|
| Persistent location | Report button visible near content and available on mobile. |
| Keyboard accessible | Report function usable without a mouse. |
| Screen-reader label | Button must have clear accessible name such as “Report this post”. |
| Plain language | No legalistic wording in the form. |
| Dropdown categories | Structured categories as listed in this policy. |
| Evidence preservation | System should capture URL, page title, content ID, user ID where available and timestamp. |
| Privacy by design | Only collect information needed to assess the report. |
| Confirmation message | Reporter receives a clear message explaining what happens next. |
| Audit trail | Internal log should record action and decision history. |
| Rate limiting / spam protection | Prevent automated misuse of the form. |
17. Member-facing sign-up and upload wording
17.1 Sign-up wording
Suggested checkbox: I understand that OpenThoughts includes a “Report this” route so members can flag personal data, copyright concerns, confidential information, abusive content, spam, supplier misuse, attribution issues and accessibility barriers. I agree to use this route in good faith and not as a way to harass, silence or retaliate against others.
17.2 Upload wording
Suggested checkbox: I understand that uploaded content may be reported by other members if it appears to include personal data, confidential information, copyright issues, broken attribution, accessibility barriers or other platform risks. I agree that OpenThoughts may temporarily hide, edit, remove or restrict access to content while a report is reviewed.
18. Links with other OpenThoughts policies
| Related policy | Connection |
|---|---|
| Terms of Use | The report function supports enforcement of member rules. |
| Privacy Policy / Data Protection Policy | Reports involving personal data may trigger privacy review or breach assessment. |
| Breach Response Procedure | Used where reported content suggests a personal data breach. |
| Copyright, Attribution and Takedown Requests Policy | Used for copyright, licence, attribution and IP reports. |
| Creative Commons Licence Decision | Used when considering whether shared content is correctly licensed or attributed. |
| Safeguarding and Do Not Post Urgent Risk Policy | Used where content includes live resident cases or urgent risk information. |
| AI Usage Policy | Used where AI-generated or AI-assisted content is undeclared, misleading or unsafe. |
| Defamation and Reputational Risk Policy | Used for allegations, negative naming, legal risk or reputational harm. |
| Procurement Neutrality Disclaimer | Used for supplier endorsement concerns or supplier misuse. |
| Complaints and Appeals Policy | Used when a reporter, member, supplier or originator wants to challenge a decision. |
| Accessibility Statement Policy | Used for reported accessibility barriers and improvement tracking. |
19. Implementation checklist
| Step | Action |
|---|---|
| 1 | Create a public “Report a concern” help page. |
| 2 | Add visible “Report this” links/buttons to all member-generated content types. |
| 3 | Build the report form with required categories and evidence fields. |
| 4 | Create an internal report register. |
| 5 | Agree moderator triage roles and escalation thresholds. |
| 6 | Add sign-up and upload checkbox wording. |
| 7 | Add report wording to forum posting pages and resource upload pages. |
| 8 | Test report process using dummy personal data, IP, spam, accessibility and confidential information scenarios. |
| 9 | Check accessibility of the button and form using keyboard and screen-reader testing. |
| 10 | Review report trends monthly after launch for the first six months. |
20. Final recommendation
OpenThoughts should adopt the “Report this” function as a launch-critical control, not a later enhancement. The platform is designed to encourage shared learning, document sharing, professional debate and supplier/member interaction. That creates enormous value, but it also creates foreseeable risks around personal data, copyright, confidentiality, accessibility, reputational harm and commercial misuse. A visible, well-governed reporting function allows the community to help protect the platform while giving OpenThoughts a fair, consistent and evidence-led process for dealing with concerns.
Appendix A: Suggested report acknowledgement
Thank you for reporting this. We have received your concern and will review it in line with the OpenThoughts Report This Function Policy. Reporting content does not automatically mean it will be removed, but it will be considered. If the issue appears urgent or high risk, we may temporarily hide or restrict the content while we review it.
Appendix B: Suggested outcome wording - no action
We have reviewed the content you reported. Based on the information available, we are not taking further action at this stage. This does not prevent you from providing new evidence or using the Complaints and Appeals route if you believe the decision has not been handled properly.
Appendix C: Suggested outcome wording - action taken
We have reviewed the content you reported and have taken action. This may include editing, correcting attribution, restricting access, removing content or contacting the relevant member or supplier. For privacy and fairness reasons, we may not be able to share every detail of the action taken.
Policy 04File Upload Risk Controls Policy
File Upload Risk Controls Policy
Policy, implementation decision and operating procedure for the OpenThoughts resource library, forums and member-generated uploads
| Recommended decision |
|---|
| OpenThoughts should allow file uploads because the resource library is central to the platform value, but uploads must be treated as a controlled, moderated and risk-managed function. The recommended approach is to launch with a restricted safe-file model: approved document, image and archive types only; no executable files; no resident personal data; no confidential employer material; no password-protected files unless specifically approved; virus/malware scanning; visible metadata warnings; upload declarations; first-upload moderation; and enhanced admin review for branded, sensitive, supplier, legal, safeguarding, safety and policy categories. |
| Item | Detail |
|---|---|
| Document owner | OpenThoughts Founder / Platform Owner |
| Applies to | Members, contributors, moderators, administrators, suppliers, advertisers and anyone uploading or submitting material to OpenThoughts |
| Version | 1.0 - approved and implemented |
| Status | Recommended for adoption before resource library launch |
| Review cycle | At launch, after first 90 days, then every 6 months or following a major incident, platform change or legal/policy update |
| Related documents | Terms of Use; Membership Rules; Creative Commons Licence Decision; Copyright, Attribution and Takedown Requests Policy; AI Usage Policy; Safeguarding and Do Not Post Urgent Risk Policy; Data Protection Policy; DPIA Screening; Breach Response Procedure; Report This Function Policy; Supplier / Advertiser Terms |
Purpose of this policy
OpenThoughts is designed as a collaborative, open-source thinking platform for the social housing sector. Its value relies on members being able to share templates, learning, policies, tools, examples, presentations, frameworks and practical resources. That same resource library also creates risk: copyright infringement, personal data exposure, confidential employer documents, malware, misleading professional material, reputational harm, unsafe advice, metadata leakage and supplier misuse.
This policy sets out the decision, rules, technical controls, moderation approach, member declarations and internal operating procedure needed to make file sharing safe, trusted and proportionate.
| Plain-English position for members |
|---|
| Share useful resources. Do not upload anything you do not have the right to share. Do not upload resident personal data, live cases, confidential employer documents, urgent safeguarding or safety information, executable files, malware, misleading content or material that could put someone at risk. Check your files before upload. OpenThoughts may review, remove, quarantine or reject files to protect members, residents, organisations and the platform. |
1. Scope
This policy applies to all files, resources, attachments, images, templates, presentations, spreadsheets, forms, guides, recordings, screenshots, graphics, zipped resources and supporting documents uploaded to OpenThoughts.
It applies to resource library uploads, forum attachments, group files, profile images, event documents, blog attachments, supplier/advertiser materials, downloadable resources and any future upload function.
It covers files uploaded directly to the platform and files submitted by email, webform, cloud link or other transfer route for publication on OpenThoughts.
2. Core principles
| Principle | What it means in practice |
|---|---|
| Useful sharing, not uncontrolled publishing | OpenThoughts should support practical sector learning while preventing avoidable harm. |
| No resident data | The platform is not a case management, safeguarding, complaints, repairs, ASB, domestic abuse or emergency route. Live resident information must not be uploaded. |
| Rights before reach | Members must only upload content they created, own, are authorised to share, or can licence under the OpenThoughts licence model. |
| Safe by default | Riskier file types, first uploads, branded content, sensitive categories and supplier materials should receive stronger checks. |
| Transparency | Members should know what they are agreeing to before upload, including licence, attribution, moderation and takedown rules. |
| Human accountability | AI-generated or AI-assisted materials may be uploaded where declared, checked and not presented as unverified professional advice. |
| Proportionate moderation | OpenThoughts should not become a legal reviewer of every file, but must have reasonable controls and a clear response route when concerns are raised. |
3. Recommended launch decision
The best solution for OpenThoughts is to adopt a staged upload model:
| Stage | Decision |
|---|---|
| Stage 1 - Launch | Only approved file types; maximum file size limits; upload declaration; automatic malware scanning; first-upload moderation; admin review for high-risk categories; no public direct upload without sign-in. |
| Stage 2 - Stabilisation | Review upload trends, rejected files, report categories, takedowns and user feedback after 90 days. Adjust size limits and moderation thresholds. |
| Stage 3 - Mature platform | Consider trusted contributor status, bulk uploads, API/resource integrations or public collections only where incident levels and moderation capacity support them. |
| Decision statement |
|---|
| OpenThoughts should not launch with unrestricted file uploads. It should launch with controlled uploads for verified members only, supported by technical controls, human moderation, clear declarations, visible report routes and a written takedown/escalation process. |
4. File types allowed and prohibited
| Category | Recommended allowed types | Controls / notes |
|---|---|---|
| Documents | PDF, DOCX, ODT, RTF, TXT | PDF preferred for final guidance; DOCX allowed for editable templates. Macro-enabled files are not allowed. |
| Spreadsheets | XLSX, ODS, CSV | XLSM and macro-enabled files not allowed. CSV should be checked for personal data before upload. |
| Presentations | PPTX, ODP | PPTM and macro-enabled files not allowed. |
| Images | JPG, JPEG, PNG, SVG, WEBP | Images must not include identifiable residents, staff ID badges, addresses, live case details or confidential screenshots unless fully authorised and anonymised. |
| Archives | ZIP only, by exception | ZIP uploads should be restricted to approved contributors or admin-reviewed packages. No nested executables or password-protected archives without approval. |
| Audio/video | MP3, MP4, MOV, WAV by admin approval | Only where necessary, rights are clear and participants have consented. Consider external hosting and transcript checks. |
| Prohibited category | Examples | Action |
|---|---|---|
| Executable and script files | EXE, MSI, BAT, CMD, COM, SCR, PS1, JS, JAR, APK, APP, DMG, ISO, DLL, VBS, SH, PY, PHP, ASP, HTML uploads that can run scripts | Blocked automatically. |
| Macro-enabled Office files | DOCM, XLSM, PPTM | Blocked automatically. Ask member to upload a macro-free version. |
| Password-protected or encrypted files | Encrypted PDF/ZIP/Office files | Blocked unless pre-approved and reviewed by admin through a secure route. |
| Files containing personal data | Resident names, addresses, phone numbers, email addresses, case references, tenancy references, complaint details, repair histories, images of homes that identify individuals | Rejected or removed. Potential data breach review may be required. |
| Confidential employer material | Internal strategies, board papers, procurement documents, HR documents, risk registers, contracts, non-public data, screenshots of internal systems | Rejected unless explicit permission is evidenced. |
| Unsafe professional material | Unverified legal, safeguarding, medical, fire safety or compliance advice presented as fact | Rejected or held for review. |
| Malicious, abusive or unlawful material | Malware, harassment, discriminatory material, defamatory allegations, extremist content, harmful instructions | Removed and escalated according to relevant policies. |
5. Maximum file size controls
| Upload type | Recommended maximum | Rationale / control |
|---|---|---|
| Standard member upload | 25 MB | Applies to common documents, templates and presentations. |
| Images | 10 MB | Encourage compression and accessible alt text. |
| Spreadsheets | 15 MB | Large data files increase risk of hidden personal data and should be admin-reviewed. |
| ZIP package | 50 MB by exception | Admin review required; virus scan and file-type inspection required. |
| Video/audio | 100 MB by admin approval | Only where needed and supported by consent/rights evidence. |
| Supplier/advertiser assets | 25 MB | All branded commercial material should be reviewed before publication. |
OpenThoughts may reduce, increase or vary size limits based on hosting performance, moderation capacity, storage cost, security incidents, accessibility requirements and user need.
6. Upload declaration
Before uploading, members should be required to tick a declaration. The upload should not proceed unless the declaration is completed.
| Mandatory upload declaration wording |
|---|
| By uploading this file, I confirm that: I have the right to share it; it does not contain resident personal data, live case information, confidential employer material or urgent safeguarding/safety concerns; it does not contain malware, executable code, password protection or hidden content that creates risk; I have checked metadata, comments, tracked changes and hidden tabs; I understand OpenThoughts may scan, moderate, remove, quarantine or reject the file; and I agree that accepted member-generated resources may be shared under the OpenThoughts default licence unless a different approved licence or restriction is clearly stated. |
| Checkbox area | Required wording / meaning |
|---|---|
| Rights confirmation | I created this file, own it, or have permission to share it. |
| Licence confirmation | I understand the applicable OpenThoughts licence and attribution requirements. |
| No resident data | This file does not include resident personal data, live cases, addresses, contact details, case references or identifiable images. |
| No confidential material | This file does not include confidential employer, client, supplier, HR, procurement, board, legal or internal system information. |
| Metadata checked | I have checked comments, tracked changes, hidden sheets, speaker notes, document properties and image metadata. |
| AI declaration | I have declared any AI-generated or AI-assisted content where relevant and checked it before sharing. |
| No urgent risk | This file is not being used to report an urgent safeguarding, emergency, ASB, repair, damp and mould, fire safety, health or legal risk. |
| Safe file | This file is not executable, malicious, password-protected or designed to bypass controls. |
7. Metadata warning and hidden content control
OpenThoughts should display a clear metadata warning before upload and should provide member guidance on checking documents before sharing.
| Metadata warning for upload page |
|---|
| Files can contain hidden information such as author names, organisation names, tracked changes, comments, hidden spreadsheet tabs, speaker notes, version history, geolocation, document properties and embedded images. Before uploading, please remove anything you would not want shared with other members. |
| File type | Common hidden risks |
|---|---|
| Word documents | Tracked changes, comments, author name, internal file paths, hidden text, document properties, previous versions. |
| Excel spreadsheets | Hidden sheets, filters, pivot cache, formulas, named ranges, comments, personal data in unused rows, workbook properties. |
| PowerPoint files | Speaker notes, comments, hidden slides, embedded files, author properties, image metadata. |
| PDF files | Author properties, comments, redaction failures, embedded files, OCR text, previous annotations. |
| Images | Location data, embedded names, faces, addresses, whiteboards, ID badges, computer screens. |
| ZIP files | Nested files, unsupported file types, duplicate files, embedded personal data, executable content. |
8. Moderation and review model
| Trigger | Publication approach | Review requirement |
|---|---|---|
| First upload by any member | Hold in moderation queue before publication | Check declaration, file type, obvious personal/confidential data, rights/attribution and category fit. |
| Trusted contributor after good history | Publish subject to automated checks and retrospective sampling | Trust can be removed following reports, rejected uploads or policy breaches. |
| High-risk categories | Admin review before publication | Applies to ASB, domestic abuse, safeguarding, supported housing, fire safety, damp and mould, legal, compliance, procurement, resident vulnerability and employer-branded content. |
| Supplier/advertiser content | Commercial review before publication | Check no implied endorsement, procurement claims, misleading evidence, prohibited wording or unsupported claims. |
| Large uploads / ZIP files | Admin review and deeper file inspection | Check contents, nested files and rights position. |
| Reported files | Temporarily restrict or remove while reviewed where risk is credible | Use Report This workflow, takedown process or breach procedure as required. |
9. Upload risk triage matrix
| Risk level | Examples | Required action |
|---|---|---|
| Low | Generic blank template with no names, no logos, no personal data and clear creator attribution. | May publish after automated checks; sample review. |
| Medium | Editable policy, presentation, branded document, AI-assisted resource, resource based on employer practice, or spreadsheet with formulas. | Moderator review before or shortly after publication depending on contributor status. |
| High | Resource relates to safeguarding, domestic abuse, ASB, damp and mould, fire safety, compliance, legal, HR, procurement, live service failure or reputational risk. | Hold for admin review before publication. |
| Critical | Contains resident personal data, urgent risk, live case details, confidential employer material, malware, executable files, defamatory allegations or suspected breach. | Do not publish. Quarantine/remove, log, notify contributor, escalate to data protection/breach/safeguarding/reputational risk process as appropriate. |
10. Resident data and confidential information rule
| Zero-tolerance rule |
|---|
| OpenThoughts must not be used to upload, share, test, store or discuss live resident cases or personal data. This includes names, addresses, contact details, tenancy references, repair records, complaint details, health information, safeguarding information, domestic abuse information, photographs of identifiable people or homes, and screenshots from internal systems. |
Where a member uploads personal data or confidential material, OpenThoughts should:
remove or restrict access to the file promptly;
log the incident and preserve proportionate evidence;
assess whether the Breach Response Procedure is triggered;
notify the member and explain why the file cannot be used;
where necessary, suspend upload privileges pending review;
use learning to improve upload wording, moderation rules and member guidance.
11. Admin review for branded or sensitive categories
| Sensitive category | Admin review focus |
|---|---|
| Employer-branded templates | Check permission to share, remove confidential wording, consider anonymised or generic version. |
| Supplier-branded resources | Check commercial disclosure, no endorsement wording, claims evidence, procurement neutrality. |
| Legal/compliance materials | Ensure not presented as professional advice. Add disclaimer where needed. |
| Fire safety/building safety | Check not case-specific, not unsafe, not misleading, not urgent risk escalation. |
| Damp and mould / health-related resources | Check no resident health data or urgent repair/case details. |
| Domestic abuse / safeguarding / vulnerability | Check no live risk, identifiable people, confidential protocols or unsafe instructions. |
| ASB/community safety | Check no allegations against named individuals, addresses, incidents or police/case data. |
| Data protection / cyber/security materials | Check no vulnerabilities, credentials, internal system details or unsafe instructions. |
| Procurement/contract materials | Check no confidential tenders, pricing, contracts, commercially sensitive data or supplier bias. |
12. Technical controls to implement
| Control | Requirement |
|---|---|
| Authentication | Only approved, verified members should upload files. Supplier/advertiser upload routes should be separated or reviewed. |
| File type allowlist | Use an allowlist rather than a blocklist. Block executable and macro-enabled files. |
| File size limits | Apply maximum file sizes by type and role. |
| Virus/malware scanning | Scan every upload before publication and after updates where technically possible. |
| Content disposition | Force downloads for risky formats where appropriate rather than rendering active content inline. |
| Storage segregation | Store uploads outside executable directories. Prevent server-side execution from upload locations. |
| Access controls | Limit who can approve, replace, delete or restore uploaded files. |
| Audit logging | Log uploader, date/time, IP/session where lawful, file name, file type, file size, checks, decision and moderator. |
| Version control | Keep controlled versions for published resources and replace unsafe versions cleanly. |
| Backups | Back up published resources securely, but ensure removed harmful files are not accidentally restored publicly. |
| Rate limiting | Prevent bulk spam uploads and automated scraping/abuse. |
| Download monitoring | Monitor unusual download activity where proportionate and disclosed in privacy/cookie notices. |
| Permissions review | Review admin/plugin permissions regularly. |
| Plugin governance | Only use upload plugins with credible maintenance, security updates and appropriate data processing terms. |
13. Internal upload workflow
| Step | Action |
|---|---|
| 1. Member prepares file | Member checks rights, personal data, confidential content, metadata, AI declaration and licence. |
| 2. Upload page warning displayed | Member sees no urgent risk, no resident data, no confidential material and metadata warning. |
| 3. Declaration completed | Upload cannot continue without mandatory checkbox confirmations. |
| 4. Automated validation | System checks account status, file type, file size, malware scan and prohibited extensions. |
| 5. Routing decision | System publishes, holds in moderation or rejects based on risk rules. |
| 6. Moderator review | Moderator checks category, title, description, attribution, obvious risks and file preview. |
| 7. Publication | Resource is published with licence/attribution/disclaimer and Report This link. |
| 8. Monitoring | Reports, takedowns, analytics, repeat issues and moderation samples are reviewed. |
| 9. Escalation | Data breach, safeguarding, IP, defamation, supplier misuse or complaint routes triggered where needed. |
| 10. Learning | Rules, guidance and controls updated following issues or patterns. |
14. Website-ready wording
| Resource library upload page notice |
|---|
| Before you upload, please check the file carefully. OpenThoughts is for sector learning and shared resources, not live casework. Do not upload resident personal data, live cases, confidential employer material, urgent safeguarding or safety concerns, executable files, password-protected files, malware, or anything you do not have the right to share. Your upload may be scanned, reviewed, moderated, removed or rejected. |
| Forum attachment notice |
|---|
| Forum attachments are visible to other members. Do not attach resident details, confidential documents, screenshots from internal systems, unverified allegations, urgent risk information or files you are not authorised to share. Use your organisation’s own escalation routes for live cases and urgent concerns. |
| Sensitive group notice |
|---|
| This group may discuss sensitive themes such as safety, vulnerability, ASB, domestic abuse, damp and mould, homelessness or safeguarding. Please keep discussion general, anonymised and learning-focused. Do not upload live resident cases, personal details, confidential documents or urgent risk information. |
| Supplier upload notice |
|---|
| Supplier and advertiser materials must be accurate, lawful, rights-cleared, accessible and clearly commercial where relevant. Publication on OpenThoughts does not mean endorsement, procurement approval, due diligence completion or fitness for purpose. |
15. Repeated misuse and account controls
| Scenario | Action |
|---|---|
| First low-level issue | File removed or corrected; member reminded of rules. |
| Repeated low-level issues | Upload privileges limited; pre-publication review required. |
| Serious issue | Immediate removal, account review, possible suspension and escalation under relevant policy. |
| Intentional misuse | Account suspension or removal, supplier/advertiser agreement termination, and possible notification to affected parties where appropriate. |
| Malware or deliberate harmful upload | Immediate account restriction and security incident response. |
| Personal data or confidential information exposure | Breach assessment and possible notification/containment actions. |
16. Accessibility requirements for uploads
OpenThoughts should encourage accessible resources. This is important because shared documents may be used by a wide range of housing professionals, residents, community groups and partner organisations.
| Upload type | Accessibility expectation |
|---|---|
| Documents | Use headings, meaningful link text, readable fonts, sufficient contrast and alt text for images. |
| PDFs | Avoid scanned image-only PDFs where possible. Provide accessible source versions when practical. |
| Spreadsheets | Use clear tab names, simple layouts, column headings and avoid colour-only meaning. |
| Presentations | Use slide titles, readable font sizes, alt text and clear reading order. |
| Images | Provide alt text or short descriptions where the image conveys meaning. |
| Video/audio | Provide captions or transcripts where possible, especially for learning resources. |
17. Roles and responsibilities
| Role | Responsibility |
|---|---|
| Platform Owner / Founder | Approves policy, decides risk appetite, oversees serious incidents, reviews performance and ensures controls are funded and maintained. |
| Administrators | Configure technical controls, review high-risk files, manage quarantines, maintain logs and apply account controls. |
| Moderators | Review queued uploads, apply policy consistently, use escalation routes and maintain records. |
| Members | Check files before upload, complete declarations honestly, comply with licence and attribution rules, report concerns promptly. |
| Suppliers / Advertisers | Ensure commercial materials are accurate, rights-cleared, non-misleading and compliant with supplier terms. |
| Technical providers | Provide secure hosting, scanning, access controls, backups, logging and support under appropriate processing terms where applicable. |
18. Records and evidence to keep
| Record | Purpose |
|---|---|
| Upload register | Uploader, file name, category, date/time, version, file size, licence, declaration, decision and moderator. |
| Moderation queue log | Held files, reason for hold, review outcome, date and reviewer. |
| Rejected upload log | Reason, member notified, learning points and whether account action was taken. |
| Removed file log | Reason for removal, report reference, takedown route, decision and restoration outcome if any. |
| Security incident log | Malware, suspicious files, plugin issues, access issues and remedial action. |
| Data breach log | Personal data incidents and decisions under the Breach Response Procedure. |
| Supplier content log | Commercial uploads, approval status, claims review and no-endorsement wording checks. |
| Policy review log | Changes to file types, size limits, moderation thresholds and upload wording. |
19. Launch implementation checklist
| Checklist item | Acceptance test |
|---|---|
| Upload allowlist configured | No upload route permits unsupported or executable files. |
| Size limits configured | Limits agreed and applied by file type. |
| Virus scanning enabled | Upload scanning tested and failure behaviour confirmed. |
| Upload declaration live | Mandatory checkboxes added to resource, forum and supplier upload routes. |
| Metadata warning live | Visible guidance placed before upload. |
| First-upload moderation enabled | First upload from every member held for review. |
| Sensitive categories configured | High-risk groups route to admin review. |
| Report This link visible | Every resource and member-generated page includes a report route. |
| Takedown process linked | Copyright/IP and complaints routes are accessible. |
| No urgent risk statement live | Terms, forums, upload pages and sensitive groups include the warning. |
| Supplier controls live | Commercial uploads reviewed and no-endorsement disclaimer displayed. |
| Admin roles limited | Only named people can approve/reject/remove/restore files. |
| Logs created | Upload, moderation, rejection, removal and incident logs ready. |
| Test files uploaded | Test allowed, blocked, oversized, suspicious, password-protected and quarantined files. |
| Privacy/cookie notices checked | Analytics, download monitoring and processor references are accurate. |
| DPIA screening updated | Upload risks and controls documented before go-live. |
20. Upload review form template
| Field | Entry |
|---|---|
| Upload title | |
| Uploader/member | |
| Date received | |
| File type and size | |
| Category/group | |
| Licence/attribution checked | Yes / No / Not clear |
| Personal data check | Clear / Concern / Escalated |
| Confidential information check | Clear / Concern / Escalated |
| Metadata checked | Yes / No / Not applicable |
| AI declaration needed | Yes / No / Declared |
| Supplier/commercial content | Yes / No / Not applicable |
| Sensitive category | Yes / No |
| Decision | Publish / Publish with edits / Hold / Reject / Remove / Escalate |
| Reason for decision | |
| Reviewer | |
| Date decision made |
21. Final policy statement
OpenThoughts should treat the resource library as both its strongest value proposition and one of its highest operational risks. The recommended position is not to avoid uploads, but to make upload safety part of the platform design from day one. The combination of restricted file types, size limits, virus scanning, metadata warnings, upload declarations, first-upload moderation, sensitive-category review, visible reporting and clear escalation routes gives OpenThoughts a practical, proportionate and trustworthy model for sector resource sharing.
This policy should be approved before launch and reviewed after the first 90 days of live uploads.
Policy 05Safeguarding and Do Not Post Urgent Risk Policy
Safeguarding and “Do Not Post Urgent Risk” Policy
A strengthened policy, website notice and moderation procedure for OpenThoughts
| Recommended decision: OpenThoughts should adopt a clear “learning and collaboration only” position. It should allow professionals to discuss themes, practice, policies, templates and lessons learned, but it must not allow urgent safeguarding concerns, live resident cases, emergency risks, personal data, confidential case files or organisation-specific incident details to be posted on the platform. The message should appear in the Terms, forum posting pages, upload pages and high-risk topic groups. |
|---|
Document status: Approved and implemented
Owner: OpenThoughts platform owner / appointed responsible person
Applies to: Members, moderators, contributors, suppliers, advertisers, guests and anyone uploading, posting or commenting on OpenThoughts
Review cycle: At least annually and immediately after any safeguarding-related platform incident, urgent-risk post, data breach, moderation failure or material change to platform features
This policy is part of the OpenThoughts governance pack and explains the standards expected when members discuss sensitive themes.
1. Executive decision
OpenThoughts should publish and enforce a dedicated safeguarding and urgent-risk posting policy. The best solution for the platform is not to create a safeguarding service, helpline, case-management route or emergency reporting route. The platform should instead make it unmistakably clear that members must use their own organisation’s safeguarding, emergency, complaints, repairs, ASB, domestic abuse, health and safety, fire safety or risk escalation procedures when a real person may be at risk.
This approach fits the ambition of OpenThoughts: open source thinking, shared sector learning and practical collaboration, without becoming an unsafe alternative to established safeguarding, emergency or landlord casework processes.
Decision statement
OpenThoughts will allow members to discuss safeguarding-related themes in a professional, anonymised and learning-focused way, but it will not host live casework, urgent risk disclosures, resident-identifiable information, emergency requests, unresolved safeguarding concerns, confidential employer documents or personal details about residents, staff, contractors, witnesses, alleged perpetrators or victims/survivors.
2. Why this policy is needed
OpenThoughts is likely to host professional discussion across areas including ASB, community safety, domestic abuse, supported housing, homelessness, damp and mould, fire safety, adaptations, accessibility, complaints, repairs, building safety, vulnerability, health and wellbeing, income, tenancy sustainment and neighbourhood management. These are valuable topics for shared learning, but they also carry a real risk that members may post details that should only be handled through formal organisational procedures.
protect residents, members, staff and the public from harm caused by misplaced reporting;
prevent the platform being treated as an emergency, safeguarding, complaints or case-management route;
reduce the risk of personal data, special category data or confidential information being posted;
make member expectations clear before they join, post or upload;
give moderators a clear basis for removing content quickly where necessary;
support the OpenThoughts ethos of open learning without unsafe disclosure.
3. Core public warning wording
This wording should be used consistently across the platform. It should appear in the Terms, forum posting pages, upload pages and relevant high-risk groups.
| Do not post urgent risk or safeguarding concerns here. OpenThoughts is not an emergency, safeguarding, legal, complaints, repair, ASB, domestic abuse, health and safety, fire safety or case-management route. Do not post live resident cases, urgent risks, names, addresses, contact details, images, case files, screenshots, allegations or personal details. If someone may be at immediate risk, or if you are dealing with a live concern, follow your organisation’s safeguarding, emergency, complaints, repairs, ASB, domestic abuse, health and safety or risk escalation procedure. In an emergency, contact the appropriate emergency service or statutory service. |
|---|
4. Plain-English member version
OpenThoughts is here for sector learning. You can share ideas, templates, general lessons, anonymised practice examples and questions about how professionals approach common challenges. You must not use OpenThoughts to report or discuss urgent or live cases where a person, household or property may be at risk.
A safe post says: “How do other organisations make safeguarding prompts clearer in ASB procedures?” An unsafe post says: “Resident X at 12 Any Street told me today that their partner is threatening them and our team has not acted.” The first supports learning. The second belongs in your organisation’s safeguarding and emergency escalation route, not on OpenThoughts.
5. Scope of this policy
This policy applies to all OpenThoughts spaces and activity, including:
member sign-up and acceptance of terms;
forum posts, replies, group discussions, comments and direct member interactions where available;
resource uploads, templates, policies, reports, presentations, screenshots, images and examples;
supplier or advertiser content where it discusses risk, safety, vulnerability or case studies;
private groups, restricted groups, pilot spaces and beta features;
AI-generated or AI-assisted uploads, summaries and discussion prompts;
moderation decisions, complaints and appeals relating to urgent-risk content.
6. What must never be posted
| Do not post | What this means |
|---|---|
| Live safeguarding concerns | Any current or recent concern where a child, adult, resident, household, staff member, contractor or member of the public may be at risk. |
| Emergency or urgent risk information | Anything requiring immediate action, urgent repair, police, fire, ambulance, local authority, landlord emergency response, safeguarding referral or duty service. |
| Resident-identifiable information | Names, addresses, dates of birth, phone numbers, email addresses, tenancy references, account numbers, images, voice notes, screenshots, case notes or unique circumstances that could identify someone. |
| Domestic abuse or victim/survivor details | Information that could reveal the identity, location, movements, support plan, perpetrator details or risk status of a victim/survivor or household. |
| ASB case details | Live or identifiable allegations, witness details, complainant details, alleged perpetrator details, evidence files, police references or legal action information. |
| Health, disability or vulnerability details | Personal health, mental health, disability, care, support, vulnerability, hoarding, substance misuse, financial hardship or family information about identifiable people. |
| Damp, mould, repairs or building safety emergencies | Information about a live urgent hazard, unsafe property, blocked escape route, fire risk, structural risk, gas/electrical risk or serious unresolved repair that requires escalation. |
| Confidential employer documents | Internal case files, risk assessments, legal advice, HR records, investigation documents, safeguarding referrals, complaint files, tenancy enforcement papers or board/executive papers not cleared for sharing. |
| Unverified allegations | Claims about individuals or organisations that could cause reputational, legal, safeguarding or employment harm if posted publicly or semi-publicly. |
| Requests for case decisions | Requests asking OpenThoughts members to decide what action should be taken in a live case, complaint, safeguarding concern, legal process, tenancy action or risk assessment. |
7. What can be posted safely
OpenThoughts should encourage useful discussion while removing live risk. The safest model is: generalise, anonymise, remove identifiers, remove urgency and focus on learning.
| Allowed learning-focused content | Example |
|---|---|
| Practice questions | How do other providers train frontline teams to recognise safeguarding indicators in repairs visits? |
| Policy comparisons | Has anyone developed a plain-English triage guide for damp and mould risk? |
| Template sharing | A blank, non-case-specific checklist for ASB vulnerability considerations. |
| Lessons learned | A fully anonymised learning summary from a closed case, cleared by the organisation and stripped of identifying details. |
| Signposting questions | What national guidance or good practice do people use when reviewing domestic abuse policy wording? |
| Process discussion | How do teams make sure safeguarding concerns raised through complaints are not missed? |
8. Required placement across the website
| Location | Required wording/control |
|---|---|
| Terms and Conditions | Include the full warning and member obligation not to post live or urgent risk information. |
| Member sign-up | Use a mandatory checkbox confirming the member understands OpenThoughts is not a safeguarding or emergency route. |
| Forum posting pages | Display a short warning immediately above the post box, with a link to the full policy. |
| Upload pages | Use a mandatory upload checkbox confirming the file contains no resident-identifiable, urgent-risk or confidential case information. |
| ASB, Community Safety and Domestic Abuse groups | Display a persistent group notice at the top of the page. |
| Supported Housing and Independent Living group | Display a persistent notice covering vulnerability, support needs and live welfare concerns. |
| Fire Safety group | Display a notice stating urgent fire risks and unsafe conditions must be escalated through formal routes. |
| Damp and Mould group | Display a notice stating urgent health, property or vulnerability risks must not be posted and must be escalated. |
| Complaints and Service Recovery group | Display a notice reminding members not to upload identifiable complaint files or active case details. |
| Footer / help centre | Include a permanent “urgent risk and safeguarding” link. |
| Resource library | Display a reminder before download/upload that shared material is for learning and not case escalation. |
| Advertiser/supplier pages | Make clear suppliers must not invite members to share live cases or resident personal data via adverts or public comments. |
9. Sign-up checkbox wording
The following checkbox should be mandatory for all members:
| I understand that OpenThoughts is not an emergency, safeguarding, legal, complaints, repair, ASB, domestic abuse, health and safety or case-management route. I will not post urgent risks, live cases, resident-identifiable information or confidential documents. Where a person, household or property may be at risk, I will follow my organisation’s formal procedures and any appropriate emergency or statutory route. |
|---|
10. Upload checkbox wording
| Before uploading, I confirm that this content does not contain live safeguarding concerns, urgent risks, resident or staff personal data, confidential case information, screenshots, addresses, contact details, images of identifiable people, employer-confidential documents or material that should be handled through a formal organisational procedure. |
|---|
11. Forum posting warning
| Pause before posting: keep this discussion general, anonymised and learning-focused. Do not post live cases, urgent risks, names, addresses, personal details, screenshots or confidential documents. Use your organisation’s formal route for safeguarding, emergency, repair, ASB, domestic abuse, complaint, fire safety, health and safety or risk escalation matters. |
|---|
12. High-risk group notices
ASB, Community Safety and Domestic Abuse
This group is for practice learning, policy discussion and professional reflection. Do not post live ASB cases, domestic abuse disclosures, victim/survivor information, witness details, alleged perpetrator details, addresses, evidence files or urgent risk concerns.
Supported Housing and Independent Living
This group may involve sensitive themes. Do not post personal information about residents, support needs, care arrangements, health, mental health, vulnerability, capacity, family circumstances or live welfare concerns.
Fire Safety
This group is for learning and improvement. Do not post live fire risks, unsafe building conditions, evacuation concerns, addresses, images of identifiable homes, risk assessments or urgent hazards. Escalate these through formal fire safety and emergency routes.
Damp and Mould
This group is for learning about prevention, communication and service improvement. Do not post live resident cases, medical information, addresses, images of identifiable homes or urgent health/property risks. Use formal repairs, complaints, safeguarding or risk escalation procedures.
Complaints and Service Recovery
Do not upload complaint files, correspondence, investigation documents or case details that identify residents, staff, contractors or organisations where the material is not approved for sharing.
Repairs and Maintenance
Do not post urgent repairs, hazards, access information, vulnerable household details or property-specific risks. Use emergency repair and escalation procedures.
Building Safety and Compliance
Do not post building-specific safety risks, access-control details, resident personal data, sensitive compliance documents or live incidents.
Homelessness and Temporary Accommodation
Do not post names, addresses, placements, vulnerability details, immigration or family information, domestic abuse locations or live homelessness casework.
13. Moderation and triage procedure
Moderators should treat possible urgent-risk content as a priority. The aim is to reduce harm quickly, preserve evidence appropriately and signpost the member back to the correct formal route without attempting to manage the case through OpenThoughts.
| Moderation step | Action |
|---|---|
| Step 1: Identify | Flag content that appears to include urgent risk, safeguarding concern, live casework, identifiable personal data, confidential documents or emergency information. |
| Step 2: Restrict visibility | Temporarily remove, hide, quarantine or limit access to the content while it is reviewed. Do not leave potentially harmful details visible while debating the issue. |
| Step 3: Do not investigate the case | OpenThoughts should not attempt to decide the underlying safeguarding, emergency, legal, repair, ASB or complaint outcome. |
| Step 4: Notify the member | Tell the member the post cannot remain on the platform and remind them to follow their organisation’s formal procedure or emergency/statutory route where appropriate. |
| Step 5: Consider data protection action | If personal data or special category data has been disclosed, assess whether the Breach Response Procedure and data protection reporting route is triggered. |
| Step 6: Record the decision | Log what was posted, what action was taken, who reviewed it, timing, risk category and whether any follow-up is needed. |
| Step 7: Escalate internally | Escalate serious or repeated issues to the platform owner or appointed responsible person. |
| Step 8: Learn and improve | Review whether warning wording, upload controls, group prompts or moderation settings need strengthening. |
14. Risk levels and response times
| Risk level | Examples | Action |
|---|---|---|
| Red: urgent or serious risk | Live safeguarding concern, emergency risk, domestic abuse details, child/adult risk, fire or building safety hazard, identifiable victim/survivor details, clear resident personal data in a harmful context. | Hide/restrict immediately when seen. Escalate to platform owner. Notify member to use formal route. Consider breach procedure. |
| Amber: potentially sensitive or confidential | Partially anonymised case, unclear urgency, identifiable organisation/staff details, internal documents, screenshots, policy extracts not obviously cleared. | Temporarily restrict if needed. Ask for anonymisation or evidence of permission. Record moderation decision. |
| Yellow: learning content needing edits | Useful discussion but includes unnecessary detail, job titles, location clues, dates, or overly specific circumstances. | Request edits before publication or edit/remove details under moderation rules. |
| Green: acceptable learning content | General, anonymised, no live risk, no personal data, no confidential files, learning-focused. | Allow to remain. Encourage good practice and anonymised examples. |
15. Member responsibilities
Use OpenThoughts for learning, not case escalation.
Anonymise examples properly and remove all direct and indirect identifiers.
Do not post anything that may need urgent action by a landlord, local authority, police, fire service, ambulance service, safeguarding partnership or other statutory service.
Do not upload confidential employer documents unless authorised to share them and they have been checked for personal data.
Do not seek legal, safeguarding or casework decisions from other members for live matters.
Correct or remove content promptly if OpenThoughts raises a concern.
Follow employer policy and professional duties before sharing examples from work.
16. Supplier and advertiser responsibilities
Suppliers and advertisers must not use OpenThoughts to collect live case information, resident personal data, safeguarding details or confidential documents through comments, forms, adverts, webinars, resource downloads or direct outreach. Any supplier tool, advert or content that invites members to share live cases must be refused or amended before publication.
Do not ask members to post case details publicly.
Do not request resident personal data through platform comments or public forms.
Do not present supplier content as a substitute for emergency, safeguarding, legal or statutory advice.
Do not use case studies unless they are properly anonymised, authorised and lawful to share.
Do not imply that OpenThoughts has assessed, approved or endorsed a safeguarding approach or casework method.
17. Relationship with other OpenThoughts policies
| Policy | Connection |
|---|---|
| Terms and Conditions | This policy should be incorporated into the member rules and acceptable use requirements. |
| Privacy Policy | Supports the rule that resident, staff and special category data must not be posted unnecessarily. |
| Breach Response Procedure | Triggered where personal data, special category data or confidential information is exposed. |
| Defamation and Reputational Risk Policy | Supports removal of allegations, naming individuals or unverified claims. |
| AI Usage Policy | AI-generated summaries or examples must not include personal/confidential data and must be checked before posting. |
| Copyright and Takedown Policy | Relevant where uploaded documents include confidential or unauthorised material. |
| Complaints and Appeals Policy | Provides routes for members to challenge moderation, while urgent-risk removals should prioritise safety. |
| Supplier / Advertiser Terms | Should prohibit suppliers from soliciting live case details or resident data through the platform. |
18. Data protection and confidentiality controls
Safeguarding and urgent-risk content often involves personal data and may involve special category data or highly sensitive confidential information. OpenThoughts should therefore treat this policy as part of its wider data protection control framework.
Build upload prompts that require members to confirm no personal data or confidential case information is included.
Use moderation filters for terms likely to indicate addresses, phone numbers, email addresses, tenancy references or personal case details.
Restrict attachments in high-risk groups until moderation controls are tested.
Create a documented review route for content reported as containing personal data.
Train moderators to recognise indirect identifiers, not just names and addresses.
Keep moderation logs proportionate and avoid copying unnecessary sensitive details into the log.
Escalate potential personal data breaches under the Breach Response Procedure.
19. Anonymisation standard
A post is not automatically safe just because names have been removed. Members must consider whether someone could still be identified from a combination of details.
Remove direct identifiers: names, addresses, phone numbers, emails, tenancy references, case numbers, photographs, screenshots and document metadata.
Remove indirect identifiers: rare circumstances, small teams, unusual locations, dates, job titles, ages, family composition, court dates, incident timings, local landmarks and unique property details.
Generalise the example: describe the process issue or learning point without giving enough detail to identify the person, household, staff member or organisation.
Check permission: do not share employer documents, case studies or internal learning unless authorised and checked.
When in doubt: do not post. Ask your organisation through the correct internal route.
20. Handling repeated breaches
OpenThoughts should take repeat misuse seriously. The goal is not to punish honest mistakes harshly, but the platform must protect residents, members and itself from repeated unsafe posting.
| Scenario | Possible action |
|---|---|
| First low-level issue | Content removed or edited. Member receives explanation and link to policy. |
| Repeated low-level issue | Warning issued. Posting or upload privileges may be temporarily restricted. |
| Serious issue | Immediate removal/restriction, account review and possible suspension. |
| Repeated serious issue | Account suspension or termination. Organisation-domain access may be reviewed if there is a wider risk. |
| Deliberate misuse | Removal, account termination, refusal of future membership and, where necessary, legal/data protection escalation. |
21. Appeals and complaints
Members may use the OpenThoughts Complaints and Appeals Policy to challenge moderation decisions. However, OpenThoughts does not have to keep urgent-risk, safeguarding, personal data or confidential case information visible while an appeal is considered. Safety, confidentiality and data protection take priority over publication during review.
OpenThoughts may decline to enter into circular arguments where the content plainly breaches this policy, exposes personal/confidential information or attempts to use the platform as a casework route.
22. Internal incident log template
| Date/time | Reporter / source | Content location | Risk level | Action taken | Member notified | Breach review needed? | Outcome / learning |
|---|---|---|---|---|---|---|---|
23. Member notification templates
Template A: content removed because it may include urgent risk or safeguarding information
Thank you for contributing to OpenThoughts. We have temporarily removed or restricted your post because it appears to include urgent risk, safeguarding, live casework or personal/confidential information. OpenThoughts is not an emergency, safeguarding, legal, complaints, repair, ASB, domestic abuse, health and safety or case-management route. Please follow your organisation’s formal procedure and any appropriate emergency or statutory route. You may repost a general, anonymised, learning-focused version if it does not include live risk or identifiable details.
Template B: upload rejected because it may contain confidential or identifiable information
We cannot approve this upload because it appears to contain information that may identify a person, household, staff member, organisation-specific case or confidential document. Please remove all personal, confidential, case-specific and urgent-risk information before resubmitting. Only upload material you are authorised to share.
Template C: reminder after minor issue
We have edited or removed some detail from your contribution to keep it safe and learning-focused. Please remember not to post live cases, urgent risks, names, addresses, screenshots, case files or confidential documents. OpenThoughts works best when examples are generalised and anonymised.
24. Website page: “Safeguarding and Urgent Risk”
OpenThoughts should create a dedicated public help page called “Safeguarding and Urgent Risk”. This page should be short, clear and linked from high-risk areas of the site.
Suggested page content
OpenThoughts is a professional learning and collaboration platform. It is not an emergency service, safeguarding referral route, case-management system, complaints route, repairs reporting route, ASB reporting route, domestic abuse reporting route, legal advice service or substitute for your organisation’s procedures.
Do not post urgent concerns, live resident cases, personal data, confidential documents, case screenshots, addresses, contact details, images of identifiable people or details of people at risk. If a person, household or property may be at risk, use your organisation’s formal procedure and any appropriate emergency, statutory, safeguarding, repair, ASB, domestic abuse, complaint, fire safety, health and safety or risk escalation route.
You are welcome to share general learning, anonymised examples, templates and reflective practice questions. Keep the focus on issues, processes, prevention and improvement, not live cases or identifiable people.
25. Implementation checklist
| Action | Timing / note |
|---|---|
| Add mandatory sign-up checkbox | Before member registration goes live. |
| Add upload checkbox | Before resource library uploads go live. |
| Add forum posting warning | Before forums go live. |
| Add persistent group notices | For ASB, Domestic Abuse, Supported Housing, Fire Safety, Damp and Mould and other high-risk groups. |
| Update Terms and Conditions | Include this policy as an acceptable use requirement. |
| Update supplier/advertiser terms | Prohibit collection of live case or resident data through the platform. |
| Create moderation playbook | Include risk levels, response times and notification templates. |
| Create incident log | Record urgent-risk and safeguarding-related moderation actions. |
| Train moderators | Cover anonymisation, urgent risk, data protection, indirect identifiers and escalation. |
| Test user journey | Confirm warnings appear at sign-up, posting and upload points. |
| Review after launch | Review within 3 months of launch, then annually or after any serious incident. |
26. Final recommended policy position
OpenThoughts should adopt this policy before launch. The final decision should be to allow open discussion about safeguarding-related learning, domestic abuse practice, ASB, vulnerability, safety, damp and mould, fire safety and homelessness only where the discussion is general, anonymised, non-urgent and focused on learning. OpenThoughts should prohibit live casework, urgent risk escalation, personal data, confidential case files, identifiable examples and attempts to obtain case decisions from the community.
This is the strongest fit for the OpenThoughts ambition: it protects people, keeps the platform focused on sector improvement, avoids unsafe informal casework, and gives members a clear, fair and visible boundary before they post.
Appendix A: Quick “safe to post?” test
Could this identify a resident, household, staff member, contractor, witness, victim/survivor, alleged perpetrator or property?
Is this about a live, unresolved or urgent matter?
Could someone need emergency, safeguarding, landlord, repair, ASB, domestic abuse, fire safety, health and safety or statutory action?
Have I included names, addresses, screenshots, case notes, photos, dates, job titles, rare details or location clues?
Is this a confidential employer document or internal case file?
Am I asking others to decide what should happen in a live case?
Would I be comfortable if my organisation’s data protection, safeguarding or legal lead saw this post?
Can I rewrite this as a general learning question instead?
If the answer to any of the first six questions is yes or maybe, do not post it. Use the correct formal route instead.
Appendix B: Examples of safer rewrites
| Unsafe post | Why it is unsafe / safer focus | Safer learning-focused version |
|---|---|---|
| A resident at [address] has severe mould and asthma and our repairs team has not attended. What should I do? | Unsafe because it contains live or identifiable case information and asks for platform-based case advice. | How do other organisations triage damp and mould cases where health vulnerabilities may be present, and how is escalation built into the process? |
| We have a domestic abuse case where the alleged perpetrator works for a contractor. Has anyone dealt with this? | Unsafe because it contains live or identifiable case information and asks for platform-based case advice. | What controls do organisations use to protect confidentiality and safety when domestic abuse risks intersect with contractor access or repairs appointments? |
| Here is our complaint file with names removed. Can someone tell me if we handled it properly? | Unsafe because it contains live or identifiable case information and asks for platform-based case advice. | Does anyone have a blank complaint learning template that helps identify safeguarding or vulnerability indicators? |
| Fire doors in Block X are being wedged open and residents are worried. | Unsafe because it contains live or identifiable case information and asks for platform-based case advice. | What engagement approaches have worked to reduce fire-door misuse in communal blocks, without discussing a live building-specific risk? |
| A tenant has threatened a neighbour and I am not sure if we should go legal. | Unsafe because it contains live or identifiable case information and asks for platform-based case advice. | How do ASB teams balance early intervention, vulnerability checks and enforcement decision points in policy design? |
Appendix C: Adoption record
| Approved by | |
|---|---|
| Date approved | |
| Version | 1.0 |
| Next review date | |
| Owner | |
| Linked policies updated | Terms and Conditions; Privacy Policy; Breach Response Procedure; AI Usage Policy; Defamation and Reputational Risk Policy; Complaints and Appeals Policy; Supplier / Advertiser Terms |
Policy 06Age Restriction and Children’s Data Policy
Age Restriction and Children’s Data Policy
Decision Paper, Policy, Website Wording and Operational Checklist
| Item | Position |
|---|---|
| Document owner | OpenThoughts founder / platform owner |
| Applies to | OpenThoughts website, member area, resource uploads, forums, groups, supplier/advertiser areas, blogs, events, contact forms and any linked community tools |
| Audience | Members, prospective members, contributors, suppliers, advertisers, moderators, administrators and platform operators |
| Recommended status | Adopt before public launch and publish clear public wording in the Terms, Privacy Policy, sign-up journey and upload journey |
| Version | 1.0 – approved and implemented |
| Review cycle | Before launch, after any major change to member functionality, and at least annually |
| Linked policies | Privacy Policy; Terms of Use; Safeguarding and Do Not Post Urgent Risk Policy; Member Upload Checklist; File Upload Risk Controls; Moderation Policy; Acceptable Use Policy; AI Usage Policy; Data Protection Impact Assessment Screening |
1. Executive decision
Recommended decision: OpenThoughts should operate as an 18+ professional platform. Membership should only be available to people aged 18 or over who are using the platform in a professional, sector, employment, governance, supplier or organisational capacity. Children and young people must not apply for membership, must not hold accounts and must not be targeted by OpenThoughts content, forums, supplier activity or marketing.
This is the best fit for the site requirements and ambition because OpenThoughts is being designed as a trusted, professional, open-source thinking space for the housing sector. Its core value is the safe sharing of learning, templates, experiences and practice between housing professionals and sector partners. It is not a youth forum, resident casework system, safeguarding route, social media platform for minors or general public advice service.
The decision should be supported by clear age wording at sign-up, in the Terms, in the Privacy Policy, on upload pages, in high-risk groups and in moderation workflows. The policy should not rely only on a hidden legal clause. It should appear wherever members might accidentally share information about residents, households, children or young people.
Decision statement for adoption
OpenThoughts membership is for adults aged 18+ only.
OpenThoughts is not aimed at children and does not knowingly offer member accounts to anyone under 18.
Under-18s must not apply for membership, upload resources, post in forums, submit blogs, create profiles or use supplier interaction tools.
Members must not upload, post or share children’s personal data, resident-identifiable information, family case details, school details, safeguarding information, photographs, names, contact details or other information that could identify a child or young person.
Any case example involving children, families, safeguarding, homelessness, youth services, domestic abuse, ASB, supported housing or vulnerability must be lawful, necessary, proportionate, fully anonymised and framed as learning rather than case management.
OpenThoughts may remove content, suspend accounts, restrict uploads, contact the uploader, record an incident and escalate under the Breach Response Procedure where children’s data or safeguarding-style information is posted.
2. Why this policy is needed
OpenThoughts will involve professional discussion across social housing, local authority, community safety, repairs, building safety, damp and mould, safeguarding-adjacent services, domestic abuse, ASB, temporary accommodation, homelessness, financial capability, supported housing and independent living. These areas can involve sensitive personal data and, in some cases, information about children or family circumstances.
Even if the platform is not aimed at children, the risk is not only that a child might apply. The bigger practical risk is that an adult member accidentally posts identifiable information about a child or young person while sharing a case example, template, learning review, complaint example, ASB scenario, safeguarding scenario, damp and mould photograph, household timeline or service failure narrative.
This policy therefore has two purposes: first, to make the platform clearly adult-only; and second, to prevent children’s personal data being introduced into the platform by adult users.
3. Legal and regulatory context
This document is a practical governance policy and not legal advice. It is intended to support UK GDPR, Data Protection Act 2018, PECR and wider good practice compliance for a UK professional platform.
The ICO Children’s Code applies to online services likely to be accessed by children in the UK. ICO guidance explains that services do not have to be specifically directed at children to be in scope if they are likely to be accessed by under-18s. The Code sets standards for how online services safeguard children’s personal data and demonstrates compliance with data protection law.
OpenThoughts should therefore document a clear position before launch: the service is not aimed at children; it is a professional adult platform; children should not be users; and the platform will implement controls to reduce the likelihood that children access the service or that children’s data is uploaded by members.
References to build into the policy framework
| Area | Relevance to OpenThoughts |
|---|---|
| ICO Children’s Code / Age Appropriate Design Code | Applies to relevant information society services likely to be accessed by children in the UK, including many websites and online services. It is not restricted to services specifically directed at children. |
| UK GDPR and Data Protection Act 2018 | Children’s personal data requires particular care. Personal data must be processed lawfully, fairly, transparently, securely and only where necessary. |
| ICO accountability expectations | OpenThoughts should document its assessment, decisions, controls and review process rather than relying on informal intent. |
| Safeguarding and sector practice | Housing-related discussion can touch on child welfare, domestic abuse, ASB, homelessness, family support and vulnerability. OpenThoughts must keep learning discussion separate from live case handling. |
4. Scope
This policy applies to all OpenThoughts functionality and all people interacting with the platform, including:
member sign-up and member profiles
forum posts, comments, replies and group discussions
resource uploads, templates, toolkits, screenshots and examples
blogs, case studies, podcasts, videos and event materials
supplier profiles, adverts, lead forms and sponsored content
contact forms, report forms and complaint routes
administrator, moderator and founder actions
third-party tools, plugins and processors used to operate the platform
This policy covers both direct children’s data and indirect information that could identify a child when combined with other information. It also covers data about families, households, schools, youth services, care arrangements, vulnerabilities, safeguarding concerns and live service situations where a child could be identifiable.
5. Definitions
| Term | Meaning for OpenThoughts |
|---|---|
| Child / young person | Anyone under the age of 18. |
| Children’s personal data | Any information relating to an identified or identifiable child, including name, photograph, address, school, family details, case history, health, disability, safeguarding circumstances, behaviour, household circumstances, service records, complaint details, repairs records or any combination of information that could identify them. |
| Resident-identifiable information | Any information that could identify a resident, household, child, young person, complainant, victim, survivor, neighbour, witness, service user or customer, either directly or by combining details. |
| Anonymised example | An example where the person cannot reasonably be identified by OpenThoughts, members, their employer, local organisations, suppliers or anyone else reading the content. |
| Pseudonymised example | An example where obvious identifiers have been removed but the person may still be identifiable through context. Pseudonymisation is not the same as anonymisation and must still be treated as personal data. |
| Live case | An active, unresolved or recent service, safeguarding, complaint, repair, ASB, domestic abuse, homelessness, tenancy, health, safety or vulnerability matter relating to a real person or household. |
| Professional learning example | A generalised, non-identifying scenario used to share lessons, improve practice, discuss processes or explain service design without exposing personal data or live case details. |
6. Public website wording
6.1 Short footer wording
OpenThoughts is a professional platform for adults aged 18+. It is not aimed at children. Please do not apply for membership if you are under 18. Members must not post or upload children’s personal data, resident-identifiable information, live case details or urgent safeguarding concerns.
6.2 Terms of Use wording
Membership is restricted to adults aged 18 or over. By applying for or using an OpenThoughts account, you confirm that you are aged 18+ and that you are using the platform in a professional, sector, organisational, supplier, governance or learning capacity.
OpenThoughts is not aimed at children and does not knowingly permit under-18s to create accounts, post content, upload resources, submit blogs, access member-only forums or use supplier interaction tools.
You must not post, upload, share, request or disclose children’s personal data, resident-identifiable information, family case details, school details, safeguarding information, health information, photographs, names, contact details or other details that could identify a child or young person. Any examples involving children, young people or families must be lawful, necessary, proportionate and fully anonymised before sharing.
OpenThoughts may remove content, hide posts, reject uploads, restrict access, suspend accounts, permanently remove accounts, record an incident and take further action where this rule is breached.
6.3 Privacy Policy wording
OpenThoughts is intended for adults aged 18+ and is not aimed at children. We do not knowingly collect account registration information from under-18s. If we become aware that an under-18 has applied for, created or used an account, we may close the account and delete or restrict related data unless we need to retain limited information for legal, security, safeguarding, complaint, moderation or audit reasons.
Members must not upload or post children’s personal data or resident-identifiable information. If such information is posted, we may remove it, restrict access to it, investigate the incident, contact the uploader, record the decision and consider whether the issue needs to be handled under our Breach Response Procedure or Safeguarding and Do Not Post Urgent Risk Policy.
6.4 Sign-up checkbox wording
I confirm that I am aged 18 or over.
I understand that OpenThoughts is a professional platform and is not aimed at children.
I will not post or upload children’s personal data, resident-identifiable information, live case details or urgent safeguarding concerns.
I understand that OpenThoughts may remove content and restrict or close accounts where this rule is breached.
6.5 Upload checklist wording
I have checked this file and it does not contain children’s personal data.
I have removed names, addresses, photographs, school details, family details, case references and any other information that could identify a child, young person, household, resident or service user.
If this resource includes a case example involving children or families, I confirm it is fully anonymised, lawful to share and included only for professional learning.
I understand that OpenThoughts may reject, remove or temporarily hide the upload if there is any concern about children’s data or resident-identifiable information.
7. Membership rules
| Rule | Required position |
|---|---|
| Minimum age | Members must be 18 or over. |
| Professional purpose | Accounts should be used for professional, sector, organisational, governance, supplier or learning purposes. |
| No child accounts | Under-18s must not create accounts, apply through organisational email addresses, use shared accounts or access member-only functions. |
| No shared child access | Adult members must not allow children or young people to use their account. |
| No children’s marketing | OpenThoughts should not target children with newsletters, advertising, supplier material, events, campaigns or member acquisition activity. |
| Account closure | Where OpenThoughts becomes aware that an account holder is under 18, the account should be closed or access suspended while the situation is reviewed. |
| Evidence retention | OpenThoughts may retain limited moderation and security records where needed to evidence account closure, misuse or safeguarding-style concerns. |
8. Children’s data: prohibited content
Members must not upload, post or share any content that includes or reveals:
a child’s name, initials where identifiable, address, telephone number, email address, school, nursery, placement, social worker details or family contact details;
photographs, videos, audio or screenshots showing a child, bedroom, home, location, school uniform or identifiable family context;
safeguarding concerns, referrals, assessment details, child protection status, domestic abuse details, exploitation concerns or social care information;
health, disability, mental health, medical, educational needs, SEND, financial hardship or vulnerability information about a child;
ASB, neighbour dispute, domestic abuse, homelessness, temporary accommodation, tenancy enforcement or legal case details that could identify a child or family;
complaint records, repairs records, damp and mould photographs, fire safety concerns or housing case notes linked to a household with identifiable children;
tracked changes, comments, filenames, metadata or screenshots that reveal children’s personal data;
employer or local authority documents containing children’s information unless they are public, lawful to share and fully anonymised.
9. What may be allowed
OpenThoughts should still allow proper professional learning about services that affect children, young people and families, provided it is shared safely. The platform should allow:
generalised learning about safeguarding processes, without live case details;
anonymised service design learning, such as how to make housing communications clearer for families;
template policies, checklists, risk frameworks and learning materials where all personal data has been removed;
publicly available guidance, statutory information or published sector reports with correct attribution;
fictional or composite scenarios that cannot identify any real person, household or organisation unless the organisation is already public and the framing is responsible;
case studies where the member has lawful authority to share and the details have been properly anonymised.
Allowed vs not allowed examples
| Scenario | Allowed if… | Not allowed if… |
|---|---|---|
| Damp and mould learning | The example is generalised and does not identify the household, address, child, school or exact timeline. | It includes photos, address clues, medical details or family circumstances that could identify a child. |
| ASB or domestic abuse discussion | The post discusses process, policy, language, survivor-centred practice or multi-agency learning in general terms. | It describes a live case, names people, gives location clues, identifies children or asks for case-specific advice. |
| Supported housing example | The scenario is fictional, composite or fully anonymised. | It includes a young person’s pathway, support notes, vulnerabilities or identifiable placement details. |
| Template upload | All examples, tracked changes, comments, screenshots, filenames and metadata have been checked and cleaned. | It includes real case names, child initials, school details, social worker references, assessment text or hidden metadata. |
| Published report | It is already public, properly attributed and shared within copyright/licence permissions. | It is an internal confidential report or contains unpublished personal data. |
10. High-risk groups requiring extra warnings
The following OpenThoughts groups should include a pinned warning and posting reminder because they are more likely to involve children, families, safeguarding, vulnerability or sensitive case issues:
ASB, Community Safety and Domestic Abuse
Supported Housing and Independent Living
Temporary Accommodation and Housing Options
Allocations, Lettings and Homelessness
Damp and Mould
Fire Safety
Building Safety and Compliance
Adaptations, Accessibility and Independent Living
Financial Capability
Tenancy Sustainment
Complaints and Service Recovery
Health and Wellbeing, if used as a group or theme
Equality, Diversity and Inclusion where personal experiences may be shared
Pinned warning for high-risk groups
Before posting: OpenThoughts is a professional learning space, not a safeguarding, emergency, legal, complaints, ASB, repair or case-management route. Do not post children’s personal data, resident-identifiable information, live case details or urgent risk concerns. Generalise the issue, remove details, and follow your organisation’s safeguarding, emergency, complaints, repairs, ASB or risk escalation procedure where appropriate.
11. Moderation response where children’s data is suspected
OpenThoughts should apply a precautionary approach. If a moderator or member believes content may include children’s data, the content should be hidden from public/member view while reviewed. The platform should not leave potentially identifying information online while debating whether it is allowed.
Triage levels
| Level | Example | Action | Target response |
|---|---|---|---|
| Red | Child name, photo, safeguarding information, live case details, school/location details, household details or urgent risk information. | Immediately hide/remove. Preserve evidence securely. Notify platform owner. Consider Breach Response Procedure and safeguarding signposting. Contact uploader if appropriate. | Immediate / same day where possible |
| Amber | Possible indirect identification, excessive case detail, unclear anonymisation, screenshots or metadata risk. | Temporarily hide. Review. Ask uploader to remove details or provide assurance. Restore only if safe. | Within 2 working days |
| Green | Generalised process learning, public guidance, fictional scenario or properly anonymised template. | Allow, with edits or reminders if needed. | Normal moderation queue |
Moderation principles
Err on the side of protecting children and residents.
Do not ask members to provide more personal data to justify an upload unless essential.
Do not republish removed personal data in moderator notes, emails or appeals unnecessarily.
Keep moderation notes factual, proportionate and access-restricted.
Use the Breach Response Procedure where the incident may involve a personal data breach.
Use the Safeguarding and Do Not Post Urgent Risk Policy where the content suggests immediate harm or live risk.
Use the Complaints and Appeals Policy if a member disputes a moderation decision.
12. Data breach link
Posting children’s personal data may be a personal data breach if it involves accidental or unlawful disclosure, access, alteration, loss or unauthorised sharing of personal data. OpenThoughts should not treat all such incidents as ordinary moderation issues. Where children’s data is involved, the platform owner should consider whether the Breach Response Procedure applies.
The breach assessment should consider the nature of the information, whether a child or family can be identified, how long the content was visible, who could access it, whether it was downloaded, whether the data is sensitive, whether safeguarding risk is indicated and whether affected individuals, employers, the ICO or other parties may need to be notified.
13. Sign-up, upload and account controls
| Control | Required implementation |
|---|---|
| Sign-up age confirmation | Mandatory checkbox: I confirm I am aged 18 or over. |
| Terms acceptance | Mandatory acceptance of Terms stating that the platform is 18+ and not aimed at children. |
| Upload declaration | Mandatory tick boxes confirming no children’s data, no resident-identifiable information, no confidential data and checked metadata. |
| First-upload moderation | First uploads from new members should enter moderation queue before publication. |
| High-risk category review | Uploads tagged safeguarding, ASB, domestic abuse, homelessness, supported housing, damp and mould, fire safety, complaints or vulnerability should be capable of admin review. |
| Report this function | Every member-generated page should have a route to report children’s data, personal data, confidential information, urgent risk or safeguarding-style concerns. |
| Supplier controls | Suppliers and advertisers must not collect or use member data to target children or request case details involving children. |
| Analytics and tracking | Do not knowingly profile children. Avoid any design that encourages under-18 access. Review analytics if there is evidence of under-18 traffic. |
| Access review | Administrators and moderators should have least-privilege access to reports involving children’s data. |
| Retention | Retain incident records only as long as necessary under the Records Retention Schedule. |
14. Member guidance: how to anonymise safely
Members should be told that removing a name is not enough. A child may still be identifiable through a combination of location, school, household size, repair history, disability, exact dates, staff names, complaint reference, local incident, photograph or rare circumstances.
Before sharing any example involving children or families, members must remove or generalise:
names, initials and nicknames
addresses, estate names, exact neighbourhoods and postcode clues
school, nursery, college, social care or health service references
photographs, videos, floorplans, bedroom images or identifiable home details
exact dates, reference numbers and unique timelines
staff names where this could identify a case
medical, disability, safeguarding, domestic abuse, ASB or vulnerability details
household composition where this could identify the family
any metadata, tracked changes, comments, document properties and filenames
Safe wording example
Risky wording: “A family in [estate name] with three children, including a disabled child at [school name], reported damp in bedroom 2 on 14 March. The case was handled by [staff name] and escalated after the GP letter.”
Safer wording: “A composite family case highlighted that damp and mould communication can fail when health concerns, repair timescales and escalation routes are unclear. The learning point was to provide clearer written next steps, named service contact routes and accessible follow-up information.”
15. Supplier and advertiser rules
Supplier and advertiser activity must respect the adult professional nature of the platform. Supplier presence on OpenThoughts must not create pressure for members to share live case details or children’s data in order to obtain advice, quotes, demos, benchmarking or support.
Suppliers must not ask members to upload or email case files containing children’s data through OpenThoughts routes.
Suppliers must not use OpenThoughts to target children, families or residents directly.
Suppliers must not claim endorsement, safeguarding approval, procurement approval or fitness for work involving children unless properly evidenced outside OpenThoughts.
Sponsored content must not include identifiable children or family cases unless it is a lawful, public, consented and properly evidenced case study approved by OpenThoughts.
Supplier breaches should be handled under Supplier/Advertiser Terms, Moderation Policy, Breach Response Procedure and Complaints and Appeals Policy as appropriate.
16. Operational workflow: if an under-18 applies or is discovered
Suspend the account or application while the issue is reviewed.
Do not request unnecessary proof or additional personal data from the under-18.
Check whether the account has posted, uploaded, messaged suppliers or accessed member content.
Remove or restrict any content posted by the under-18 if needed.
Delete the account data where appropriate, unless limited retention is required for safety, legal, security, complaint, moderation or audit purposes.
Record the decision in the moderation/security register.
Consider whether sign-up wording, age gates or membership checks need strengthening.
17. Operational workflow: if children’s data is uploaded
Hide or remove the content immediately if there is any realistic identification risk.
Preserve a restricted evidence copy only if needed for investigation, complaint, audit, legal or breach assessment purposes.
Notify the platform owner or nominated data protection lead.
Assess whether the content includes personal data, special category data, safeguarding information, confidential employer information or resident-identifiable information.
Assess whether the Breach Response Procedure applies, including ICO notification and affected-individual notification considerations.
Contact the uploader with a factual explanation and require a corrected anonymised version if appropriate.
Record the action, decision, timeframe and outcome.
Apply member sanctions if the upload was reckless, repeated or deliberate.
Update guidance, upload checklist or moderation filters if the incident reveals a gap.
18. Policy relationship map
| Policy / control | How it links to this document |
|---|---|
| Terms of Use | Confirms 18+ membership and no children’s personal data. |
| Privacy Policy | Explains that OpenThoughts is not aimed at children and how children’s data incidents are handled. |
| Member Upload Checklist | Builds children’s data checks directly into the upload process. |
| File Upload Risk Controls | Controls file types, metadata, moderation and sensitive uploads. |
| Safeguarding and Do Not Post Urgent Risk Policy | Stops members using the platform for live safeguarding or urgent risk escalation. |
| Moderation Policy | Sets removal, hiding, suspension, appeal and evidence rules. |
| Report This Function | Allows members to report children’s data, personal data, urgent risk or confidential information. |
| Breach Response Procedure | Handles personal data breach assessment and reporting decisions. |
| DPIA Screening | Documents pre-launch risk assessment around children’s data and professional identity. |
| Supplier/Advertiser Terms | Prevents suppliers from misusing member data or requesting live case information. |
19. Governance and review
The platform owner should review this policy before launch, after significant functionality changes and at least annually. A review should also be triggered if OpenThoughts introduces open public registration, youth-focused content, resident-facing services, direct messaging with suppliers, events aimed at students or apprentices under 18, or any tool likely to attract children.
The review should check whether the 18+ position remains accurate in practice. If analytics, enquiries or user behaviour suggest that under-18s are likely to access the service, OpenThoughts should revisit the DPIA screening and consider whether additional Children’s Code controls are required.
20. Implementation checklist
| Action | Complete? | Notes / owner |
|---|---|---|
| Public Terms state membership is 18+ only | ☐ | |
| Privacy Policy explains the site is not aimed at children | ☐ | |
| Sign-up form includes mandatory age confirmation checkbox | ☐ | |
| Upload form includes children’s data declaration | ☐ | |
| High-risk groups include pinned “do not post urgent risk / children’s data” warning | ☐ | |
| Report This function includes “children’s data / personal data” category | ☐ | |
| Moderation workflow includes immediate hide/remove route for suspected children’s data | ☐ | |
| Breach Response Procedure refers to children’s data and resident-identifiable information | ☐ | |
| Supplier/Advertiser Terms prevent requests for live case information | ☐ | |
| File upload controls include metadata and tracked changes warning | ☐ | |
| First-upload moderation is enabled for new members | ☐ | |
| DPIA screening completed before launch | ☐ | |
| Staff/moderator guidance issued | ☐ | |
| Incident register created | ☐ | |
| Annual review date set | ☐ |
21. Final member understanding checklist
This wording can be used at the end of the upload journey or as a short confirmation panel before a member posts into higher-risk groups.
☐ I understand OpenThoughts is for adults aged 18+ only.
☐ I understand OpenThoughts is not aimed at children and under-18s must not apply for membership.
☐ I understand I must not upload or post children’s personal data.
☐ I understand I must not post resident-identifiable information, live case details, safeguarding concerns or urgent risk information.
☐ I have anonymised any example involving children, families, safeguarding, ASB, homelessness, vulnerability, damp and mould, repairs, complaints or safety.
☐ I have checked documents for hidden information, including tracked changes, comments, filenames and metadata.
☐ I understand OpenThoughts may remove content, reject uploads, restrict my account and record an incident if I breach this rule.
☐ I understand that if there is an urgent concern, I must use my organisation’s safeguarding, emergency, complaints, repairs, ASB or risk escalation procedure, not OpenThoughts.
22. Website page: suggested final public version
Age Restriction and Children’s Data
OpenThoughts is a professional platform for adults aged 18+. It is not aimed at children and under-18s must not apply for membership or use member-only areas.
Because OpenThoughts supports discussion across housing, communities, safety, ASB, domestic abuse, supported housing, homelessness, damp and mould, repairs and related services, members must take extra care not to post information about residents, families, children or young people.
Do not post or upload children’s personal data, resident-identifiable information, live case details, safeguarding concerns, urgent risk information, photographs, addresses, school details, household details or confidential employer information.
You may share generalised learning, anonymised examples, templates, policies and practice resources where you have the right to share them and where no person can be identified. Removing a name is not always enough. Please remove context that could identify a child, household or case.
OpenThoughts may remove content, reject uploads, hide posts, suspend accounts, record incidents and take further action where content creates a risk to children, residents, members, employers or the platform.
OpenThoughts is not an emergency, safeguarding, complaints, repairs, legal, ASB or case-management route. If something is urgent or relates to a live concern, follow your organisation’s own safeguarding, emergency, complaints, repairs, ASB or risk escalation procedure.
23. Source notes
This policy has been prepared with reference to the ICO Children’s Code / Age Appropriate Design Code guidance, including the point that the Code applies to relevant information society services likely to be accessed by children in the UK and is not limited only to services specifically directed at children. It also reflects ICO guidance that the Code helps organisations safeguard children’s personal data and demonstrate compliance with data protection law.
Official source references to retain for policy evidence:
ICO: Age appropriate design: a code of practice for online services
ICO: Services covered by the Children’s Code
ICO: Introduction to the Children’s Code
ICO: Children’s Code guidance and resources
Policy 07Breach Response Procedure Policy
Strengthened Breach Response Procedure Policy
Personal Data Breach, Security Incident and Near-Miss Management Procedure
| Document control item | Detail |
|---|---|
| Organisation | OpenThoughts |
| Document owner | Founder / Data Protection Lead |
| Applies to | All OpenThoughts directors, employees, contractors, moderators, suppliers, advertisers, platform administrators and any person processing personal data on behalf of OpenThoughts |
| Policy status | Approved and implemented |
| Version | 1.0 |
| Approval date | 04 May 2026 |
| Review cycle | Annual, and immediately after any significant incident, platform change, supplier change, new processing activity or ICO/regulatory update |
| Related documents | Privacy Policy; Cookie Policy; Data Processing Register; Records Retention Schedule; Supplier / Advertiser Terms; Accessibility Statement; Information Security controls; Data Protection Impact Assessments; Data Subject Rights Procedure |
Important note: This policy is a governance and operational template. It does not replace tailored legal advice. OpenThoughts should review and approve it against its actual platform design, data flows, suppliers, insurance position and contractual arrangements before publication or internal adoption.
1. Purpose
This policy sets out how OpenThoughts will identify, contain, assess, record, escalate, report, communicate and learn from personal data breaches, security incidents and near misses. It is designed to protect members, contributors, advertisers, suppliers, staff and the integrity of the OpenThoughts platform.
ensure incidents are recognised and escalated quickly;
minimise harm to individuals and the organisation;
meet UK GDPR and Data Protection Act 2018 accountability obligations;
support timely decisions on whether the Information Commissioner's Office (ICO) or affected individuals must be notified;
create a complete evidence trail for all incidents, including those not externally reportable;
embed learning so that controls, training, contracts and platform design improve over time.
2. Scope
This procedure applies to all information security incidents and suspected or confirmed personal data breaches involving OpenThoughts data, systems, website, membership areas, communities, resources, forums, newsletters, advertising relationships, analytics, moderation activity or supporting suppliers.
2.1 In scope
member registration data and email verification information;
forum posts, private messages, comments, resource uploads and community contributions;
advertiser and supplier contact, contract and billing records;
newsletter, marketing, event and consent records;
website analytics, cookie identifiers and device information where linked or linkable to an individual;
administrator accounts, passwords, access logs and authentication records;
payment, invoice and accounting records;
complaints, moderation, safeguarding-style concern notes, disputes and investigation records;
records shared with or received from platform providers, hosting companies, email tools, analytics tools, payment processors, CRM tools, design contractors, moderators, advertisers or other processors.
2.2 Out of scope but still reportable internally
Events that do not involve personal data may still be security incidents and must be reported internally. For example, website defacement, attempted phishing, malware alerts, denial-of-service activity, failed login spikes, suspected credential stuffing, or unauthorised changes to website content. These may become personal data breaches if personal data is accessed, lost, altered, disclosed or becomes unavailable.
3. Definitions
| Term | OpenThoughts meaning |
|---|---|
| Personal data | Any information relating to an identified or identifiable living person, including names, email addresses, IP addresses, account identifiers, member profile data, posts, comments, images, opinions, work contact details and online identifiers. |
| Special category data | More sensitive personal data requiring extra protection, such as health information, disability information, race or ethnicity, religious or philosophical beliefs, trade union membership, political opinions, sex life or sexual orientation, where such data is present in platform content or correspondence. |
| Personal data breach | A breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. This includes confidentiality, integrity and availability incidents. |
| Security incident | Any event that may compromise confidentiality, integrity or availability of systems, data or services, whether or not personal data is confirmed to be affected. |
| Near miss | An event that could have resulted in a breach but was prevented, detected early or caused no actual compromise. Near misses must still be logged and reviewed. |
| Controller | The organisation deciding why and how personal data is processed. OpenThoughts will usually be a controller for its own website, membership, communications and advertising activities. |
| Processor | An organisation processing personal data on OpenThoughts' behalf, such as hosting, email, CRM, analytics, development, payment or moderation providers. |
| High risk | A breach likely to result in significant harm or adverse effects for individuals, such as fraud, identity theft, discrimination, reputational damage, distress, financial loss, loss of confidentiality or loss of control over personal data. |
4. Legal and regulatory basis
This policy is aligned to UK GDPR, the Data Protection Act 2018 and ICO breach-management expectations. The ICO expects organisations to have procedures to detect, manage and record personal data breaches, to assess all incidents, and to report relevant breaches within statutory timescales.
UK GDPR Article 5(1)(f): integrity and confidentiality principle.
UK GDPR Article 32: security of processing.
UK GDPR Article 33: notification of a personal data breach to the supervisory authority where required.
UK GDPR Article 34: communication of a personal data breach to affected individuals where required.
UK GDPR Article 33(5): requirement to document facts, effects and remedial action for personal data breaches.
Accountability principle: OpenThoughts must be able to demonstrate compliance through records, decisions, controls and learning actions.
5. Policy statement
OpenThoughts will treat all suspected data breaches seriously, act promptly, put people first, and maintain a clear evidence trail. The organisation will not ignore low-level incidents, near misses or supplier-reported issues because these provide early warning signs and opportunities to reduce future harm.
All incidents must be reported immediately using the internal breach route.
No individual should attempt to hide, delay or quietly fix a potential breach without logging it.
The 72-hour ICO reporting clock may begin when OpenThoughts becomes aware of a personal data breach, not when the investigation is complete.
When facts are incomplete, OpenThoughts will make proportionate decisions using the information available, update records as facts change, and, where needed, notify in phases.
Affected individuals will be told clearly and without unnecessary delay where the breach is likely to result in a high risk to their rights and freedoms.
Suppliers and advertisers must cooperate promptly where their systems, content or conduct may have caused or contributed to an incident.
6. Roles and responsibilities
| Role | Responsibilities |
|---|---|
| Founder / Senior Responsible Owner | Owns this policy, ensures resources are available, approves ICO and affected-individual notifications where practical, oversees reputational and contractual decisions, and ensures post-incident learning is implemented. |
| Data Protection Lead | Coordinates breach response, maintains the breach log, completes risk assessments, prepares ICO reports, liaises with processors, advises on affected-individual communications and stores the evidence pack. |
| Website / Platform Administrator | Secures systems, suspends compromised accounts, preserves logs, rotates credentials, liaises with hosting and development suppliers, validates containment and recovery steps. |
| Community / Forum Moderators | Escalate accidental disclosures, harmful posts, unauthorised sharing of personal data, doxxing, inappropriate content, member complaints and platform abuse. |
| Finance / Commercial Lead | Escalates payment, invoicing, advertiser, supplier and contract-related data incidents; supports fraud prevention and insurance notification. |
| Suppliers / Processors | Must notify OpenThoughts without undue delay of any actual or suspected breach affecting OpenThoughts data, provide facts, cooperate with containment and not communicate externally about the incident without agreed handling unless legally required. |
| Advertisers / Promoters | Must report any misuse, unauthorised harvesting, onward disclosure, targeting issue or accidental access involving OpenThoughts members or leads. |
| All staff / contractors | Must report suspected incidents immediately, preserve evidence, avoid deleting or altering relevant material unless instructed, and follow confidentiality requirements. |
7. Breach response principles
Speed with control: respond quickly but record decisions and avoid uncontrolled changes that destroy evidence.
Contain first, investigate in parallel: stop further exposure while preserving logs and affected data samples.
People-first risk assessment: assess harm from the affected person's perspective, not only from the organisation's reputational perspective.
Least disclosure: share incident information only with those who need it to respond.
Evidence-led decisions: document what is known, unknown, assumed, decided and completed.
No blame reporting culture: encourage rapid reporting so incidents can be contained and learned from.
8. Examples of reportable incidents and near misses
| Scenario | Why it matters | Initial action |
|---|---|---|
| Member email list sent using CC rather than BCC | Unauthorised disclosure of member email addresses and potential association with OpenThoughts membership. | Recall if possible, notify Data Protection Lead, preserve sent email, assess recipients and sensitivity. |
| Admin account compromised | Potential unauthorised access to member, content, billing, forum or settings data. | Disable account, reset credentials, revoke sessions, preserve logs, check admin actions. |
| Forum post includes another person's personal details without permission | Public or member-only disclosure may cause distress, reputational harm or safety risk. | Remove or restrict content, preserve evidence, contact poster if appropriate, risk assess affected person. |
| Supplier confirms hosting or email platform security incident | Processor incident may involve OpenThoughts data. | Request supplier breach details, affected records, timescales, controls and confirmation of containment. |
| Lost laptop or phone containing exported membership data | Loss of device may expose personal data if not encrypted and access-controlled. | Confirm encryption, remote wipe, access controls, data stored, and whether backup/export existed. |
| Accidental publication of hidden spreadsheet columns or metadata | Personal data may be exposed in downloadable resources. | Remove resource, replace safe version, assess download/access logs. |
| Phishing email sent from OpenThoughts mailbox | May expose recipients to fraud and undermine trust. | Secure mailbox, warn recipients if needed, review sent items/rules, rotate credentials. |
| Advertiser uses OpenThoughts member contact details outside agreed purpose | Unlawful direct marketing or misuse of member data. | Suspend campaign, require deletion evidence, assess complaints, consider contract breach and affected-individual notice. |
| Ransomware or malware affects website or CRM | Availability, integrity and confidentiality may be compromised. | Isolate systems, contact host/security support, preserve forensic evidence, assess backups and personal data access. |
| Near miss: wrong attachment almost sent but spotted before sending | No external disclosure, but process weakness exists. | Log as near miss, review naming/checking controls and training. |
9. Immediate reporting route
Any suspected breach must be reported immediately and no later than the same working day. Where an incident is discovered outside working hours, the person discovering it should use the emergency contact route set by OpenThoughts.
| Contact point | Details to complete |
|---|---|
| Primary breach email | [Insert dedicated email address, e.g. [email protected]] |
| Emergency phone / WhatsApp | [Insert number] |
| Senior escalation contact | [Insert name and contact details] |
| Website / hosting support route | [Insert supplier portal / urgent support route] |
| Cyber insurance / legal helpline | [Insert policy details if applicable] |
10. First 24-hour response checklist
| Timeframe | Action | Owner | Evidence to save |
|---|---|---|---|
| Immediately | Receive report, open breach log entry and assign incident reference. | Data Protection Lead | Initial report, time/date, reporter, discovery details. |
| Immediately | Preserve evidence: screenshots, emails, logs, URLs, file names, access records and supplier notices. | Reporter / Platform Admin | Evidence folder with restricted access. |
| 0-2 hours | Contain exposure: remove content, suspend account, disable link, revoke access, isolate system, pause campaign or stop processing. | Platform Admin / Supplier | Containment actions and timestamps. |
| 0-4 hours | Decide whether personal data is involved and identify likely data subjects. | Data Protection Lead | Initial breach triage form. |
| 0-8 hours | Assess severity, affected data, affected people, likely harm and whether specialist support is required. | Data Protection Lead / Senior Owner | Risk assessment notes. |
| 0-12 hours | Contact relevant processor/supplier and request incident facts if supplier-related. | Data Protection Lead | Supplier correspondence and responses. |
| 0-24 hours | Make provisional decision on ICO notification pathway and affected-individual communication. | Senior Owner / Data Protection Lead | Decision record with reasons. |
| 0-24 hours | Prepare holding lines for internal team and, if needed, affected users. | Senior Owner / Communications Lead | Approved communications draft. |
11. Breach response stages
| Stage | Objective | Key actions |
|---|---|---|
| 1. Identify | Confirm whether an incident may have occurred. | Receive report, preserve initial evidence, create incident reference, assign owner. |
| 2. Contain | Stop or reduce further harm. | Remove public exposure, disable links, suspend accounts, restrict permissions, recover data, secure devices, pause campaigns. |
| 3. Triage | Establish facts quickly. | What happened, when, who found it, what data, how many people, who accessed it, whether it is ongoing. |
| 4. Assess risk | Decide likely impact on individuals. | Assess sensitivity, volume, identifiability, vulnerability, potential harm, mitigation and likelihood. |
| 5. Notify where required | Meet legal and ethical notification duties. | Decide ICO notification, affected-individual notification, supplier/customer notifications, insurer/legal routes. |
| 6. Recover | Restore safe operation. | Patch weakness, reset credentials, validate backups, monitor abuse, confirm processor remediation. |
| 7. Learn | Prevent recurrence. | Root cause review, update policies, improve controls, train staff, amend supplier terms, report to senior owner. |
| 8. Close | Complete accountability record. | Close log when actions are complete, evidence retained and residual risks accepted. |
12. Risk assessment framework
Every incident involving personal data must be assessed using the following factors. The assessment must be completed even where OpenThoughts decides not to notify the ICO or affected individuals.
| Factor | Questions to consider |
|---|---|
| Nature of data | Does it include names, work emails, personal emails, phone numbers, forum posts, opinions, location, images, payment data, login details, IP addresses, special category data or complaint/safeguarding-style information? |
| Volume | How many people and records are affected? Is this a single person, a small group, a mailing list, all members or unknown? |
| Identifiability | Can individuals be identified directly or indirectly? Could the data be combined with other information? |
| Context | Does membership, contribution or content reveal employment, resident involvement, whistleblowing-style concerns, complaints, vulnerabilities or sensitive professional opinions? |
| Vulnerability | Are affected people potentially vulnerable because of age, disability, health, housing circumstances, employment relationship, complaint status or power imbalance? |
| Access and exposure | Was data publicly available, accessed by a known recipient, accessed by multiple recipients, indexed by search engines, downloaded, copied or exfiltrated? |
| Security controls | Was data encrypted, password-protected, pseudonymised, access-controlled, expired, backed up or recoverable? |
| Likely harm | Could there be distress, embarrassment, discrimination, fraud, phishing, identity theft, financial loss, professional harm, reputational damage, loss of confidentiality, safety risk or loss of control? |
| Mitigation | Can recipients be trusted to delete it? Can links be disabled? Can passwords be reset? Can search indexing be removed? Are logs available? |
| Evidence quality | Are facts confirmed, partly confirmed or unknown? If unknown, does uncertainty increase risk? |
13. Severity rating matrix
| Severity | Description | Typical action |
|---|---|---|
| Green - low | Near miss or minor incident with no external disclosure and no realistic risk to individuals. | Log, contain, learn, no ICO notification usually required. |
| Amber - moderate | Limited personal data disclosure, small number of people, low sensitivity, harm possible but mitigated quickly. | Log, risk assess, senior review, consider ICO threshold, consider individual communication if helpful. |
| Red - significant | Sensitive, high-volume, public, unknown recipients, compromised account, potential financial/reputational/distress harm or vulnerable people affected. | Urgent senior escalation, consider ICO notification, prepare affected-individual notice, supplier/legal/cyber support. |
| Black - critical | Major compromise, ransomware, large-scale data exposure, special category data, serious safety risk, ongoing attack or high likelihood of substantial harm. | Activate incident team, immediate containment, external expert support, ICO notification likely, affected-individual communication likely, senior governance oversight. |
14. ICO notification decision
OpenThoughts must notify the ICO without undue delay and, where feasible, within 72 hours of becoming aware of a personal data breach, unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. A decision not to notify must be recorded with reasons.
14.1 Information normally needed for ICO notification
nature of the personal data breach;
categories and approximate number of individuals affected;
categories and approximate number of personal data records affected;
name and contact details of the Data Protection Lead or other contact point;
likely consequences of the breach;
measures taken or proposed to address the breach, including mitigation;
reasons for any delay if notification is later than 72 hours;
whether affected individuals have been or will be informed.
14.2 Phased notification
If not all facts are known within the reporting window, OpenThoughts may submit an initial notification with available information and provide updates as the investigation progresses. The evidence log must record what was known at each point, why decisions were made and when updates were sent.
15. Communicating with affected individuals
OpenThoughts must communicate a personal data breach to affected individuals without undue delay where the breach is likely to result in a high risk to their rights and freedoms. Even where legal notification is not required, OpenThoughts may still choose to communicate if doing so is transparent, proportionate and helpful.
15.1 Affected-individual notice should include
a clear description of what happened in plain English;
what information was involved;
when the incident happened and when OpenThoughts became aware;
what OpenThoughts has done to contain and reduce risk;
what the person can do to protect themselves;
contact details for questions or concerns;
whether the ICO has been informed, where appropriate;
an apology where appropriate, without making speculative admissions or unsupported claims.
15.2 Communication standards
Use clear, accessible UK English.
Avoid minimising language where risk exists.
Do not overload affected people with technical terms.
Provide alternative formats or reasonable adjustments where required.
Coordinate communications where email or website channels have been compromised.
Keep a copy of all versions sent and the recipient list.
16. Supplier, processor and advertiser breach obligations
Contracts with suppliers, processors, advertisers and promotional partners should contain clear breach obligations. OpenThoughts should not rely on informal goodwill where third parties may handle data, generate leads, host content, run campaigns or access systems.
| Requirement | Minimum expectation |
|---|---|
| Notification speed | Supplier must notify OpenThoughts without undue delay and preferably within 24 hours of becoming aware of an actual or suspected incident affecting OpenThoughts data. |
| Information sharing | Supplier must provide facts, affected data categories, number of records, systems affected, containment steps, likely impact, law-enforcement or regulator contact, and updates as facts change. |
| Cooperation | Supplier must support containment, investigation, ICO reporting, affected-individual communications and evidence preservation. |
| No unauthorised communication | Supplier or advertiser must not contact OpenThoughts members or make public statements about the incident without agreed handling unless legally required. |
| Sub-processors | Supplier must identify any sub-processors involved and ensure they provide equivalent breach cooperation. |
| Security evidence | Supplier must provide reasonable evidence of security controls, remediation, deletion, restoration and lessons learned. |
| Costs and liability | Contract should set out responsibility for costs arising from breach caused by supplier fault, negligence, non-compliance or unauthorised processing. |
| Termination / suspension | OpenThoughts may suspend access, pause campaigns or terminate arrangements where breach risk is unacceptable or cooperation is inadequate. |
17. Evidence preservation and investigation pack
A restricted-access breach evidence folder must be created for each incident. Evidence must be preserved in a way that supports investigation, accountability and, if necessary, legal or regulatory review.
initial incident report and breach log entry;
screenshots, URLs, downloadable files, message headers, email copies and attachments;
system, access, admin, audit, firewall, hosting and application logs;
user account activity, IP addresses, login history and permission changes;
supplier notifications, tickets, reports and remediation evidence;
risk assessments and decision records;
ICO reports, reference numbers and correspondence;
affected-individual notification drafts, approvals, recipient lists and sent copies;
internal communications and senior approvals;
root cause review and action plan closure evidence.
18. Breach log template
| Field | Entry |
|---|---|
| Incident reference | |
| Date and time discovered | |
| Date and time OpenThoughts became aware | |
| Reported by | |
| Incident owner | |
| Summary of incident | |
| Systems / suppliers involved | |
| Personal data involved | |
| Number of people / records affected | |
| Containment actions and times | |
| Risk rating | Green / Amber / Red / Black |
| ICO notification decision | Notify / Do not notify / Pending |
| Reason for ICO decision | |
| Affected-individual notification decision | Notify / Do not notify / Pending |
| Reason for affected-individual decision | |
| Senior approval | |
| Lessons learned actions | |
| Closure date |
19. Internal breach report form
This form should be made available to staff, contractors and moderators. It should also be adapted for supplier reporting.
| Question | Response |
|---|---|
| Who is reporting the incident? | |
| How can we contact you urgently? | |
| What happened? | |
| When did it happen? | |
| When did you discover it? | |
| Is the incident still happening? | |
| What data or systems are involved? | |
| Whose data may be affected? | |
| How many people may be affected? | |
| Who may have seen, accessed, received or downloaded the data? | |
| What has already been done to contain it? | |
| Have any files, emails, screenshots or logs been saved? | |
| Are any suppliers, advertisers or third parties involved? | |
| Is there any immediate risk of harm, fraud, distress or safety concern? |
20. Communications templates
20.1 Internal incident alert
Subject: Urgent data incident alert - [Incident reference]
A suspected data incident has been reported. Please do not delete, amend or forward any related material unless asked by the Data Protection Lead. The incident owner is [name]. The current containment action is [summary]. Further updates will follow. If you hold any relevant evidence, send it to [secure route] immediately.
20.2 Supplier information request
Subject: Urgent breach information request - OpenThoughts data
We have been notified of a suspected incident involving OpenThoughts data or systems. Please provide, without delay, the facts known to you, time discovered, systems affected, data categories, number of records, whether data was accessed or exfiltrated, containment steps, sub-processors involved, remedial action, likely consequences and your incident contact point. Please preserve all logs and evidence until further notice.
20.3 Affected-individual notification template
Subject: Important information about your OpenThoughts data
We are contacting you because we have identified a personal data incident that may affect you. [Explain what happened clearly]. The information involved was [data categories]. We became aware on 2026 and have taken the following action: [containment/remediation]. The possible risks are [plain English risk]. We recommend that you [practical steps]. You can contact us at [contact details]. We are sorry this happened and will update you if further information becomes available.
21. Special handling situations
| Situation | Additional controls |
|---|---|
| Compromised email account | Reset password, revoke sessions, check forwarding rules, review sent/deleted items, warn recipients if phishing risk exists. |
| Public web exposure | Remove page/resource, disable downloads, purge cache/CDN, request search engine de-indexing where relevant, review access logs. |
| Forum or community disclosure | Restrict or remove post, preserve screenshot, assess whether other members copied/replied, consider moderation action. |
| Payment or financial data | Contact payment processor, do not handle card data directly unless authorised, assess fraud risk, consider bank/payment notifications. |
| Special category or vulnerability-related data | Escalate as high priority, consider high-risk threshold, minimise further circulation and use senior approval for communications. |
| Cyber attack or ransomware | Isolate systems, avoid paying ransom without specialist advice, involve hosting/security support, preserve forensic evidence, check backups. |
| Law enforcement request | Validate request, record legal basis, disclose minimum necessary data, involve senior owner. |
| Media or public attention | Use approved holding statement only, protect affected individuals, avoid speculation, keep regulator communications consistent. |
22. Post-incident review
Every Amber, Red or Black incident, and any repeated Green incident or near miss, must have a post-incident review. The aim is not blame; it is learning and risk reduction.
| Review question | Response / action |
|---|---|
| What was the root cause? | |
| Was the incident detected quickly enough? | |
| Was it reported internally quickly enough? | |
| Did containment work? | |
| Were suppliers responsive and contractually compliant? | |
| Were ICO and individual notification decisions made on time? | |
| Were communications clear, accessible and accurate? | |
| What controls failed or were missing? | |
| What training, contract, technical or process changes are needed? | |
| Who owns each improvement action and by when? | |
| How will completion be evidenced? |
23. Training and awareness
All staff, contractors and moderators must receive induction guidance on recognising and reporting breaches before handling personal data.
People with admin, moderation, finance, marketing, supplier-management or platform-access roles must receive role-specific training.
Refresher training should be provided at least annually and after any significant incident.
Training should include real or anonymised examples relevant to OpenThoughts, including email mistakes, forum disclosures, supplier incidents, phishing and accidental publication.
OpenThoughts should encourage a no-blame reporting culture so near misses are reported rather than hidden.
24. Testing and assurance
OpenThoughts should test this procedure at least annually through a tabletop exercise. Suggested scenarios include an accidental email disclosure, compromised administrator account, public download exposure, supplier breach, and advertiser misuse of member contact data.
| Assurance activity | Frequency | Evidence |
|---|---|---|
| Breach log review | Quarterly or after incidents | Completed log review notes and actions. |
| Supplier breach clauses review | At onboarding and annual review | Contract checklist and supplier due diligence. |
| Access permissions review | Quarterly | Admin/account access report. |
| Back-up and recovery check | At least annually | Successful restore evidence or supplier assurance. |
| Tabletop breach exercise | Annually | Scenario, attendance, findings and action plan. |
| Policy review | Annually and after material changes | Updated policy version and approval record. |
25. Retention of breach records
Breach records should be retained in line with the OpenThoughts Records Retention Schedule. As a minimum, incident logs, decision records, ICO correspondence, affected-individual communications and lessons-learned evidence should be retained for long enough to demonstrate compliance, respond to complaints and defend legal or regulatory claims. Access must be restricted to those with a genuine need to know.
26. Integration with other policies and controls
Privacy Policy and privacy notices: breach handling must match promises made to users.
Cookie Policy: incidents involving analytics, tracking tools or consent platforms must be assessed.
Supplier / Advertiser Terms: third-party breach obligations must be contractually enforceable.
Data Processing Register: incident findings may require updates to processing records.
Records Retention Schedule: breach records and exposed records must follow approved retention and disposal rules.
Accessibility Statement: affected-individual communications must be accessible and available in alternative formats where needed.
Professional Advice Disclaimer: breach communications must not provide specialist legal, financial or cyber advice beyond appropriate signposting.
27. Approval checklist before adoption
| Action | Complete? | Notes |
|---|---|---|
| Insert named owner, contact routes and emergency escalation details. | ||
| Confirm whether a Data Protection Officer is appointed or whether a Data Protection Lead is used. | ||
| Check supplier contracts include breach notification and cooperation clauses. | ||
| Confirm cyber/security support routes and any insurance notification requirements. | ||
| Set up restricted breach evidence folder and breach log template. | ||
| Train anyone with website, community, advertising, finance or admin access. | ||
| Run a tabletop exercise before or shortly after launch. | ||
| Review against final website build, plugins, hosting, CRM, email and payment tools. |
28. Source guidance checked
This template has been drafted with reference to current ICO guidance on personal data breaches, breach response and monitoring, breach management accountability, reporting processes, training expectations and UK GDPR accountability requirements. OpenThoughts should check the ICO website at each review date because regulatory guidance can change.
ICO, Personal data breaches: a guide.
ICO, Data protection audit framework: personal data breach management - accountability, training and reporting processes.
ICO, Accountability and governance guidance.
UK GDPR Articles 5(1)(f), 32, 33 and 34.
Appendix A - Quick decision flow
Has something happened that could affect confidentiality, integrity or availability of personal data? If yes, log it immediately.
Is personal data involved or reasonably suspected? If yes, open breach assessment and preserve evidence.
Can the issue still cause harm? If yes, contain first and investigate in parallel.
Is there a risk to individuals' rights and freedoms? If yes or uncertain, consider ICO notification within 72 hours.
Is there likely to be a high risk to individuals? If yes, prepare affected-individual notification without undue delay.
Are suppliers, advertisers or processors involved? If yes, require urgent information and cooperation.
Have all decisions, actions and reasons been recorded? If no, update the breach log before closure.
Has learning been implemented? If no, keep the incident open with assigned actions.
Appendix B - Minimum breach file index
| Folder item | Included? |
|---|---|
| 01 Initial report | |
| 02 Evidence and screenshots | |
| 03 Logs and access records | |
| 04 Supplier correspondence | |
| 05 Risk assessment | |
| 06 ICO decision and notification | |
| 07 Affected-individual decision and notification | |
| 08 Internal communications | |
| 09 Remediation evidence | |
| 10 Lessons learned report | |
| 11 Closure approval |
Policy 08AI Usage Policy
AI Usage Policy
A full and strengthened policy for responsible AI-generated and AI-assisted content on the OpenThoughts platform
| Document owner | OpenThoughts Founder / Platform Owner |
|---|---|
| Applies to | Members, contributors, moderators, suppliers, advertisers, invited guests and anyone submitting content to OpenThoughts |
| Version | 1.0 - Approved and implemented |
| Effective date | To be inserted on approval |
| Review cycle | At least every 6 months, or sooner if AI law, ICO guidance, platform functionality or risk changes |
| Related documents | Member Terms, Upload Agreement, Creative Commons Licence Decision, Copyright and Takedown Policy, Privacy Policy, Data Protection Register, Accessibility Statement, Moderation Rules, Supplier / Advertiser Terms |
| Recommended decision for OpenThoughts OpenThoughts should actively allow AI-generated and AI-assisted work, provided it is clearly declared, checked by a human, lawfully shareable, not misleading, and not presented as verified professional, legal, financial, safeguarding, technical or regulatory advice unless independently checked by a competent person. This is the best fit for the ambition of OpenThoughts: open-source thinking, practical sharing, innovation and sector learning, with clear guardrails that protect trust, attribution, data protection and professional integrity. |
|---|
1. Purpose of this policy
OpenThoughts is designed to help people working across social housing, local authorities, councils, community organisations and related sectors share ideas, templates, resources, conversations and practical learning. AI tools can support that mission by helping people draft, summarise, structure, translate, simplify and improve content. The purpose of this policy is to make AI use acceptable, transparent, safe and useful rather than hidden, careless or misleading.
This policy sets out what members, contributors, suppliers, advertisers and OpenThoughts itself must do when creating, uploading, adapting, promoting, moderating or relying on AI-generated or AI-assisted material.
2. Plain-English position
| Plain-English policy statement OpenThoughts has no issue with AI work or AI-generated work. We welcome it when it helps people share useful thinking, save time and make knowledge easier to understand. But please say when it has been generated or materially supported by AI, and please make sure it has been tried, tested, checked and sense-checked before you share it. AI should support human judgement, not replace it. |
|---|
You may upload AI-assisted content if you are entitled to share it and you declare it clearly.
You must not upload personal, confidential, commercially sensitive or restricted information into an AI tool before sharing it on OpenThoughts.
You must not present AI-generated content as professional advice, legal advice, compliance assurance, safety advice or verified sector guidance unless it has been properly checked by a competent person.
You must not upload deepfakes, fake evidence, impersonations, misleading generated media or synthetic content designed to deceive.
You must check AI summaries, templates, translations, accessibility versions and research-style outputs before sharing them.
3. Final decision: the best solution for OpenThoughts
The recommended model is a “permitted with declaration and human checking” approach. This is stronger and more practical than banning AI-generated content, because the platform is intended to encourage open thinking, practical resource sharing and modern collaboration. It is also stronger than allowing AI without declaration, because the value of OpenThoughts depends on trust, attribution and the ability for members to understand how material was produced.
| Option | Decision | Reason |
|---|---|---|
| Ban AI-generated content | Not recommended | This would be unrealistic, hard to enforce and contrary to OpenThoughts’ innovation ethos. |
| Allow AI content without declaration | Not recommended | This weakens trust and increases the risk that poor-quality or misleading content is presented as human expertise. |
| Allow AI content with clear declaration, human checking and restrictions | Recommended | This supports innovation while protecting members, organisations, copyright, confidentiality, professional integrity and platform credibility. |
| Require all AI content to be independently approved before publication | Use only for high-risk content | This may be suitable for legal, safety, regulatory, safeguarding, financial, employment or technical content, but would be too restrictive for general templates and discussion posts. |
4. Scope
This policy applies to all AI-generated, AI-assisted, AI-edited or AI-enhanced material connected with OpenThoughts, including:
forum posts and group discussions
downloadable resources, templates, toolkits and checklists
blogs, articles, newsletters and learning content
member profiles, bios, comments and summaries
graphics, images, video, audio, diagrams and generated media
advertiser and supplier content
AI-assisted translations, plain-English versions and accessibility edits
moderation, search, recommendation, categorisation and content suggestion tools used by OpenThoughts
any future AI function built into the OpenThoughts website.
5. Definitions
| Term | Meaning for this policy |
|---|---|
| AI tool | Any software or system that generates, summarises, classifies, predicts, translates, rewrites, analyses or creates content using artificial intelligence or machine learning. |
| AI-generated content | Content substantially created by an AI tool from prompts, data, examples, images, audio, code or instructions. |
| AI-assisted content | Content created by a human but materially supported by AI, such as drafting, structuring, editing, summarising, translation or idea generation. |
| Human-checked | Reviewed by a person who has considered accuracy, relevance, quality, confidentiality, intellectual property, bias, risk and whether the content is suitable for the audience. |
| High-risk content | Content that could affect rights, safety, legal duties, regulatory compliance, health, safeguarding, employment decisions, finances, property safety, procurement, contractual commitments or organisational reputation. |
| Synthetic media | Images, audio, video or other media generated or altered using AI, including realistic faces, voices, screenshots, documents or events. |
6. Core principles
| Principle | What it means |
|---|---|
| Transparency | Members should be able to tell when content has been materially AI-generated or AI-assisted. |
| Human accountability | A person remains responsible for what they upload, publish, advertise or rely on. |
| Tried and tested | Practical templates, processes and advice-style resources should be checked against real-world use before being promoted as reliable. |
| No confidential leakage | Personal data, tenant information, staff data, contracts, complaints, live case details, confidential business information and restricted documents must not be put into AI tools unless this is lawful, authorised and properly protected. |
| No false authority | AI output must not be dressed up as verified legal, regulatory, health and safety, financial, procurement or professional advice. |
| Fairness and inclusion | AI should not be used to create discriminatory, exclusionary or harmful content, or to reinforce stereotypes about residents, staff, communities or organisations. |
| Attribution and ownership | AI does not remove the need to respect copyright, Creative Commons terms, original creators, licences and third-party rights. |
| Safety and integrity | AI must not be used to deceive, impersonate, fabricate evidence, fake endorsements, manipulate discussions or create misleading media. |
7. What members may do
Members may use AI in positive, practical and creative ways, including to:
draft first versions of templates, checklists, discussion papers and articles
turn long content into plain English, accessible summaries or quick-read guides
generate ideas for workshops, consultation prompts, resident engagement activities or learning sessions
create example forms, policies or scripts where these are clearly marked as draft or example content
improve spelling, grammar, tone, structure and readability
translate or simplify content, provided the translation or accessible version is checked before use
create images, diagrams or illustrations, provided synthetic media is not misleading and does not infringe rights
summarise public guidance or open-source material, provided the output is checked and source links are included where appropriate.
8. What members must declare
A declaration is required where AI has materially shaped the content. Minor spelling or grammar checks do not need to be declared unless the AI tool substantially rewrote the meaning, structure or conclusions.
| Use of AI | Declaration required? | Example wording |
|---|---|---|
| AI drafted most or all of the content | Yes | This resource was AI-assisted and human checked before upload. |
| AI summarised a document or meeting notes | Yes | This summary was produced with AI support and checked by the uploader. |
| AI translated or simplified content | Yes | This version was AI-assisted and should be checked against the original before formal use. |
| AI generated an image, voice, video or diagram | Yes | This image/media was AI-generated or AI-edited. |
| AI helped improve grammar only | Usually no | No declaration required unless meaning was changed. |
| AI produced advice-style wording on law, regulation, safety, finance, employment or procurement | Yes, and must be clearly caveated | This is AI-assisted draft content and is not professional advice. It must be checked before use. |
9. Upload checkbox wording
9.1 Required upload declaration
OpenThoughts should add a compulsory checkbox at upload where content is shared as a resource, template, article, toolkit, image, downloadable file or promoted post.
| Recommended upload checkbox I confirm that I am entitled to upload this content, that it does not contain personal, confidential or restricted information, and that any AI-generated or AI-assisted elements have been clearly declared and checked by a human before sharing. |
|---|
9.2 AI-specific upload question
A simple yes/no field should be added:
| AI upload question Has this content been materially generated, drafted, summarised, translated, edited or enhanced using AI? [ ] Yes [ ] No |
|---|
9.3 AI declaration text box
If the answer is yes, the uploader should be asked to add a short public declaration. Suggested placeholder text:
| Declaration field placeholder Example: “This resource was drafted with AI support and has been reviewed, edited and checked before upload.” |
|---|
10. Sign-up checkbox wording
The member sign-up process should include a clear acknowledgement because AI expectations should apply before the first upload or post.
| Recommended sign-up checkbox I understand that OpenThoughts allows AI-generated and AI-assisted content where it is lawful, transparent, human checked and not misleading. I agree to declare material AI use when uploading or publishing content, and I will not use AI to create or share confidential, personal, infringing, unsafe or deceptive material. |
|---|
11. Prohibited AI uses
Uploading confidential, personal, sensitive, commercially restricted or identifiable case information into an AI tool before sharing it on OpenThoughts, unless there is a lawful basis, proper authorisation and appropriate protections.
Publishing AI-generated legal, regulatory, health and safety, safeguarding, employment, finance, procurement or professional advice as though it is verified fact.
Using AI to create fake endorsements, false testimonials, fabricated case studies, invented statistics, fake consultation results or misleading “resident voice” material.
Creating or uploading deepfakes, voice clones, fake screenshots, fake documents, realistic synthetic people presented as real people, or manipulated media intended to mislead.
Impersonating another member, organisation, resident, regulator, councillor, supplier, advertiser or public body.
Using AI to scrape, copy, repackage or pass off another person’s material without permission or proper attribution.
Using AI to generate discriminatory, harassing, hateful, bullying, exploitative or unsafe content.
Using AI to evade moderation, generate spam, flood groups, manipulate ratings, create fake accounts or distort platform engagement.
Using AI-generated content to make claims about a supplier, advertiser, housing provider, council or individual without evidence.
Uploading AI-generated images of identifiable people without appropriate permission, context and disclosure.
12. High-risk content rules
Some content should carry stronger controls because it could affect real-world decisions, compliance, safety or organisational risk.
data protection, UK GDPR, privacy and cyber security
building safety, fire safety, damp and mould, repairs obligations, health and safety and property compliance
complaint handling, legal rights, tenancy enforcement, allocations, homelessness duties and ASB processes
financial advice, procurement, contracting, insurance, grant funding and fundraising compliance
employment, HR, conduct, disciplinary, equality law and competence requirements
safeguarding, domestic abuse, mental health, vulnerability and risk escalation
any document that claims to be “approved”, “compliant”, “legally checked”, “regulator-ready” or “board-assurance ready”.
| High-risk decision High-risk AI-assisted content may be shared as learning, discussion or draft material, but must not be presented as formal advice or definitive compliance guidance unless it has been checked by an appropriately qualified person or competent organisation. |
|---|
13. Professional advice and legal advice restriction
AI-generated content can be useful for drafting, framing and exploring ideas. It should not be treated as professional advice. OpenThoughts should include the following wording wherever AI-assisted resources are uploaded in areas of legal, regulatory, safety, financial, employment or technical risk:
| Required disclaimer wording This content may have been AI-assisted and is shared for learning, discussion and general information only. It is not legal, regulatory, financial, technical, safety, procurement, HR or professional advice. You must check it against your own organisation’s policies, contracts, legal duties, regulator guidance and professional advice before using it. |
|---|
14. Personal data, confidentiality and AI tools
Members must not place personal data or confidential information into AI tools unless they have the right to do so and have considered data protection, confidentiality, security, supplier terms and organisational rules. This is especially important for social housing because prompts can accidentally include resident names, addresses, vulnerabilities, complaints, arrears, repairs, ASB, safeguarding details, health information or staff case data.
Do not paste resident complaints, tenancy files, repair histories, safeguarding notes, staff records, board papers, contracts, unpublished strategies or commercially sensitive data into public AI tools.
Use anonymised, fictionalised or heavily redacted examples where AI is used to help structure or simplify learning content.
If a member uses an organisational AI tool, they must still follow their employer’s AI, data protection, information security and confidentiality policies.
OpenThoughts may remove content if it appears to include personal data, confidential information or information that should not have been shared.
Where personal data may have been disclosed, the Breach Response Procedure should be followed immediately.
15. Copyright, licence and attribution rules
AI does not remove copyright responsibilities. Members must not use AI to launder, disguise, copy, repackage or pass off third-party material. If the source material is not theirs, not properly licensed, confidential, restricted or subject to another organisation’s copyright, it should not be uploaded.
Where content is uploaded under the OpenThoughts default Creative Commons approach, AI-assisted elements must be compatible with that licence and the uploader’s rights.
Members should credit original sources, creators, organisations and licences where required.
Attribution corrections should be handled through the Copyright, Attribution and Takedown Requests process.
OpenThoughts may temporarily remove content while copyright, licensing or attribution concerns are reviewed.
16. AI-generated images, video, voice and media
Generated media can be useful for blogs, learning, campaign visuals and explainers, but it creates specific risks. The following rules apply:
AI-generated or AI-edited media must be declared where it could reasonably be mistaken for real media.
Images of synthetic people should not be presented as real residents, staff members, complainants, case-study subjects or endorsers.
Voice clones and realistic impersonations are not allowed without explicit documented consent and a legitimate purpose approved by OpenThoughts.
AI-generated media must not be used to misrepresent a housing provider, council, supplier, regulator, tenant group or individual.
AI-generated “before and after”, repair, safety, damp and mould, fire safety or neighbourhood images must not be used as evidence unless clearly illustrative and labelled as such.
Advertisers and suppliers must not use AI-generated media to create false product claims, false customer testimonials or misleading performance evidence.
17. AI summaries, translations and accessibility versions
AI can help make content more accessible, but unchecked summaries and translations can change meaning or miss nuance.
AI summaries must be checked against the original before being treated as accurate.
AI translations should be checked by a competent person before they are relied upon for important decisions, legal notices, safety information or formal consultation.
AI-generated plain-English or easy-read style versions should be reviewed for accuracy, tone, dignity and accessibility.
Where an AI summary is published, it should state that the full source should be checked before action is taken.
18. OpenThoughts use of AI
OpenThoughts may use AI to improve the platform, but this should be disclosed clearly and governed carefully. Permitted uses may include:
search support and content discovery
resource tagging and categorisation
suggested related groups or resources
drafting platform guidance, help text or summaries
moderation triage or risk flagging
accessibility improvements such as summaries or alternative text suggestions
spam detection and duplicate content detection.
| Disclosure decision OpenThoughts should publish a short AI transparency statement explaining whether AI is used for moderation, search, recommendations, content suggestions or accessibility support. AI should support moderation decisions but should not be the only basis for high-impact decisions such as membership removal, long-term suspension or advertiser termination. |
|---|
19. Moderation and enforcement
OpenThoughts may take action where AI use breaches this policy, member terms or platform rules. Action may include:
asking the member to add or correct an AI declaration
editing or adding a label where appropriate
temporarily hiding content while it is reviewed
removing content that is misleading, unsafe, infringing, confidential or unlawful
issuing a warning or requiring retraining/acknowledgement of the rules
restricting upload privileges
suspending or removing membership
terminating supplier or advertiser access where relevant
reporting serious issues to relevant organisations or authorities where required by law or policy.
| Circular arguments wording OpenThoughts will look at genuine concerns properly. We will not enter into circular arguments about obvious breaches, repeated misuse, deliberate concealment of AI-generated content, fake evidence, impersonation, harassment, spam or attempts to bypass moderation. |
|---|
20. Appeals and disputes
Members may challenge an AI-related moderation decision through the OpenThoughts Complaints and Appeals Policy. This includes disputes about whether AI was declared properly, whether content was misleading, whether an upload was removed fairly or whether a restriction is proportionate.
An appeal should explain what decision is being challenged, why the member believes the decision was wrong and any supporting evidence.
Content may remain hidden during an appeal where there is a risk of harm, confidentiality breach, copyright infringement, misleading claims or reputational damage.
Final appeal outcomes should be recorded for governance and learning.
21. Supplier and advertiser rules
Suppliers and advertisers may use AI to create adverts, sponsored articles, images, product explainers and promotional resources, but they must be transparent and accurate.
AI-generated claims must be backed by real evidence.
AI-generated case studies or testimonials must not be presented as real unless they are real and permission has been obtained.
AI-generated images of products, services, people, homes, repairs or outcomes must not mislead members about what is being offered.
Sponsored content that is AI-assisted must still comply with OpenThoughts advertising, supplier, accessibility, copyright and moderation rules.
OpenThoughts may reject or remove AI-assisted advertising that is exaggerated, unverifiable, unsafe, discriminatory, deceptive or inconsistent with the site’s ethos.
22. Practical labels for the website
| Label | When to use |
|---|---|
| AI-assisted | For content drafted, structured, summarised, translated, edited or materially improved using AI. |
| AI-generated image | For images substantially created by AI. |
| AI-edited media | For media materially changed using AI. |
| Human checked | For AI-assisted content reviewed by a person before upload. |
| Draft / example only | For templates that need organisational checking before use. |
| Professional check required | For high-risk topics that should not be relied on without qualified review. |
| Illustrative only | For images, examples, scenarios or case studies that are not real evidence. |
23. Website page wording
The following wording can be used on a public AI Usage page:
| Website-ready wording OpenThoughts welcomes the responsible use of AI. Members may share AI-generated or AI-assisted content where it is useful, lawful, transparent, human checked and not misleading. We ask members to say when AI has materially helped create a post, resource, image, summary or template. We do not allow AI to be used to upload confidential or personal information, create fake evidence, impersonate people, mislead members, breach copyright or present unverified material as professional advice. AI should help us think better together - not replace judgement, honesty or accountability. |
|---|
24. Internal review checklist for moderators
[ ] Has the member declared material AI use? [ ] Does the content contain personal, confidential or restricted information? [ ] Could the content be mistaken for professional advice? [ ] Does the content make legal, regulatory, safety, financial, employment or technical claims? [ ] Are any statistics, case studies or evidence claims sourced or clearly caveated? [ ] Could any image, voice, video, screenshot or case study mislead people into thinking it is real? [ ] Does the content respect copyright, Creative Commons rules and attribution expectations? [ ] Is the content discriminatory, harmful, defamatory, manipulative or unsafe? [ ] Does the content need a label, disclaimer, correction, temporary removal or escalation? [ ] Does the issue need to be recorded in the moderation log, IP complaint register, breach log or complaints register?25. Records to keep
OpenThoughts should maintain proportionate records of AI-related governance decisions, including:
AI-related moderation decisions
member warnings or restrictions for AI misuse
AI declaration corrections
removed AI-generated or AI-assisted content
deepfake, impersonation or synthetic media concerns
copyright, attribution and takedown issues involving AI
data protection or confidentiality concerns linked to AI prompts or outputs
supplier and advertiser AI content disputes
platform AI tools used by OpenThoughts and their purposes
AI risk assessments and review notes.
26. Governance and review
Because AI tools, regulation and public expectations are changing quickly, this policy should be reviewed at least every six months. It should also be reviewed after any serious AI-related incident, complaint, takedown request, data protection issue, misleading content concern or major change to platform functionality.
The Platform Owner should approve the policy and any material changes.
Moderators should receive short guidance on how to apply the policy consistently.
Upload and sign-up wording should be tested with members to make sure expectations are clear.
Suppliers and advertisers should be required to comply through their terms and booking process.
The policy should be cross-linked from the Upload Agreement, Member Terms, Privacy Policy, Copyright and Takedown page, Complaints and Appeals page and Supplier / Advertiser Terms.
27. Implementation plan
| Action | Owner | Priority | Evidence of completion |
|---|---|---|---|
| Approve “AI allowed with declaration and human checking” as the platform position | Platform Owner | High | Signed policy approval |
| Add AI declaration checkbox to upload forms | Website / Platform Admin | High | Live upload form screenshot |
| Add AI acknowledgement to member sign-up | Website / Platform Admin | High | Live registration screenshot |
| Create public AI Usage page | Platform Owner / Content Lead | High | Published page |
| Add AI labels to resource cards and posts | Website / Platform Admin | Medium | Labels visible on test uploads |
| Update supplier and advertiser terms to cover AI-generated claims and synthetic media | Platform Owner | High | Updated terms |
| Create moderation checklist and log fields | Moderation Lead | High | Moderation template |
| Train moderators on AI risk categories and escalation | Platform Owner | Medium | Training note or attendance log |
| Add AI-related categories to complaints, takedown and breach logs | Governance Lead | Medium | Updated registers |
| Schedule six-month review | Platform Owner | Medium | Review date recorded |
28. Source and reference notes
This policy has been prepared as a practical governance document for OpenThoughts and should be checked before formal adoption. It is informed by current UK expectations around responsible AI, transparency, accountability and data protection. Key reference points include:
ICO guidance on AI and data protection: https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/artificial-intelligence/guidance-on-ai-and-data-protection/
ICO generative AI and data protection consultation response: https://ico.org.uk/about-the-ico/what-we-do/our-work-on-artificial-intelligence/response-to-the-consultation-series-on-generative-ai/
UK Government AI regulatory principles: safety, security and robustness; transparency and explainability; fairness; accountability and governance; contestability and redress: https://www.gov.uk/government/publications/implementing-the-uks-ai-regulatory-principles-initial-guidance-for-regulators/implementing-the-uks-ai-regulatory-principles-initial-guidance-for-regulators
OpenThoughts should take legal advice where AI use intersects with data protection, confidentiality, professional advice, intellectual property, regulated advertising, employment, safeguarding or safety-critical content.
Appendix A - Recommended member-facing AI declaration examples
This post was drafted with AI support and edited by me before sharing.
This template was AI-assisted and has been adapted from my own experience. Please check it against your organisation’s policies before use.
This summary was generated with AI support and checked against the original document.
This image is AI-generated and used for illustrative purposes only.
This is an AI-assisted plain-English version. Please refer to the original policy for formal wording.
This resource is a draft/example and not professional advice.
Appendix B - AI incident escalation guide
| Issue | Immediate action | Escalation route |
|---|---|---|
| Undeclared AI-generated resource | Ask for correction or add label | Moderation log |
| AI-generated legal or safety advice presented as fact | Hide pending review and add disclaimer if reinstated | Moderation lead / platform owner |
| Personal or confidential information appears in AI-assisted content | Hide immediately and assess breach risk | Breach Response Procedure |
| Deepfake or impersonation | Remove immediately pending review | Platform owner / Complaints and Appeals |
| Copyright concern involving AI-generated or AI-assisted content | Temporarily remove if credible | Copyright, Attribution and Takedown Requests process |
| Supplier advert uses misleading AI-generated claims | Suspend advert pending evidence | Supplier / Advertiser Terms process |
| Repeated AI misuse by member | Restrict upload rights or suspend | Complaints and Appeals / Membership decision process |
Policy 09Safe, Fair and Responsible Discussion Policy
Defamation and Reputational Risk Policy
Forum, resource, comment, article, supplier and member content controls
| Field | Position |
|---|---|
| Document owner | OpenThoughts Founder / Platform Lead |
| Applies to | Members, contributors, moderators, authors, advertisers, suppliers, partners and anyone submitting content to OpenThoughts |
| Recommended public page title | Safe, Fair and Responsible Discussion |
| Linked public wording | Do not post unverified allegations. Discuss issues, processes and learning, not personal attacks. |
| Status | Approved and implemented governance policy |
| Review cycle | Every 12 months, or sooner after a serious complaint, legal threat, platform incident or regulatory change |
This policy explains how OpenThoughts supports constructive discussion while managing legal, fairness and reputational risk.
1. Recommended Decision
Decision: OpenThoughts should adopt a clear, published defamation and reputational risk policy that permits robust sector learning and constructive challenge, but prohibits unverified allegations, personal attacks, naming individual staff negatively, unsupported claims of unlawful conduct, malicious or reckless statements, and content that creates avoidable legal or reputational risk for OpenThoughts or others.
Best solution for the site: The policy should sit publicly as a plain-English page called “Safe, Fair and Responsible Discussion”, while the full operational policy is retained internally for moderators and decision-makers. This gives members clear expectations before they post, gives moderators a consistent basis for action, and protects the site ethos: open-source learning without becoming a place for blame, rumour or reputational harm.
| Decision area | Recommended position | Why this fits OpenThoughts |
|---|---|---|
| Default approach | Allow honest, evidence-led, constructive discussion of service issues, processes, learning and improvement. | OpenThoughts is designed to improve the sector through shared learning, not to silence challenge. |
| Hard line | Do not allow unverified allegations, personal attacks, or negative naming of individual staff members. | This protects people from unfair harm and stops forums drifting into blame or gossip. |
| Organisational criticism | Allow responsible, evidenced discussion of organisations where information is public, factual, proportionate and framed around learning. | This allows useful debate while reducing legal and reputational risk. |
| Moderation power | Reserve the right to edit, hide, remove, restrict or escalate content where there is legal, safety, confidentiality, data protection or reputational risk. | The platform must be able to act quickly where risk is high. |
| Repeated misuse | Use staged sanctions: guidance, warning, temporary restrictions, suspension and account removal. | This is fair, transparent and avoids endless informal argument. |
2. Legal and Risk Context
OpenThoughts is a UK-facing platform for professional discussion, shared resources, templates, ideas and sector learning. Because the site will include forums, comments, resource descriptions, adapted documents, supplier content and member-generated posts, it needs clear guardrails for reputational risk.
Under the Defamation Act 2013, a statement is not defamatory unless its publication has caused, or is likely to cause, serious harm to the reputation of the claimant. For bodies that trade for profit, serious harm means serious financial loss or likely serious financial loss.
The Act also includes defences including truth, honest opinion and publication on a matter of public interest, but OpenThoughts should not rely on members understanding these legal tests before posting. The safer approach is clear user rules, evidence standards and fast moderation routes.
The Online Safety Act 2023 also reinforces the importance of user-to-user services having systems and processes to reduce risks from illegal content and to respond when content appears. OpenThoughts should treat legal and reputational complaints as platform governance issues, not only as informal disputes.
Source references: Defamation Act 2013 - legislation.gov.uk; Defamation Act 2013 explanatory notes on serious harm; UK Government Online Safety Act explainer
3. Purpose of this Policy
Protect OpenThoughts as a professional, trusted and constructive sector platform.
Allow open discussion, honest learning and improvement without allowing personal attacks, rumour or unfair reputational harm.
Give members, advertisers and suppliers clear rules before they post, upload, comment or publish.
Give moderators a fair and consistent decision framework.
Create a clear route for complaints, corrections, takedowns, appeals and repeated misuse.
Support the OpenThoughts ethos: share what helps the sector learn; do not use the platform to attack, shame or accuse others without proper basis.
4. Scope
| Covered content | Examples |
|---|---|
| Forum posts and replies | Discussion threads, comments, peer challenge, resource feedback, member-to-member replies. |
| Uploaded resources | Templates, case studies, toolkits, policies, checklists, guidance notes and adapted documents. |
| Blogs and articles | Member-written articles, OpenThoughts editorial content, guest posts, opinion pieces and interviews. |
| Profiles and listings | Member profiles, organisation descriptions, supplier profiles, advertiser listings and promotional copy. |
| AI-assisted content | AI-generated or AI-assisted summaries, templates, discussion prompts, images, videos or resource descriptions. |
| Events and learning content | Webinars, event descriptions, recordings, slides, chat transcripts and Q&A notes. |
| Private messages where available | Any direct messaging, reporting tools or community messaging functions hosted by OpenThoughts. |
Out of scope: This policy does not replace the Privacy Policy, Data Protection Complaints process, Copyright and Takedown Requests policy, AI Usage Policy, Accessibility Statement, Supplier / Advertiser Terms, or the wider Platform Complaints and Appeals Policy. Those documents should cross-refer to this policy where reputational risk or harmful allegations are involved.
5. Core Principles
| Principle | Meaning |
|---|---|
| Constructive challenge is welcome | Members may challenge ideas, systems, service design, processes, communication, policy, regulation, evidence and outcomes. Challenge must be framed respectfully and with a learning purpose. |
| Attack the issue, not the person | Members must discuss the process, decision, system, document, service, barrier or learning point. They must not use OpenThoughts to shame or attack named individuals. |
| Evidence before allegation | Where a claim could harm reputation, the member must have a reasonable basis for it and should present it carefully, proportionately and with context. |
| Public information must still be framed responsibly | Even where something is public, members must avoid exaggerated, misleading, malicious or selective framing. |
| No naming individual staff negatively | Individual staff members, residents, complainants, contractors or members of the public should not be named in a negative or accusatory way unless there is a strong public-interest basis and OpenThoughts has reviewed the risk. |
| No trial by forum | OpenThoughts is not a court, regulator, employer grievance route, complaints handler for housing providers, or place to run personal disputes. |
| Moderation is risk management, not censorship | OpenThoughts may remove, edit, hide, restrict or escalate content where it creates legal, safety, confidentiality, safeguarding, data protection or reputational risk. |
| Fair process matters | Where practical, members should be told why content has been moderated and given a fair route to challenge a decision, except where doing so would increase risk or undermine safety. |
6. The Clear Line for Members
OpenThoughts position: Say what happened, what was learned, what could improve and what evidence supports it. Do not use the platform to accuse, shame, threaten or speculate about people or organisations.
| Allowed | Not allowed |
|---|---|
| “This process caused delay because the handoff between teams was unclear. Here is the learning.” | “The repairs manager at [name] is incompetent and should be sacked.” |
| “In our experience, residents were confused by the wording in this letter. We changed it and complaints reduced.” | “This organisation deliberately misleads tenants.” |
| “The Ombudsman published findings on this case; here are the public learning points.” | “I know they are breaking the law but cannot share how I know.” |
| “This policy may create risk if vulnerable residents cannot understand the escalation route.” | “This team does not care about vulnerable residents.” |
| “I disagree with this supplier’s approach because the evidence suggests it may exclude digitally marginalised residents.” | “This supplier is a scam.” |
7. Prohibited Defamation and Reputational Risk Content
Unverified allegations about unlawful, dishonest, corrupt, discriminatory, abusive, negligent, unsafe or malicious behaviour.
Negative naming of individual staff members, residents, board members, councillors, contractors, suppliers or members of the public.
Accusations that an organisation has acted unlawfully unless the matter is public, evidenced, proportionate and responsibly framed.
Claims based on rumour, hearsay, screenshots without context, private messages, anonymous sources, or “people are saying” statements.
Content that invites pile-ons, harassment, targeted pressure, doxing, humiliation or coordinated reputational attack.
Misleading editing of quotes, images, recordings, AI outputs, case studies or documents.
Content that presents opinion as fact where it could damage reputation.
Personal grudges, employment disputes, live complaints, litigation, grievance matters or unresolved contractual disputes framed as public allegations.
Posting confidential, privileged, embargoed, internal or commercially sensitive information to support an allegation.
AI-generated accusations, summaries or profiles that have not been checked and evidenced by a human.
8. Responsible Framing Rules
| Use this framing | Avoid this framing |
|---|---|
| “The published report says…” | “They are clearly guilty of…” |
| “Based on the information available to me…” | “Everyone knows…” |
| “This may indicate a risk…” | “This proves they…” |
| “The learning point appears to be…” | “They do not care…” |
| “This is my professional view, and others may see it differently…” | “Only an idiot would…” |
| “The issue seems to be with the process…” | “The named officer caused…” |
| “A safer approach may be…” | “This provider always lies…” |
Members should use neutral, evidence-led language, especially when discussing named organisations, suppliers, policies, public decisions, published Ombudsman findings, regulatory action or sector incidents.
9. Website-Ready Public Page Wording
Recommended page title: Safe, Fair and Responsible Discussion
OpenThoughts is here for learning, not personal attacks
OpenThoughts exists to help people across housing, local government and related sectors share ideas, resources, practice and learning. We welcome constructive challenge. We do not allow the platform to be used for unverified allegations, personal attacks, naming individual staff negatively, or damaging claims that cannot be responsibly evidenced.
Talk about issues, processes and learning
Please focus on what happened, what the learning is, what could improve, and what evidence supports your point. Discuss policies, systems, service design, communication, engagement, outcomes and resident experience. Do not attack individuals.
Do not post unverified allegations
Do not post allegations that a person or organisation has acted unlawfully, dishonestly, corruptly, abusively, discriminatorily, negligently or maliciously unless the matter is public, evidenced, proportionate and responsibly framed. OpenThoughts may remove or restrict content that creates legal or reputational risk.
Naming people
Do not name individual staff members, residents, complainants, contractors or members of the public in a negative or accusatory way. Where a public report names someone, still focus on the published learning and avoid unnecessary personal criticism.
If something is serious
If your concern involves danger, safeguarding, fraud, discrimination, criminal activity, data breach, professional misconduct or unlawful behaviour, use the proper reporting route first. OpenThoughts is not a regulator, court, employer grievance process or complaints body.
Moderation
We may edit, hide, remove or restrict content where it creates legal, safety, confidentiality, data protection or reputational risk. We will look at genuine concerns properly. We will not enter into circular arguments about obvious breaches.
10. Sign-Up, Upload and Posting Controls
10.1 Recommended sign-up checkbox
I agree to use OpenThoughts for constructive professional discussion and shared learning. I will not post unverified allegations, personal attacks, negative naming of individual staff members, or content that could unfairly damage the reputation of a person or organisation.
10.2 Recommended upload checkbox
I confirm that this upload does not contain unverified allegations, confidential information, personal attacks, negative naming of individual staff members, or content that could create avoidable legal or reputational risk. I have removed or anonymised unnecessary names and identifiers.
10.3 Recommended forum reminder
Before posting: is this evidence-led, fair, necessary and focused on learning? Please discuss issues, processes and improvement, not personal attacks.
11. Moderation and Review Process
| Stage | Action | Target timescale |
|---|---|---|
| 1. Identification | Content is identified through moderator review, member report, automated flag, keyword alert, complaint or legal notice. | Immediate once identified |
| 2. Initial risk triage | Moderator assesses whether content is low, medium, high or urgent risk. | Same working day where possible |
| 3. Temporary action | Content may remain live, be edited, be hidden, be locked, or be removed temporarily pending review. | Immediate for high or urgent risk |
| 4. Evidence check | OpenThoughts considers whether the statement is factual, opinion, evidenced, public, proportionate and necessary for learning. | Within 3 working days where practical |
| 5. Decision | Decision may include no action, attribution/correction, edit request, partial removal, full removal, warning, restriction or escalation. | Normally within 5 working days |
| 6. Communication | Where appropriate, OpenThoughts tells the member and/or complainant the outcome in proportionate terms. | Within 2 working days of decision |
| 7. Appeal | Member may appeal through the Complaints and Appeals Policy, except where the content is obviously unlawful, unsafe, malicious, repetitive or subject to legal instruction. | Appeal normally within 10 working days |
12. Defamation and Reputational Risk Triage Matrix
| Risk level | Indicators | Default action |
|---|---|---|
| Low | General criticism of a process or policy. No named individual. No allegation of unlawful or dishonest conduct. Evidence-led and constructive. | Leave live. Moderator may add guidance or ask for clearer framing. |
| Medium | Named organisation criticised strongly. Potentially reputational wording. Evidence unclear. Could be reframed as learning. | Temporarily edit, ask author to provide evidence/reframe, or hold for moderation. |
| High | Allegation of unlawful, dishonest, unsafe, discriminatory, corrupt, abusive, negligent or malicious behaviour. Named organisation or identifiable person. Evidence weak or private. | Hide or remove pending review. Escalate to Platform Lead. Consider legal advice. |
| Urgent | Legal threat, injunction risk, doxing, harassment, live litigation, serious allegation against identifiable person, confidential evidence, safeguarding or criminal allegation. | Remove or disable immediately. Preserve evidence. Escalate. Consider legal/safeguarding/data protection route. |
13. Naming Individuals and Organisations
13.1 Individual staff members and private individuals
Do not name individual staff members negatively.
Do not identify people through job title plus organisation if that would make them easy to identify.
Do not upload screenshots, letters, call notes, complaint records or correspondence showing names, email addresses, phone numbers, signatures or personal identifiers unless there is a clear lawful basis and moderation approval.
Use role-level or process-level wording instead, such as “the repairs team”, “the contractor pathway”, “the complaint escalation stage” or “the communication process”.
13.2 Organisations
Named organisations may be discussed where the discussion is factual, fair, proportionate, relevant and preferably based on public information.
Where criticism is based on a public report, link or clearly identify the public source and focus on learning.
Do not imply unlawful conduct, dishonesty, corruption or deliberate harm unless that is clearly supported by a public, reliable source and is framed responsibly.
Where in doubt, anonymise the organisation and focus on the learning point.
14. Reports, Complaints and Appeals
| Scenario | Route |
|---|---|
| A person says content damages their reputation | Use the Defamation / Reputational Risk Report route and log in the Moderation and Legal Risk Register. |
| A member says their content was unfairly removed | Use the Platform Complaints and Appeals Policy. |
| A person says their personal data has been exposed | Use the Data Protection Complaints and Breach Response Procedure. |
| A copyright owner says material has been misused | Use the Copyright, Attribution and Takedown Requests Policy. |
| An advertiser disputes moderation of promotional content | Use Supplier / Advertiser Terms and the Complaints and Appeals Policy. |
| A serious allegation may need external reporting | Consider safeguarding, fraud, whistleblowing, legal, regulatory or police routes as appropriate. |
15. Defamation / Reputational Risk Report Form
| Information requested | Notes / response |
|---|---|
| Your name | |
| Your email address | |
| Your organisation, if relevant | |
| Are you reporting content about yourself, your organisation or someone else? | |
| URL or location of the content | |
| Date you saw the content | |
| Exact words or material you are concerned about | |
| Why do you believe the content is false, unfair, misleading or damaging? | |
| Is the content about an identifiable person? If yes, who? | |
| Is any legal action already underway or threatened? | |
| What outcome are you requesting? | Correction / edit / attribution change / temporary removal / full removal / right of reply / other |
| Supporting evidence | |
| Declaration | I believe the information in this report is accurate and I am raising it in good faith. |
16. Repeat Misuse and Member Sanctions
| Level | Trigger | Possible action |
|---|---|---|
| Guidance | First minor issue, poor wording, accidental naming, unclear evidence. | Moderator guidance, edit request, reminder of rules. |
| Warning | Repeated low-level issue or one medium-risk post. | Written warning, temporary pre-moderation, restricted posting. |
| Restriction | Repeated warnings, refusal to edit, inflammatory conduct, repeated naming or allegations. | Temporary suspension, posting limits, removal from groups, loss of upload rights. |
| Removal | Serious breach, malicious allegation, doxing, legal threat, harassment, confidentiality breach, repeated refusal to follow rules. | Account suspension or termination, supplier/advertiser removal, referral to relevant route where necessary. |
17. AI, Images, Video and Misleading Media
AI-generated or AI-assisted content must be declared in line with the AI Usage Policy.
AI must not be used to generate allegations, fake evidence, fabricated quotes, false screenshots, false images, manipulated recordings or misleading profiles.
Deepfakes, impersonation, misleading generated media and synthetic content that could damage a person or organisation are prohibited.
AI summaries of reports, complaints, Ombudsman findings or regulatory documents must be checked by a human before publication.
Where AI content discusses a named organisation, the author must verify the source material and avoid presenting AI interpretation as fact.
18. Evidence Preservation and Records
OpenThoughts should keep a Moderation and Legal Risk Register for high-risk reports, legal threats, takedown decisions and appeals.
Before removing high-risk content, capture a secure copy of the content, URL, date, author account, report received and moderation decision, unless doing so would itself create an unlawful retention risk.
Retain records in line with the Records Retention Schedule and data protection principles.
Do not share complainant details with the author unless necessary, lawful and proportionate.
Where formal legal correspondence is received, keep an audit trail and seek legal advice before making detailed admissions, denials or public statements.
19. Moderator Decision Checklist
Is a person, organisation, supplier, staff member, contractor or resident named or identifiable?
Does the content allege unlawful, dishonest, corrupt, abusive, discriminatory, unsafe, negligent or malicious behaviour?
Is the statement presented as fact, opinion, experience or question?
What evidence is provided? Is it public, reliable and proportionate?
Could the same learning point be made without naming the person or organisation?
Is the content necessary for sector learning, or is it mainly personal attack or reputational pressure?
Does the content include personal data, confidential material, screenshots or private correspondence?
Is there any indication of live litigation, employment dispute, grievance, police matter, safeguarding matter or regulator involvement?
Would a reasonable reader understand the content as fair comment and learning, or as an accusation?
Should the content be left live, edited, anonymised, hidden, removed, locked, escalated or referred for legal advice?
20. Template Responses
20.1 To a member whose post needs editing
Thanks for contributing to OpenThoughts. Your post raises a potentially useful learning point, but some wording could create reputational or legal risk because it names or identifies a person/organisation and includes allegations that are not evidenced on the platform. Please reframe the post around the issue, process, evidence and learning, and remove unnecessary names or identifying details. We are happy to support constructive challenge, but we cannot host personal attacks or unverified allegations.
20.2 To a complainant reporting reputational concern
Thank you for raising this concern. We will review the content against our Defamation and Reputational Risk Policy. While we review it, we may temporarily hide or restrict the content if we believe there is a potential legal, safety, confidentiality, data protection or reputational risk. We may ask you for further information, including the exact wording you are concerned about, where it appears, why you believe it is inaccurate or harmful, and what outcome you are requesting.
20.3 Moderation outcome: content removed
We have removed or restricted the content because it did not meet OpenThoughts’ rules on safe, fair and responsible discussion. The platform supports constructive learning and challenge, but we do not allow unverified allegations, personal attacks, negative naming of individual staff members, or content that creates avoidable legal or reputational risk. You may appeal this decision through the Platform Complaints and Appeals Policy, unless the content involved an obvious breach or formal legal risk.
21. Implementation Plan
| Action | Owner | Priority |
|---|---|---|
| Publish public page: “Safe, Fair and Responsible Discussion”. | Platform Lead / Web Admin | High |
| Add sign-up checkbox confirming no unverified allegations or personal attacks. | Web Admin | High |
| Add upload checkbox covering reputational risk and unnecessary names. | Web Admin | High |
| Add forum reminder above post box for evidence-led, fair and learning-focused posts. | Web Admin | High |
| Create report form for reputational concerns. | Platform Lead | High |
| Create moderation and legal risk register. | Platform Lead / Moderator | High |
| Train moderators on the triage matrix and decision checklist. | Platform Lead | High |
| Cross-link to AI Usage Policy, Copyright Takedown, Complaints and Appeals, Supplier Terms and Data Protection documents. | Web Admin | Medium |
| Review forum categories and resource upload journeys for high-risk content prompts. | Moderator / Web Admin | Medium |
| Annual policy review and post-incident review after high-risk cases. | Platform Lead | Medium |
22. Governance and Review
| Governance item | Requirement |
|---|---|
| Policy owner | OpenThoughts Founder / Platform Lead. |
| Operational owner | Moderation Lead or appointed platform administrator. |
| Review cycle | At least annually, or sooner after a legal complaint, takedown dispute, high-risk moderation case, supplier dispute or relevant legal/regulatory change. |
| Legal advice trigger | Formal pre-action correspondence, solicitor letter, court correspondence, injunction threat, repeated allegations about a named person, high-profile organisation dispute, or uncertain public-interest defence. |
| Training | All moderators should understand this policy before reviewing forums, resources, comments or complaints. |
| Audit | Quarterly sample review of moderation decisions and complaints to check consistency, fairness and learning. |
Appendix A: Plain-English Member Guide
Be brave about ideas, but careful with allegations.
Challenge systems, not people.
Use evidence, not rumour.
Anonymise where possible.
Do not name staff members negatively.
Do not accuse an organisation of breaking the law unless you are relying on public, reliable evidence and you frame it responsibly.
If the issue is serious, use the proper reporting route first.
OpenThoughts may remove content if it creates legal or reputational risk, even if the author intended to help.
Policy 10Creative Commons Licence, Upload Terms and Attribution Rules
Creative Commons Licence Decision, Upload Terms and Attribution Rules
Recommended default licence: CC BY-NC-SA 4.0 International
| Final Decision OpenThoughts should adopt Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, known as CC BY-NC-SA 4.0, as the default licence for member-uploaded resources, templates, guides, learning materials, discussion outputs, good practice examples and other copyrightable content that the site is designed to share for sector learning. This is the best fit because it protects the open-source ethos of the platform, requires attribution, prevents unauthorised commercial reuse, and keeps adapted versions available under the same non-commercial share-alike terms. | Final Decision OpenThoughts should adopt Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International, known as CC BY-NC-SA 4.0, as the default licence for member-uploaded resources, templates, guides, learning materials, discussion outputs, good practice examples and other copyrightable content that the site is designed to share for sector learning. This is the best fit because it protects the open-source ethos of the platform, requires attribution, prevents unauthorised commercial reuse, and keeps adapted versions available under the same non-commercial share-alike terms. |
|---|---|
| Document owner | OpenThoughts website owner / platform administrator |
| Applies to | OpenThoughts website, groups, forums, resource library, downloadable materials, member uploads and advertiser/supplier submissions where expressly accepted |
| Version | 1.0 |
| Effective date | 04 May 2026 |
| Review cycle | At least annually, or sooner if Creative Commons guidance, platform use, legal risk or commercial model changes |
| Status | Approved and implemented policy and upload agreement wording |
1. Purpose of this document
This document sets out the recommended Creative Commons licensing position for OpenThoughts and provides ready-to-use wording for the website, sign-up flow, upload flow, attribution guidance and contributor agreement. It is designed to reduce ambiguity, protect the platform, and make clear to members and contributors what they are agreeing to when they upload or use shared materials.
It should be used alongside the OpenThoughts privacy policy, terms of use, cookie policy, professional advice disclaimer, supplier/advertiser terms, accessibility statement, records retention schedule and breach response procedure.
2. Executive recommendation
The recommended default licence for OpenThoughts is:
Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0).
This should be the default licence for normal community contributions and platform-published learning content, unless a specific page, download, advertiser submission, commissioned resource, paid product or third-party material clearly states a different licence or usage permission.
3. Why CC BY-NC-SA 4.0 is the best fit for OpenThoughts
It supports the movement philosophy: OpenThoughts is built around sharing ideas, resources, practical learning and sector-wide improvement. The licence allows people to copy, share, adapt and build on material, which matches the platform’s open learning purpose.
It protects against commercial extraction: The NonCommercial element means others cannot take member-shared resources and use them primarily for commercial advantage or monetary compensation without separate permission.
It preserves the commons: The ShareAlike element means adapted versions must be shared under the same terms, helping to prevent a shared sector resource being closed down, re-sold or locked away.
It gives contributors credit: The Attribution element requires users to credit the creator, link to the licence and indicate if changes were made.
It is familiar and globally recognised: Creative Commons licences are widely recognised and suitable for copyrightable works such as text, templates, diagrams, learning materials and guidance documents.
It creates a clear upload standard: The same default position can be built into sign-up, upload forms, resource pages, website terms and contributor prompts.
4. Important limitation: the deed is not the legal licence
OpenThoughts should not rely only on the plain-English Creative Commons deed. Creative Commons makes clear that the deed is a summary, not the legal code. The binding licence terms are contained in the legal code. The website should therefore link to both the readable deed and the full legal code, and explain that users are responsible for checking the official licence terms before relying on them.
Official licence deed: https://creativecommons.org/licenses/by-nc-sa/4.0/
Official legal code: https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode
5. Scope: what the default licence should apply to
| Content type | Apply CC BY-NC-SA 4.0? | Notes / exceptions |
|---|---|---|
| Member-uploaded documents, templates and practical tools | Yes | Default licence unless the upload form states otherwise or the contributor does not own the rights. |
| Forum posts, comments and discussion contributions | Yes, with care | The platform terms should say that members grant OpenThoughts permission to host, display, preserve, moderate and share contributions under the default licence, where copyright applies. |
| OpenThoughts-created free resources | Yes | Use the default licence unless the resource is part of a paid product, restricted download or commissioned work. |
| Paid downloads, premium content or commercial products | Not automatically | Use separate paid-content terms. CC BY-NC-SA 4.0 may undermine commercial sales if applied to paid products unintentionally. |
| Advertiser or supplier promotional material | No, unless expressly agreed | Advertisers should grant OpenThoughts a hosting/display licence, not necessarily Creative Commons rights for all users. |
| Third-party articles, images, diagrams or extracts | No, unless compatible | Only upload where the contributor has the right to license the material under CC BY-NC-SA 4.0 or the third-party licence is compatible. |
| Personal data, confidential information or case-specific resident stories | No | Do not treat consent, confidentiality or data protection as solved by copyright licensing. Separate permissions and anonymisation are required. |
| Software code, plugins or technical scripts | Usually no | Creative Commons itself does not recommend CC licences for software. Use an appropriate software licence if code sharing becomes part of the site. |
6. Plain-English website explanation
Recommended wording for the public website:
| OpenThoughts default sharing licence OpenThoughts exists to help people working across social housing, councils, local authorities and related services share practical learning, ideas and resources for the benefit of the sector. Unless a resource clearly says otherwise, member-uploaded resources and OpenThoughts free learning materials are shared under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International licence, known as CC BY-NC-SA 4.0. This means you may copy, share, remix, adapt and build on the material for non-commercial purposes, provided you give appropriate credit, link to the licence, say whether you made changes, and share any adapted version under the same licence. You must not use the material for commercial purposes without separate written permission. You must not upload material if you do not own it, do not have permission to share it, or cannot license it under these terms. The Creative Commons deed is a helpful summary, but the legal code is the licence that matters. Please check the official licence before relying on it. |
|---|
7. Upload checkbox wording
The upload form should include mandatory unchecked boxes. The contributor should not be able to upload until each required box is ticked.
☐ Rights ownership: I confirm that I own this material or have the necessary rights and permissions to upload it to OpenThoughts.
☐ Creative Commons licence: I agree that, unless OpenThoughts agrees otherwise in writing, this material will be made available under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International licence, known as CC BY-NC-SA 4.0.
☐ Non-commercial sharing: I understand that other users may copy, share, adapt and build on this material for non-commercial purposes, with attribution and under the same licence.
☐ No restricted material: I confirm that the material does not contain confidential information, personal data, resident-identifiable details, commercially sensitive information, copyrighted third-party material, or anything I am not allowed to share.
☐ No professional advice reliance: I understand that OpenThoughts is a learning and sharing platform, and uploaded resources should not be presented as legal, financial, regulatory, medical, procurement or professional advice unless this is expressly authorised and properly qualified.
☐ Accuracy and responsibility: I confirm that the material is accurate to the best of my knowledge and that I remain responsible for the content I upload.
8. Sign-up checkbox wording
The member sign-up flow should include a licence acknowledgement, so members cannot later say that they did not realise the platform used Creative Commons sharing terms.
☐ I understand that OpenThoughts is a sector learning and collaboration platform where eligible content may be shared under Creative Commons terms.
☐ I understand that, unless stated otherwise, free resources and member-uploaded materials may be available under CC BY-NC-SA 4.0.
☐ I agree not to upload material unless I have the right to share it and license it on these terms.
☐ I agree not to use OpenThoughts content for commercial purposes unless the licence permits it or I have separate written permission.
☐ I agree to give proper attribution when reusing, adapting or sharing OpenThoughts materials.
9. Attribution wording
OpenThoughts should give users a simple copy-and-paste attribution format. This should appear near downloads and in a help page.
Recommended attribution format:
| “[Title of resource]” by [Creator name / organisation], shared via OpenThoughts, licensed under CC BY-NC-SA 4.0. Available at: [URL]. Changes made: [yes/no and brief description]. |
|---|
Example:
“Resident Engagement Workshop Template” by Jane Smith, shared via OpenThoughts, licensed under CC BY-NC-SA 4.0. Available at: www.openthoughts.example/resources/resident-engagement-workshop-template. Changes made: shortened and adapted for a neighbourhood consultation session.
10. Commercial use restriction
OpenThoughts should define commercial use in plain English without trying to rewrite the official licence. Suggested wording:
| You may not use CC BY-NC-SA 4.0 OpenThoughts materials primarily for commercial advantage or monetary compensation without separate written permission. This includes, for example, selling the material, placing it behind a paid product, using it as paid consultancy collateral, packaging it into a commercial training product, or using it to promote a supplier service as if it were your own proprietary content. This does not stop genuine non-commercial learning, internal sector improvement, staff development, resident engagement planning, or public-benefit use within eligible housing, council, local authority, voluntary, academic or community settings, provided the licence terms are followed. |
|---|
11. Platform terms: licence grant to OpenThoughts
OpenThoughts also needs permission to host, display, moderate, back up, preserve and make uploaded content available. The Creative Commons licence governs reuse by the public or members, but the platform terms should include a separate operational licence from the contributor to OpenThoughts.
Recommended clause:
| By uploading or submitting content to OpenThoughts, you grant OpenThoughts a worldwide, non-exclusive, royalty-free licence to host, store, copy, display, publish, moderate, adapt for accessibility, index, promote, archive and make that content available through the platform for the purposes of operating, improving and promoting OpenThoughts and its sector learning objectives. Unless a different licence is clearly stated and accepted by OpenThoughts, you also agree that eligible uploaded content may be made available to users under CC BY-NC-SA 4.0. |
|---|
12. What users must not upload
Material they did not create and do not have permission to share under CC BY-NC-SA 4.0.
Confidential employer documents, internal board papers, unpublished strategies, procurement documents, commercial proposals or legally privileged material.
Personal data, resident names, addresses, photographs, case references, complaints details or identifiable lived-experience stories unless fully anonymised and lawfully shared.
Images, logos, diagrams, paid templates, screenshots or extracts owned by third parties unless the contributor has explicit permission or the licence is compatible.
Material that is defamatory, discriminatory, harassing, misleading, unsafe or unlawful.
Professional advice presented as definitive legal, financial, regulatory, medical, safeguarding, procurement or technical advice without appropriate qualification and approval.
13. Recommended content labels
| Label | Meaning |
|---|---|
| OpenThoughts Free Resource - CC BY-NC-SA 4.0 | Default free resource licence. |
| Member Upload - CC BY-NC-SA 4.0 | Default user-generated resource licence. |
| Restricted Use - See Terms | For paid downloads, commissioned materials, advertiser content or materials with special restrictions. |
| Third-Party Content - Licence Varies | For content not owned by OpenThoughts or the uploader. |
| No Reuse Without Permission | For sensitive, paid, commissioned or restricted material. |
14. Decision note: why not another licence?
| Option | Why it was considered | Decision |
|---|---|---|
| CC BY 4.0 | Most open and allows reuse with attribution, including commercial use. | Too open for OpenThoughts because suppliers or consultants could commercially extract member content. |
| CC BY-SA 4.0 | Open, attribution-based and requires adaptations to stay share-alike. | Allows commercial use, which is not aligned with the current protection need. |
| CC BY-NC 4.0 | Prevents commercial use while allowing adaptation. | Does not require adaptations to be shared under the same terms, so the commons is weaker. |
| CC BY-NC-ND 4.0 | Strongly protects against modification. | Too restrictive for a platform based on remixing, adapting, improving and building shared learning. |
| All Rights Reserved | Maximum control. | Contradicts the open-source learning ambition and makes reuse unclear. |
| CC BY-NC-SA 4.0 | Allows sharing and adaptation, requires attribution, prevents commercial use, and keeps adaptations under the same terms. | Recommended default licence. |
15. Governance controls
Upload moderation: OpenThoughts should retain the right to review, reject, edit, remove, restrict or relabel uploaded content at any time.
Licence visibility: Every download page should display the licence label, attribution format and reuse restriction before download.
Audit trail: The platform should record who uploaded the resource, when they uploaded it, which boxes they ticked, what licence was accepted and the version of terms in force at that time.
Takedown process: OpenThoughts should provide a route for copyright complaints, confidentiality concerns, data protection concerns and licence disputes.
Commercial permissions: Requests for commercial reuse should be routed to OpenThoughts for written permission and, where needed, consent from the original contributor.
Annual review: The licence model should be reviewed annually alongside the platform’s commercial model, advertiser offer, paid resource strategy and legal risk register.
16. Takedown and licence dispute clause
Recommended website clause:
| If you believe material on OpenThoughts infringes copyright, includes confidential information, contains personal data, breaches licence terms or has been uploaded without proper authority, please contact OpenThoughts immediately with the resource link, your concern, your contact details and any supporting evidence. OpenThoughts may temporarily remove or restrict access to the material while the matter is reviewed. Where appropriate, OpenThoughts may contact the uploader, amend the licence label, remove the content, preserve evidence, or take further action under the platform terms. |
|---|
17. Implementation checklist
☐ Add CC BY-NC-SA 4.0 wording to the website footer, terms of use and resource library pages.
☐ Add sign-up acknowledgement checkboxes for licence awareness and non-commercial use.
☐ Add upload checkboxes confirming ownership, permission, licence acceptance and no restricted material.
☐ Show the licence label and attribution wording on each eligible resource page.
☐ Create a “How to Attribute OpenThoughts Resources” help page.
☐ Separate advertiser/supplier content from member resource content.
☐ Create a takedown and rights complaint route.
☐ Record consent, licence version and timestamp for each upload.
☐ Train moderators/admins on copyright, confidentiality, personal data and commercial use red flags.
☐ Review paid content, premium resources and supplier materials so they are not accidentally licensed under CC BY-NC-SA 4.0.
18. Recommended final policy statement
| OpenThoughts should proceed with CC BY-NC-SA 4.0 as its default licence for free, copyrightable, member-shared and OpenThoughts-created learning resources. This gives the site the right balance: open enough to enable practical sector sharing and adaptation, but protected enough to prevent commercial exploitation and preserve the shared learning commons. The licence should be supported by plain-English website wording, mandatory checkboxes at sign-up and upload, visible attribution rules, clear commercial-use restrictions, a separate platform operating licence, and a robust takedown process. |
|---|
19. Source references for final checking
Creative Commons CC BY-NC-SA 4.0 deed: https://creativecommons.org/licenses/by-nc-sa/4.0/
Creative Commons CC BY-NC-SA 4.0 legal code: https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode
Creative Commons licence chooser: https://creativecommons.org/chooser/
Creative Commons licence overview: https://creativecommons.org/cc-licenses/
20. Legal review note
This document is a policy and operational drafting aid. It is not legal advice. OpenThoughts should obtain professional legal advice before publication, particularly because the site will combine member-generated content, supplier/advertiser activity, possible paid resources, professional sector discussion and user uploads.
Policy 11Copyright, Attribution and Takedown Requests Policy
Copyright, Attribution and Takedown Requests Policy
A strengthened notice-and-takedown process for shared resources, templates, logos, adapted documents and member-generated content
| Decision for OpenThoughts The recommended solution is to publish a dedicated website page called “Copyright, Attribution and Takedown Requests” and to make this process part of the member terms, upload process and supplier/advertiser terms. The page should not be hidden in a long privacy policy. It should be easy to find from the footer, upload page, resource library and member help area. |
|---|
| Document control | Details |
|---|---|
| Owner | OpenThoughts website owner / platform administrator |
| Applies to | Members, contributors, moderators, suppliers, advertisers, partners and visitors who upload, share, adapt, download or complain about content on OpenThoughts |
| Version | 1.0 – approved and implemented policy |
| Status | Approved and implemented for website publication |
| Default content licence alignment | CC BY-NC-SA 4.0 International for eligible member-shared resources, subject to the Creative Commons licence decision document and exceptions stated below |
| Review cycle | Every 12 months, or earlier after a serious IP complaint, repeated misuse, platform change or legal change |
1. Purpose of this policy
OpenThoughts is designed as an open-source thinking and resource-sharing space for the UK housing, local authority and community sectors. Its value depends on members being able to share learning, templates, adapted documents, presentations, tools, discussion prompts, case studies and practical resources in a safe, lawful and respectful way.
This policy creates a formal, transparent and fair route for copyright, trade mark, attribution and intellectual property complaints. It explains what someone must provide when reporting a concern, what OpenThoughts will do during review, when content may be temporarily removed, how originators can challenge misuse, how attribution corrections are handled and what happens if a member repeatedly uploads material they do not own or cannot licence.
2. Recommended decision
| Recommended decision OpenThoughts should adopt a “notice, pause, review, resolve and learn” process. This means that OpenThoughts does not try to decide complex legal disputes as a court would, but it does act quickly, keeps evidence, pauses access where risk is credible, asks both sides for information, corrects attribution where appropriate, removes or restores material based on the evidence available, and records repeated misuse. |
|---|
This approach is the best fit for the site because OpenThoughts will host a high volume of member-shared material, including resources that may be adapted from organisational templates, presentations, policy wording, logos, images, diagrams, meeting packs and training tools. A clear takedown route protects contributors, reduces the risk of misuse, supports trust in the platform and reinforces the Creative Commons ethos without allowing “open sharing” to become accidental copying.
| Decision area | Position for OpenThoughts |
|---|---|
| Default route | Dedicated website page: “Copyright, Attribution and Takedown Requests”. |
| Default licence assumption | Eligible member-uploaded resources are shared under CC BY-NC-SA 4.0 International only where the uploader owns the rights or has authority to share on those terms. |
| When to temporarily remove content | Where a complaint is credible, the material is high-risk, the rights position is unclear, the content includes logos or third-party materials, or continuing publication could cause harm. |
| When to correct rather than remove | Where the concern is missing attribution, incorrect title/source, wrong creator credit, missing licence wording or an honest metadata error. |
| When to permanently remove content | Where the uploader cannot show ownership/permission, a rights-holder objects with sufficient evidence, material breaches the upload rules, or the content includes restricted third-party material. |
| Repeated misuse | Escalating sanctions: education, warning, upload restrictions, temporary suspension, removal from groups, account termination and, where necessary, notification to affected parties. |
| Legal disputes | OpenThoughts should not provide legal advice or adjudicate complex ownership disputes. It should preserve evidence, pause content where proportionate and encourage parties to seek independent advice. |
| Legal and licensing basis Creative Commons states that the CC BY-NC-SA 4.0 deed is only a summary and the legal code is the operative licence. The UK Intellectual Property Office explains that copyright protects original works such as written, artistic, photographic and digital material, and that online image use can raise copyright issues even where content is easy to copy from the internet. OpenThoughts should therefore combine open licensing with a practical takedown process and careful upload declarations. |
|---|
3. Scope
This policy applies to content uploaded, posted, linked, embedded, displayed, shared or adapted through OpenThoughts, including:
resource library documents, templates, checklists, reports, slide decks and spreadsheets;
forum posts, group posts, comments, articles, blogs and member updates;
images, photographs, graphics, icons, diagrams, illustrations, infographics and screenshots;
logos, badges, organisational marks, branded templates and trade marks;
training materials, workshop tools, facilitation resources and forms;
advertiser, sponsor, supplier and partner content;
materials adapted from other organisations, publications, conferences, websites or internal work products;
metadata such as creator name, licence wording, attribution statement and source link.
4. Definitions
| Term | Meaning for OpenThoughts |
|---|---|
| Copyright concern | A concern that content has been copied, uploaded, adapted, distributed or displayed without the right to do so. |
| IP complaint | A complaint about copyright, trade marks, logos, moral rights, database rights, design rights, confidential content or similar rights. |
| Attribution correction | A request to correct the creator name, source, title, link, copyright notice, licence statement or acknowledgement attached to content. |
| Originator | The person or organisation that created the material or owns/controls the relevant rights. |
| Uploader | The member, supplier, advertiser or partner who uploaded or posted the material to OpenThoughts. |
| Temporary removal | A precautionary step where content is hidden, unpublished or access-restricted while a concern is reviewed. |
| Repeat misuse | A pattern of uploading content without ownership, permission or accurate attribution, even after warnings or guidance. |
5. OpenThoughts upload rule
The following rule should appear at sign-up, upload, resource contribution and supplier/advertiser submission points:
| Website upload rule Only upload content that you created, own, are authorised to share, or are legally entitled to licence through OpenThoughts. Do not upload content if you cannot allow it to be used under the OpenThoughts default licence, or if it contains third-party material, logos, images, paid content, confidential information, personal data or employer-owned material that you do not have permission to share. |
|---|
6. Required upload declarations
OpenThoughts should add mandatory checkboxes to the upload journey. These reduce later disputes and help evidence the basis on which content was accepted.
☐ I confirm that I created this content, own the rights, or have permission to upload and share it through OpenThoughts.
☐ I confirm that the content does not include third-party copyright material unless I have permission or it is clearly identified and lawfully reusable.
☐ I confirm that the content does not include logos, branding, photographs, screenshots, paid resources, confidential documents or employer-owned material unless I am authorised to share them.
☐ I understand that eligible member-shared resources may be made available under CC BY-NC-SA 4.0 International, unless OpenThoughts has approved a different licence or restriction.
☐ I understand that OpenThoughts may remove, restrict or edit metadata for this content if a copyright, attribution or IP concern is raised.
☐ I understand that repeated misuse may lead to upload restrictions, suspension or removal of my account.
7. Public website page wording
The following wording can be used as the public page, with practical contact details added before publication.
| Suggested page introduction OpenThoughts is built on shared learning, practical resources and open-source thinking for the housing and community sectors. We want members to share useful materials, but we also respect copyright, attribution, trade marks and the rights of original creators. If you believe that content on OpenThoughts uses your material without permission, uses your logo or brand incorrectly, misses required attribution, or is otherwise a copyright or intellectual property concern, please contact us using the process below. |
|---|
8. How to report a copyright, attribution or IP concern
A complainant should be asked to provide enough information for OpenThoughts to identify the content, understand the concern and assess what action is proportionate. OpenThoughts should provide a form as well as an email route.
| Information required | Why OpenThoughts needs it |
|---|---|
| Your full name and organisation, if relevant | To understand who is making the request and whether they are the rights-holder or authorised representative. |
| Your contact email address and telephone number | To acknowledge, ask questions and confirm the outcome. |
| URL, group name, resource title or screenshot of the content | To locate the exact material complained about. |
| The rights you say are affected | To distinguish copyright, attribution, trade mark/logo, confidentiality, image rights or other concerns. |
| Evidence that you own or control the rights | For example, original publication link, source file, contract, licence, creation date, organisational ownership statement or other evidence. |
| What outcome you are requesting | For example, correction, attribution update, temporary removal, permanent removal, restriction of download, or contact with the uploader. |
| A statement that the information is accurate | To discourage misuse of the complaint route. |
| Whether urgent harm is alleged | For example, commercial harm, personal data, confidential content, safeguarding concern, reputational harm or misleading use of a logo. |
9. Complaint intake and acknowledgement
OpenThoughts should acknowledge receipt promptly and create a case log. The initial acknowledgement should not admit liability or make a final decision. It should confirm that the complaint will be reviewed and that content may be temporarily restricted if appropriate.
| Stage | Target approach |
|---|---|
| Initial acknowledgement | Within 2 working days where reasonably practicable. |
| Triage | Assess urgency, credibility, content type, ownership evidence and risk. |
| Temporary action | Hide, restrict or pause downloads where the complaint is credible or the risk is material. |
| Uploader contact | Ask the uploader to respond and provide evidence of ownership, permission, licence or source. |
| Decision | Decide whether to restore, correct, restrict or remove content based on evidence available. |
| Record keeping | Keep the complaint, evidence, decision, communications and outcome. |
10. Triage categories
| Category | Examples | Default action |
|---|---|---|
| Low risk attribution issue | Missing creator name, broken source link, incomplete licence wording, incorrect title. | Correct metadata where evidence supports the change. Notify uploader where appropriate. |
| Medium risk rights concern | Template appears copied from an organisation, adapted policy with unclear origin, unlicensed image, copied article extract. | Temporarily restrict while asking uploader for evidence. Remove if evidence is insufficient. |
| High risk IP concern | Use of another organisation’s logo, paid training material, commercially licensed image, confidential employer document, copied branded toolkit. | Temporarily remove immediately pending review. Escalate internally. |
| Urgent harm concern | Personal data in a document, confidential information, safeguarding content, potentially defamatory or misleading material. | Remove or restrict immediately and refer to the relevant OpenThoughts procedure, such as breach response, moderation or safeguarding-style escalation. |
| Bad-faith or unclear complaint | Complaint lacks evidence, appears vexatious, targets lawful criticism, or seeks to suppress fair comment. | Ask for further evidence. Do not remove solely because someone dislikes the content, unless risk justifies temporary restriction. |
11. What OpenThoughts will do while reviewing
☐ Log the complaint with date, time, complainant, content URL, uploader, evidence received and initial risk rating.
☐ Preserve a copy of the content, upload metadata and relevant communications before removal where lawful and proportionate.
☐ Consider whether the content should be temporarily hidden, download-disabled, access-restricted or left online during review.
☐ Contact the uploader unless doing so would increase risk or conflict with legal advice.
☐ Ask the uploader for evidence of ownership, permission, licence, source, employer authorisation or lawful reuse.
☐ Assess whether attribution can solve the concern or whether rights/permission are genuinely disputed.
☐ Keep communications neutral and avoid giving legal advice to either party.
☐ Escalate to the platform owner and legal adviser where there is serious risk, repeated misuse or a threat of legal action.
12. When content may be removed temporarily
Temporary removal is a risk-control step, not a final finding that infringement has occurred. It should be used where proportionate, especially when continuing publication could cause further harm or make the dispute worse.
| Temporary removal should normally happen where | Reason |
|---|---|
| The complaint includes credible evidence of ownership or infringement | OpenThoughts should not continue making disputed material available while evidence is checked. |
| The content includes logos, branding, trade marks or official-looking materials | Misuse could imply endorsement or partnership. |
| The content appears to be a paid resource, training pack, commercial template or restricted publication | Commercial rights may be affected. |
| The content includes personal data, confidential information or internal organisational material | Other legal and trust risks may apply. |
| The uploader cannot be contacted or does not respond within a reasonable time | OpenThoughts should not keep hosting unclear material indefinitely. |
| There is a threat of legal action or platform takedown by a hosting provider | Escalation and risk containment are needed. |
13. Uploader response process
Where content is challenged, the uploader should be given a fair opportunity to explain the rights position unless immediate removal is required. OpenThoughts should ask for practical evidence, not assumptions.
☐ Confirm whether the uploader created the material personally.
☐ Confirm whether the uploader created it in the course of employment and, if so, whether their employer allows sharing.
☐ Ask whether any third-party content is included, such as photos, icons, extracts, screenshots, logos or branded templates.
☐ Ask for any licence, written permission, source link or evidence that the material is available for reuse.
☐ Ask whether the material has already been published under Creative Commons or another open licence.
☐ Ask whether the uploader is willing to amend, remove third-party elements, correct attribution or replace the file.
14. Decision outcomes
| Outcome | When appropriate | Action |
|---|---|---|
| No action | Complaint is unsupported, unclear or not an IP issue. | Tell complainant why no action is being taken and keep the record. |
| Attribution correction | Creator, source, licence, title or link is missing or wrong. | Correct the metadata and notify relevant parties. |
| Content amendment | Issue can be resolved by removing a logo, replacing an image, shortening an extract or adding permission notes. | Ask uploader to amend or OpenThoughts to replace the file where appropriate. |
| Temporary restriction remains | Evidence is incomplete but risk remains credible. | Keep hidden while parties provide evidence or seek advice. |
| Permanent removal | Uploader cannot show ownership/permission, complaint is well evidenced, or content breaches upload rules. | Remove content and issue guidance or warning to uploader. |
| Account action | Repeated or serious misuse, deliberate copying, false declarations or ignoring warnings. | Restrict uploads, suspend account, terminate membership and record the reason. |
| Legal escalation | Threat of proceedings, trade mark dispute, financial claim, complex ownership issue or repeated high-risk behaviour. | Seek independent legal advice and preserve evidence. |
15. Attribution correction process
Not every issue requires full takedown. OpenThoughts should actively encourage correction where the problem is credit, licence wording or source information. This supports the site ethos of openness, learning and respect for originators.
| Correction type | Example wording/action |
|---|---|
| Creator credit | “Created by [Name/Organisation]. Shared on OpenThoughts by [Uploader].” |
| Source link | Add the original URL or document source where available. |
| Licence statement | “Licensed under CC BY-NC-SA 4.0 International, unless otherwise stated.” |
| Adaptation statement | “Adapted from [Original Title] by [Creator], used under [Licence/Permission]. Changes made by [Uploader].” |
| Logo/brand clarification | “Logo used with permission” or remove the logo if permission cannot be evidenced. |
| Employer ownership note | “Shared with permission of [Organisation]” where the content was created in an employment context. |
16. How originators can challenge misuse
An originator should be able to challenge misuse without needing to become a member. The process should respect creators and keep communication clear.
☐ Originators can submit a complaint form or email OpenThoughts directly.
☐ OpenThoughts will ask for evidence of ownership, original source or authority to act.
☐ OpenThoughts may temporarily hide the disputed content while the issue is reviewed.
☐ OpenThoughts may contact the uploader for evidence and explanation.
☐ OpenThoughts may correct attribution, restrict access, remove content or refuse the request depending on the evidence.
☐ OpenThoughts will confirm the outcome to the originator where appropriate.
☐ OpenThoughts will not disclose unnecessary personal data about members or complainants.
17. Repeat misuse and member sanctions
The member community must understand that OpenThoughts is not a place to upload whatever is useful if the uploader does not have the right to share it. Repeated misuse undermines the whole platform.
| Level | Behaviour | Action |
|---|---|---|
| Level 1 – education | First minor attribution mistake or misunderstanding. | Correction, guidance and reminder of upload rules. |
| Level 2 – warning | Uploading content without clear rights, failing to respond, or repeated metadata errors. | Formal warning and removal/restriction of content. |
| Level 3 – upload restriction | Repeated questionable uploads or failure to follow guidance. | Temporary restriction on uploads and requirement for pre-approval. |
| Level 4 – suspension | Serious or repeated misuse, false declaration, misuse of logos, copied paid resources. | Temporary account suspension pending review. |
| Level 5 – removal | Deliberate infringement, repeated breach after warning, refusal to cooperate or serious risk to OpenThoughts. | Account termination and removal from groups/resource access as permitted by member terms. |
18. Supplier, advertiser and partner content
Suppliers and advertisers should be held to a higher standard because their content may promote paid services and could use third-party creative assets. The supplier/advertiser terms should include the following strengthened clause.
| Supplier / advertiser IP warranty The supplier or advertiser warrants that all content, copy, images, logos, claims, graphics, downloads, advertisements and promotional materials supplied to OpenThoughts are owned by the supplier/advertiser or are used with full permission. The supplier/advertiser must indemnify OpenThoughts against reasonable losses, claims, costs, complaints and expenses arising from alleged or actual infringement caused by their supplied material, subject to legal review of final contract wording. |
|---|
19. Records and evidence log
Every complaint should be recorded in a central IP complaints register. This helps spot patterns, respond consistently and demonstrate responsible platform governance.
| Field | What to record |
|---|---|
| Case reference | Unique complaint number. |
| Date received | Date and time complaint arrived. |
| Complainant details | Name, organisation, contact details and authority to act. |
| Content details | URL, title, file name, uploader, group, resource category and upload date. |
| Complaint type | Copyright, attribution, trade mark/logo, confidential material, personal data, other. |
| Evidence received | Links, files, screenshots, ownership evidence, licence evidence, permission evidence. |
| Initial risk rating | Low, medium, high or urgent. |
| Temporary action | None, metadata correction, hidden, downloads disabled, removed, escalated. |
| Uploader response | Summary and evidence provided. |
| Decision | Restore, correct, amend, restrict, remove, sanction, legal escalation. |
| Outcome date | Date closed or next review date. |
| Learning action | Upload checkbox change, guidance update, moderation training, supplier warning, system change. |
20. Response templates
20.1 Acknowledgement to complainant
| Template Thank you for contacting OpenThoughts about a copyright, attribution or intellectual property concern. We have logged your request and will review the information you have provided. We may temporarily restrict access to the material while we consider the issue. We may also contact the uploader for further information. Please note that OpenThoughts cannot provide legal advice or act as a court in disputed ownership matters, but we will take proportionate steps in line with our Copyright, Attribution and Takedown Requests process. |
|---|
20.2 Request for further information
| Template To help us assess your request, please provide the exact URL or title of the content, evidence that you own or control the relevant rights, the specific concern, and the outcome you are asking for. If you are acting on behalf of an organisation or rights-holder, please confirm your authority to do so. |
|---|
20.3 Notice to uploader
| Template A copyright, attribution or intellectual property concern has been raised about content you uploaded to OpenThoughts. We have temporarily restricted access while we review the issue. Please confirm whether you created the material, own the rights, have permission to share it, or relied on an open licence. Please also identify any third-party content included in the material, such as images, logos, screenshots or extracts. |
|---|
20.4 Attribution correction outcome
| Template We have reviewed the concern and have corrected the attribution/licence/source information attached to the content. The material remains available subject to the corrected information. Thank you for helping us keep shared resources accurate and respectful of originators. |
|---|
20.5 Removal outcome
| Template We have reviewed the information available and have removed or restricted the content because the rights position could not be confirmed, or because the material does not meet the OpenThoughts upload requirements. This decision is based on platform governance and risk management, not a final legal determination of ownership. |
|---|
21. Website form fields
| Form field | Field type |
|---|---|
| Your name | Required text field |
| Your organisation | Optional text field |
| Your email address | Required email field |
| Are you the rights-holder or authorised representative? | Required dropdown: yes / no / unsure |
| Type of concern | Required dropdown: copyright / attribution / logo or trade mark / confidential material / personal data / other |
| URL or title of the OpenThoughts content | Required text field |
| Describe the concern | Required text area |
| What outcome are you asking for? | Checkboxes: attribution correction / temporary removal / permanent removal / contact uploader / other |
| Evidence upload | Optional upload field for screenshots, original files or permission evidence |
| Declaration | Required checkbox confirming that the information is accurate to the best of the submitter’s knowledge |
22. Interaction with other OpenThoughts policies
| Policy/process | How it connects |
|---|---|
| Creative Commons Licence Decision and Upload Agreement | Sets the default licence and confirms that only eligible rights-owned material can be shared under CC BY-NC-SA 4.0. |
| Member Terms and Community Rules | Provides user obligations, prohibited uploads and account sanctions. |
| Supplier / Advertiser Terms | Requires supplier ownership, permission, warranties and indemnity for promotional materials. |
| Privacy Policy and Data Protection Register | Applies where a takedown concern includes personal data. |
| Breach Response Procedure | Applies where uploaded material exposes personal data, confidential information or security-sensitive content. |
| Accessibility Statement | Applies when correcting documents, images, alt text or resource metadata. |
| Records Retention Schedule | Sets retention periods for complaint records and evidence. |
23. Practical implementation checklist
☐ Create a footer page titled “Copyright, Attribution and Takedown Requests”.
☐ Add a “Report copyright or attribution concern” link to every resource page.
☐ Add mandatory upload checkboxes confirming ownership, permission and licence position.
☐ Add a licence/attribution metadata field to resource uploads.
☐ Add moderation guidance so admins know when to hide, correct or remove content.
☐ Create an internal IP complaints register.
☐ Update member terms to include repeat misuse sanctions.
☐ Update supplier/advertiser terms to include IP warranties and indemnity wording.
☐ Add a takedown email address or webform inbox monitored by the platform owner.
☐ Train moderators on copyright basics, Creative Commons, attribution and escalation.
☐ Review the process annually and after any serious complaint.
24. Recommended public footer wording
| Footer link wording Copyright, Attribution and Takedown Requests – OpenThoughts respects creators, contributors and rights-holders. Report copyright, attribution, logo, licence or IP concerns here. |
|---|
25. References for legal review
The following sources should be reviewed when finalising the public wording and legal terms:
Creative Commons, Attribution-NonCommercial-ShareAlike 4.0 International deed: https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en
Creative Commons, Attribution-NonCommercial-ShareAlike 4.0 International legal code: https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode.en
UK Intellectual Property Office / GOV.UK, Copyright notice: digital images, photographs and the internet: https://www.gov.uk/government/publications/copyright-notice-digital-images-photographs-and-the-internet/copyright-notice-digital-images-photographs-and-the-internet
GOV.UK, Intellectual property and copyright guidance: https://www.gov.uk/topic/intellectual-property/copyright
26. Final publication note
This document is a governance and implementation draft for OpenThoughts. It is not legal advice. The public webpage, member terms, supplier/advertiser terms and any indemnity wording should be reviewed by a suitably qualified legal adviser before publication or contractual use.
Policy 12Accessibility Statement Policy
Accessibility Statement Policy
Strengthened website accessibility statement, operational policy and improvement framework
| Document owner | OpenThoughts Founder / Website Owner |
|---|---|
| Applies to | OpenThoughts website, member areas, forums, groups, resources, blogs, forms, downloads and supplier/advertiser content |
| Prepared for | OpenThoughts |
| Version | 1.0 |
| Date approved | 04 May 2026 |
| Next review | Within 12 months or sooner after major website, platform, content or legal changes |
Important: this document is a strong policy and website statement template. It should be checked against the final live website, platform configuration, accessibility audit findings and legal position before publication.
Contents
1. Purpose of this policy
2. Accessibility commitment
3. Scope of the statement
4. Legal and standards context
5. Website accessibility statement for publication
6. What users should be able to do
7. Compliance status and known limitations
8. Non-accessible content and disproportionate burden approach
9. Third-party, member and advertiser content
10. Alternative formats and reasonable adjustments
11. Feedback, reporting barriers and complaints
12. Testing and monitoring approach
13. Roles and responsibilities
14. Accessibility by design requirements
15. Content standards for OpenThoughts editors
16. Supplier and advertiser accessibility requirements
17. Accessibility improvement plan
18. Review and governance
19. Evidence record and audit log
20. Appendix A: accessibility checklist
21. Appendix B: source notes
1. Purpose of this policy
This Accessibility Statement Policy sets out OpenThoughts’ commitment to making its website, member spaces, digital resources and published content accessible to as many people as possible. It provides both:
a strengthened accessibility statement suitable for publication on the OpenThoughts website;
an internal policy framework for maintaining accessibility as the site grows;
practical standards for content creators, moderators, suppliers, advertisers and administrators;
an improvement and evidence framework to support accountability.
OpenThoughts is designed as an open-source thinking and collaboration space for the social housing sector. Accessibility is therefore not an optional enhancement. It is central to the purpose of the movement: creating a place where housing professionals can share ideas, resources and learning without avoidable digital, communication or participation barriers.
2. Accessibility commitment
OpenThoughts is committed to providing a website and digital community that is accessible, usable and inclusive. Our aim is that people can access the site regardless of disability, neurodivergence, assistive technology, digital confidence, device type, connection quality or preferred way of engaging.
OpenThoughts will work towards meeting Web Content Accessibility Guidelines WCAG 2.2 Level AA as the target accessibility standard for the website and core digital content. This means designing and maintaining content so that it is perceivable, operable, understandable and robust.
Our commitment includes:
using plain English wherever possible;
building pages with clear headings and logical structure;
supporting keyboard navigation;
providing meaningful link text;
adding alternative text to informative images;
avoiding colour-only communication;
ensuring forms are clear and labelled;
reviewing downloadable resources for accessibility before publication;
making reasonable adjustments and alternative formats available where practicable;
embedding accessibility into supplier, advertiser and member contribution expectations.
3. Scope of the statement
This policy applies to the OpenThoughts website and associated digital services, including:
public website pages;
membership registration and login journeys;
member profile and account areas;
groups, forums and discussion spaces;
blogs, articles and insight pages;
downloadable documents, templates and resources;
event listings, booking pages and promotional pages;
advertising, sponsor and supplier promotional spaces;
contact, enquiry, consent and subscription forms;
email templates and automated website communications where controlled by OpenThoughts.
Where OpenThoughts links to external websites, tools or third-party platforms, those external services are outside OpenThoughts’ direct control. However, OpenThoughts will seek to choose accessible tools and suppliers wherever reasonably possible.
4. Legal and standards context
OpenThoughts is not being presented here as a public sector body. However, because its intended audience includes housing associations, councils, local authorities and professionals delivering public-facing services, the site should adopt a strong accessibility approach aligned with recognised UK public sector expectations and international accessibility standards.
The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require public sector bodies to make websites and mobile apps accessible and to publish an accessibility statement. Although OpenThoughts may not be directly in scope as a private or independent platform, using this structure creates a stronger, more credible standard.
The Web Content Accessibility Guidelines are internationally recognised. WCAG 2.2 is the current W3C recommendation and covers recommendations for making web content more accessible. OpenThoughts’ working target is WCAG 2.2 Level AA for core website pages and member journeys.
This policy should be reviewed if OpenThoughts changes legal status, enters into public-sector delivery contracts, receives public funding, provides commissioned services, or becomes responsible for delivering digital services on behalf of a public sector body.
5. Website accessibility statement for publication
The following section can be published on the OpenThoughts website, once the details in square brackets have been completed and checked against the live website.
OpenThoughts Accessibility Statement
This accessibility statement applies to www.openthoughts.co.uk.
OpenThoughts is committed to making its website accessible to as many people as possible. We want people using our site to be able to access information, join relevant groups, read and share resources, take part in discussions, complete forms and engage with the OpenThoughts community without unnecessary barriers.
We aim to make the website clear, inclusive and practical for people using different devices, browsers, screen readers, magnification tools, speech recognition software, keyboard navigation or other assistive technologies.
We want users to be able to:
change colours, contrast levels and fonts using browser or device settings;
zoom in without text spilling off the screen;
navigate most of the website using a keyboard;
navigate most of the website using speech recognition software;
listen to most of the website using a screen reader;
understand pages because they use clear headings and plain English;
complete forms with clear labels, instructions and error messages;
access content in alternative formats where reasonable and practicable.
We are working towards meeting the Web Content Accessibility Guidelines version 2.2 Level AA standard across the core OpenThoughts website.
Compliance status
This website is [fully compliant / partially compliant / not yet compliant] with WCAG 2.2 Level AA. We are currently working through accessibility checks and improvements as the website develops.
At the time of publication, the website may contain some areas that are not yet fully accessible. These are likely to include older documents, third-party embedded tools, member-generated content, supplier or advertiser content, and some downloadable files that were not originally created to accessibility standards.
Feedback and contact information
We welcome feedback on the accessibility of OpenThoughts. If you find any accessibility problems, need information in a different format, or experience difficulty using the site, please contact us:
Email: [email protected]
Website contact form: the OpenThoughts contact form
Postal address: [insert if applicable]
Response aim: we aim to acknowledge accessibility enquiries within 5 working days and provide a full response or next step within 20 working days.
When contacting us, please tell us the page or document you were trying to access, the issue you experienced, the assistive technology or device used if relevant, and the format or support that would help.
Alternative formats
Where reasonable and practicable, we can provide information in alternative formats such as accessible Word documents, large print, plain text, simplified summaries or other formats agreed with the person requesting support. Some specialist formats may take longer to arrange.
Reporting accessibility problems
We are always looking to improve the accessibility of OpenThoughts. If you find a problem that is not listed on this page, please tell us so we can investigate and prioritise improvements.
Enforcement and escalation
If OpenThoughts is not directly subject to public sector accessibility enforcement, users should still be able to raise concerns with OpenThoughts and expect a considered response. If OpenThoughts provides services to or on behalf of a public sector body, additional escalation routes may apply and should be identified in the relevant service or contract documentation.
Technical information about this website’s accessibility
OpenThoughts is committed to making its website accessible in line with WCAG 2.2 Level AA. We use a combination of manual checks, automated testing and user feedback to identify and resolve accessibility issues.
Preparation of this statement
This statement was prepared on 04 May 2026. It was last reviewed on 04 May 2026.
This website was last tested on 04 May 2026 using internal review, automated accessibility checks, manual keyboard checks and screen reader sampling.
The next planned accessibility review is 04 May 2026.
6. What users should be able to do
OpenThoughts should be designed so that users can complete the following core tasks as independently as possible:
| Area | Core accessibility outcome |
|---|---|
| Joining | Register for membership, understand eligibility, complete sign-up forms and receive clear confirmation or refusal reasons. |
| Finding content | Use search, menus, headings and filters to find groups, topics, resources, blogs and discussions. |
| Reading | Read pages with good contrast, responsive layout, clear fonts, meaningful headings and plain English. |
| Participating | Join groups, post in forums, comment on blogs or upload resources without avoidable interface barriers. |
| Submitting forms | Use contact, advertising, enquiry and consent forms with labelled fields, clear instructions and error recovery. |
| Downloading resources | Access documents that are structured, readable and compatible with assistive technology where reasonably practicable. |
| Advertising/supplier pages | Understand paid advertiser content clearly and distinguish it from editorial or member content. |
7. Compliance status and known limitations
The accessibility statement must be honest. OpenThoughts should not claim full compliance unless there has been enough testing to support that statement. Until a full audit has been completed, the recommended wording is “partially compliant” or “working towards compliance”.
Known or likely limitations to review include:
PDF documents that may not be fully tagged or readable by screen readers;
older Word, PowerPoint or spreadsheet downloads without headings, alt text or accessible table structures;
embedded video or audio without captions, transcripts or summaries;
third-party plugins, widgets, membership tools or forum components;
member-generated posts that include inaccessible images, unclear links or uploaded documents;
advertiser artwork that does not meet contrast or text readability expectations;
forms with unclear labels, weak error messages or reliance on placeholder text;
visual design elements that rely too heavily on colour, icons or complex imagery;
CAPTCHA, authentication or anti-spam tools that create barriers;
interactive elements that may not have sufficient keyboard focus visibility.
8. Non-accessible content and disproportionate burden approach
Where OpenThoughts identifies non-accessible content, the default position should be to fix it. A disproportionate burden position should only be used after a reasoned assessment, not as a general excuse for inaction.
Before relying on disproportionate burden, OpenThoughts should consider:
the number and type of users affected;
the importance of the content or function;
whether the content is essential to membership, safety, rights, payment, participation or decision-making;
whether there is a lower-cost accessible alternative;
whether the issue can be resolved during normal content maintenance;
whether a third-party supplier can fix the issue;
the size, resources and stage of development of OpenThoughts;
the risk to reputation, inclusion and user trust if the issue remains unresolved.
Where a disproportionate burden decision is made, it must be recorded in the evidence log with the reason, alternative support offered, owner and review date.
9. Third-party, member and advertiser content
OpenThoughts may include content created by members, suppliers, advertisers, sponsors or third-party platforms. This creates additional accessibility risk and must be actively managed.
OpenThoughts should require contributors to follow basic accessibility rules when submitting content, including:
use clear titles and headings;
avoid images of text unless essential;
provide alt text or a short description for meaningful images;
use accessible file formats wherever possible;
avoid low contrast graphics;
avoid flashing or rapidly moving content;
use descriptive link text instead of “click here”;
ensure videos include captions or transcripts where practicable;
make paid-for promotions clearly identifiable as advertising or sponsored content;
avoid PDFs where an accessible web page would be better.
OpenThoughts may reject, pause, edit or request replacement content where supplier, advertiser or member content creates accessibility barriers or undermines the inclusive purpose of the site.
10. Alternative formats and reasonable adjustments
OpenThoughts should respond positively to reasonable requests for alternative formats or support. Alternative formats may include:
accessible Word document;
plain text version;
large print version;
simplified summary;
HTML web page instead of PDF;
captioned video or transcript;
telephone or email support where an online process is difficult;
step-by-step guidance for completing forms or joining groups.
Requests should be handled consistently using the following process:
acknowledge the request;
confirm what information or support is needed;
identify whether the requested format is reasonable and practicable;
provide the accessible alternative or explain the proposed alternative;
record the request and outcome in the accessibility evidence log;
use repeated requests as evidence for future website improvements.
11. Feedback, reporting barriers and complaints
OpenThoughts should make it easy for users to report accessibility barriers. Accessibility feedback should be treated as service improvement insight, not simply as a complaint.
The website should include a visible accessibility contact route and should capture:
name and contact details, where the user wishes to provide them;
page URL, document title or feature affected;
description of the barrier;
device, browser or assistive technology, where relevant;
impact on the user;
preferred response method;
alternative format or reasonable adjustment requested;
consent to contact the user for follow-up testing, where appropriate.
Accessibility complaints should be triaged by impact:
| Priority | Example issue | Target response approach |
|---|---|---|
| High | Prevents registration, payment, member access, complaint/enquiry submission or core participation. | Acknowledge quickly, provide workaround, assign owner and prioritise fix. |
| Medium | Makes important content difficult to use but workaround exists. | Record, assess and schedule improvement. |
| Low | Minor readability or content issue not blocking task completion. | Add to improvement backlog and fix during routine updates. |
12. Testing and monitoring approach
OpenThoughts should use a blended testing approach. Automated testing is useful but cannot prove accessibility on its own. Manual and user-based checks are essential.
Minimum testing should include:
automated checks using reputable accessibility testing tools;
manual keyboard-only navigation across key journeys;
screen reader sampling on representative pages;
browser zoom and reflow testing at 200% and 400% where relevant;
colour contrast checks;
form label and error message checks;
review of heading hierarchy and page landmarks;
downloadable document accessibility checks;
mobile and tablet checks;
testing of new plugins, templates and major design changes before release.
Core journeys to test regularly:
homepage to joining as a member;
searching for a group;
joining or following a group;
posting or replying in a discussion;
downloading a resource;
submitting a contact enquiry;
submitting an advertiser enquiry;
viewing an advertiser or supplier page;
reading a blog article;
updating account details or preferences.
13. Roles and responsibilities
| Role | Responsibilities |
|---|---|
| Website owner / Founder | Owns the accessibility statement, approves priorities, ensures accessibility is part of website governance and supplier arrangements. |
| Website administrator | Checks pages, menus, plugins, forms, updates and technical changes for accessibility impact. |
| Content editor | Creates accessible pages, headings, links, images, documents and blog content. |
| Community moderator | Encourages accessible member contributions and flags inaccessible uploads or posts. |
| Supplier / developer | Builds and maintains platform features to agreed accessibility standards and fixes defects. |
| Advertiser / promoter | Provides accessible artwork, copy, links, documents and promotional content. |
| Members | Use reasonable care when posting content and follow community accessibility guidance. |
14. Accessibility by design requirements
Accessibility must be considered before publication, not retrofitted after problems occur. OpenThoughts should apply the following design rules:
design for keyboard users as well as mouse and touch users;
keep layouts responsive and avoid horizontal scrolling;
ensure focus indicators are visible;
make calls to action clear and consistent;
avoid complex navigation with hidden or unpredictable menus;
make forms short, labelled and forgiving;
avoid time limits unless essential;
allow users to pause, stop or hide moving content;
make error messages specific and helpful;
ensure membership and advertiser journeys are not dependent on inaccessible documents or images.
15. Content standards for OpenThoughts editors
Every page or article published on OpenThoughts should meet the following content standards:
| Content area | Required standard |
|---|---|
| Headings | Use one clear page title and logical heading levels. Do not use headings only for visual styling. |
| Plain English | Use short sentences where possible. Explain specialist terms. Avoid unnecessary jargon. |
| Links | Use meaningful link text, for example “Download the membership guide” rather than “click here”. |
| Images | Add alt text for informative images. Use empty alt text only for purely decorative images. |
| Tables | Use tables for data, not layout. Include header rows and avoid merged cells where possible. |
| Documents | Prefer accessible web pages. Where downloads are needed, use structured Word or tagged PDF where possible. |
| Video/audio | Provide captions, transcripts or written summaries where practicable. |
| Colour | Do not rely on colour alone to explain meaning. Check contrast. |
| Forms | Use clear field labels, instructions, validation and error messages. |
| SEO | SEO should not override accessibility. Titles, meta descriptions and tags should remain clear and human-readable. |
16. Supplier and advertiser accessibility requirements
Suppliers and advertisers should be required to support OpenThoughts’ accessibility commitment. The following clause can be added to supplier and advertiser terms:
Supplier / advertiser accessibility clause: The Supplier or Advertiser must provide content, artwork, documents, links and promotional materials that are accessible, readable and suitable for publication on an inclusive website. OpenThoughts may reject, remove, suspend or require replacement of any material that fails to meet reasonable accessibility expectations, including poor colour contrast, unreadable text, images of text without alternative copy, inaccessible PDFs, flashing content, unclear links or content that cannot be accessed using assistive technology. The Supplier or Advertiser must co-operate promptly with reasonable accessibility improvement requests.
Advertiser artwork should also meet the following standards:
avoid small text embedded in images;
use clear contrast between text and background;
provide the same key message in text on the page, not only in the graphic;
avoid flashing animation or rapidly changing content;
ensure destination landing pages are accessible where reasonably possible;
provide alt text or image descriptions for promotional images;
ensure promotional claims and calls to action are clear.
17. Accessibility improvement plan
The improvement plan should be maintained as a live action log. A suggested starting plan is set out below.
| Action | Owner | Priority | Evidence of completion | Review date |
|---|---|---|---|---|
| Complete baseline accessibility audit of key public pages. | Website owner / developer | High | Audit report and issue log | 04 May 2026 |
| Test membership registration and login journey using keyboard only. | Website administrator | High | Completed test notes and fixes | 04 May 2026 |
| Review all forms for labels, help text and error messages. | Website administrator | High | Form checklist completed | 04 May 2026 |
| Create accessibility guidance for members posting resources or images. | Content editor | Medium | Guidance page published | 04 May 2026 |
| Add supplier and advertiser accessibility clause to terms. | Website owner | High | Updated terms approved | 04 May 2026 |
| Audit downloadable files and prioritise high-use documents. | Content editor | Medium | Document audit log | 04 May 2026 |
| Check colour contrast across brand palette and buttons. | Designer / developer | High | Contrast report | 04 May 2026 |
| Review plugins and embedded tools for accessibility risks. | Developer | Medium | Plugin review log | 04 May 2026 |
| Publish final accessibility statement on website. | Website owner | High | Statement live and linked in footer | 04 May 2026 |
| Set annual review cycle and post-launch user feedback route. | Website owner | Medium | Review calendar and inbox process | 04 May 2026 |
18. Review and governance
This Accessibility Statement Policy should be reviewed:
at least annually;
after a major website redesign or platform change;
after adding a major plugin, member feature, payment function or forum feature;
after a significant accessibility complaint;
after a legal or regulatory change;
before entering into any public-sector service agreement where accessibility obligations may apply.
The published website statement should include the date it was prepared, last reviewed and last tested. These dates should be kept accurate.
19. Evidence record and audit log
OpenThoughts should maintain an evidence record to demonstrate active accessibility management. This does not need to be complex, but it should be consistent.
| Evidence item | What to record | Frequency |
|---|---|---|
| Accessibility statement | Published version, Date approved, review date, owner. | At publication and every review |
| Audit results | Tool used, pages tested, issues found, severity and owner. | At least annually and after major changes |
| User feedback | Barrier reported, impact, response, fix or workaround. | As received |
| Alternative format requests | Request, decision, format provided, timescale and learning. | As received |
| Supplier checks | Accessibility expectations issued, content reviewed, issues resolved. | For each supplier or advertiser |
| Document checks | High-use downloads reviewed and remediated where needed. | Quarterly or during content refresh |
| Disproportionate burden assessments | Reason, evidence, alternative offered and review date. | Only where relied upon |
20. Appendix A: accessibility checklist
Use this checklist before publishing new pages, resources, advertiser content or major updates.
| Check | Yes/No/N/A | Notes |
|---|---|---|
| Page has a clear title and one H1 heading. | ||
| Headings follow a logical order. | ||
| Text is plain, clear and easy to scan. | ||
| Links explain where they go. | ||
| Images have appropriate alt text or are marked decorative. | ||
| Colour contrast has been checked. | ||
| Information is not conveyed by colour alone. | ||
| Buttons and links can be reached by keyboard. | ||
| Keyboard focus is visible. | ||
| Forms have labels, instructions and helpful error messages. | ||
| Tables have header rows and are not used for layout. | ||
| Videos have captions, transcripts or summaries where practicable. | ||
| Downloads are accessible or an alternative is available. | ||
| Mobile layout works without loss of content. | ||
| No flashing, rapidly moving or auto-playing content creates a barrier. | ||
| Member, supplier or advertiser content has been reviewed before publication. | ||
| Accessibility issue log updated if any problems remain. |
21. Appendix B: source notes
This document has been drafted with reference to recognised accessibility guidance and examples, including:
GOV.UK guidance on accessibility requirements for public sector websites and apps: https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps
GOV.UK accessibility statement example: https://www.gov.uk/help/accessibility-statement
W3C Web Content Accessibility Guidelines WCAG 2.2: https://www.w3.org/TR/WCAG22/
W3C Web Accessibility Initiative WCAG overview: https://www.w3.org/WAI/standards-guidelines/wcag/
GOV.UK Service Manual overview of WCAG 2.2: https://www.gov.uk/service-manual/helping-people-to-use-your-service/understanding-wcag
Note: these references are included for governance traceability. The final website statement should be checked against the live website, actual testing completed and OpenThoughts’ legal status before publication.
Policy 13Complaints and Appeals Policy
Complaints and Appeals Policy
Platform complaints, membership appeals, moderation appeals, takedown disputes, advertiser concerns, data protection complaints and conduct complaints
| Document control | Details |
|---|---|
| Document owner | OpenThoughts Platform Owner / Governance Lead |
| Applies to | Members, contributors, applicants, moderators, suppliers, advertisers, partners and visitors using OpenThoughts |
| Recommended public page title | Complaints and Appeals |
| Version | 1.0 |
| Status | Approved and implemented |
| Review cycle | Every 12 months, or sooner after a major platform, legal, moderation or data protection change |
Decision statement
Recommended solution: OpenThoughts should publish a dedicated “Complaints and Appeals” page, supported by an internal complaints register, defined response times and a clear two-stage review route. This is the best fit for the ambition of the site because OpenThoughts is designed to encourage open sharing while also protecting trust, fairness, moderation standards, intellectual property, data rights and the reputation of the community. The policy should be practical, firm and transparent: genuine concerns will be reviewed properly, but OpenThoughts will not enter into circular arguments about obvious breaches, bad-faith complaints or repeated misuse of the platform.
1. Purpose of this policy
OpenThoughts exists to help people working in social housing, councils, local authorities and connected organisations share ideas, resources, learning, templates, practice examples and discussion in a constructive way. Because the platform relies on membership decisions, moderation, shared resources, advertiser relationships, data handling and member conduct, there must be a clear route for raising concerns and challenging decisions.
This policy sets out how OpenThoughts will handle platform complaints and appeals. It is not a resident complaint procedure, housing landlord complaint procedure, statutory service complaint route or substitute for any employer, regulator, ombudsman or legal process.
membership rejection queries and appeals;
moderation appeals and content restriction decisions;
resource takedown disputes and attribution concerns;
supplier and advertiser complaints;
data protection complaints and data rights concerns;
conduct complaints involving members or contributors;
concerns about unfair treatment, access, accessibility or platform process;
response times, escalation routes and final decision-making.
2. Policy position and final decision
OpenThoughts should adopt a single platform complaints and appeals framework rather than managing complaints informally by email or direct message. The site’s ambition is to be open, collaborative and sector-led, but this only works if decisions are consistent, recorded and capable of fair review.
| Decision area | Recommended position | Reason |
|---|---|---|
| Public page | Create a public page called “Complaints and Appeals”. | Members and non-members need a single, visible route for platform concerns. |
| Scope | Cover membership, moderation, resource disputes, advertisers, data protection, conduct and accessibility/process concerns. | These are the areas most likely to create disagreement, reputational risk or lengthy informal exchanges. |
| Tone | Use plain English: fair, firm, open and proportionate. | The approach should match the OpenThoughts ethos without weakening standards. |
| Stages | Use a two-stage route: Stage 1 review and Stage 2 appeal/final review. | This gives fairness without creating an excessive or endless process. |
| Data protection | Fast-track data protection complaints and data rights issues to the Data Protection Lead. | Privacy matters may have statutory timescales and must be handled separately where required. |
| Moderation | Allow appeals but preserve the right to remove content or restrict accounts while risks are reviewed. | The platform must be able to act quickly where there is harm, misuse, confidentiality risk, IP risk or abusive conduct. |
| Circular arguments | Close repeated, vexatious, abusive or already-decided matters where no new evidence is provided. | This protects the platform and keeps the process fair for everyone. |
| Record keeping | Maintain an internal complaints and appeals register. | This supports consistency, audit trails, lessons learned and trend monitoring. |
3. Plain-English website wording
The following wording can be used on the OpenThoughts website.
OpenThoughts is built on trust, fairness and shared learning. We know that sometimes people may disagree with a decision we make about membership, moderation, uploaded resources, advertising, data protection or conduct on the platform. If you have a genuine concern, we will look at it properly, explain what we can, and take proportionate action where something has gone wrong. We will not enter into circular arguments about obvious breaches of our terms, repeated misuse, abusive behaviour or matters we have already reviewed unless new evidence is provided.
4. What this policy covers
| Complaint or appeal type | Examples | Likely lead |
|---|---|---|
| Membership rejection query | Applicant believes their housing-sector eligibility has been misunderstood or their organisational email was incorrectly rejected. | Membership Lead |
| Moderation appeal | Member disagrees with removal, editing, hiding, warning, suspension, group restriction or forum moderation decision. | Moderation Lead |
| Resource takedown dispute | Contributor disputes removal of a template, guide, image, document, adapted document or attribution decision. | IP / Content Lead |
| Attribution correction | Creator believes they have not been credited properly or a licence statement is incomplete. | IP / Content Lead |
| Advertiser complaint | Supplier/advertiser disagrees with advert rejection, removal, category exclusivity decision, payment issue or compliance concern. | Commercial Lead |
| Data protection complaint | Concern about personal data, consent, privacy notice, erasure, access, marketing preferences, breach handling or misuse of data. | Data Protection Lead |
| Conduct complaint | Concern about bullying, harassment, discrimination, intimidation, spam, sales pressure, misuse of member information or repeated bad-faith behaviour. | Platform Governance Lead |
| Accessibility/process concern | Concern about access barriers, reasonable adjustment, inaccessible content or difficulty using the complaints route. | Accessibility Lead / Platform Governance Lead |
5. What this policy does not cover
resident complaints about a landlord, local authority or housing provider service;
employment grievances between a member and their employer;
professional negligence, legal advice or commercial disputes that must be handled through a contract or formal legal route;
complaints about external websites, services or organisations that OpenThoughts does not control;
requests to resolve sector debates, personal disagreements or policy disagreements where no platform rule has been breached;
anonymous allegations where there is not enough information to review the matter, although OpenThoughts may still investigate risk or safety concerns where possible.
6. Principles
| Principle | What it means in practice |
|---|---|
| Fairness | People affected by a platform decision should be able to understand the reason for the decision and provide relevant evidence. |
| Proportionality | OpenThoughts will not use a heavy process for minor issues, but serious concerns will be handled carefully and recorded. |
| Safety and trust | The platform may remove, restrict or pause content/accounts while reviewing risk. |
| No endless loops | A final decision can be issued where a matter has been reviewed and no new evidence is provided. |
| Evidence-led decisions | Decisions should be based on platform rules, uploaded evidence, terms, policies, licence position, data protection requirements and behaviour records. |
| Respectful communication | People using the complaints route must communicate respectfully. Abusive, threatening or discriminatory contact may lead to restrictions. |
| Privacy by design | Complaint information will be handled confidentially and shared only where needed to review, respond or comply with legal duties. |
| Learning culture | OpenThoughts will use complaint trends to improve guidance, checkboxes, moderation rules, accessibility, supplier arrangements and member communications. |
7. How to raise a platform complaint or appeal
A complaint or appeal should be submitted through the online form or by email to the published OpenThoughts contact route. The form should require enough information to understand the issue without asking people to share unnecessary personal data.
| Information requested | Why it is needed |
|---|---|
| Name and contact email | So OpenThoughts can acknowledge and respond. |
| Membership status | To identify whether the person is an applicant, member, contributor, advertiser, supplier, visitor or affected rights holder. |
| Complaint/appeal category | To route the issue to the right lead. |
| Date of issue or decision | To check response times and relevant records. |
| Relevant URL, group, post, resource, advert or message | To identify the content or decision being challenged. |
| What happened | To understand the concern in the complainant’s own words. |
| What outcome is requested | To understand whether the person wants a correction, reinstatement, apology, explanation, refund review, account review or another action. |
| Evidence or attachments | To support fair review. People must not upload confidential or personal data that is not necessary. |
| Confirmation checkbox | To confirm the complaint is made honestly and that the person understands OpenThoughts may process the information to review and respond. |
8. Response times
The following response times are recommended. They should be published so people know what to expect, but OpenThoughts should keep flexibility for complex matters, legal issues, data protection issues or matters requiring external input.
| Stage or issue | Target response time | Notes |
|---|---|---|
| Acknowledgement | Within 5 working days | Confirm receipt, category and expected next step. |
| Stage 1 platform complaint response | Within 15 working days | May be extended by a further 10 working days if complex. |
| Stage 1 moderation appeal | Within 10 working days | Content or account restrictions may remain in place while reviewed. |
| Urgent safety, abuse, confidentiality or IP risk | Initial review as soon as reasonably possible | OpenThoughts may remove or restrict content immediately while reviewing. |
| Data protection complaint | Acknowledge within 5 working days and route to Data Protection Lead | Data rights requests should follow applicable statutory timescales and privacy procedures. |
| Stage 2 appeal request | Must normally be submitted within 10 working days of Stage 1 decision | Late appeals may be accepted where there is a good reason. |
| Stage 2 final review | Within 20 working days | May be extended if legally or technically complex. |
| Final closure | After Stage 2 decision or earlier if outside scope, abusive, repeated or no new evidence | Explain closure reason where appropriate. |
9. Stage 1: review and response
Stage 1 is the first formal review. The relevant lead should review the complaint, relevant content, policies, terms, member records, moderation notes, upload declarations, licence statements, advertiser agreements, data records and any evidence provided.
Log the complaint or appeal in the internal register.
Check whether urgent action is needed, such as temporary removal, account restriction, advertiser pause, safeguarding-style escalation, data protection escalation or IP review.
Confirm the complaint category and responsible lead.
Review the evidence and any relevant platform terms or policies.
Seek information from relevant internal roles where needed.
Decide whether the complaint is upheld, partly upheld, not upheld, outside scope or closed for another stated reason.
Send a plain-English response explaining the decision, any action taken and appeal options where available.
10. Stage 2: appeal and final review
Stage 2 is not a complete rehearing of every point. It is a review of whether the Stage 1 decision was reasonable, whether relevant evidence was missed, whether the correct policy was applied, or whether new evidence changes the outcome.
The appeal should be reviewed by someone not directly responsible for the original decision where possible.
The appellant should explain why the Stage 1 decision is wrong or incomplete.
OpenThoughts may refuse an appeal that simply repeats the same points without new evidence or a clear review reason.
The Stage 2 response should be marked as the final platform decision unless there is a legal, data protection or contractual route that remains open.
11. Membership rejection queries and appeals
OpenThoughts is designed for the housing arena and may require a confirmed housing association, council, local authority, supplier, regulator, charity, professional or relevant organisational email depending on the membership type. Membership may be refused where eligibility cannot be verified or where there is a risk to the integrity of the community.
| Possible issue | OpenThoughts approach |
|---|---|
| Applicant used a personal email address | Request a qualifying organisational email where membership rules require this. |
| Applicant says they work in housing but cannot use a work email | Consider alternative evidence only where the site has chosen to allow it; otherwise explain the membership rule. |
| Supplier or advertiser applied as a housing member | Redirect to the correct supplier/advertiser route if appropriate. |
| Previous account restriction or conduct concern | Review the history and decide whether membership would create risk. |
| Appeal accepted | Approve, request further evidence, approve with conditions, or redirect to another membership category. |
| Appeal not accepted | Explain the rule and close unless new evidence is provided. |
12. Moderation appeals
OpenThoughts should allow members to appeal moderation decisions, but it must protect the community from misuse. Moderation decisions may include editing, hiding, removing or locking content; issuing a warning; pausing posting rights; suspending or removing a member; limiting access to groups; or restricting direct contact features.
| Moderation risk | Typical action while reviewing |
|---|---|
| Abuse, harassment, discrimination, bullying or intimidation | Content removed or hidden; account may be restricted pending review. |
| Confidential organisational material | Content hidden immediately while ownership and permission are checked. |
| Copyright/IP concern | Content temporarily removed or restricted pending IP review. |
| Spam or aggressive sales activity | Posts removed; account or advertiser access may be restricted. |
| Potentially inaccurate professional guidance | Content may be flagged, edited, contextualised or removed depending on risk. |
| Circular or disruptive arguments | Thread may be locked; member may be warned or restricted. |
| Accidental policy breach | OpenThoughts may correct, educate and reinstate where appropriate. |
13. Resource takedown disputes and attribution corrections
Where a resource is removed because of copyright, attribution, confidentiality, licence, personal data or quality concerns, the contributor may challenge the decision. OpenThoughts should keep the resource unavailable while the review is ongoing if there is a credible rights, confidentiality or data protection concern.
Attribution corrections should usually be treated as a correction request first, not as an adversarial complaint.
If attribution is missing or incomplete but the licence position is otherwise clear, OpenThoughts may correct the attribution rather than remove the resource.
If ownership, permission or licence rights are unclear, OpenThoughts may keep the resource removed unless the uploader provides evidence they are entitled to share it.
If a third-party rights holder raises a credible complaint, temporary removal is the safest default while reviewing.
Repeated upload of material a member does not own or cannot licence may lead to account restrictions or removal.
14. Advertiser and supplier complaints
Advertisers and suppliers should use this route for complaints about advert rejection, removal, copy changes, category restrictions, placement concerns, payment disputes, exclusivity concerns or platform treatment. This policy works alongside the Supplier / Advertiser Terms and Agreement. Contractual terms will take priority where there is a conflict.
| Issue | Recommended approach |
|---|---|
| Advert rejected before publication | Explain the reason, such as quality, relevance, compliance, unsuitable claims, conflict with values or category limits. |
| Advert removed after publication | Explain whether removal is temporary or permanent and what evidence or correction is needed. |
| Advertiser challenges restricted category numbers | Refer to the OpenThoughts policy of limiting advertiser numbers by category to protect user experience and trust. |
| Complaint about performance or clicks | Review only where a specific commitment was made; avoid promising traffic, leads or conversion unless contracted. |
| Payment or invoicing issue | Route to the Commercial Lead and finance process. |
| Supplier conduct complaint | Review against supplier terms, member feedback, platform rules and evidence of behaviour. |
15. Data protection complaints
Data protection complaints must be handled carefully and routed to the Data Protection Lead. They may include concerns about privacy notices, consent, marketing preferences, cookies, breach handling, data accuracy, deletion, access requests, membership verification, profiling or use of personal information in complaints or moderation decisions.
Log and acknowledge the complaint.
Route promptly to the Data Protection Lead.
Check whether the issue is a complaint, a data rights request, a breach concern, a consent withdrawal or a marketing preference update.
Do not disclose other members’ personal data when responding.
If a personal data breach is suspected, follow the Breach Response Procedure immediately.
Tell the person about their right to complain to the ICO where required or appropriate.
16. Conduct complaints
Conduct complaints may involve behaviour by members, contributors, advertisers, suppliers, moderators or platform representatives. OpenThoughts should respond proportionately while protecting members from harassment, discrimination, intimidation, misuse of direct messaging, spam, excessive sales pressure or bad-faith behaviour.
| Conduct outcome | When it may be used |
|---|---|
| No action | The issue is not supported by evidence or no platform rule has been breached. |
| Informal reminder | Minor issue, misunderstanding or low-level breach. |
| Content correction or removal | Specific post, resource, message or advert breaches rules. |
| Warning | Conduct is inappropriate but may be corrected. |
| Restriction | Posting, messaging, uploading, advertising or group access limited for a period. |
| Suspension | Serious or repeated issue requiring account pause. |
| Removal/termination | Serious breach, repeated misuse, unsafe conduct, bad-faith behaviour or refusal to follow rules. |
| External referral | Where required by law, contract, regulator, platform provider or serious risk assessment. |
17. Unreasonable, repeated or bad-faith complaints
OpenThoughts should remain open to challenge, but it does not need to continue exchanges that become abusive, repetitive, unreasonable or circular. This protects staff, moderators, volunteers and members, and keeps the platform focused on constructive collaboration.
repeating the same issue after a final response without new evidence;
using abusive, threatening, discriminatory or intimidating language;
raising multiple complaints to disrupt moderation or avoid platform rules;
demanding outcomes OpenThoughts cannot provide;
sending excessive messages that prevent proportionate handling;
misusing the complaints route to harass another member, supplier or moderator.
Where this happens, OpenThoughts may limit contact to one channel, issue a final response, pause further responses, restrict account access or take further action under the member terms.
18. Confidentiality and privacy
Complaint and appeal information should be shared only with people who need it to assess, respond, investigate, take action or comply with a legal or contractual duty. OpenThoughts should avoid disclosing unnecessary personal data, private messages, identity information, membership verification information or commercially sensitive supplier details.
Complaint records should be stored securely and access should be limited.
OpenThoughts should not promise complete confidentiality where a fair review requires information to be shared with a relevant person.
People raising complaints should be asked not to include unnecessary third-party personal data.
Data protection complaints and suspected breaches should follow the relevant privacy and breach procedures.
Complaint records should be retained in line with the Records Retention Schedule.
19. Complaints and appeals register
OpenThoughts should keep a simple but robust internal register. This helps demonstrate fairness, spot repeat issues and prevent informal back-and-forth becoming the main decision record.
| Register field | Purpose |
|---|---|
| Reference number | Unique complaint/appeal ID. |
| Date received | Tracks response times. |
| Name/contact | Allows response and audit trail. |
| Category | Membership, moderation, takedown, advertiser, data protection, conduct, accessibility or other. |
| Content/account/resource/advert involved | Identifies the subject of the complaint. |
| Immediate action taken | Temporary removal, account restriction, advertiser pause, escalation or no urgent action. |
| Lead owner | Person responsible for response. |
| Stage 1 outcome | Upheld, partly upheld, not upheld, outside scope, withdrawn or closed. |
| Stage 2 outcome | Final outcome and reason. |
| Actions completed | Corrections, reinstatement, removal, apology, warning, restriction, process change or learning action. |
| Lessons learned | Improvement to wording, terms, upload process, moderation rules, checkboxes or guidance. |
| Closure date | Confirms end of process. |
20. Decision outcomes
| Outcome | Meaning |
|---|---|
| Upheld | OpenThoughts accepts something went wrong and will take corrective action. |
| Partly upheld | Some issues are accepted, but not all requested outcomes will be provided. |
| Not upheld | The decision or action was reasonable based on available evidence and policies. |
| Resolved informally | The issue was corrected quickly without a formal decision. |
| Withdrawn | The person raising the complaint withdraws it. |
| Outside scope | The issue is not covered by this policy. |
| Closed due to conduct | The complaint cannot continue because of abusive, threatening, vexatious or bad-faith behaviour. |
| Closed after final response | OpenThoughts has completed Stage 2 or issued a final decision with no further internal appeal. |
21. Public form wording
Recommended complaint form introduction:
Use this form to raise a platform complaint or appeal about OpenThoughts. This includes membership decisions, moderation decisions, resource takedown disputes, attribution issues, advertiser concerns, data protection concerns or conduct on the platform. Please explain the issue clearly and include links or evidence where relevant. We will review genuine concerns properly. We will not enter into circular arguments about obvious breaches, repeated misuse, abusive behaviour or issues we have already reviewed unless new evidence is provided.
Recommended checkbox wording:
I confirm that the information I have provided is accurate to the best of my knowledge.
I understand OpenThoughts will process this information to review and respond to my complaint or appeal.
I understand that OpenThoughts may restrict or remove content while a complaint, takedown, conduct or moderation issue is being reviewed.
I understand that abusive, threatening, discriminatory or repeated bad-faith contact may lead to the complaint being closed and/or account restrictions being applied.
22. Suggested website page structure
Page title: Complaints and Appeals
Short statement: We will review genuine concerns properly and will not enter circular arguments about obvious breaches.
What you can complain or appeal about
What this process does not cover
How to submit a complaint or appeal
What information to provide
What we may do while reviewing
Response times
Stage 1 review
Stage 2 final review
Data protection complaints
Conduct expectations when using the complaints process
Complaint form link and contact email
23. Governance, review and improvement
The Platform Governance Lead should review complaint trends quarterly during the first year of operation and at least annually after that. The purpose is not simply to count complaints, but to identify where terms, moderation rules, upload guidance, advertiser arrangements, privacy wording, accessibility, membership checks or user journeys need to be improved.
number of complaints by category;
percentage upheld or partly upheld;
common causes of confusion;
repeat conduct or upload issues;
response time performance;
policy or wording changes needed;
training or moderator guidance needed;
risks requiring escalation to the platform owner.
24. Internal responsibility matrix
| Role | Responsibilities |
|---|---|
| Platform Owner | Approves policy, final escalation decisions, serious restrictions and policy changes. |
| Platform Governance Lead | Owns complaints framework, register, quality checks, final reviews and reporting. |
| Membership Lead | Handles membership rejection queries and eligibility appeals. |
| Moderation Lead | Handles moderation appeals, conduct reviews and content restrictions. |
| IP / Content Lead | Handles takedown disputes, attribution corrections and resource licence concerns. |
| Commercial Lead | Handles advertiser and supplier complaints, payment or placement concerns. |
| Data Protection Lead | Handles data protection complaints, privacy concerns and suspected breaches. |
| Accessibility Lead | Handles access barriers and reasonable adjustment concerns. |
| Moderators / Administrators | Record decisions, apply temporary action and provide evidence for review. |
25. Implementation checklist
| Action | Owner | Status |
|---|---|---|
| Create public “Complaints and Appeals” page | Platform Owner | Not started |
| Create complaint/appeal online form | Website Lead | Not started |
| Add complaint category dropdown | Website Lead | Not started |
| Create internal complaints and appeals register | Platform Governance Lead | Not started |
| Link policy to membership terms, community rules, supplier/advertiser terms, privacy notice and takedown policy | Platform Governance Lead | Not started |
| Add moderator guidance for recording decisions | Moderation Lead | Not started |
| Add data protection escalation note | Data Protection Lead | Not started |
| Create standard response templates | Platform Governance Lead | Not started |
| Create quarterly trend review agenda item | Platform Owner | Not started |
| Review policy after first 6 months of platform operation | Platform Owner | Not started |
26. Response templates
26.1 Acknowledgement template
Thank you for contacting OpenThoughts. We have received your platform complaint/appeal and will review it under our Complaints and Appeals Policy. We may contact you if we need further information. Our target is to provide a Stage 1 response within the published timescale for this type of issue.
26.2 Stage 1 decision template
We have reviewed your concern about [brief description]. We considered [evidence/policy/records]. Our decision is [upheld/partly upheld/not upheld/outside scope]. We will take the following action: [actions]. If you believe we have missed relevant evidence or applied the policy incorrectly, you may request a Stage 2 review within 10 working days, explaining the reason for your appeal.
26.3 Final response template
We have completed the Stage 2 review. We considered your appeal points, the Stage 1 decision and the relevant platform policies. Our final decision is [outcome]. This is now the final OpenThoughts platform decision on this matter unless new evidence becomes available or a separate legal, data protection or contractual route applies.
26.4 Closure due to repeated or unreasonable contact
We have reviewed this matter and have already provided our decision. Your latest message does not provide new evidence or a new issue that changes the outcome. We will not continue circular correspondence on this matter. Further messages repeating the same points may not receive a response and may be considered under our conduct rules.
27. Approval statement
This policy should be approved before launch or before the platform allows member uploads, active moderation, supplier advertising or formal membership rejection decisions. It should sit alongside the OpenThoughts Membership Terms, Community Rules, Supplier / Advertiser Terms, Creative Commons Licence Decision, Copyright Attribution and Takedown Requests Policy, Privacy Policy, Records Retention Schedule and Breach Response Procedure.
Policy 14Professional Advice Disclaimer
Professional Advice Disclaimer
Website, community platform, resources, blogs, templates, discussion groups and advertiser content
| Purpose of this document: to provide a full professional advice disclaimer that can be displayed on the OpenThoughts website and used as an internal governance record. It is designed for a UK social housing knowledge-sharing platform, but should be checked by a suitably qualified legal adviser before publication. |
|---|
| Document owner | OpenThoughts |
|---|---|
| Document type | Website disclaimer / professional advice disclaimer |
| Intended publication location | Website footer, Terms area, resource download pages, group/forum sign-up journey and advertiser information page |
| Status | Approved and implemented |
| Version | 1.0 |
| Review frequency | At least annually, and whenever the platform, paid advertising model, resource library, AI tools, moderation process or legal/regulatory position changes |
1. How to use this disclaimer
This disclaimer is written so it can be adapted for OpenThoughts and displayed as a standalone website page. It should also be linked from relevant areas of the website where members, visitors, advertisers, contributors or subscribers may rely on information, templates, events, forum posts, examples, downloads or peer discussions.
Use alongside wider website terms. This disclaimer should sit alongside the Privacy Policy, Cookie Policy, Terms of Use, Community Guidelines, Advertising Terms, Accessibility Statement and any paid membership or subscription terms.
Do not treat it as a substitute for legal advice. The wording is a strong working draft, but should be reviewed against the actual website functionality, risk profile and business model before publication.
Keep it visible. Include a footer link called “Professional Advice Disclaimer” or “Disclaimer”, and repeat short notices on resource pages, blog pages, discussion forums and advertiser pages.
Review it when services change. Update it when OpenThoughts introduces new tools, paid services, webinars, AI-generated summaries, member directories, advice-style content, downloadable templates or sponsored content.
2. Suggested short notice for website footer
| Suggested footer wording: OpenThoughts shares sector learning, peer insight and practical resources for information and discussion only. Content on this website is not professional, legal, financial, regulatory, safeguarding, HR, procurement, technical or housing management advice. Always take appropriate professional advice before acting on information from this site. |
|---|
3. Suggested short notice for resources, templates and downloads
| Suggested resource page wording: This resource is provided as a general prompt or example only. It may not reflect your organisation’s policies, resident profile, legal duties, contractual position, risk appetite or regulatory obligations. Please adapt it carefully and obtain suitable advice before use. |
|---|
4. Full professional advice disclaimer for publication
4.1 About this disclaimer
This Professional Advice Disclaimer explains the limits of information, resources, discussions, examples and other content provided through OpenThoughts. By using the website, joining groups, reading articles, downloading resources, attending events, using templates, interacting with members, viewing advertiser content or contributing to discussions, you acknowledge and accept the limits set out in this disclaimer.
4.2 Information and discussion only
OpenThoughts is designed as a knowledge-sharing, collaboration and discussion platform for people and organisations working in or around social housing, local government, resident engagement, customer influence, community investment, service improvement and related areas. Content made available through OpenThoughts is provided for general information, learning, professional reflection and peer discussion only.
4.3 Not professional advice
Nothing on OpenThoughts should be treated as professional advice. This includes, but is not limited to, legal advice, regulatory advice, financial advice, tax advice, accounting advice, procurement advice, HR advice, employment advice, safeguarding advice, clinical advice, health and safety advice, building safety advice, fire safety advice, technical property advice, planning advice, governance advice, complaints handling advice or specialist housing management advice.
4.4 No professional-client relationship
Use of OpenThoughts does not create a solicitor-client, consultant-client, adviser-client, professional-client, fiduciary or similar relationship between you and OpenThoughts, its owners, contributors, moderators, advertisers, sponsors, partners, members or any person posting content on the platform.
4.5 No substitute for organisation-specific advice
Content on OpenThoughts may not take account of your organisation’s policies, governance structure, resident profile, homes, geography, risk controls, insurance position, contractual duties, statutory duties, funding conditions, regulator expectations, internal delegations, procurement rules, equality duties or local operating arrangements. You must take appropriate professional advice before making decisions or taking action based on information obtained through OpenThoughts.
4.6 Accuracy, completeness and currency
OpenThoughts aims to encourage useful, practical and constructive sharing. However, it does not guarantee that content is accurate, complete, up to date, suitable for your purpose or free from error. Housing law, regulation, funding, policy, practice, sector guidance, technology and professional standards can change. You are responsible for checking whether any information is current and applicable before relying on it.
4.7 User-generated content
OpenThoughts may include posts, comments, discussion threads, uploads, examples, questions, answers, opinions, shared resources and other content created by members or third parties. User-generated content represents the views and experiences of the relevant contributor and does not necessarily represent the views of OpenThoughts. OpenThoughts does not endorse, verify or accept responsibility for user-generated content unless expressly stated in writing.
4.8 Moderation does not equal verification
OpenThoughts may moderate content to support respectful, lawful and constructive use of the platform. Moderation is not a professional review, legal review, technical review or quality assurance process. The presence of content on the platform does not mean it has been approved as accurate, safe, compliant, lawful, fair, current, suitable or best practice.
4.9 Templates, examples and model documents
Any templates, checklists, prompts, policies, letters, forms, toolkits, frameworks, matrices, dashboards, workshop outlines, scripts, model clauses or example documents provided through OpenThoughts are starting points only. They must be reviewed, adapted and approved by competent people within your organisation before use. You should not copy and use any template without considering whether it is suitable for your facts, residents, staff, systems, risks, equality impacts and legal duties.
4.10 Housing, resident engagement and regulatory content
Where OpenThoughts content refers to housing management, resident engagement, tenant satisfaction, complaint handling, building safety, fire safety, damp and mould, repairs, allocations, supported housing, leasehold, shared ownership, homelessness, consumer regulation or related topics, it is intended to support learning and discussion. It should not be treated as a definitive statement of your legal, regulatory or contractual obligations.
4.11 Advertising, sponsorship and promoted content
OpenThoughts may display advertising, sponsorship, promoted content, supplier profiles, product information or partner material. Paid or promoted content does not amount to professional advice or an endorsement that a product, service, supplier, adviser or organisation is suitable for you. You must carry out your own checks, due diligence, procurement assessment, information governance review, contract review, value-for-money assessment and risk assessment before entering into any arrangement.
4.12 External links and third-party websites
OpenThoughts may link to external websites, publications, tools, resources, events or third-party services. These links are provided for convenience and information only. OpenThoughts does not control third-party websites and is not responsible for their content, availability, accuracy, privacy practices, security, accessibility, lawfulness or suitability.
4.13 AI, automation and generated content
Where OpenThoughts uses, hosts or references AI-assisted tools, summaries, prompts, generated content or automated features, the output should be checked carefully by a competent person before use. AI-generated or AI-assisted content may contain inaccuracies, omissions, bias, outdated information or wording that is unsuitable for your circumstances.
4.14 Events, webinars and peer learning sessions
Any events, webinars, workshops, podcasts, training-style sessions or peer learning sessions promoted or hosted through OpenThoughts are for general learning and discussion unless a separate written agreement expressly states otherwise. Questions answered during events are not a substitute for taking professional advice on your own facts.
4.15 Safeguarding, emergencies and urgent risk
OpenThoughts is not an emergency reporting route, safeguarding service, repairs reporting service, landlord service desk, complaints route or professional casework service. If there is an immediate risk to life, safety, health, welfare, property or safeguarding, you should contact the relevant emergency service, landlord, local authority, professional adviser, safeguarding body or responsible organisation directly.
4.16 Decisions remain your responsibility
You are responsible for your own decisions, actions, omissions and use of information obtained through OpenThoughts. You should apply professional judgement, organisational approval processes and appropriate advice before acting. OpenThoughts is not responsible for decisions made by users or organisations who rely on content from the website.
4.17 No warranties
To the fullest extent permitted by law, OpenThoughts provides the website and its content on an “as is” and “as available” basis. OpenThoughts does not give any warranty, representation or guarantee that the website or its content will be uninterrupted, error-free, secure, virus-free, accurate, complete, current, compliant, suitable or available at all times.
4.18 Limitation of liability
Nothing in this disclaimer excludes or limits liability where it would be unlawful to do so. Subject to that, OpenThoughts will not be liable for loss or damage arising from reliance on information, resources, discussions, advertisements, third-party content, external links, templates, downloads, events or user-generated content available through the website.
4.19 Your obligation to verify
Before using or relying on content from OpenThoughts, you should verify the information, consider whether it applies to your circumstances, check relevant law and guidance, obtain appropriate professional advice, follow your organisation’s governance processes and document the basis for any decision made.
4.20 Changes to this disclaimer
OpenThoughts may update this disclaimer from time to time. The latest version should be published on the website and will apply from the date it is posted. Continued use of the website after changes are made indicates acceptance of the updated disclaimer.
5. Recommended “high-risk content” warning panels
Use these shorter warnings at the point where users may be more likely to rely on content without checking it.
| Where to display | Risk being managed | Suggested wording |
|---|---|---|
| Resource downloads | Copy-and-paste use of templates | Please review, adapt and approve this resource before use. It is not advice and may not suit your organisation. |
| Forums and groups | Peer opinion mistaken for expert advice | Group discussions are for peer learning. They are not verified professional advice. |
| Advertiser pages | Supplier promotion mistaken for endorsement | Paid or promoted content is not an OpenThoughts endorsement. Please carry out your own due diligence. |
| Blogs and insight articles | General commentary relied on as current regulation | This article is for information and reflection only. Check current law, regulation and guidance before relying on it. |
| AI/prompt pages | Generated output used without checking | AI-assisted content must be checked by a competent person before use. |
| Events and webinars | General Q&A used as case-specific advice | Event discussions are general learning only and are not a substitute for professional advice on your own circumstances. |
| Safeguarding/risk topics | Urgent cases raised in the wrong channel | OpenThoughts is not an emergency or safeguarding reporting route. Contact the responsible organisation or emergency services where needed. |
6. Internal publication checklist
| Check | Owner | Complete? | Evidence / notes |
|---|---|---|---|
| Disclaimer reviewed against actual website functions and member journey | Site owner / governance lead | ☐ | |
| Legal review completed before publication | Legal adviser | ☐ | |
| Footer link added to every website page | Website admin | ☐ | |
| Short warning added to resource downloads and templates | Content owner | ☐ | |
| Forum/group warning added to community areas | Community manager | ☐ | |
| Advertiser/sponsor wording aligned with advertising terms | Commercial lead | ☐ | |
| AI-related warning added where AI prompts, summaries or generated content are used | Product/content lead | ☐ | |
| Safeguarding and urgent risk wording checked for clarity | Governance lead | ☐ | |
| Version/date/review owner added to website page | Website admin | ☐ | |
| Annual review date diarised | Document owner | ☐ |
7. Suggested page metadata
| SEO title | Professional Advice Disclaimer | OpenThoughts |
|---|---|
| Meta description | Read the OpenThoughts Professional Advice Disclaimer. Our content, resources, discussions, templates and advertiser material are for information and peer learning only, not professional advice. |
| Suggested URL slug | /professional-advice-disclaimer/ |
| Suggested footer label | Professional Advice Disclaimer |
8. Document control
| Version | Date | Author/owner | Change made | Approval/status |
|---|---|---|---|---|
| 1.0 | 04 May 2026 | OpenThoughts | First full draft prepared for review | Draft |
Important note
This policy is published as part of the OpenThoughts governance pack.Thoughts publishes it or relies on it as part of its website terms.
Policy 15Supplier and Advertiser Terms and Agreement
Advertiser Terms and Agreement
Strengthened commercial terms for suppliers, promoters, sponsors and advertisers using the OpenThoughts platform
OpenThoughts
Version 1.0 - Approved and implemented
Important status of this document
This is a practical business template drafted in UK English for OpenThoughts. It is not legal advice. It should be reviewed by a qualified UK solicitor before being issued, relied upon, published, or signed. Bracketed items should be completed or deleted before use.
| Document control | Details |
|---|---|
| Document owner | OpenThoughts / OpenThoughts |
| Version | V1.0 Approved and implemented |
| Effective date | 04 May 2026 |
| Review cycle | At least annually, or sooner following material legal, platform or product changes |
| Applies to | All suppliers, sponsors, promoters, advertisers, featured partners and commercial contributors |
| Related documents | Privacy Policy; Cookie Policy; Data Processing Register; Records Retention Schedule; Professional Advice Disclaimer; Website Terms; Community Rules |
How to use this document
This document is designed to give OpenThoughts stronger control over who may advertise or promote services through the platform, what standards advertisers must meet, how paid listings are managed, and how risks are handled. It can be used as:
website advertiser terms linked from a sales or media pack;
a signed supplier / advertiser agreement;
a schedule attached to an insertion order or booking form;
a due diligence checklist before accepting a promoter;
a risk-control document for sector credibility, member trust and legal compliance.
Recommended implementation: use the main terms as the binding agreement, then attach Schedule 1 as the commercial booking form for each advertiser, sponsor or featured partner. Do not allow advertising to go live until the booking form, declaration and payment terms are agreed.
Plain English summary
OpenThoughts exists to support open-source thinking, shared learning and responsible collaboration across social housing, councils, local authorities and the wider housing arena. Paid promotion must support that philosophy rather than overwhelm it. These terms therefore limit and control advertising so that members can trust the platform.
Advertisers must be relevant to the housing, community, public service, resident engagement or local authority arena.
Advertising is not an endorsement unless OpenThoughts expressly says so in writing.
OpenThoughts can reject, pause, edit, remove or refuse advertising where it creates risk, reputational concern or poor member experience.
Advertisers remain responsible for the truth, lawfulness and evidence behind their claims.
Advertisers must not misuse member data, scrape the platform, spam members, or use OpenThoughts as a lead-generation loophole outside agreed permissions.
Category exclusivity is limited, conditional and not guaranteed unless written into the booking form.
Professional advice, regulated services and technical claims must be appropriately qualified, evidenced and caveated.
Payment, cancellation, performance, reporting and termination rules are set out clearly.
Supplier / Advertiser Terms and Agreement
1. Parties and agreement structure
1.1 These Supplier / Advertiser Terms and Agreement are between OpenThoughts (“OpenThoughts”, “we”, “us”, “our”) and the supplier, sponsor, advertiser, promoter, agency or commercial partner identified in the relevant booking form (“Advertiser”, “you”, “your”).
1.2 These terms apply to all paid or value-exchange advertising, promotion, sponsorship, directory listings, featured content, newsletter placements, resource promotions, event sponsorship, display advertising, partner profiles, marketplace placements, lead-generation activity or other commercial visibility made available through OpenThoughts.
1.3 The agreement is made up of these terms, the booking form or insertion order, any campaign specification, any approved artwork or content brief, and any special terms agreed in writing by OpenThoughts.
1.4 If there is a conflict, the following order applies unless expressly stated otherwise: special written terms signed by OpenThoughts; booking form; campaign specification; these terms; general platform guidance.
2. Definitions
In this agreement:
Advertising Materials means all copy, images, banners, logos, claims, links, landing pages, video, audio, files, documents, case studies, offers, testimonials, calls to action and other content provided or approved by the Advertiser.
Campaign means the advertising or promotional activity described in the booking form.
Category means a defined advertising product or service area, such as repairs technology, resident engagement tools, tenant communication services, consultancy, training or community investment support.
Confidential Information means non-public information relating to OpenThoughts, its members, platform, strategy, pricing, data, suppliers or advertisers.
Member means a registered or approved user of OpenThoughts.
Platform means the OpenThoughts website, member areas, forums, groups, newsletters, resources, directories, events, social channels and any connected digital or offline channel.
Restricted Sector means any sector or product category that OpenThoughts decides is unsuitable for the platform or its members, including the categories listed in clause 10.
3. OpenThoughts advertising philosophy
3.1 OpenThoughts is built around useful collaboration, trusted sector learning and responsible sharing of ideas. Advertising must add value to the member experience and must not dilute the purpose of the platform.
3.2 OpenThoughts may restrict the number of advertisers in each Category to protect quality, relevance and member trust. Any such restriction is a commercial curation decision and does not create permanent exclusivity unless expressly stated in the booking form.
3.3 OpenThoughts may prioritise advertisers whose products, services, ethics, evidence base and tone align with the platform purpose.
4. Eligibility and approval
4.1 All advertisers are subject to approval before any Campaign goes live. OpenThoughts may request evidence of trading status, company registration, insurance, professional qualifications, licences, references, case studies, product information, pricing clarity, complaints history, safeguarding arrangements or data protection compliance.
4.2 OpenThoughts may reject any Advertiser or Campaign at its discretion, including where the proposed promotion may be irrelevant, misleading, low quality, reputationally risky, unsuitable for social housing audiences, inconsistent with community standards, or in conflict with OpenThoughts’ values.
4.3 Approval of one Campaign does not guarantee approval of future Campaigns.
5. Booking, campaign specification and go-live requirements
5.1 A Campaign is not confirmed until OpenThoughts accepts the booking form and any required deposit, prepayment or purchase order arrangement has been agreed.
5.2 Before go-live, the Advertiser must provide:
final approved Advertising Materials in the requested format and dimensions;
destination URLs and landing pages that are live, secure and relevant;
evidence for objective claims, including performance, savings, compliance, customer satisfaction, environmental, AI, safety, legal, financial or regulatory claims;
contact details for an authorised campaign owner;
any required accessibility text, image descriptions and alternative text;
a completed supplier / advertiser declaration where requested.
5.3 OpenThoughts is not responsible for delay caused by late, incomplete, inaccessible, technically unsuitable or non-compliant materials.
6. Advertising standards and claims
6.1 The Advertiser is responsible for ensuring that all Advertising Materials and linked landing pages are legal, decent, honest, truthful, accurate, substantiated, socially responsible and not materially misleading.
6.2 Advertising must comply with all applicable advertising, consumer protection, competition, data protection, intellectual property, equality, accessibility, sector-specific and platform rules.
6.3 The Advertiser must hold evidence for any objective claim before publication. Claims about results, savings, compliance, outcomes, user numbers, satisfaction, carbon impact, artificial intelligence, safety, legal compliance, resident experience, return on investment or regulatory assurance must be capable of substantiation.
6.4 Testimonials, reviews, endorsements and case studies must be genuine, permissioned, current, fairly presented and not misleading. Fake reviews, manipulated reviews or undisclosed incentivised testimonials are prohibited.
6.5 Environmental, sustainability, net zero or social value claims must be specific, proportionate, evidenced and not likely to create a misleading impression about the whole product, service or organisation.
6.6 The Advertiser must not imply that OpenThoughts, its members, housing providers, councils or public bodies endorse the Advertiser unless this has been expressly approved in writing.
7. Professional, regulated and specialist services
7.1 Where the Advertiser promotes legal, financial, insurance, health, safety, fire safety, building safety, technical, procurement, compliance, safeguarding, HR, audit, cyber-security, data protection, consultancy or other specialist services, the Advertiser must ensure that promotional content is appropriately qualified and does not present general marketing material as professional advice.
7.2 The Advertiser must disclose any required authorisations, accreditations, qualifications, memberships, regulatory status, professional indemnity insurance requirements or limitations that are material to the promoted service.
7.3 OpenThoughts may require enhanced disclaimers, evidence, professional credentials or legal sign-off for high-risk products or services.
8. Member trust, tone and behaviour
8.1 The Advertiser must engage with the OpenThoughts community respectfully and constructively. Sales activity must not undermine the collaborative purpose of the platform.
8.2 The Advertiser must not:
pressure, harass, shame, mislead or manipulate members;
use aggressive sales tactics or dark patterns;
post repeated promotional messages in groups or forums unless permitted;
present sales copy as independent sector insight;
create fake accounts, fake engagement or undisclosed paid comments;
target vulnerable individuals or communities in an exploitative way;
misrepresent its connection with OpenThoughts or any housing provider, council, regulator or professional body.
9. Content review, changes and removal
9.1 OpenThoughts may review, request changes to, refuse, pause, hide, downgrade, label, move or remove Advertising Materials at any time where it considers this necessary to protect members, comply with law, maintain quality, manage complaints, avoid reputational harm, prevent confusion, or preserve the purpose of the platform.
9.2 Where practical, OpenThoughts will explain the issue and allow the Advertiser to submit corrected materials. However, OpenThoughts may remove content immediately without notice where urgent action is required.
9.3 OpenThoughts may label content as sponsored, promoted, partner content, advertisement, supplier content or equivalent.
10. Restricted and prohibited advertising
10.1 OpenThoughts may refuse any advertising category it considers unsuitable. The following are prohibited unless OpenThoughts gives express written approval and all legal, safeguarding and reputational risks are resolved:
illegal goods or services;
weapons, ammunition, explosives or harmful products;
adult sexual services or explicit adult content;
gambling, betting or high-risk prize promotions;
tobacco, vaping, cannabis, recreational drugs or unregulated substances;
payday lending, high-cost credit, debt exploitation or misleading financial products;
political campaigning or party-political advertising;
religious proselytising or divisive ideological campaigning;
misleading housing, legal, immigration, benefits, debt or financial advice;
products or services that exploit residents, tenants, leaseholders or vulnerable groups;
content that is discriminatory, hateful, abusive, defamatory, unsafe or likely to cause serious offence;
surveillance, spyware, scraping, unlawful tracking or intrusive monitoring tools;
unsubstantiated health, safety, fire, building, net zero, AI or compliance claims.
10.2 OpenThoughts may also reject products or services that are lawful but inconsistent with the platform’s purpose or likely to damage member trust.
11. Category limits and exclusivity
11.1 OpenThoughts may limit the number of advertisers in each Category to maintain quality and avoid overwhelming members. Category limits are not exclusivity unless the booking form expressly states “exclusive”.
11.2 Where exclusivity is agreed, it will apply only to the precise Category, territory, channel, period and package specified in the booking form.
11.3 Exclusivity does not prevent OpenThoughts from publishing editorial content, member discussions, independent resources, sector news, member recommendations, procurement commentary, competitor mentions, regulatory updates or historical content relating to the Category.
11.4 OpenThoughts may refuse, suspend or end exclusivity if the Advertiser breaches these terms, fails to pay, provides poor-quality content, creates material member complaints, or no longer aligns with OpenThoughts’ quality standards.
12. Advertising placement and performance
12.1 OpenThoughts will use reasonable skill and care to deliver the agreed Campaign placements, but does not guarantee specific sales, enquiries, clicks, impressions, conversions, member engagement, search ranking, procurement outcomes or commercial return unless expressly stated in the booking form.
12.2 Any estimated reach, traffic, engagement, member numbers or audience profile is provided as a good-faith estimate and is not a guarantee.
12.3 OpenThoughts may vary placement, timing, rotation, size, visibility, grouping or format where reasonably necessary for technical, editorial, platform, accessibility, legal or user-experience reasons.
13. Fees, payment and taxes
13.1 Fees are set out in the booking form or rate card. Unless stated otherwise, fees are exclusive of VAT and any applicable taxes.
13.2 Payment terms are payment in advance before go-live unless agreed otherwise in writing. OpenThoughts may require payment in advance for new advertisers, high-risk advertisers, short campaigns, one-off promotions or overdue accounts.
13.3 If payment is overdue, OpenThoughts may pause or remove the Campaign, suspend further services, withdraw Category access or exclusivity, charge interest and recovery costs permitted by law, and refuse future bookings.
13.4 The Advertiser must not set off or withhold payment because of a dispute unless required by law. Any disputed amount must be raised promptly and the undisputed amount must be paid on time.
14. Cancellation, postponement and refunds
14.1 Cancellation rights, notice periods and refund rules should be stated in the booking form. Unless the booking form says otherwise, the default position is:
cancellation more than 30 days before go-live: 75% refund or credit, less committed costs;
cancellation 15-30 days before go-live: 50% refund or credit, less committed costs;
cancellation 14 days or less before go-live: no refund;
campaigns already live: no refund for delivered or reserved inventory;
OpenThoughts may offer a credit at its discretion where cancellation is due to reasonable operational circumstances.
14.2 No refund is due where a Campaign is paused or removed because of Advertiser breach, non-payment, misleading claims, unlawful content, reputational risk, data misuse or failure to provide required evidence.
15. Advertiser warranties
The Advertiser warrants that:
it has full power and authority to enter into this agreement;
its Advertising Materials and linked pages comply with applicable law and regulation;
it owns or has permission to use all intellectual property in the Advertising Materials;
all claims are accurate, current, fair and substantiated;
all testimonials, case studies and logos have been permissioned;
it will not introduce malware, malicious code, tracking pixels or cookies without written approval;
it will comply with data protection, direct marketing and privacy law;
it will maintain adequate insurance for its activities;
it will not do anything likely to bring OpenThoughts into disrepute.
16. Intellectual property and licence to publish
16.1 The Advertiser retains ownership of its Advertising Materials, subject to the licence granted below.
16.2 The Advertiser grants OpenThoughts a non-exclusive, royalty-free, worldwide licence to host, copy, display, publish, resize, format, adapt for accessibility, promote, report on and archive the Advertising Materials for the purpose of delivering and evidencing the Campaign.
16.3 OpenThoughts retains all rights in its platform, brand, editorial materials, design, community structure, member insights, reports, analytics, templates, resources and underlying know-how.
16.4 The Advertiser must not use the OpenThoughts name, logo, screenshots, member comments, platform data, community content or endorsement language without prior written permission.
17. Data protection, privacy and direct marketing
17.1 Each party must comply with UK data protection and privacy law in relation to any personal data it processes under or in connection with this agreement.
17.2 Unless a separate data processing agreement states otherwise, each party is an independent controller for the personal data it collects and uses for its own business purposes.
17.3 The Advertiser must not scrape, harvest, copy, export, enrich, profile, sell, rent, infer, track or reuse member data obtained from the Platform unless expressly permitted by OpenThoughts and lawful under applicable privacy law.
17.4 The Advertiser must not send unsolicited marketing to OpenThoughts members unless it has a lawful basis and any required consent or soft opt-in requirements are satisfied.
17.5 Any tracking links, cookies, pixels, remarketing tags, analytics tools or lead forms must be disclosed to OpenThoughts in advance and must not be used without approval.
17.6 Where the Campaign involves lead capture, webinar registration, downloadable resources, sponsored forms or member sign-ups, the booking form must specify who is controller, what privacy notice applies, what data will be collected, how consent or lawful basis is managed, and what data will be shared.
18. Confidentiality
18.1 Each party must keep the other party’s Confidential Information confidential and must not use it except for the purpose of performing this agreement.
18.2 Confidential Information may be shared with employees, contractors, advisers and professional representatives who need to know it and who are bound by confidentiality obligations.
18.3 Confidentiality does not apply to information that is public through no breach, already lawfully known, independently developed, lawfully received from a third party, or required to be disclosed by law or regulator.
19. Compliance with platform rules and community standards
19.1 The Advertiser must comply with OpenThoughts’ community rules, moderation standards, website terms, accessibility standards, image specifications, editorial rules and any reasonable instructions issued by OpenThoughts.
19.2 If employees, agents or representatives of the Advertiser participate in the Platform, they must identify any commercial interest where relevant and must not disguise promotional activity as independent member discussion.
20. Complaints, corrections and takedown process
20.1 The Advertiser must promptly assist OpenThoughts with any complaint, concern, regulatory enquiry, member challenge, intellectual property claim, data protection concern or factual correction relating to the Campaign.
20.2 Where a complaint appears credible, OpenThoughts may pause or remove the Advertising Materials while the issue is reviewed.
20.3 The Advertiser must provide supporting evidence, corrected copy or written explanation within the timescale requested by OpenThoughts. Failure to respond may result in removal and termination without refund.
21. Indemnity
21.1 The Advertiser will indemnify OpenThoughts against losses, claims, damages, liabilities, costs and expenses arising from or connected with:
Advertising Materials or linked landing pages;
misleading, inaccurate or unlawful claims;
breach of advertising, consumer, data protection, privacy, intellectual property, equality or sector-specific law;
unauthorised use of logos, testimonials, case studies, images, music, video or third-party content;
data misuse, scraping, spam, unlawful tracking or direct marketing;
products or services supplied by the Advertiser to members or third parties;
breach of this agreement by the Advertiser or its representatives.
22. Liability
22.1 Nothing in this agreement limits or excludes liability that cannot legally be limited or excluded, including liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation.
22.2 Subject to the above, OpenThoughts is not liable for indirect, consequential or special loss; loss of profit; loss of revenue; loss of contracts; loss of goodwill; loss of anticipated savings; or loss arising from procurement decisions, member decisions or third-party conduct.
22.3 Subject to the above, OpenThoughts’ total aggregate liability under or in connection with a Campaign is limited to the fees paid by the Advertiser for that Campaign in the three months preceding the event giving rise to the claim.
22.4 OpenThoughts is not responsible for platform downtime, technical interruption, search engine changes, social media changes, third-party hosting issues, email deliverability issues, member decisions, or events outside its reasonable control, except where caused by OpenThoughts’ failure to use reasonable skill and care.
23. Suspension and termination
23.1 OpenThoughts may suspend or terminate a Campaign immediately by notice where the Advertiser breaches this agreement, fails to pay, provides misleading information, misuses data, creates reputational risk, breaches community rules, becomes insolvent, or engages in conduct inconsistent with the platform purpose.
23.2 Either party may terminate the agreement if the other commits a material breach and fails to remedy it within 14 days of written notice, where the breach can be remedied.
23.3 Termination does not affect accrued rights, payment obligations, confidentiality, intellectual property rights, data protection obligations, indemnities, limitations of liability or any clause intended to survive termination.
24. Non-circumvention and member contact
24.1 The Advertiser must not use OpenThoughts access to bypass platform rules, scrape member data, mass-contact members, harvest leads, or build unauthorised marketing lists.
24.2 Where OpenThoughts introduces a member, housing provider, council, local authority, partner or supplier opportunity to the Advertiser as part of a paid package, the Advertiser must act transparently and must not misrepresent the source or nature of the introduction.
24.3 Any direct commercial relationship between the Advertiser and a member is solely between those parties. OpenThoughts is not responsible for the Advertiser’s products, services, pricing, advice, delivery or performance.
25. Anti-bribery, conflicts and fair dealing
25.1 The Advertiser must comply with anti-bribery, anti-corruption, modern slavery, tax, competition and procurement laws applicable to its activities.
25.2 The Advertiser must disclose any conflict of interest that may affect the Campaign, including connections with OpenThoughts personnel, public sector procurement processes, member organisations, reviewers, case study subjects or sponsored content contributors.
25.3 The Advertiser must not offer inappropriate inducements, personal benefits or hidden commissions to OpenThoughts, members, public bodies or decision-makers.
26. Accessibility and inclusion
26.1 OpenThoughts may require Advertising Materials to meet reasonable accessibility standards, including readable contrast, plain English where appropriate, alternative text for images, accessible PDFs, captioned video, and avoidance of inaccessible design elements.
26.2 Advertising must not unlawfully discriminate or exclude protected groups. The Advertiser should consider the diverse needs of housing professionals, residents, community groups and digitally excluded audiences.
27. Force majeure
27.1 Neither party is liable for delay or failure caused by events outside its reasonable control, including major platform failure, cyber incident, fire, flood, pandemic, government action, serious supplier outage, strike, civil disruption or widespread network failure.
27.2 The affected party must notify the other as soon as reasonably practical and take reasonable steps to reduce the effect of the event.
28. Assignment and subcontracting
28.1 The Advertiser must not assign, transfer or subcontract its rights or obligations under this agreement without OpenThoughts’ prior written approval.
28.2 OpenThoughts may use contractors, hosting providers, designers, editors, payment providers, analytics tools and other suppliers to operate the Platform and deliver Campaigns.
29. Notices
29.1 Formal notices must be sent to the addresses or email contacts stated in the booking form. Email notices are deemed received on the next working day after sending unless a delivery failure notice is received.
29.2 Operational campaign communications may be managed by email or through agreed project management channels.
30. Governing law and jurisdiction
30.1 This agreement is governed by the law of England and Wales unless the booking form states otherwise.
30.2 The courts of England and Wales have exclusive jurisdiction unless the parties agree otherwise in writing.
Schedule 1 - Supplier / Advertiser booking form
Complete this schedule for every paid advertiser, sponsor, supplier profile, category partner or featured promoter.
| Field | Details |
|---|---|
| Advertiser legal name | |
| Trading name | |
| Company number / charity number | |
| Registered address | |
| Main contact name and role | |
| Email and telephone | |
| Website URL | |
| Campaign title | |
| Campaign category | |
| Campaign package | |
| Channel(s) | Website / group / forum / newsletter / directory / resource hub / event / social / other |
| Campaign start date | |
| Campaign end date | |
| Go-live deadline | |
| Creative dimensions and file types | |
| Destination URL(s) | |
| Fee | |
| VAT position | |
| Payment terms | |
| Category exclusivity agreed? | No / Yes - describe precisely |
| Evidence required for claims | |
| Special restrictions or approvals | |
| Reporting included | |
| Cancellation terms | |
| Authorised signatory for Advertiser | |
| Authorised signatory for OpenThoughts |
Schedule 2 - Advertising material approval checklist
| Check | Question | Pass / fail | Notes / action |
|---|---|---|---|
| Relevance | Does the product or service clearly support housing, local government, resident engagement, public service, community value or sector learning? | ||
| Claim evidence | Have all objective claims been evidenced before publication? | ||
| Misleading risk | Could the average reader misunderstand price, results, availability, savings, compliance or endorsement? | ||
| Professional advice | Does the advert need a disclaimer because it relates to legal, financial, technical, safety, HR, procurement or compliance matters? | ||
| Testimonials | Are reviews, case studies and logos genuine, permissioned and current? | ||
| Environmental claims | Are green, carbon, net zero or sustainability claims specific and substantiated? | ||
| Data protection | Does the campaign collect, track or share personal data? Has this been mapped and approved? | ||
| Accessibility | Does the creative have readable text, alternative text and accessible linked content? | ||
| Sponsored labelling | Is the content clearly labelled as promoted, sponsored or advertiser content? | ||
| Restricted sectors | Does the advertiser fall into any prohibited or restricted category? | ||
| Conflict of interest | Could the campaign create a procurement, endorsement, governance or reputational issue? | ||
| Landing page | Is the landing page secure, live, relevant and consistent with the advert? | ||
| Member experience | Does the promotion add value without overwhelming the platform? |
Schedule 3 - Supplier / advertiser declaration
The Advertiser confirms that:
all information supplied to OpenThoughts is accurate and not misleading;
the Advertiser has authority to promote the relevant products and services;
all advertising claims are accurate, current, fair and substantiated;
the Advertiser has permission to use all logos, images, testimonials and case studies supplied;
the Advertiser will not misuse OpenThoughts member data or send unlawful marketing;
the Advertiser will comply with applicable advertising, data protection, privacy, consumer, intellectual property and sector-specific rules;
the Advertiser accepts that OpenThoughts may reject, pause, remove or require changes to advertising where necessary;
the Advertiser understands that advertising on OpenThoughts does not create endorsement unless expressly agreed in writing.
| Signature field | Details |
|---|---|
| Signed for Advertiser | |
| Name | |
| Role | |
| Date | |
| Signature |
Schedule 4 - Data protection and lead capture schedule
Use this schedule where a Campaign collects or shares personal data, such as sponsored downloads, lead forms, event registration, webinar sign-ups or enquiry forms.
| Field | Details |
|---|---|
| Campaign data activity | |
| Data collected | Name / role / organisation / email / telephone / interests / other |
| Who collects the data? | OpenThoughts / Advertiser / joint / third party |
| Controller position | Independent controllers / joint controllers / processor arrangement - describe |
| Privacy notice used | |
| Lawful basis | |
| Consent wording if used | |
| Direct marketing permission | |
| Data shared with Advertiser | |
| Retention period | |
| Security controls | |
| International transfers | |
| Data subject rights process | |
| Tracking pixels / cookies | No / Yes - describe |
| DPIA or risk assessment needed? | No / Yes - describe |
Schedule 5 - Model advertiser-facing wording for the website
The following wording can be adapted for an advertiser page, media pack or checkout page.
Supplier and advertiser standards OpenThoughts welcomes relevant suppliers, sponsors and advertisers who can add value to the social housing, local authority and community sectors. We carefully limit and review paid promotion so that members are not overwhelmed by adverts and can trust the platform. Paid promotion does not mean automatic endorsement. All advertisers must meet our relevance, evidence, data protection, accessibility and community standards before advertising goes live.
Schedule 6 - Internal risk rating for advertisers
| Risk rating | Indicators | Required action |
|---|---|---|
| Low | Established supplier with relevant sector offer, clear evidence, no direct member data capture, standard display advert only. | Standard approval and annual review. |
| Medium | New supplier, consultancy, sponsored content, claims requiring evidence, lead capture, or sensitive operational service area. | Enhanced evidence check, privacy review and director approval. |
| High | Legal, financial, safety, compliance, fire, building safety, AI, safeguarding, debt, vulnerable resident, procurement or significant public claims. | Legal review, enhanced due diligence, written sign-off and stronger disclaimers before go-live. |
| Reject / pause | Misleading claims, poor evidence, prohibited sector, aggressive sales, data misuse, reputational concern or breach of community purpose. | Do not publish or remove immediately. Record reason and notify advertiser if appropriate. |
Reference points used when preparing this template
This template was prepared with reference to the following publicly available UK sources. OpenThoughts should check these again before publication because regulatory guidance and fee levels can change:
Information Commissioner’s Office guidance on controllers and processors under UK GDPR.
Information Commissioner’s Office data sharing code and Article 28 processor contract requirements.
Information Commissioner’s Office guidance on the data protection fee.
Advertising Standards Authority and CAP Code guidance on misleading advertising, substantiation and fake reviews.
UK company and business name trading disclosure requirements.
Final legal review checklist
Insert the correct OpenThoughts legal entity name, company number, trading address and VAT status.
Confirm whether OpenThoughts will contract with advertisers as a company, sole trader, partnership or other legal structure.
Review the limitation of liability cap and indemnity with a solicitor.
Confirm cancellation, refund and payment terms match the commercial model.
Confirm data protection arrangements for sponsored downloads, lead forms, events and tracking.
Agree which categories will be restricted, capped or exclusive.
Ensure the wording aligns with the website terms, privacy policy, cookie policy and professional advice disclaimer.
Create a short advertiser declaration form to collect before go-live.
Keep a record of claim evidence, approvals and takedown decisions.
Transparency note: OpenThoughts keeps this governance pack visible so members, contributors, suppliers and advertisers understand the rules before they join, share, upload, report, advertise or rely on content. These policies should be reviewed at least annually, or sooner if the platform, law, supplier model, member features or risk profile changes.


