orgo community
Platform Resources Pricing Platform Documentation About us Blog Pricing
Membership
Membership Management Fees, renewals and records, automated
Contacts CRM Every contact and member in one database
Multi-Chapter National, regional and local chapters in one account
Community
Events Ticketing, QR check-in and attendance
Discussions & Groups Forums and groups that keep members active
Newsletter Segmented emails with open analytics
Fundraising Donation campaigns and recurring giving
Courses & Badges Training, certification and badges for members
Governance
e-Voting Anonymous, verifiable elections and decisions
eDocuments & eSignatures Send, e-sign and archive documents
Files Drive Secure shared storage for your documents
Project Management Member support tickets and team tasks
Privacy & Security GDPR compliance, EU hosting, access control
Operations
Analytics Reports and dashboards for board decisions
Branding & Customization Your logo, domain, languages and fields
Integrations Stripe, SSO, HubSpot, n8n and more
Ask Orgo AI Plain-language answers from your data
MCP Server Connect AI assistants to your data
Documentation
API Reference
Changelog
Sign in
Get a demo
Sign in Get a demo

Child Safety Standards

Standards against child sexual abuse and exploitation (CSAE)
S.C. ORGO INFORMATICS SRL
Last Updated: August 1, 2026

Orgo has no tolerance for child sexual abuse material or for any conduct that sexualizes, exploits or endangers a child. This page states what is prohibited on the platform, how to report it, what we do when a report reaches us, and who is responsible for what.

It is written to be accurate rather than reassuring. Where a control belongs to the organization running its Orgo space rather than to us, we say so, because a standard that misplaces responsibility protects nobody.


1. Scope, and who is responsible for what

Orgo is a white-label membership platform. Associations, federations, scouting and youth movements, schools, parties and NGOs each run a closed space for their own members. Orgo is not a public social network: access to a space runs through membership granted by that organization, and its administrators are named individuals appointed and accountable to it.

That structure decides the split:

The organization Orgo
Sets the rules for its space and moderates the content in it Sets the platform-wide floor these standards describe
Vets, trains and supervises its administrators Provides the access controls, roles and audit logging they use
Holds the safeguarding duty toward its own members Acts on reports, and on anything we otherwise become aware of
Reports safeguarding concerns to the competent authorities Reports to law enforcement where the law requires us to

The organization's obligations are contractual, not aspirational: background checks and safeguarding training for administrators with access to children's data are required by Organization Terms of Service §5.5.11.3 and DPA Annex 5 §7. Failure to meet them is grounds for immediate suspension or termination under Annex 5 §15.1.


2. What is prohibited

The following are prohibited on Orgo without exception, for every user and every organization, and no organization's own rules can permit them.

Child sexual abuse material (CSAM). Any visual depiction of sexually explicit conduct involving a minor, including photographs, video, drawings, animation and computer- or AI-generated imagery; text that depicts or describes the sexual abuse of a child; links or references directing others to such material anywhere; and any content or tooling that facilitates its creation, distribution or access.

Child sexual exploitation and abuse (CSAE). Grooming or any attempt to establish contact with a child for sexual purposes; sextortion; the solicitation, arrangement or advertising of sexual contact with a child; child trafficking or commercial sexual exploitation; the sexualization of a minor in any context, including captions, comments and profile content; and the sharing of a minor's contact or location data for these purposes.

These prohibitions restate, in one place, what User Terms of Service §3.2.6 already forbids. They apply to every part of the platform — profiles, discussions, direct messages, files, events, courses and uploads.


3. How to report

Anyone can report. No Orgo account is needed, and no special tool is required.

Report to the organization. If you are a member, the administrators of your organization hold the moderation tools for the content in their space and can act fastest. This is the right first step for most concerns.

Report to Orgo — abuse@orgo.space. Use this for CSAM, CSAE, or any other illegal content. This is the notice-and-action channel required by Article 16 of Regulation (EU) 2022/2065 (the Digital Services Act). Tell us, as precisely as you can, what the content is and where it is — a URL, or a description of where it appears. You do not have to give your name or email address when your notice concerns child sexual abuse material.

A child is at immediate risk — security@orgo.space, subject line URGENT — Child Safety Concern. This reaches the company's administrator directly; there is no ticket queue in between.

A child is in danger right now — call the police. Dial 112 anywhere in the EU, or your local emergency number. Contact the authorities first and us second; we are not an emergency service.

Reports of child sexual abuse take priority over every other notice we receive.


4. What we do when a report reaches us

  1. Assess immediately, ahead of all other notices.
  2. Preserve the evidence before anything is deleted, so that it remains available to law enforcement.
  3. Remove the content and suspend the account responsible, together with any other account we can attribute to the same person.
  4. Inform law enforcement promptly where we become aware of information giving rise to a suspicion that an offence involving a threat to the life or safety of a person has been, is being or is likely to be committed — the obligation in Article 18 of the Digital Services Act.
  5. Notify the organization whose space is affected. It is the controller of the data concerned and carries its own safeguarding and mandatory-reporting duties.
  6. Tell the reporter what we decided, and tell the member whose content was removed why it was removed — except where doing either would prejudice an investigation or endanger a child.

