Privacy Notice · Cooking Drama

Who we are

Cooking Drama is operated by the Cooking Drama team. This notice explains what personal data the studio handles during its private preview, and applies alongside our Terms of Service.

What we collect

Account details: Your name, email address, and whether it is verified. Your password is stored only as a one-way scrypt hash; we never see or store it in plain text.
Sessions: When you log in we create a session that records the time, your IP address, and your browser’s user-agent string, so we can keep you logged in and investigate unfamiliar access.
Organizations: Names and identifiers of organizations you create or join, your role, and the email addresses of people you invite.
Projects and media: What you put into your projects, such as ideas, scripts, characters, images, voices, and video, and what generation returns. Project data is kept in our database and media files in private storage.
Generation records: For each generation: the project, the kind of request, the model, who started it, its status, its result, and when it ran. We use these records to show your history and enforce daily limits.
Earlier provider keys: Provider API keys saved during an earlier version of the preview stay encrypted with AES-GCM and are no longer used. They are never shown back to anyone, including you.
Security records: A log of security-relevant actions (logins, sessions ending, organization and membership changes) with the account and organization involved and the time. These records never contain passwords or key values.
Abuse protection: Short-lived counters keyed by IP address that limit repeated login, sign-up, and email requests. They reset within minutes.
Technical logs: Our hosting provider records basic request logs, such as time, path, and status, to operate and secure the service.

What we don’t do

No advertising, and no third-party analytics or tracking.
We do not sell or rent personal data.
We do not use your data to train AI models. The content of each generation goes to BytePlus, as described under “Who sees it”.

Cookies

We use a single, strictly necessary cookie: your session cookie. It is HTTP-only (scripts cannot read it), sent only over secure connections, and limited to same-site requests. It expires after 7 days without use and is refreshed while you use the studio. Logging out removes it. Because the studio cannot work without it, there is nothing to opt into or out of.

How we use it

to create and secure your account and keep you logged in;
to send account emails you need (verification, password reset, email changes, and invitations you or your collaborators send);
to run organizations and enforce who can access what;
to generate scripts, images, and video when you or your editors ask, and to apply daily generation limits;
to prevent abuse and investigate security problems; and
to diagnose errors and keep the studio working.

We process this data to provide the service you signed up for and for our legitimate interest in keeping it secure. We do not send marketing email.

Your collaborators. Members of an organization you belong to can see your name, email address, and role in it.

Service providers process data for us under their own data-protection terms, and may do so outside your country:

Cloudflare — Hosting, network delivery, private storage (R2) for project media, and request and error logs. Query strings are redacted, and error logs keep only a route label, error type, and stack trace, with no names, emails, URLs, or request contents.
Neon — Our PostgreSQL database, where account and project data is stored.
BytePlus ModelArk — Generating scripts, images, and video clips on our account. It receives the text, prompts, and images each generation needs.
Resend — Delivering account emails: verification, password reset, email change, and invitations.

We may also disclose data if the law requires it, or to protect the safety and rights of our users and the studio.

How long we keep it

Account and organization data: while your account exists.
Sessions: until you log out or after 7 days without use.
Invitations: organization invitations until they are accepted, declined or canceled; project invitations for 14 days.
Projects and their media: until you delete them or your account.
Earlier provider keys: until you delete your account.
Security records: as long as needed to protect accounts and investigate abuse.

Database backups may keep deleted information, still encrypted where it was encrypted before, until those backups expire.

Security

Connections are encrypted with TLS, passwords are hashed, media is kept in private storage and reached only through your session or a link that expires within an hour, sensitive actions are rate-limited, and changing your password logs out your other sessions. No system is perfectly secure; if we learn of a breach affecting your data, we will tell you.

Your choices and rights

You can update your name and email, log out other devices, and delete your account in your settings. Depending on where you live, you may also have the right to access, correct, export, or delete your data, or to object to how we use it. For anything settings can’t do, email privacy@cooking-drama.example and we will respond within 30 days. You can also complain to your local data-protection authority.

Children

The studio is for people aged 18 and over. We do not knowingly collect data from children; if you believe a child has an account, contact us and we will delete it.

Changes

We will update this notice as features such as billing arrive. Material changes will be announced by email or in the studio before they take effect.

Contact

Questions or requests about your data? Write to privacy@cooking-drama.example.