User Safety Compliance

User safety compliance ensures that features protect users from harmful content, abuse, and unsafe defaults. These checks apply to any recipe that displays, generates, or accepts user-contributed content, as well as features whose configuration choices can affect user wellbeing.

Applicability

This category applies to recipes and guidelines that involve user-generated content, content display or generation, social features, configurable behavior with safety implications, or content targeting specific age groups.

Checks

content-moderation

User-generated content MUST be moderated before public display.

Applies when: recipe accepts and displays content submitted by users.

Guidelines:


age-appropriate-content

Content MUST be classified and gated per platform age-rating requirements.

Applies when: recipe displays or generates content that may not be suitable for all ages.


abuse-prevention

User-facing input surfaces MUST implement rate limiting and abuse prevention measures.

Applies when: recipe exposes input fields, forms, or APIs to end users.

Guidelines:


harmful-content-filtering

Content pipelines MUST filter harmful, illegal, or policy-violating material.

Applies when: recipe processes, transforms, or displays content from external or user sources.

Guidelines:


reporting-mechanism

Features with user-generated content SHOULD provide a mechanism to report problematic content.

Applies when: recipe includes UGC or social features.


safe-defaults

Features MUST default to the safest configuration; riskier options require explicit opt-in.

Applies when: recipe has configurable behavior affecting user safety.

version
1.0.0
status
draft
tags
compliance, user-safety
author
Mike Fullerton
modified
2026-03-28

Change History

Version Date Author Summary
1.0.0 2026-03-28 Mike Fullerton Initial creation