How Screencake protects your scripts

Local Mode stores scripts on your device without an account or connection. If you never sign in, we never hold a copy of your work.

With a paid plan, sign-in automatically uploads local scripts to your private workspace. Screencake keeps the local copy and syncs later changes. In the desktop and mobile apps, downloaded personal scripts remain available after sign-out. In a browser, sign-out removes them from the browser. Team, shared, and encrypted scripts require account access.

When you sign in and sync, scripts are transmitted over TLS and stored on our hosting infrastructure, with backups in Cloudflare R2. Sync is offline-first and resumes from your local copy; an interrupted sync never destroys local work. Storyboard images are stored in Cloudflare R2 (a private bucket) and are deleted with the script. They are served from media.screencake.com through Cloudflare's cache on short-lived signed links (15 minutes) that Screencake issues only to people allowed to see the script; a removed image can remain in that edge cache for up to a day.

Paid plans include end-to-end encryption for scripts. Your device encrypts the script before sync. Collaborators receive the script key from an authorized device. The key exchange is hybrid post-quantum: ML-KEM-768 with P-256. We do not have the readable key or access to the encrypted pages, comments, tags, or schedule.

We can still see the title, logline, title-page fields, production members and roles, edit times, script size, version labels and dates, and @mentions.

Your password can unlock your encryption keys on a new device. After a password reset, use your recovery key. We cannot recover your encryption keys for you. Keep your recovery key in a safe place.

Removing a collaborator stops future updates. It does not remove a copy or key that their device already received.

Cloud AI is off by default. When you turn it on and ask, the excerpt you chose goes from our server to the provider over TLS, and nothing of the request or its result is kept beyond a day. The browser itself never connects to an AI vendor. Encrypted scripts and Local Mode never use it, and a workspace can forbid it for its scripts.

Choosing Ask the docs sends your question and public documentation from our server to Fireworks over TLS. We don't attach your account identity or script content. The browser never connects to Fireworks, and search alone makes no AI request. Answers are limited to the public manual and link to its sections; they can still be wrong.

Collaboration is scoped to workspaces and productions. Every collaborator holds one of six roles: owner, admin, writer, editor, producer, or reader. The server enforces every permission check. Removing a collaborator revokes their access immediately.

A Studio workspace can additionally require a passcode on every guest link, forbid downloads through them, cap how long a link lives, require that its scripts be encrypted before they are shared or exported, and cap how long a sign-in lasts — and can require single sign-on through its identity provider, on a verified domain.

Accounts authenticate with an email address and password over encrypted connections. Passwords are stored bcrypt-hashed, and resetting your password signs out every existing session. We will never ask for your password by email.

You can add a second factor to your account: an authenticator app (six-digit codes) or a passkey, which uses your device's fingerprint, face or PIN. A passkey can also replace your password entirely at sign-in. Turning either on signs out every other session.

When you add your first second factor, Screencake creates ten single-use recovery codes if you do not already have unused codes. Save them when shown. These codes work across the second factors on your account. If you lose all your second factors, use a recovery code to sign in. Email cannot reset two-factor authentication.

Workspace owners can require two-factor authentication for everyone in their workspace. Collaborators who don't yet have it are asked to enroll before they can carry on working.

macOS builds are notarized by Apple, and the Mac app verifies every auto-update's minisign signature before installing it; an update that doesn't match the key doesn't run. The Windows app is signed, delivered and updated by the Microsoft Store. The Linux app verifies its updates the same way.

You can export any script to PDF, Final Draft or Fountain at any time, and you can delete a script or your account. Deleted scripts are removed from active systems and age out of routine backups. A Studio workspace's owner can also request an archive of every production in it — one zip, its download link valid for seven days.

If you believe you have found a security issue, email support@screencake.com with steps to reproduce. Please give us a reasonable window to respond before disclosing publicly. We do not pursue legal action against good-faith research that avoids privacy violations, data destruction and service disruption. The same contact is published in machine-readable form at /.well-known/security.txt (RFC 9116).

Screencake does not hold any third-party security certification or audit. If that changes, this page changes with it.