Skip to content

Instantly share code, notes, and snippets.

@shubham2892
Created April 28, 2026 05:42
Show Gist options
  • Select an option

  • Save shubham2892/4e32ba9d18a8fb6b5b30eec2cd03889f to your computer and use it in GitHub Desktop.

Select an option

Save shubham2892/4e32ba9d18a8fb6b5b30eec2cd03889f to your computer and use it in GitHub Desktop.
layout default
title Child Safety Standards — Campus Net

Campus Net — Child Safety Standards

Effective date: April 27, 2026 Last updated: April 27, 2026 Compliance contact: campusnet@proton.me

Campus Net is a social platform for verified university students. We are committed to keeping our platform free of child sexual abuse and exploitation (CSAE) material. This page describes the standards we apply, the safeguards built into the product, and how to report violations.

This policy is published in compliance with Google Play's Child Safety Standards Policy and Apple's App Store Review Guidelines.


1. Who can use Campus Net

Campus Net is intended for currently enrolled university students aged 17 years or older. We enforce this in three ways:

  1. University email verification. Sign-up requires a valid .edu or .edu.in email address. We deliver a one-time verification code to that address and only create the account once it is confirmed. This restricts the platform to students at accredited universities, who are overwhelmingly adults.
  2. Apple App Store age rating: 17+. Our App Store listing is rated 17+, which Apple enforces at install time on devices with parental controls.
  3. Google Play target age: Adults (18+). Our Play Store listing targets the Adults audience and is excluded from the Designed for Families programme.

Accounts found to belong to anyone under 13 are deleted immediately upon discovery. Accounts of users aged 13–16 are deleted unless we receive verifiable parental consent (we currently do not offer a path for under-17 users to remain on the platform).


2. Prohibited content

The following are strictly prohibited on Campus Net under our Terms of Service and the Acceptable Use sections of our Privacy Policy:

  • Child sexual abuse material (CSAM) of any kind, in any form (image, video, text, audio, link, or file)
  • Sexual content involving any person under the age of 18, or any person appearing or described as under 18
  • Grooming, sexualised attention, or sexual solicitation directed at minors
  • Content that sexualises children, including AI-generated, drawn, animated, rendered, or "cartoon" CSAM
  • Sharing personal contact details, location, school name, or any other identifying information about a minor without that minor's parent's verifiable consent
  • Content promoting, glorifying, normalising, or providing instructions for the abuse, exploitation, or trafficking of children

Violations result in immediate, permanent account termination and, where the law requires it, reporting to relevant authorities (see Section 6).


3. In-app reporting mechanism

Every post and comment on Campus Net carries a tap-target overflow menu () that includes a Report action. Choosing Report:

  1. Opens a category picker (Spam, Harassment, Hate Speech, Sexual Content, Violence, Self-harm, Other).
  2. Records a report against the content with the reporter's account, the selected category, and an optional free-text description.
  3. Auto-hides the content pending review once it accumulates a small number of reports of the same category from distinct users.
  4. Notifies the platform moderation team for human review of high-severity categories (Sexual Content, Self-harm, CSAE-related Other).

A report can be filed in two taps from any feed, thread, or profile view. No account verification beyond a logged-in user is required.

For content that appears to be CSAM specifically, users are asked in the report flow to use the dedicated CSAM reporting channel (Section 4) in addition to filing the in-app report, since the platform team needs to preserve evidence in a forensically-sound way that an in-app report alone does not guarantee.


4. Direct CSAM reporting channel

If you encounter content on Campus Net that you believe constitutes child sexual abuse material, please report it through both:

  1. The in-app Report feature (Section 3), so the content is hidden from other users immediately, and
  2. Direct email to campusnet@proton.me with the subject line "CSAE REPORT — URGENT". Include:
    • The username of the account that posted the content
    • The post or comment URL or screenshot (if safe for you to provide)
    • The approximate date and time you saw the content
    • Any other context you believe is relevant

We monitor this address continuously and aim to acknowledge CSAE reports within 24 hours, with action taken within 72 hours at the latest.

You may also report CSAM directly to the National Center for Missing & Exploited Children (NCMEC) at report.cybertip.org, or to your local law enforcement. We cooperate with all such authorities and will preserve and disclose relevant data when legally required.


5. Platform-side safeguards

In addition to user-driven reporting, Campus Net runs the following automated and human safeguards:

  • Content moderation blocklist. Posts and comments are scanned at publication time against a maintained blocklist of words and phrases associated with sexual abuse, exploitation, and grooming. Matches trigger one of: silent flag for human review, soft-block (the post is hidden from feeds but visible to the author), or hard-block (the post is rejected before insertion). The blocklist is multilingual and normalises common Unicode obfuscation tricks.
  • User blocklist. Users can block other users from the same overflow menu ( → Block user). Blocked users' posts, comments, and reactions are hidden from the blocker's view. Blocking is symmetric: the blocked user cannot see the blocker either.
  • Anonymous-by-default posting. Most post types are anonymous to other users by default, but the platform always retains the link between the post and the authenticated account internally. This means even anonymously-posted CSAE can be traced to the actual author for enforcement and reporting purposes.
  • Hidden post enforcement. Posts that are hidden by moderation (auto-hide threshold, blocklist match, or human review) lose the Campus Rep awarded to the author and are removed from public feeds, hot rankings, and search.
  • Account deletion. Accounts can be deleted by their owner from Settings, and are deleted by the platform team in response to confirmed CSAE violations. Account deletion fully purges associated content within 30 days.

6. Cooperation with law enforcement

Campus Net cooperates fully with law enforcement on CSAE matters. We will:

  • Preserve account, content, and access-log data when we receive a preservation request from a law enforcement agency, in accordance with applicable law (e.g., 18 U.S.C. § 2703(f) in the United States).
  • Disclose preserved data in response to valid legal process (subpoena, court order, or search warrant as appropriate to the data category).
  • Proactively report apparent CSAM to NCMEC's CyberTipline as required by 18 U.S.C. § 2258A and to the equivalent national authorities in other jurisdictions where we operate.

7. Compliance contact

For all CSAE-related compliance enquiries, including from law enforcement, researchers, child-safety organisations, or platform regulators:

  • Email: campusnet@proton.me
  • Subject line for urgent CSAE matters: "CSAE COMPLIANCE — URGENT"
  • Response SLA: 24 hours for acknowledgement of urgent reports; 72 hours for substantive response on enforcement actions; 7 business days for general compliance questions.

8. Updates to this policy

We will update this page when our practices change. The effective date and last-updated date at the top of this page reflect the current version. We do not send proactive notifications for changes to this policy specifically; material changes that affect users are also reflected in the Terms of Service update notifications inside the app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment