Data privacy and governance

Radiant records product usage events (page views, feature actions, session heartbeats, and pipeline lifecycle events such as lead created or deal won). Each event carries your company id, the acting user id, an event type, and small pieces of context such as the entity affected. We also keep an audit log of sensitive actions, for example role changes and data exports.

Usage data powers your own dashboards, the admin drill-downs, and platform benchmarks. It also feeds AI improvements that suggest better workflows across all installers using Radiant.

Cross-installer analysis, including any AI learning layer, reads only from a strict anonymisation view. That view exposes only the event type, the entity type, the event day, and an opaque one-way hash of the company id. It never exposes user ids, session ids, routes, entity ids, raw timestamps, or event metadata. Company identity cannot be reversed out of the hash.

If your company opts out of contribution, no rows from your company appear in that view at all.

In Settings, open the "Privacy and data" tab and turn off "Contribute anonymised usage to cross-installer benchmarks and AI improvements". The change takes effect immediately for new reads of the anonymised view.

Company admins can request a JSON export of their company's platform data (analytics events, sessions, form submissions, and the current consent record). Radiant admins can trigger this from the HQ installer drill-down. Every export is written to the audit log.

Analytics events are automatically deleted after 24 months. Audit log entries are retained for the life of the account for security and compliance.