Platform
RLX Legal
Backend-managed legal pages, footer links, policy versioning, user acceptance records, and optional compliance cross-links.
What it does
Features at a glance
- Starter legal pages for Terms, Privacy, Cookie Policy, GDPR/Data Rights, Acceptable Use, Community Guidelines, Refund Policy, Copyright/DMCA, Safety Center, and Self-Hosted Deployment Responsibility
- Custom legal page creation for additional policies
- Markdown policy editor using the shared RLX editor toolbar
- White-label tokens that resolve at render time from addon settings and core site identity
- Per-policy nav placement: no nav, left, center, or right
- Per-policy footer placement: no footer, left, center, or right
Built for your workflow
Who it’s for
- Platform projects that need this focused capability
- Owners who want to activate only the workflows their site needs
Setup and fit
Compatibility
Requires a valid LifeRaft OS core license and a supported installation.
No additional add-on is listed as a required dependency.
From setup to everyday use
A straightforward starting point
- Activate RLX Legal and review its add-on settings
- Starter legal pages for Terms, Privacy, Cookie Policy, GDPR/Data Rights, Acceptable Use, Community Guidelines, Refund Policy
- Custom legal page creation for additional policies
Before you choose
Common questions
What does RLX Legal do?
Backend-managed legal pages, footer links, policy versioning, user acceptance records, and optional compliance cross-links.
What does RLX Legal need to run?
RLX Legal runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.
How ready is RLX Legal for deployment?
Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.
Review the launch checklist
- Admin setup — Confirm settings, navigation placement, permissions, and any required starter content before launch.
- Public QA — Review the public page, empty states, mobile layout, and activated/deactivated states.
- Package QA — Confirm the module fits the selected product package and does not expose unused workflows.
- Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.
Make RLX Legal part of your build.
Discuss the fit, requirements, and next steps for your project.