VillagersVillagers

Private concern

Raise a private or identifying concern.

Use this protected boundary for a concern that names people, includes identifying context, or should not enter a public correction process.

Review audience

Commander private-concern reviewers

This destination writes only to its named database boundary. It does not forward the submission into Contact or the general contribution queue.

40–8,000 characters. Names and identifying context remain inside the private-concern boundary. Do not include passwords, access tokens, or unrelated personal data.

Email is stored only inside this boundary and is never included in public criticism or notification email.

Completing the security check… If it remains here, reload this page; your browser may be blocking the check.

Wrong boundary? Return to all four accountability routes.

Use only necessary identifying context.

Name people or relationships only when the private reviewer needs them to understand the concern.

State the action you seek.

Ask for a private review, protected follow-up, safeguard, or bounded resolution.

Keep security detail separate.

A vulnerability belongs in the security-disclosure boundary, even when it also raises an accountability concern.

This boundary is private, not anonymous to reviewers if you include identifying context. It is not an emergency service and does not guarantee a particular outcome.

Private concern