INT.EXT
The Page Ownership Updates Tour Help Terms Login
Join BetaBeta

Beta Draft

Privacy & Cookies

INT.EXT treats screenplay work as unpublished manuscript data. The beta is built around quiet writing, file ownership, and minimal collection.

What This Covers

This notice explains how INT.EXT Online handles beta requests, beta accounts, feedback, browser storage, cookies, and screenplay content during the private beta.

Last updated: 8 July 2026.

What We Collect

For beta requests, INT.EXT collects the details you submit, such as your name, email address, and the screenwriting app you currently use.

If you are invited into the beta, INT.EXT stores account details needed to run the beta, including your email address, password hash, invite status, session records, email preferences, membership or entitlement status, and operational admin notes.

If you send feedback, INT.EXT stores the issue description and related operational metadata. Please describe issues without sending screenplay pages, project files, raw FDX/Fountain, title-page contact details, or private manuscript material.

Screenplay Content

The writing surface keeps screenplay content in the browser unless you choose a server-side operation. PDF rendering sends the project to the PDF worker for that export. Optional Cloud Copies encrypt project titles, project keys, and screenplay snapshots in your browser before upload. INT.EXT stores the encrypted data and operational metadata needed to retrieve it, but does not receive the recovery key.

If you lose the Cloud Copies recovery kit and every device that is still unlocked, the encrypted cloud copies cannot be recovered by you or INT.EXT. A password reset does not decrypt them. Saving an INTX file remains the direct way to keep an owned copy outside INT.EXT.

INT.EXT does not use your screenplay content to generate screenplay prose. Operational logs and admin activity should not contain screenplay text, INTX payload bodies, notes, title-page contact details, raw FDX/Fountain, or uploaded project files.

Browser Storage

INT.EXT uses browser storage, such as IndexedDB, local storage, and similar browser features, for recovery, saved preferences, recent local work, beta notice acknowledgement, and local working data.

Browser recovery is a safety net, not the source of truth. Saving an INTX file or exporting PDF, FDX, or Fountain gives you an owned file outside the browser.

Cookies

INT.EXT uses essential cookies for beta account sessions, security checks, CSRF protection, and email preference links. These cookies are needed for the service you ask to use.

INT.EXT does not currently use advertising cookies or third-party tracking cookies. If optional analytics or marketing cookies are added later, they should not be set until you have been told what they do and given a choice.

How We Use Data

INT.EXT uses beta and account data to manage invites, provide beta access, secure accounts, send requested beta emails, receive feedback, operate the service, troubleshoot issues, and improve the screenwriting product.

INT.EXT does not sell beta request data or screenplay content.

Retention

Beta request, invite, account, feedback, email preference, and operational records are kept only as long as they are useful for running the beta, supporting writers, meeting security needs, or meeting legal obligations.

Screenplay files you download are yours to keep or delete. Browser recovery data can be cleared through your browser storage controls.

Your Choices

You can choose not to join the beta queue, unsubscribe from non-essential beta updates, clear browser storage, or stop using the beta.

You can ask about access, correction, deletion, or privacy questions by emailing beta@intextwriter.com.

INT.EXT

A quiet tool for a loud enough job.

Home Tour Help Login Terms Cookies Contact

Online first. Writer-first.
No generated screenplay prose.

© INT.EXT