Skip to main content
This report summarizes the date-related findings for all 17 MDX documents in the /legal directory. The audit date is April 22, 2026.

Summary table

Flagged items

Expired documents

These campaigns have ended and carry an expiration warning banner in the document:
3 documents have already expired and should be reviewed for archival or removal from active navigation.
All three expired documents already include a <Warning> banner indicating the campaign has ended.

Expiring soon (within 30 days)

1 document expires within 30 days and requires immediate attention.

Documents missing expiration dates

The following core documents have no stated expiration or renewal date. This is standard for ongoing terms of service but should be noted:
  • Terms & Conditions - General Operation
  • Terms & Conditions - Partner Program
  • Terms & Conditions - Referral Program
  • Terms & Conditions - Auto Earn (BTC Earn)
  • Terms & Conditions - OTC Services
  • OTC Terms of Service - Roxom Securities
  • Risk Notice
  • User Communication Manual
All of these include clauses allowing Roxom to amend or terminate at its discretion, which is the intended mechanism for updates.

Annual review required

The Privacy Policy explicitly states it must be reviewed annually. The version history shows v1.0 dated 10/07/2024, with the current effective date of October 7, 2025. The next annual review is due by October 7, 2026.

Per-participant validity periods

Version history inconsistencies

Minor date format inconsistencies found in version history tables across documents.

Recommendations

  1. Auto-Earn Boost (urgent): The promotional period ends April 30, 2026. A decision is needed within the next 8 days on whether to extend, update the terms, or add an expiration banner.
  2. Expired campaigns: Consider whether the three expired campaign pages should remain in navigation or be moved to an archive section to reduce clutter.
  3. Privacy Policy review: Schedule the annual review before October 7, 2026 as required by section 11 of the document.
  4. Version history alignment: Consider standardizing version history entries to always reflect the document’s effective date and use a consistent date format (ISO 8601 recommended).
  5. Trading Program tracking: Implement a mechanism to track individual participant expiration dates, since the 1-year validity is calculated per trader from their Program Communication date.
Last modified on April 22, 2026