The platform uses account information such as email, display name, username, role, profile details, and contribution history to operate identity, attribution, editorial review, moderation, and notifications.

Public contribution activity may include accepted suggestions, comments, reactions, profile names, AI labels, reputation signals, and version credits.

Suggestions, comments, reports, saved scenes, reactions, and editorial decisions are stored so the screenplay can maintain a durable creative record.

Some activity is public by design. Private or editor-only surfaces, such as moderation notes and certain editorial notes, are limited to authorized accounts.

The production stack is designed for Vercel hosting and Supabase auth/database services. Optional services such as error monitoring or transactional email may be enabled when configured in the environment.

Secrets and service-role keys are server-only and should never be exposed to browser code.

Authentication uses secure session mechanisms from the configured auth provider. These are needed to keep users signed in, enforce permissions, and protect admin workflows.

The current product does not require behavioral advertising cookies for the core screenplay and contribution experience.

Reports may include the reported item, reporter identity, reason, notes, status, reviewer identity, and review timestamps. This information is used for safety, audit history, and editorial accountability.

Administrators may preserve records when needed to investigate abuse, rights concerns, spam, impersonation, or repeated policy violations.

You can update your public profile from your account dashboard. Some contribution records may remain visible or archived when they are part of public version history, accepted canon, moderation logs, or editorial audit trails.

For production launch, add a support contact and formal data request process before inviting the public at scale.