Skip to main content

Privacy Policy

How Pika H3 handles account details and creative inputs — draft

Draft — pending confirmation. This page describes data flows found in the current implementation. It does not certify the production configuration or third-party practices. Unresolved items are marked [TO CONFIRM].

Who operates the service

[TO CONFIRM: operator's legal identity, address, official domain, privacy contact, applicable regions and effective date.]

Data used by the workspace

  • Account information: account name, email address, authentication records and sessions support sign-in and access to your workspace.
  • Creative inputs: prompts, reference media and generation settings are used to submit the job you request. The current video integration sends generation inputs and uploaded reference media to Pika when a job is submitted.
  • Job records: the current implementation stores the user association, request details, job status, output links, error codes and charge records so that jobs can be tracked and results retrieved.
  • Support messages: if the contact channel is enabled, your name, email and message are sent through the configured email service to support.
  • Billing information: if payments are enabled, the selected payment service processes checkout, and the application records payment references and status. [TO CONFIRM: production payment provider and exact data shared.]

Providers and processing locations

The application is designed for Cloudflare hosting, database and file storage. Pika is the current video integration. Optional email, sign-in, analytics and payment services depend on configuration.

[TO CONFIRM: production providers, processing purposes and legal bases, recipients, countries of processing, transfer safeguards and provider contract terms.] Code integrations alone do not establish a provider's retention or training practices.

Retention, deletion and model training

[TO CONFIRM: retention periods for accounts, prompts, uploaded media, output files, logs and backups; deletion workflow and timing; whether each provider uses inputs or outputs for model training; opt-out controls.] We do not claim that data is immediately deleted or never used for training while these details are unresolved.

Your choices and requests

Account settings provide profile and security controls. [TO CONFIRM: the scope of account deletion, access/export/correction/deletion request process, identity checks, response times and applicable complaint authority.] Deleting an account must not be assumed to remove every provider-held copy of a file.

Cookies and optional services

See the Cookie Policy for authentication and preference storage and the outstanding review of optional analytics. [TO CONFIRM: newsletter consent, production analytics and consent controls.]

Contact and updates

Privacy contact details and an effective date remain [TO CONFIRM]. The contact page will show the support channel when it is available.