LizzFlix
LegalPrivacy policy
Archived version

Privacy Policy

This policy explains what data LizzFlix processes, why it is processed, which providers receive it, and how EEA privacy requests are handled.

Effective date · 2026-10-10Open the current versionVersion history

This is an earlier version of this document and no longer applies.

1. Controller and core promise

LizzFlix provides a private-by-default beta workspace for image, video, and voice generation.

Your prompts, uploads, project data, and outputs are private by default, and LizzFlix does not use them to train its own models. The AI providers that run the generations you start process them under their own terms, and some of those terms let the provider use inputs and outputs to improve its models: Runway's terms of use allow it. See AI content for each provider's policy.

2. Data we process

  • Account data such as email, display name, language, and authentication identifiers.
  • Workspace data such as series, episodes, scenes, notes, prompts, dialogue, and job history.
  • Uploaded and generated media such as images, audio, and videos.
  • Billing and plan data such as credits, purchases, grants, and recent usage.
  • Operational data such as logs, error reports, and anti-abuse signals. We do not record your screen.

3. Why we process it

  • To create and secure accounts.
  • To run generation, rendering, uploads, and background jobs.
  • To process billing, prevent fraud, and support disputes.
  • To debug failures, improve reliability, and respond to support or legal requests.

4. Subprocessors and providers

LizzFlix uses third-party infrastructure and model providers to deliver the service. Depending on the action you run, your data may be processed by Cloudflare, Vercel, Stripe, Runway, Fal, ElevenLabs, OpenRouter, or Replicate. Error reports go to Sentry. Google and Apple process sign-in and push notifications when you use them.

Only the fields reasonably necessary for the selected action are sent to a provider. We do not intentionally send your whole workspace to every provider.

5. Retention and deletion

We keep account, workspace, job, billing, and error records for as long as needed to run the beta, comply with law, defend claims, prevent abuse, and support support investigations.

You can request deletion, access, correction, or export using the contact route.

6. EEA rights

  • Access, rectification, erasure, restriction, objection, and portability where applicable.
  • The right to complain to a supervisory authority.
  • Submit requests through the in-app contact page.

7. Security and transfers

We use access controls, environment secrets, provider-scoped credentials, and operational logging to protect the service, but no online system can guarantee absolute security.

Some subprocessors may process data outside your country. Where required, we rely on provider transfer mechanisms and contractual safeguards.