Child Safety & CSAM Policy

Version: 1.0 (pending final legal review before public launch)
Effective Date: 2026-07-22
Last Updated: 2026-07-22
Operator: Vallabh Sakhare, trading as ScatterBrain (“we”, “us”)
Child-safety / CSAE reports: support@pipchat.in (also via in-app Report)

This is Dinner Date’s published Child Safety Standards policy addressing child sexual abuse and exploitation (CSAE) and child sexual abuse material (CSAM), provided to satisfy platform requirements (including the Google Play Child Safety Standards / CSAE policy for social and dating apps) and applicable law. It forms part of the Dinner Date legal framework alongside the Terms of Service, Community Guidelines, Content Moderation Policy, and Reporting & Enforcement Policy. This document should receive independent legal review before public launch, and the reporting-authority and designated-contact details must be finalised.

1. Zero tolerance

Dinner Date is an adults-only (18+) platform. We have zero tolerance for child sexual abuse and exploitation. The following are strictly prohibited and will result in immediate removal, a permanent ban, preservation of evidence, and reporting to the relevant authorities:

child sexual abuse material (CSAM) — any image, video, or depiction of a minor in a sexual context,

real, drawn, or AI/computer-generated;

sexualisation of minors in text, imagery, or conversation;
grooming, enticement, or solicitation of a minor for sexual purposes;
attempting to arrange a meeting with a minor for sexual purposes;
trafficking of minors, or facilitating any of the above;
any use of minors in profile photos, or use of the platform by anyone under 18.

2. Age assurance and eligibility

Dinner Date is restricted to users 18 years or older. Date of birth is collected at sign-up and age is enforced server-side; accounts that do not meet the minimum age are blocked or removed. We may take additional steps to detect and remove underage accounts and accounts that misrepresent age. Details are in the Age & Eligibility Policy.

If you believe a minor is using Dinner Date, or that an account belongs to someone under 18, report it immediately via in-app Report or support@pipchat.in.

3. How we prevent and detect CSAE

Adults-only design and age gate at registration (see §2).
Reporting tools on profiles, messages, and dates, with evidence upload, so users can flag child-

safety concerns; child-safety reports are treated as the highest priority.

Human review of reported content and accounts, with the ability to remove content, suspend, and ban.
Prohibition of child sexualisation in all content, enforced under the Community Guidelines and

Content Moderation Policy.

Preservation of evidence relating to suspected CSAE for the purpose of reporting to and cooperating

with authorities.

Implementation note (internal, remove before publication):
Built and live in the codebase: every upload path (profile photos, report evidence, receipts) is routed through a scanning seam before anything reaches storage; a positive verdict quarantines the bytes outside every public namespace, opens a CsamIncident with a 90-day preservation window, suspends the account and revokes its sessions, and returns a non-revealing error to the uploader. Preservation is enforced against both the data-retention sweep and account deletion, and there is a token-guarded operator queue for recording a filing with an authority. Covered by npm run verify:safety.
Still required before public launch: the actual detection corpus. MEDIA_SCAN_PROVIDER defaults to none, in which case uploads are accepted and recorded with an unscanned verdict — no detection occurs. Known-CSAM hash lists (NCMEC/IWF/PhotoDNA/Thorn Safer) are released only to vetted entities under contract, so a vendor must be engaged and configured; and the operator must register with the relevant reporting body (e.g. NCMEC as an ESP) before a CyberTipline report can actually be filed. Also still to finalise: the named reporting authority and the designated child-safety contact below. Do not represent detection capabilities as live until a provider is configured in production.

4. Reporting and escalation

Anyone can report suspected CSAE:

In-app: use Report on the profile, message, or date, and attach evidence where possible.
Email: support@pipchat.in with the subject “CHILD SAFETY”.

On a credible child-safety report we will, consistent with Applicable Law: remove the content and account, preserve the content and associated account data as evidence, and report to the competent authorities. In India this includes obligations under the Protection of Children from Sexual Offences (POCSO) Act, 2012 and the Information Technology Act and rules; internationally we will report to the appropriate body (for example, a NCMEC CyberTipline report where applicable). We cooperate with lawful requests from law enforcement as described in the Law Enforcement Request Policy.

5. Consequences

Any account involved in CSAE is permanently banned with no appeal, and the operator will not knowingly allow that person to return. We will provide relevant information to authorities as required or permitted by law, even where a user has requested account deletion — deletion does not erase evidence needed for a child-safety investigation.

6. If you are a victim, or in danger now

If a child is in immediate danger, contact your local emergency services first. In India you can also contact Childline 1098. You can report abuse material and exploitation to the police and to child- protection authorities. Dinner Date will support lawful investigations, but we are not an emergency service or a substitute for law enforcement.

7. Designated contact and standards commitment

Dinner Date commits to maintaining these child-safety standards, to reviewing them regularly, and to publishing a designated point of contact for child-safety matters and for platform/regulatory reporting (to be finalised before public launch). Until then, child-safety correspondence is received at support@pipchat.in.

8. Changes

We will update this policy as our detection and reporting capabilities and legal obligations evolve.