> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pup.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Member-profile rules

> The privacy and policy boundary for member-profile signals.

Pup does **not** automate member-profile rules. Discord's Developer Policy
prohibits using API data to profile Discord users or their identities, so Pup
does not inspect usernames, display names, guild nicknames, avatar images,
bios, profile changes, message text, appearance, style, or interests for a
moderation decision. It does not store profile snapshots, hashes, pattern
matches, confidence scores, or an early-message window for this purpose.

Discord-visible account creation time and bot status remain available to the
[join-admission guard](/join-guard). Account age is not a person's age. These
signals are bounded, uncertain review cues; they do not establish identity or
personal age and Pup never automatically kicks, bans, or sanctions a member
from them.

## Human review and corrections

A moderator can handle a statement a member voluntarily submits through the
normal moderation process. For automated profile moderation, Pup does not
extract or classify statements from a profile or chat history, or send Discord
API data to an AI provider. The optional Assistant has separate
[AI processing and memory disclosures](/privacy#assistant-memory). A claim that someone is under 18 is human-submitted review
only, never an automated age assessment.

Any resulting moderation action remains deliberate, authorized, and subject to
the normal case and correction process. For join admission, an authorized
moderator can restore access; the restoration removes only the exact
Pup-recorded quarantine role, so a later policy change or profile change cannot
remove a server-managed restriction. See [Data and privacy](/privacy) for
retention and correction details.

## What Discord exposes—and what it does not

Discord documents a user's username, display name, avatar hash, and bot status,
plus a guild member's nickname and avatar hash. It does not expose a bio,
birthdate, or verified human age to a bot. Pup does not scrape Discord or try
to derive those missing facts.

This boundary is intentional. If Discord changes its policy or grants written
permission for a distinct use, Pup needs a new reviewed design, disclosure,
retention contract, correction path, and implementation before any profile
automation can be offered.

## Reviewed categories, not automated matching

Server administrators can configure the narrow categories a human reviewer may
record: username, display name, avatar, account age, bot status, or an already
approved pattern. Pup stores the selected categories and a reviewer-selected
confidence level, not the profile values, avatar pixels or hashes, pattern
contents, or an identity conclusion. The policy can include or exempt members by their current Discord roles and has a 1–90 day review-record retention limit. Pup checks current membership, role scope, exemptions and protected subjects before accepting a new record.

A Discord profile-change event makes an active human conclusion **stale**. It
does not produce a new match or an automatic enforcement action. An authorized
reviewer can revisit the record and mark the old assessment corrected. This updates the review record only; it does not remove a Discord restriction. This is a correction workflow, not evidence of a
person's identity, age, alternate accounts, or other hidden attributes.

## Record or correct a human review

Open **Protection overview → Profile review**. Automated profile inspection is unavailable; the page separately configures human review records. Enable records, select allowed categories, set member role scope and retention, then save.

Under **Record a human review**, choose a current member, the categories considered and your confidence. **Record review without restriction** records a completed human assessment without changing Discord access. Pup never asks for profile text, an image or a raw restriction reference.

Existing records show their categories, confidence, retention and whether another human review is needed. A historical restriction reference is not confirmation of the member's current Discord access. Use **Open member moderation** to inspect or change access through the normal authorized workflow. **Mark review corrected** corrects a stale record only.