# Abuse & Child Safety

**Last updated:** September 8, 2025

**If anyone is in immediate danger, contact your local emergency services first.**\
\
VDO.Ninja is a peer-to-peer tool with minimal central control. We do **not** proactively monitor or record calls, and we do **not** run 24/7 moderation.

***

### How to report

Email: **<steve@seguin.email>**

We review reports about **child safety**, **harassment**, **hate**, **spam**, **fraud/phishing**, **malware**, **doxxing**, and other **Terms of Service** violations.

Please include:

* **Room link/name** (and any join tokens, stream IDs, hashes, or passwords)
* **Timestamps** (with time zone)
* **Screen names** of participants involved
* The **type of issue** (e.g., child safety, harassment, spam) and a **plain, non-graphic description** of what you personally observed
* If you reported to a national hotline (e.g., **Cybertip.ca**, **NCMEC**), the **hotline report number**

**Do not send illegal media** (e.g., CSAM). Submit such evidence to your national hotline and share the **report number** with us instead.

***

### Important limitations (set expectations)

* **No 24/7 response:** We handle reports **best-effort** and may not see your email before a live stream ends.
* **No proactive monitoring:** We **do not** watch or scan sessions.
* **No uninvited access:** We **do not** join private/passworded rooms unless the **room host explicitly invites us** or we are **legally required** to do so.
* **P2P reality:** We **cannot** forcibly end calls already in progress, remove content from participant devices, or reliably identify people (no global accounts).
* **Not an emergency service:** For urgent risk, contact local authorities and/or a national hotline.

***

### What we can do (best-effort, within P2P limits)

* **Record the report** and keep minimal incident metadata (e.g., hashed room token, timestamps, IPs involved) **when legally required and able.**
* **Coordinate with hotlines/LEA**: file or supplement a hotline report when appropriate and cooperate with lawful requests.
* **Restrict at the edge (when feasible):** disable a **specific link** we control, or block/rate-limit **IP(s)/ASN(s)** via our providers (e.g., Cloudflare).
* **Display a neutral safety notice** on reported links **when technically available**. (This is not guaranteed and may not appear for short-lived rooms.)

***

### When we disable (“hard-block”) a link

Because live/P2P rooms are short-lived and easily replaced, hard-blocking is **rare** and used only when we have **credible confirmation** of serious harm or a legal requirement. Examples include:

* A **national hotline report number** (Cybertip.ca/NCMEC) that **matches** the link/timeframe;
* A **law-enforcement/court order**;
* **Multiple independent** detailed reports (from distinct networks/regions) indicating **child exploitation**, **credible threats**, **malware**, or doxxing dumps;
* Direct verification **with host consent** or in a **public broadcast** the host asked us to check.

If the room is already over or rotating links is trivial, a late hard-block may have little value; a neutral notice (when available) or no action may be more appropriate.

***

### What we won’t do

* Publicly label a room “abusive/illegal” based only on a single unverified report.
* Request or accept illegal media from you.
* Join private/passworded rooms without **host consent** or legal compulsion.

***

### Hosts: reduce risk (no central tooling required)

* Treat **room links/tokens** like passwords; share only with trusted participants.
* Rotate links/tokens for recurring shows; set **passwords** and change them after incidents.
* If you want us to help **verify a report**, please email from the **host’s email address**:

  > “I am the host of **\[room link]** and consent to VDO.Ninja safety staff joining to verify a report.”\
  > \&#xNAN;*(If the room is passworded, include the password and a short time window you’re comfortable with.)*

***

### Child safety (CSAM/grooming)

* For suspected child exploitation, **report to your national hotline** and share the **report number** with us. We may file our own report and **preserve relevant logs** as required by law.
* We may restrict or disable a link **without verification** when evidence includes a hotline number, a legal order, or strong corroboration.
* Any user-facing page remains **neutral** (e.g., “Access disabled due to a safety/legal issue.”).

***

### Privacy & preservation

* We keep **minimal operational data** and only as long as needed.
* For safety/legal matters, we may **preserve incident-related logs** for the legally required period.
* **Cloudflare** maintains its **own** request logs (IP, full URL including query parameters, user-agent, country, etc.) under its policies. See our [Privacy Policy](/help/privacy-and-security-details/vdo.ninja-privacy-policy.md).

***

**Contact:** **<steve@seguin.email>**\
\
(Send plain descriptions only—**no illegal media**. For child-safety evidence, report to your national hotline and include the **report number** when you email us.)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vdo.ninja/help/privacy-and-security-details/abuse-and-child-safety.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
