Community
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.
What it does
Features at a glance
- 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
- Turns scattered community information into managed pages and repeatable content flows
- Gives owners a stronger reason to keep members inside the RLX site
- Theme-aware cookie banner with accept all, reject optional, and granular save actions
- Localized privacy navigation labels and consent banner text through the platform language packs
Built for your workflow
Who it’s for
- Community owners organizing member participation
- Creators and teams adding focused social workflows
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 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
Before you choose
Common questions
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.
What does RLX Compliance need to run?
RLX Compliance 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 Compliance 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 Compliance part of your build.
Discuss the fit, requirements, and next steps for your project.