Community Safety Policy

APEX exists to help Roblox-connected Discord communities protect members, especially communities where minors may be present.

APEX supports identity verification, Force Account Link, Member Review, reports, scans, notifications, Activity Logs, appeal-review requests, correction requests, deletion/privacy requests, and privacy-aware safety governance.

APEX uses a private safety review model.

Safety signals, flagged member records, owner-safe summaries, Member Review records, and review recommendations are intended for authorized community staff and APEX platform review workflows.

APEX is not a public blacklist, public reputation score, or public shame list. APEX does not encourage public shaming, retaliation, harassment, doxxing, or vigilante action.

A safety signal may indicate that a Roblox or Discord account should be reviewed, linked, restricted from certain workflows, handled with additional caution, or escalated under approved safety processes.

Safety signals may come from scans, reports, server context, APEX review, third-party safety providers, appeal history, correction history, or platform trust and safety workflows.

A safety signal does not mean APEX has made a legal determination. It is a private review input.

APEX may provide safety check or member review tools for authorized staff.

These tools are private staff tools. They are not member-facing lookup services, public reputation systems, public accusation tools, or public posting tools.

Where implemented, they should be:

• staff-only
• permissioned
• private, ephemeral, or limited to configured staff channels
• audited
• rate-limited where appropriate
• limited to owner-safe wording

Results should use limited owner-safe wording such as:

• review recommended
• no active APEX safety status found
• appeal or correction pending
• status corrected or reduced

No active APEX safety status found does not guarantee that an account is safe.

APEX should not expose raw evidence, detection logic, thresholds, provider internals, reporter identities, staff-only notes, legal hold data, or platform trust and safety internals through safety check or member review tools.

APEX safety tools are designed for authorized community safety workflows.

APEX should not be used as a public lookup system for members to check other members' safety status.

Members should be encouraged to report concerns through approved report channels rather than search private safety records.

Server owners and staff should:

• use APEX signals as review inputs
• consider local server context
• avoid public accusations
• avoid public shaming, retaliation, harassment, or doxxing
• keep APEX records private
• restrict staff access
• document moderation decisions
• respect appeals and correction requests
• avoid retaliatory moderation
• escalate urgent danger through appropriate official channels

APEX may notify authorized staff about account-link status, Force Account Link status, review recommendations, flagged member status, scan findings, report status changes, safety workflow events, and Activity Log entries.

Notifications should be owner-safe and should not expose platform trust and safety internals, confidential reports, hidden source data, provider internals, detection methods, thresholds, legal hold data, or staff-only notes.

APEX does not disclose private platform trust and safety notes, raw provider internals, hidden detection logic, thresholds, confidential reporter identities, legal hold details, unsafe evidence, account-correlation internals, or staff-only notes to ordinary users or normal server staff.

APEX recognizes that reports and safety signals may be incomplete, outdated, or incorrect.

Users may submit correction or appeal-review requests. Where APEX confirms that a record was inaccurate, outdated, incomplete, or linked to the wrong account, APEX may correct, reduce, remove, or mark the relevant record as corrected where appropriate.

Where a prior APEX safety status affected a community workflow, APEX may later provide a limited owner-safe correction notice in a supported workflow.

APEX may limit access, reject reports, restrict accounts, or suspend customers who misuse APEX for harassment, retaliation, doxxing, public shaming, false reporting, evasion, or unauthorized disclosure.

APEX may use automated or semi-automated safety signals to help identify accounts for review.

Severe or lasting restrictions should be subject to human review, appeal review, or correction review where appropriate.

APEX should not treat automated signals as final determinations without appropriate safeguards.

APEX is not an emergency service.

If someone is in immediate danger, contact emergency services. Serious child-safety concerns should be reported to appropriate official reporting channels or law enforcement.

APEX provides request paths for privacy, deletion, correction, objection, and appeal-review concerns. Use the dashboard where available.

If you cannot access the dashboard, use the contact information on the Contact page. APEX may need to verify account ownership before disclosing, deleting, correcting, or reviewing account-related information.