Your work is yours.
Never trained on
The writer owns everything — auditable, undoable, deletable, exportable. This page is the proof. It tells you where your scripts live, what AI sees, what is never sent off our servers, and how to take it all back the moment you choose to leave.
Every row is a category of data your account holds.
| What | Where | Protection |
|---|---|---|
| Your script: scenes, dialogue, action, beats, character notes | Our database, owned by your authenticated account. | Encrypted at rest and in transit. Only you can access it. |
| Vault projects (NDA / sensitive work) | Same database, encrypted with a key we don't hold. | End-to-end encrypted. We cannot read this content. |
| Continuity Reader request | Sent to Anthropic's API for one pass, then discarded. | TLS in transit. Not stored after the call. |
| Research Panel question | Your typed question only — never the script — sent to Anthropic's API and discarded. | TLS in transit. Not stored. |
| Voice Surfacer statistics | Computed in your browser. Never leaves your device. | Local only. |
| AI training corpora | Nothing. Your work is never used as training data — by Arqo or any provider. | N/A. |
Full mechanics — per-AI-surface inventory, WGA alignment — live on /data-policy.
Arqo will never use your scripts, scenes, or dialogue as training data for any AI model — including models operated by Arqo, JMNPR Labs, or any third-party provider. This is a guarantee, not a setting you have to find.
When AI runs on your work (Continuity Reader, Research Panel), the request hits an API, returns a result, and the payload is discarded. There is no logging-pipeline, no training-data side-channel, no “we'll keep a copy for quality assurance.” The data has nowhere to go except back to you.
We document every AI call in your account's transparency log: which surface, when, what was sent (summarized), what came back. The log is exportable.
Signed by the Arqo founders and acting CEO on April 26, 2026. Quoted verbatim.
- We will never write the writer’s work for them.
- We will never sell the writer’s work to anyone.
- We will never tell a studio our tool replaces a writer.
- We will say what we believe in public and live with the cost.
These are constraints on our behaviour, in public. The longer argument lives at /manifesto.
One click. Every script you own, packaged as Final Draft (.fdx), Fountain, and a production-ready PDF. You don't need to ask, and you don't need to leave Arqo to keep your work.
Nothing about the export is gated, throttled by tier, or contingent on cancelling anything.
When you delete a script, we email you a one-page receipt: the title, the script ID, the exact timestamp of deletion, and a hash of the content we purged. The hash lets you — or anyone you ask to verify — confirm that what was deleted matched what you intended.
The certificate states, plainly:
“This script and all derived data were purged.”
We keep an internal audit record so that if you ever contact us about a script you remember deleting, we can confirm the date and the hash. We can't recover the content — that is the point — but we can prove the deletion happened.
Account deletion works the same way at a larger scale: a 30-day grace period, then a full purge across our systems. Documented at /data-policy.
- /values — the short reference card for what Arqo is and is not.
- /manifesto — the long argument: amplifier-not-replacement framing, the four vows, named opposition to studio writer-replacement AI.
- /data-policy — the operational data commitments, AI surface inventory.