Pika Labs

Pika explicitly states it may use Content (including Inputs and Outputs) to train and improve its machine learning models without requiring opt-in consent. The only exception is AI Self inputs, which are limited to training that specific AI Self. This broad training right applies by default to all user data.

“[ToS] "Unless otherwise agreed in writing, you acknowledge that Pika may use Content—including Inputs, Outputs, and your interactions with the Service—to train, improve, and develop its machine learning models, algorithms, and related technologies and services."”

Pika claims a broad, perpetual, irrevocable, worldwide, sublicensable license to User Content for service operation and improvement. The license survives as long as content is stored on the service and includes rights to modify, adapt, and create derivative works. This is highly unfavorable to enterprise users.

“[ToS] "By submitting User Content, you hereby grant Pika a worldwide, nonexclusive, royalty-free, transferable, sublicensable license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, perform, and display your User Content as necessary to operate, improve, and promote the Service."”

The ToS mentions sharing with 'service providers and contractors' but does not provide a detailed sub-processor list or explicit DPA requirements. The Privacy Policy is referenced but not fully provided, making it difficult to assess the full scope of third-party sharing. Moderate concern due to vague language around 'service providers.'

“[ToS] "This license includes the right for Pika to make User Content available to its service providers and contractors in connection with providing and supporting the Service."”

The ToS states Pika may delete content upon account termination but is 'not obligated to do so' and has 'no obligation to retain any User Content beyond the limits set by your Plan.' The Privacy Policy is referenced but not fully provided, leaving retention periods vague. Moderate concern due to lack of clear timelines and deletion guarantees.

“[ToS] "Pika may delete or remove any of your Content in connection with the suspension or termination of your Account, but we are not obligated to do so. We are not responsible for the deletion or failure to delete any of your Content."”

Pika states it does not claim ownership of Outputs and assigns all interest to the user. However, Pika retains broad rights to use Outputs for model training and improvement. The language is somewhat contradictory—while ownership is assigned, Pika's usage rights are extensive, creating ambiguity about practical control.

“[ToS] "Pika does not claim ownership of any Inputs you submit or Outputs generated through your use of the Service. As between you and Pika, you retain all interest in those Outputs. To the extent Pika acquires any interest in the Outputs, we hereby assign all interest to you."”

No compliance certifications (SOC 2, GDPR, ISO 27001, HIPAA) are mentioned in either the ToS or the provided Privacy Policy excerpt. No security documentation, trust page, or DPA is referenced. This represents a significant gap in enterprise security standards.

“Not found in documents”