Deletion & Correction Policy

APEX provides deletion and correction workflows so users can request deletion of nonessential data or correction of inaccurate, outdated, incomplete, or wrongly linked information.

A deletion request asks APEX to delete, reduce, or de-identify information where it is no longer needed.

APEX may delete ordinary profile data, stale display fields, duplicate records, safe/no-action data, or other nonessential information where appropriate.

Deletion does not always mean immediate full erasure of limited safety, audit, appeal, correction, security, or legal records.

APEX may retain limited information where necessary and proportionate for child/community safety, abuse prevention, anti-evasion, appeal processing, correction handling, audit integrity, legal obligations, or defense of legal claims.

A correction request asks APEX to review information that may be inaccurate, outdated, incomplete, or linked to the wrong account.

Correction categories may include:

• profile information
• identity-link information
• reviewed safety status
• appeal decision
• report information
• case or Member Review information
• other information

Correction can include wrong identity links, outdated statuses, incomplete reports, or records linked to the wrong account.

If a Discord-to-Roblox link appears wrong, outdated, or inaccurate, the user should submit a correction request under identity-link.

APEX may review the link, verification history, account identifiers, and relevant audit context.

APEX does not treat normal account changes as privacy requests. Users may use different Discord or Roblox accounts.

APEX may still retain limited safety or account-correlation records where necessary and proportionate for child/community safety, anti-evasion, audit integrity, appeals, corrections, legal obligations, or legal claims.

If a user believes a reviewed safety status is wrong, outdated, incomplete, or based on mistaken identity, the user may submit a correction request or appeal-review request.

APEX may review the relevant record and provide a safe user-facing decision message.

APEX may not disclose private evidence, hidden source data, detection logic, thresholds, provider internals, reporter identities, staff-only notes, legal hold data, or other protected information.

Some request decisions may require manual review, staged follow-up, future workflow support, or additional verification.

APEX may record that a request is granted, partially granted, denied, closed, accepted, or partially accepted in review, but certain deletion or correction actions may require controlled internal handling.

APEX should not automatically delete safety history, audit logs, legal hold records, appeal/correction records, or evidence records where limited retention remains necessary.

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

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.

Users may see user-safe request status messages.

These messages are intended to explain the general outcome without exposing private evidence, protected internal notes, confidential reports, hidden source data, or evasion-sensitive details.

Use the dashboard where available to submit:

• privacy request
• deletion request
• correction request
• objection request
• appeal-review request

Contact information is available on the APEX Contact page.

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.