FAQ
Questions about Meridian.
Our position on consent and control, then answers on privacy, deployment, and integrations.
Our position
Meridian 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 Meridian 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 compare plans on Pricing.
Meridian 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. Enterprise supports custom retention and residency.
Business workflows can route alerts to your IT or security lead. Business Pro will add SSO and SIEM integrations* — on the active roadmap, not yet available. See Pricing for tier details.
Meridian 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 rollout tier and onboarding path.
Free puts Meridian in individual hands. Business and Enterprise deployments begin through early access, onboarding, and a live demo with the Lurion team.
Get started
Ready to see Meridian on a live call?
Book a demo with the Lurion team, or compare seat pricing for your rollout.