Recording and Voice Processing Policy

MenerFlow does not enable call recording in the current release. No workspace, integration, policy field, or administrator setting can turn it on. Customers must not work around this prohibition and represent an external recording as a MenerFlow feature.

A connected voice provider can process live audio to conduct a conversation even when no recording is intentionally requested or stored. MenerFlow can receive call status, duration, outcome, transcript, summary, or extracted details such as name, email, address, service, and urgency. Those records are personal information.

Before any voice workflow, Menerai must verify the actual provider contract, plan, audio saving, transcript retention or zero-retention setting, model-improvement setting, region, access, and deletion. The Customer must provide required notice and authority for live-audio and transcript processing. Outbound synthesized voice remains blocked until consent, automated-call, DNCL, do-not-call, identification, calling-hour, script, suppression, and record controls pass.

Recording cannot be introduced by changing this Policy. It requires a separate product design, appropriate-purpose and jurisdiction review, call-start notice and consent, alternative path for objection, provider verification, access, retention, deletion, security, order update, founder approval, and staging/browser tests.

Voiceprints, biometric identification, and emotion inference are outside the approved pilot. If a Customer independently records outside MenerFlow, it remains responsible for that activity and must not upload the recording without lawful authority and separate written approval.