FAQ
Questions about Lurion.
Our position on consent and control, then answers on privacy, deployment, and integrations.
Our position
Lurion Live does not replace human judgment. It protects it.
No passive monitoring. No surveillance infrastructure. No behavioral scoring running in the background without consent. The employee controls when Lurion Live activates. Always.
Clean calls are discarded. Flagged attacks are retained for reports and detection improvement. That is the line.
Not
- Passive monitoring
- Employee surveillance
- A training checkbox
Is
- User-initiated
- Consent-first
- Plain English under pressure
Questions
What teams ask before rollout.
If your question is not here, email founders@lurion.org or review the company plan on Pricing.
Lurion Live is user-initiated. The employee taps to activate during a live call. Clean call data is discarded.
Flagged-call analyses are retained for incident reports and detection improvement. Talk with Lurion about current retention practices before deployment.
Current business workflows can route available alerts to your IT or security lead. Talk with Lurion about the integrations available for your rollout.
Lurion Live is built around consent-first activation. Teams should still follow their own call recording, monitoring, and employee notice requirements by state, country, and industry.
The product is designed for iOS, Android, and desktop meeting workflows. Availability depends on the current product rollout and onboarding path.
Company deployments begin with onboarding and a conversation with the Lurion team. A limited number of structured pilots may be available for a focused group of employees.
Get started
Ready to see Lurion Live on a live call?
Book a demo with the Lurion team, or review the company plan for your rollout.