Privacy Policy

Scope

This policy applies to dramafork.com and DramaFork's public pages, blog, workspace, project management, AI generation, export, and playable previews. Public pages can be read without signing in; saving cloud projects and continuing production generally requires an account.

Third-party websites and services follow their own policies. This document covers data processing that DramaFork can control or configure.

Account and identity data

Google sign-in provides an account identifier, email address, display name, and avatar. Session data and necessary cookies verify access, protect projects, and reduce repeated sign-ins. Authentication, database, and file storage use Supabase.

Creator partnership applications

When you apply for the creator partnership program, we store the name or creator name, contact email, selected creative directions, representative-work link, optional creative plan, page language, policy consent time and version, and your account identifier if you are signed in. This private information is used to review the proposal, prevent duplicate submissions, contact suitable applicants, and manage any later collaboration; it is not shown on public pages.

Project content and assets

Ideas, scripts, character designs, storyboards, interaction nodes, images, videos, audio, uploads, and generated results are processed to save, preview, continue, and export your project. Guest ideas are temporarily stored in the current browser session; signed-in projects are associated with the account.

Do not include unnecessary sensitive data. Confirm that you have permission before uploading portraits, trademarks, media, or other people's work.

AI generation requests

When you generate or regenerate content, the prompt, relevant project context, references, and task settings are sent to the configured AI provider. The deployed provider depends on the feature and environment. Providers may retain records for safety, support, billing, or service quality under their own policies.

Sharing, export, and deletion

Downloaded or shared packages can be copied by recipients. Remote-URL packages may expose referenced assets to anyone who receives the link. Deleting a project removes the application record and may disable remote packages, but cannot recall downloaded copies or immediately erase third-party logs, caches, or backups.

Cookies and optional analytics

Necessary cookies and browser storage support sign-in, session security, temporary guest work, and remembering your privacy choice. Optional GA4 analytics stay disabled and the Google tag is not loaded until you select Allow optional analytics. Declining does not affect sign-in or creation. DNT and GPC signals are respected. Custom events exclude email, profile details, project names, creative text, and project IDs.

Your choice is stored in this browser for up to 180 days. You can reopen Cookie settings at any time. Disabling analytics stops future events and clears accessible GA cookies, but does not retract data already sent.

Required logs and security

Authentication cookies, quota checks, generation status, export status, and error logs are required to operate and protect the service. Hosting, authentication, storage, and AI providers may process request logs for security, abuse prevention, reliability, and debugging.

Your choices and contact

You can decide whether to sign in, enable analytics, upload references, export a work, or delete a project. Google, Supabase, and AI providers may offer additional data controls. This policy may change as the product evolves; the update date identifies the latest revision.