diff --git a/internal/api/routes/web.go b/internal/api/routes/web.go index 3448fbb..a96791d 100644 --- a/internal/api/routes/web.go +++ b/internal/api/routes/web.go @@ -33,6 +33,9 @@ func RegisterWebRoutes(r chi.Router, oauthClient *oauth.OAuthClient, userService // Legal pages r.Get("/privacy", handlers.PrivacyHandler) + // Safety pages + r.Get("/safety/child-safety", handlers.ChildSafetyHandler) + // Static files (images, etc.) r.Get("/static/*", func(w http.ResponseWriter, r *http.Request) { // Serve from project's static directory diff --git a/internal/web/handlers.go b/internal/web/handlers.go index 9fad31a..6179714 100644 --- a/internal/web/handlers.go +++ b/internal/web/handlers.go @@ -181,3 +181,11 @@ func (h *Handlers) PrivacyHandler(w http.ResponseWriter, r *http.Request) { http.Error(w, "Internal server error", http.StatusInternalServerError) } } + +// ChildSafetyHandler handles GET /safety/child-safety requests and renders the child safety standards page. +func (h *Handlers) ChildSafetyHandler(w http.ResponseWriter, r *http.Request) { + if err := h.templates.Render(w, "child-safety.html", nil); err != nil { + slog.Error("failed to render child safety standards template", "error", err) + http.Error(w, "Internal server error", http.StatusInternalServerError) + } +} diff --git a/internal/web/templates/child-safety.html b/internal/web/templates/child-safety.html new file mode 100644 index 0000000..6f21ac4 --- /dev/null +++ b/internal/web/templates/child-safety.html @@ -0,0 +1,304 @@ + + + + + + Child Safety Standards - Coves + + + + +
+ ← Back to Coves + +

Child Safety Standards

+

Effective Date: January 27, 2026

+ +

Coves.social is committed to the safety of all users, with particular emphasis on protecting children from sexual abuse and exploitation. This document outlines our standards and practices for preventing, detecting, and responding to child sexual abuse and exploitation (CSAE) and child sexual abuse material (CSAM) on our platform.

+ +
+

Scope: These standards apply specifically to content accessed through coves.social and the official Coves mobile applications. Other services using Coves software or the AT Protocol may have their own policies.

+
+ +
+

Zero Tolerance Policy: Coves.social has a zero tolerance policy for child sexual abuse material (CSAM) and any content or behavior that sexually exploits, abuses, or endangers children.

+
+ +

1. Our Commitment

+

Coves.social is dedicated to:

+ + +

2. Prohibited Content and Conduct

+

The following is strictly prohibited on Coves:

+ +

2.1 Child Sexual Abuse Material (CSAM)

+

Any visual depiction involving a minor or minor-aged character engaging in sexually explicit conduct, including but not limited to:

+ + +

2.2 Grooming and Predatory Behavior

+

Any attempt to build trust with a minor for the purpose of sexual exploitation or abuse, including:

+ + +

2.3 Coercion and Sextortion

+ + +

2.4 Child Trafficking

+

Any content or conduct related to the trafficking of minors for sexual purposes, including recruitment, transportation, or facilitation of such activities.

+ +

2.5 Minor Personal Information

+

Sharing or soliciting information about minors that could endanger their safety, including:

+ + +

3. Age Requirements

+

Coves.social is intended for users who are 18 years of age or older. Users must be at least 18 to create an account and use our services. We do not knowingly allow users under 18 to access coves.social.

+ +

3.1 Age Verification

+

We implement age restrictions through:

+ + +

3.2 Underage User Response

+

If we have reason to believe a user is under 18:

+ + +

4. Detection and Prevention

+

We employ multiple measures to detect and prevent CSAE on coves.social:

+ + +

5. Reporting Mechanisms

+

We provide multiple ways for users to report CSAE or CSAM:

+ +

5.1 In-App Reporting

+

Users can report content or accounts directly within the official Coves mobile app using the built-in reporting feature. Reports are reviewed promptly by our moderation team.

+ +

5.2 Email Reports

+

Users can report concerns via email to support@coves.social. Please include as much detail as possible, including usernames, content descriptions, and screenshots if safe to do so.

+ +

5.3 External Reporting

+

In addition to reporting to Coves, we encourage users to report CSAM to:

+ + +

6. Response Procedures

+

When we receive a report or identify potential CSAE or CSAM:

+ + +

7. Compliance with Law

+

Coves.social complies with all applicable laws regarding child safety, including but not limited to:

+ + +

8. AT Protocol and Federation

+

Coves.social is built on the AT Protocol, a federated social networking protocol. Federation does not exempt content from our safety standards—prohibited content is not permitted regardless of its origin.

+ +

8.1 How Federation Works

+

In the AT Protocol ecosystem:

+ + +

8.2 Handling CSAM from External Sources

+

When CSAM originating from another PDS is identified in our AppView:

+ + +

8.3 Our Scope of Control

+ + +

9. Safety Resources

+

If you or someone you know is a victim of child sexual abuse or exploitation, please contact:

+ + +

10. Contact Information

+

For questions about our child safety standards or to report concerns:

+ +
+

Coves Safety Team

+

Email: support@coves.social

+
+ +

11. Updates to This Policy

+

We may update these standards from time to time to reflect changes in our practices, technology, legal requirements, or industry best practices. We will post any updates on this page and update the effective date accordingly.

+ +
+

Our Pledge: Coves.social is committed to maintaining a safe environment and will continue to invest in tools, training, and partnerships to combat child sexual abuse and exploitation on our platform.

+
+
+ +