Leilani is designed to use customer data only to provide the functionality customers expect from the product.
At a high level, that means:
- customer data is processed to run callflows, generate responses, produce transcripts and summaries, route calls, and deliver outputs
- customer data is not used to train Leilani
- customer data is not sold, rented, or used for advertising
- customer data is not used for unrelated product or business purposes outside delivering and securing the service
Live call audio
Leilani processes live call audio in real time so it can participate in the call.
Leilani does not create or retain call recordings.
In practical terms:
- Leilani does not record call audio
- live audio is processed transiently to support the active call
- call audio is not stored as a recording artifact by the Company
Transcripts and outputs
Leilani may generate transcripts, summaries, and other outputs as part of the product experience.
Those outputs exist to provide functionality, not to create a secondary use for customer data.
At a high level:
- transcripts and summaries are generated to support the service
- transcripts are held in memory for active call handling rather than stored as a persistent dataset
- transcripts can be delivered to the customer when configured
- transcripts are not retained by the Company after active call processing is complete
In practical terms, Leilani does not keep a stored transcript archive. Transcript data exists to support the live call and, when configured, to deliver the post-call transcript output to the customer.
Data use boundaries
Leilani's default posture is narrow use.
Customer data is used to:
- operate the service
- complete the requested workflow
- maintain security, reliability, and abuse prevention
- satisfy legal and compliance obligations where required
Customer data is not used to:
- train Leilani
- create call recordings
- build advertising audiences
- resell or monetize customer communications data
Infrastructure and providers
Leilani uses infrastructure and third-party providers where needed to deliver the service, including AI processing, email delivery, hosting, and payments.
Those providers process data only to support service delivery under contractual confidentiality and security obligations.
Security and operational logging
Like most production systems, Leilani retains limited technical and security data needed to operate safely and reliably.
That can include:
- SIP signaling metadata
- authentication and access logs
- endpoint and network information
- service and error logs
These exist for operational integrity, troubleshooting, fraud prevention, and compliance, not for model training or unrelated data use.
In plain language
The trust model is simple:
- Leilani processes what it needs to make the product work
- Leilani does not record calls
- Leilani does not keep a stored archive of call transcripts
- Leilani does not train on customer data
- Leilani does not use customer data for unrelated purposes
For the formal legal terms, see Privacy Policy and Terms of Service.