LEGAL
Support, Complaints, Accessibility, and Security
Release APX-LGL-V3-DRAFT-2026-07-21 | Last updated July 21, 2026 | Effective date Pending legal approval
This document is prepared for APX launch readiness and should be reviewed by qualified legal/accounting counsel before paid public launch.
# THE APX METHOD™ — Support, Complaints, Accessibility, and Security
1. Support
Primary support route: [email protected]
Additional legal/privacy/security role inboxes must not be published until activated and monitored.
2. Complaints
APX should provide a clear complaint process:
1. customer sends complaint with order/account details; 2. APX acknowledges receipt; 3. APX investigates payment, access, session, support, privacy, or instructor records as relevant; 4. APX provides a written outcome; 5. customer may request one internal review; 6. mandatory regulator or consumer routes remain available.
Arabic complaint access is required for Egyptian consumer launch.
3. Accessibility
APX aims to make account creation, checkout, LMS, tasks, support, legal pages, and video/session workflows accessible. Do not claim WCAG conformance until tested.
Pre-launch tests should cover keyboard navigation, focus states, contrast, form labels, error messages, screen-reader names, captions/transcripts, payment forms, and legal acceptance controls.
4. Security statement
Customer-facing security wording must describe only controls that are actually implemented and verified.
Do not publish claims like nightly encrypted backups, monthly restore testing, MFA, rate limiting, log redaction, deletion automation, or restricted Drive sharing until evidence exists.
5. Responsible disclosure
Security reports should go to [email protected] only after the inbox exists and is monitored. APX may state that it does not intend to pursue good-faith security research conducted safely, but counsel must review any safe-harbor language.