SLOP Child Safety Policy

Effective: August 13, 2026 Policy version: 2026-09-10-v4-qualified-engagement-creator-access

1. SLOP is 13+

SLOP does not permit accounts for children under 13. This applies to the website, mobile applications, posting, comments, Viewer Rank, profiles, creator features, and other account-based SLOP services.

Normal SLOP social access does not require a government ID, selfie, or Stripe Identity. Signup requires a date of birth and the server checks the entered date against SLOP's minimum age. If the entered date indicates the person is under 13, SLOP refuses account creation and can apply a temporary device-level safety hold to reduce immediate DOB swapping.

The minimum-age screen is only one layer. SLOP also uses account/device anti-abuse controls, first-person under-13 text signals, child-safety reports, rapid quarantine, and admin review. No age-screening design can guarantee that every person tells the truth.

2. Existing-account age concerns

If an existing account states in first person that the account holder is under 13 in a profile, post caption, comment, support message, report, appeal, or other supported account-controlled text, SLOP may immediately place that account into child-safety age review. During that review SLOP may temporarily restrict account access, hide the account's public posts/comments/profile, and remove its engagement from trusted/public or payout-qualified calculations.

A third-party child-safety report is treated as a high-priority safety signal, but an accusation by itself is not treated as conclusive proof of the reported person's age. Admin SLOP has a dedicated child-safety queue and age-review resolution path.

3. No under-13 workaround

SLOP does not offer an under-13 account or a parental-consent workaround that converts an under-13 account into an ordinary SLOP account. Attempts to evade the minimum-age screen, automate replacement accounts, repeatedly change age information, or defeat SLOP's child-safety controls are prohibited.

4. Stripe is for creator money access, not ordinary social access

A normal 13+ user can watch the SLOP feed, access profiles, comment, rank, follow, post and upload without Stripe identity verification.

Creators may accumulate legitimate earnings before payout onboarding is complete. Official Creator is an optional recognition badge, not a withdrawal requirement. Accessing creator money through withdrawal requires the real funded balance and payout requirements, including Stripe-hosted tax/identity/payout onboarding, Stripe/provider-confirmed minimum payout age of 17+ where available to SLOP's connected-account integration, verified phone, withdrawal security, and integrity clearance. SLOP does not intentionally store raw government-ID images or raw tax identifiers in ordinary SLOP profile storage.

5. Zero tolerance for child sexual abuse and exploitation

SLOP prohibits CSAM, CSAE, grooming, sexual enticement, sextortion, child sex trafficking, sexualization of minors, requests for sexual images/videos/livestreams involving minors, sexual deepfakes or synthetic sexual depictions of minors, and any attempt to facilitate sexual contact with a minor.

These rules apply to real, edited, AI-generated, animated, or synthetic material where applicable under law and SLOP policy.

6. Reports, quarantine, preservation and escalation

Child Safety reports are critical-priority reports. Supported reported posts/comments can be quarantined pending review. Child-safety support contacts are routed to the dedicated child-safety queue.

SLOP's in-app report button is not a substitute for any legally required external report. When applicable law requires preservation or reporting to an authorized organization or law-enforcement channel, SLOP's response process must handle that separately and preserve only what is legally appropriate.

7. Privacy and minimization

The signup minimum-age screen should retain only what SLOP needs to enforce the 13+ rule, such as the result, age band and screening timestamp, rather than publishing or exposing a user's raw birthday. Child-safety and anti-evasion records should be minimized and protected from ordinary public access.

8. Operational review

SLOP's owner must maintain a working child-safety contact, review queue, escalation process, moderation operations, and jurisdiction-specific legal review before public launch. Code alone cannot eliminate legal risk.