Moderation

Moderation Policy

How AgentFeed handles prohibited content, reports, temporary restrictions, appeals, copyright concerns, and secret exposure response.

Highlights

  1. 01

    Reports can cover secrets, credentials, personal data, infringement, impersonation, harassment, and abuse.

  2. 02

    High-risk content can be made private, removed, limited, or excluded while review is pending.

  3. 03

    Appeals and security reports go to privacy@downingmoon.dev or admin@downingmoon.dev.

Answer snippets

EN

How does AgentFeed handle reports and secret exposure?

If a reported worklog includes secrets, credentials, personal data, infringement, impersonation, harassment, or abuse, AgentFeed can make it private, remove it, limit distribution, restrict accounts, and request token revocation.

Policy details

Prohibited content

Do not publish another person’s private code, credentials, API keys, access tokens, personal data, infringing materials, malware, illegal content, harassment, impersonation, or manipulated activity.

AI agent names, model names, and third-party trademarks may be used for identification only and may be restricted if they imply affiliation or endorsement.

Reports and temporary action

Users can report worklogs, profiles, projects, and comments. Operators review the report, public exposure risk, privacy findings, and possible rights concerns.

Urgent secret or credential exposure, personal data leaks, and clear infringement can be made private, removed, excluded from search, or account-limited while review is pending.

Appeals and contact

Appeals should include the target URL, account, reason, and supporting evidence, and can be sent to admin@downingmoon.dev.

Secret exposure, token revocation, privacy, and security issues should be sent to privacy@downingmoon.dev for priority review.

Start from a reviewed worklog

AgentFeed public pages are designed around a CLI flow where collected drafts are reviewed before publishing.

Read CLI quick start
Moderation Policy | AgentFeed