Community add-on
RLX Compliance
Adds GDPR/UK GDPR/Australia Privacy Act support with theme-aware consent UI, localized privacy links, data exports, erasure requests, retention registry, and compliance audit logs.
About this add-on
RLX Compliance for LifeRaft OS
Adds GDPR/UK GDPR/Australia Privacy Act support with theme-aware consent UI, localized privacy links, data exports,
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Keeps member value inside the owned community instead of losing activity to third-party tools
Capabilities and outcomes
How RLX Compliance improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Supports participation, discovery, support, and communication from one coherent product surface
Community builds that need RLX Compliance without forcing it into every install
Standalone value
What it does by itself
RLX Compliance can run as its own Community workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX Support, RLX Newsletter, RLX Chat, RLX Polls, and RLX Survey, RLX Compliance can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Community builds that need RLX Compliance without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Compliance and review its add-on settings
- Public privacy center with controller, contact, lawful basis, retention, subprocessors, and regional notice sections
- Consent categories for required, preferences, analytics, marketing, and third-party embeds
- Theme-aware cookie banner with accept all, reject optional, and granular save actions
- RLX Compliance loads from rlx-compliance/addon.php and should be configured through the add-on registry, permissions,
Works well with
The strongest builds connect the right modules
RLX Compliance becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Support, RLX Newsletter, RLX Chat, RLX Polls, RLX Survey, depending on the customer package and what the site needs to accomplish.
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.
Customer FAQ
Common questions about RLX Compliance
What does RLX Compliance do?
Adds GDPR/UK GDPR/Australia Privacy Act support with theme-aware consent UI, localized privacy links, data exports, erasure requests, retention registry, and compliance audit logs.
Who is RLX Compliance best for?
Admin-managed content and settings. Public pages with clean presentation. Designed to run as an optional RLX module.
Can RLX Compliance run by itself?
RLX Compliance can run as its own Community workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Compliance should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX Support, RLX Newsletter, RLX Chat, RLX Polls, and RLX Survey, RLX Compliance can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Compliance?
RLX Compliance commonly pairs with RLX Support, RLX Newsletter, RLX Chat, RLX Polls, RLX Survey. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Compliance?
RLX Compliance should be launched with its real data model and public routes in mind. Routes: RLX Compliance is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold. Add screenshots of public pages, admin controls, member workflows, moderation options, and example content types Include a short scenario showing how RLX Compliance helps a community owner reduce support load or publish cleaner
How much does RLX Compliance cost?
RLX Compliance has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Compliance?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Compliance for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Compliance fit into a real LifeRaft OS build?
Activate RLX Compliance and review its add-on settings. Public privacy center with controller, contact, lawful basis, retention, subprocessors, and regional notice sections. Consent categories for required, preferences, analytics, marketing, and third-party embeds. Theme-aware cookie banner with accept all, reject optional, and granular save actions.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Compliance in your LifeRaft OS build?
RLX Compliance is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.