We cooperate with lawful requests from law enforcement and from the competent authorities, and we retain records of the action taken.


5. What we do not do, stated plainly

Orgo does not proactively scan or monitor member content, and no automated system on our platform detects CSAM. We say this rather than implying a capability we do not run. There is no general monitoring obligation on a hosting service under Article 8 of the Digital Services Act, and User Terms of Service §4.4.3 states the same position contractually.

What detection rests on instead is structural: spaces are membership-gated rather than open to the internet, administrators are named and vetted by the organization that appointed them, every action against member data is recorded in an application audit trail, and the reporting channels above are open to anyone.

If we introduce content-scanning capability, this page will say so on the day it goes live and not before.


6. Children's data

The protection of children's personal data — parental consent, age thresholds, data minimization, parental rights, retention and deletion — is a separate subject and lives in one place: DPA Annex 5 — Children's Data Processing. The digital age of consent varies between 13 and 16 across EU member states, and the applicable threshold is determined per jurisdiction.

Children's personal data is never used to train, fine-tune or improve any AI model, ours or a third party's. That prohibition is absolute and cannot be varied by customer instruction or consent — Annex 5 §11.5.


7. Orgo personnel

Orgo staff do not moderate or browse the content inside customer spaces. Access to production systems is limited to named individual accounts, requires multi-factor authentication without exception, follows least privilege, is reviewed on a documented quarterly cycle, and is recorded in AWS CloudTrail with log file validation. Everyone with access is under a written confidentiality obligation, and the contract prohibits processing outside the customer's documented instructions. Full detail: Annex 2 — Security Measures and Trust & Security.


8. Legal framework

  • Regulation (EU) 2022/2065 (Digital Services Act) — Article 16 notice and action, Article 18 notification of suspected criminal offences, Article 8 (no general monitoring obligation)
  • Directive 2011/93/EU on combating the sexual abuse and sexual exploitation of children and child pornography
  • Romanian Criminal Code — including Art. 374 (child pornography) and Art. 222 (solicitation of a minor for sexual purposes)
  • Romanian Law 272/2004 on the protection and promotion of the rights of the child
  • GDPR Article 8 and Romanian Law 190/2018, as implemented in Annex 5
  • COPPA (15 U.S.C. §§ 6501–6506), where a customer organization is subject to US jurisdiction

Orgo is established in Romania and has no US establishment, so the mandatory NCMEC reporting duty under 18 U.S.C. § 2258A does not apply to us. We nonetheless use the CyberTipline where a report concerns a child located in the United States.


9. Reporting to authorities and support lines

Emergency, child in immediate danger 112 (EU) or your local emergency number
National CSAM hotlines inhope.org — the INHOPE network operates a reporting hotline in most countries
United States NCMEC CyberTipline — report.cybertip.org
Child helpline (EU) 116 111
Missing child hotline (EU) 116 000
Romania — data protection authority ANSPDCP — dataprotection.ro

10. Point of contact and review

Orgo's designated point of contact for child safety and CSAE matters is reachable at security@orgo.space. Notices about illegal content go to abuse@orgo.space; questions about children's personal data go to privacy@orgo.space.

These standards are reviewed at least annually, and whenever the law or the product changes materially.


11. Status of this document

These standards state Orgo's position and the measures we apply. They supplement, and do not vary, the Organization Terms of Service, the User Terms of Service, the DPA and its annexes; where this page and a contractual document differ, the contractual document governs. Nothing here limits any obligation imposed on Orgo by law.


Company: S.C. ORGO INFORMATICS SRL · J29/2796/2019 · CIF RO41650396 Str. Gheorghe Grigore Cantacuzino nr. 14, etaj parter, ap. 1, Ploiești, județul Prahova, Romania

Last Updated: August 6, 2026 · Version 1.0

Table of Contents

    orgo community
    • Platform
    • Features
    • Branded App
    • Trust & Security
    • iOS app↗
    • Android app↗
    • Company
    • About us
    • Contact
    • Get a demo
    • Resources
    • Documentation↗
    • Changelog↗
    • API reference↗
    • Blog
    • Alternatives
    • Comparisons
    • Delete your account
    • Sitemap
    • Use Cases
    • NGOs
    • Scouts
    • Associations
    • Federations
    • Political Parties
    • Fundraising Campaign
    🇬🇧 English
    🇩🇪 Deutsch 🇫🇷 Français 🇮🇹 Italiano 🇪🇸 Español 🇵🇱 Polski 🇷🇴 Română 🇨🇿 Čeština 🇸🇰 Slovenčina
    © 2026 Orgo Informatics.
    Terms User Terms Privacy Cookies DPA Subprocessors AI Addendum

    Before you go — got 2 minutes?

    No newsletters. No 10 follow-up calls. We just want to see if Orgo is the right fit for you. A 20-min demo, calendar open right now.

    Please complete this required field.

    Please complete this required field.

    Please enter a valid email address.

    Please complete this required field.

    By submitting, I acknowledge I have read and understand Orgo's Privacy Notice.

    Dear ,

    Your meeting is booked! We look forward to learning about your organization and showing you how Orgo can help.