Lilac

The clause provides a deletion or time-bounded retention path.

“We retain your information according to this schedule: User account information: Duration of service plus 30 days after account closure. Transaction logs: 7 years, as required for financial compliance. API logs: 90 days. Deleted user data: 30 days soft-delete period, after which data is permanently removed. We may retain certain information longer as required by law or for legitimate business purposes.”

The clause provides a deletion or time-bounded retention path.

“We retain your information according to this schedule: User account information: Duration of service plus 30 days after account closure. Transaction logs: 7 years, as required for financial compliance. API logs: 90 days. Deleted user data: 30 days soft-delete period, after which data is permanently removed. We may retain certain information longer as required by law or for legitimate business purposes.”

The clause includes sublicensable, transferable, or assignable rights.

“Lilac retains all rights in the Services. You receive a limited, non-exclusive, non-transferable right to use the Services per these Terms. If you provide feedback, we may use it without restriction or obligation. Each party will protect the other's non-public information with reasonable care and use it only as needed to perform under these Terms. This does not limit Lilac's data commitments in the "Your...”

The clause affirms user ownership or retention of rights.

“Ownership. "Customer Content" means the prompts, inputs, files, datasets, container images, and code you submit, batch inputs and results, fine-tuned model artifacts created for you, and model outputs processed through the Services. As between the parties, you own your Customer Content. You grant Lilac the limited right to host and process Customer Content solely to provide, secure, and support the Services. Lilac...”

The clause requires defense, indemnity, or hold-harmless obligations.

“You will defend and indemnify Lilac against third-party claims arising from your Customer Content; the workloads, code, images, datasets, and model weights you submit; your products; or your breach of the Acceptable Use section.”

model training improved from high/training permitted to low/no training claim.

model training worsened from low/no training claim to high/training permitted.

Latest stance: deletion or time bound on data retention

“We retain your information according to this schedule: User account information: Duration of service plus 30 days after account closure. Transaction logs: 7 years, as required for financial compliance. API logs: 90 days. Deleted user data: 30 days soft-delete period, after which data is permanently removed. We may retain certain information longer as required by law or for legitimate business purposes.”

Latest stance: sale or sell on training use

“We understand that the inputs you provide to our API and the outputs it generates may contain your Personal Information. We will not store, sell, or train using this data. Your API inputs and outputs are not stored at rest after the response is returned — they exist only in memory during the inference process and are deleted immediately afterward. We only retain metadata related to token counts and usage for billing and debugging purposes. No training: We do not use your API inputs or outputs for training models — ever. No sharing: We do not share the data you submit to our APIs with any third party. Your prompts and completions remain private to your account. Logs: We do not log your prompts or completions. We only log metadata — request ID, token counts, and sampling parameters — for billing and debugging purposes.”

Latest stance: third party or vendor sharing on training use

“We understand that the inputs you provide to our API and the outputs it generates may contain your Personal Information. We will not store, sell, or train using this data. Your API inputs and outputs are not stored at rest after the response is returned — they exist only in memory during the inference process and are deleted immediately afterward. We only retain metadata related to token counts and usage for billing and debugging purposes. No training: We do not use your API inputs or outputs for training models — ever. No sharing: We do not share the data you submit to our APIs with any third party. Your prompts and completions remain private to your account. Logs: We do not log your prompts or completions. We only log metadata — request ID, token counts, and sampling parameters — for billing and debugging purposes.”

Latest stance: third party or vendor sharing on privacy data use

“Service providers: See our subprocessor list below for the complete list of third parties that process data on our behalf. Identity providers: If you link your account to Google, we share data as needed to maintain that connection. Organization members: Your profile may be visible to other members of your organization. Legal requirements: Law enforcement or government authorities when required by law. Business transfers: In connection with a merger, acquisition, or sale of assets. Professional advisors: Lawyers, auditors, and insurers as needed.”