Company

LugemiPolicies

How Lugemi handles consent, synthetic speech, and workspace data.

Policies

Voice cloning requires authorization. Generated speech should be identifiable where it could be mistaken for a live person. Workspace keys, RBAC, and usage logs support accountability. Legal counsel should review final terms before commercial filings — this page states product controls that already exist.

Disclosure-aware speaking turn

Can you repeat that in Twi for my customer?

Aane — me bɛka bio wɔ Twi mu. Lugemi nne ma ɔka adwuma a wɔyɛ wɔ Africa kasa ahorow mu.

Play each turn, or play the full agent conversation.

Use cases, demos & developer kit

How teams ship with Policies: interactive demos above, step guides below, and the same /v1 surface for APIs and SDKs.

Use case guide

Policy controls tour

Confirm the controls in product paths — not only on this page.

Play the disclosure-aware speaking turn demo above.
Review clone approval states in Voice / Studio after sign-in.
Set retention and branding under Data; invite teammates under Identity.

Safety Legal integrity Data settings Identity API docs

Consent for clones

Authorization is required before cloning a voice. Profiles can be reviewed, approved, rejected, or disabled by workspace owners and admins.

Synthetic disclosure

Mark generative speech where listeners could reasonably assume a live person. Watermark requirements apply on clone speech paths.

Honest coverage

Availability is published per language and task. Catalog membership is not a quality certificate.

Data controls

Retention, residency pins, source-text persistence, and vendor-training flags live under Data settings. Email branding (logo, address, socials) is editable there for system mail.