Shooting Draft

Terms of Use, Privacy Policy & Community Guidelines

Last updated 2026-09-22. Questions: contact support@shootingdraft.com.

Terms of Use

1. The agreement

These terms are an agreement between you and Shooting Draft LLC, a Florida limited liability company at 400 N Tampa St, Ste 1550 #523488, Tampa, FL 33602, USA (“Shooting Draft”). By creating an account or using the service you accept them. You must be at least 13 years old (and old enough to form a binding contract where you live, or have a parent or guardian's consent). If you use the service on behalf of a company, you accept for that company.

2. Your work is yours

You keep every right to the scripts, stories, images, audio and other content you create or upload. Shooting Draft claims no ownership of your work and does not train AI models on your private projects, except as described in the “Training and your content” clause below (which happens only at your explicit, per-run request, and only for you). You grant the service only the narrow license it needs to function: to store, back up, process and transmit your content solely to operate the features you use, at your direction. That license ends for content you delete; deleting a project also deletes the media files it generated, except files another of your projects still uses. Occasional stray files (for example, superseded renders) may persist until your account is deleted.

2b. Training and your content

Default: never. Shooting Draft does not use your scripts, images, audio or any other content to train, fine-tune or improve any AI model - not ours, not a third party's - and does not permit its model providers to do so with content routed through the platform's keys.

The one exception is a feature you invoke, for a model that is yours. Where the service offers an explicit training feature (today: the character lens, which fine-tunes a small image adapter on the reference images of one character, and the look lens, which fine-tunes a small style adapter on the frames a project has kept), training runs only when you request that specific run and give consent in the same action. The training set is exactly the content the feature names and shows you - nothing else from your account. The resulting trained artifact (for example, a lens file) is your content under Section 2: it is stored with your media, it is used only to fulfil your own generations, we do not use it for anything else, and deleting it is a real deletion. Training is executed by third-party model providers (today fal.ai, or Oxen.ai for the character lens), under the processing license in Section 2, solely to produce your artifact and return it. When you train on Oxen with your own Oxen account, the reference set and the finished weights are written into a repository in that account, under Oxen's terms, and they are yours to keep or delete there; on the Studio lane the same files pass through the platform's Oxen account only long enough to train and return your lens.

Trained artifacts inherit the base model's license where one applies; if you export and redistribute an artifact, complying with that license is your responsibility. Nothing in this clause changes the default above: no request, no training.

3. The service and AI features

Shooting Draft provides writing and production tools, including AI generation routed to third-party model providers. AI features are labeled (for example ✨, 🎬, 🎞, 🔊); when you use one you are interacting with AI, not a human. AI output can be wrong, derivative, or unsuitable: do not rely on factual assertions in AI output without independently verifying them, and review anything before you use it. AI outputs are provided as-is, with no warranty that they are original or non-infringing; clear rights before commercial release. Model providers and specific models can change or become unavailable; where a listed model is discontinued, a comparable alternative may be offered, and features may be modified as the provider landscape changes.

4. Credits, subscriptions and billing

Paid generation is metered in credits. Credits are consumed by use, are good for 12 months from the date they are granted (each grant carries its own 12-month clock, the soonest-expiring credits are always spent first, and any expiry is shown in your Account ledger), are redeemable only within Shooting Draft, and, except where required by law, are not redeemable for cash. If a generation fails, its credits are refunded automatically. Payments are processed by Stripe; card details never touch Shooting Draft's servers. Subscription plans renew each billing period and grant that period's allowance on renewal; you can cancel any time and keep access (and your credits) through the end of the paid period. Free trials: where a trial is offered, it lasts the number of days stated at checkout, a payment method is taken at sign-up but not charged during the trial, and the trial converts automatically into a paid subscription when it ends unless you cancel first. Cancel any time before the trial ends and you are not charged. You may also end a trial early, which starts the paid subscription that day and sets your billing date to that day. The trial allowance is for the trial: any part of it you have not used expires when the trial ends. If the trial converts to a paid subscription, whatever is left of the allowance stays in your account on the ordinary 12-month terms, alongside that period's own allowance. Credit packs are one-time purchases. Prices may change with notice; a price change never affects credits you already own. If the service is ever discontinued entirely, you will get reasonable advance notice to use your remaining credits.

5. Your responsibilities

Don't break the law, don't upload content you have no right to use, don't abuse the service (scraping, flooding, probing, or circumventing limits or model guardrails), and don't use the service, including AI generation, to produce content that violates the Community Guidelines below or the acceptable-use policies of the model providers the service routes to. Likeness and voice: only upload or generate from a real person's image or voice with that person's consent (or your own); generating a real person's likeness or voice without it is prohibited. Accounts that violate these terms may be limited, suspended, or removed.

6. The service itself is protected

Your work is yours (Section 2); the service is Shooting Draft's. The software, its design, interfaces, features, workflows, documentation, branding, and everything else that makes up the service (other than your content and third-party model output) are proprietary and protected by copyright, trademark, and other intellectual-property laws. Except for the normal use these terms allow, you may not copy, modify, distribute, sell, lease, or create derivative works of the service; reverse engineer, decompile, or extract source code from it (except where the law grants that right despite this term); systematically scrape, harvest, or bulk-extract its content, structure, prompts, or data; or use the service, its output about itself, or access to it to build, train, or improve a competing product. No rights are granted except those expressly stated here.

7. Your own API keys

You may connect your own provider API keys for the writing assistant (for example Anthropic, OpenAI, or xAI). Pictures, clips and audio can run on Studio credits, on your own local ComfyUI, on an app you connect under Section 7b, or - for training a character lens - on your own Oxen.ai account.

Keys you paste are stored only in your browser, pass through the server solely to make the request you asked for, and are never written to server storage. That includes the Oxen.ai key used to train a lens. Two consequences of that key are worth stating plainly, because they are different in kind from a writing key: while it is in use it can act on your Oxen account, and the repository, dataset and finished weights a training run creates are written into your own Oxen namespace, where they are yours to keep or delete under Oxen's terms (Section 2b). Usage under any key you bring is billed to you by that provider under that provider's terms, never as Studio credits.

A browser is not a vault. A key kept in your browser is readable by anything that can run code on that page or on that device, and it is not covered by the encryption and access controls that protect the rest of your account. Use a key scoped to what you need, remove it when you are finished, and do not paste a key you would not be willing to rotate.

7b. Connected apps

You can connect apps you already use (today Higgsfield, Runway, OpenArt, Kling, Pika, Ideogram, Krea, Magnific, and any app that publishes an MCP address, such as fal, Comfy Cloud, Leonardo or ElevenLabs) so that The Desk and the producer can ask them to make pictures and clips on your instruction and land the results on your shots. Connecting is a sign-in in your browser at that app (or a token or API key you paste). The connection token is stored on your account on the server (it is never shown back to you in full) so the connection keeps working between sessions; disconnecting in Account deletes it, and it is used for nothing except calling that app for you. When a connected app runs, the prompt you approved and any reference pictures you chose are sent to that app, and that app bills your own account there, under its own terms - never Studio credits. What it returns is copied into your project's media with a record of which app made it.

8. Connected agents and API keys you mint

Shooting Draft can mint API keys so your own AI agents and tools (for example over MCP) can read and write your projects. The same is true of an AI client you authorise through the sign-in flow (for example a claude.ai or ChatGPT connector): it acts as your account for as long as its authorisation lasts, and Account → Connected agents lists every live one and revokes it in one click. Anything done with your key or through an authorised agent counts as done by you: guard keys like passwords, set an expiry when you mint them if you want one, and revoke them the moment one may be exposed.

8b. Sharing a project, and what an exported file carries

You can invite other people into a project as collaborators or reviewers. Anyone you invite sees that project's script, media and records and, depending on the role you give them, can edit it live; you can remove them at any time, and removing them ends their access. A reviewer link is a link: whoever holds it can see what it opens, so share it as carefully as the work itself.

Every picture, clip and audio file the service generates carries its production record inside the file - the prompt that ran, the model, the seed, the references and lenses used, the cost, and the account label that ran it - so a file stays explainable after it leaves the service. The same record, and a line-by-line record of which words were typed by you and which were written by an assistant, is in the project exports. If you would rather a file travel without its record, strip the metadata before you send it.

9. Publishing is optional and public

Nothing you make is public unless you explicitly publish it. Work published to the Community (where available) is visible to anyone and, if you allow it, may be forked (copied) by other users under these terms. You can unpublish at any time; forks made while it was public remain with their forkers. Likewise, if you export a podcast RSS feed or share a media link, anyone who holds that URL can access that content: you are the publisher of what you choose to share.

10. Ending the relationship

You can stop using the service at any time and can export your projects first (full backup files belong to you). The service may suspend or close accounts that violate these terms. Sections that by their nature survive (your ownership of your work, limitations of liability, dispute terms) survive account closure.

11. Disclaimers and limitation of liability

The service is provided as-is and as-available, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. To the maximum extent permitted by law, Shooting Draft is not liable for indirect, incidental, special, consequential or punitive damages, or lost profits, revenues, or data; and total liability for any claim related to the service is limited to the amount you paid for the service in the twelve months before the claim. Some jurisdictions do not allow certain limits; where a limit is not allowed, it does not apply to you.

12. Indemnity

If a third party brings a claim arising from content you uploaded or published in violation of these terms, or from your unlawful use of the service, you agree to cover the reasonable costs and damages of that claim.

13. Governing law and disputes

These terms are governed by the laws of the State of Florida, USA, without regard to conflict-of-law rules, and disputes will be resolved in the state or federal courts located in Hillsborough County, Florida, unless the law where you live requires otherwise. Before filing anything, contact support@shootingdraft.com: most issues can be fixed directly.

14. Changes

These terms may be updated; material changes will be reflected on this page with a new date. Continued use after a change is acceptance. If any part of these terms is found unenforceable, the rest stands.

Privacy Policy

Who is responsible for your data. Shooting Draft LLC, 400 N Tampa St, Ste 1550 #523488, Tampa, FL 33602, USA. Reach the company about anything in this policy at support@shootingdraft.com.

The short version. Shooting Draft stores what it needs to run and nothing more, sells nothing, shows no ads, runs no analytics or tracking, and never trains AI models on your private work. On the desktop app your projects live on your own device.

What is collected

Your account (email and a hashed password, or your sign-in provider identity), your projects and the media you generate or upload, purchase and credit-ledger records (Stripe processes card details; they never touch Shooting Draft's servers), and the minimal operational logs needed to run and debug the service. Also collected, only when you use the feature: an email address you give the website to receive the desktop download link (and whether that link was opened), or leave on the app's front page to ask for access, together with your answer to “How did you hear about Shooting Draft?” if you choose to give one; voice samples you upload to make a custom read voice; the connection tokens for apps you connect (Section 7b); and the feedback and crash reports you choose to send from the app, which include the message you wrote, the screen you were on and the error text. Signing in sets one HttpOnly session cookie so you stay signed in. If you arrive through a referral link, the website keeps that referral code in one first-party cookie for 30 days so a sign-up can be credited to the person who referred you; it is never read by anyone else. There are no advertising or cross-site tracking cookies and no third-party analytics of any kind.

Where your data lives

On the desktop app, your projects and media are stored on your own device and stay there unless you use a cloud feature. On the hosted service, they are stored on the service's infrastructure (including object storage where enabled) in order to serve them back to you.

How your data is used

Only to operate the service. When you run an AI feature, the relevant prompt and content are sent to the model provider you selected (for example Anthropic for text; fal.ai for image, video and audio; Oxen.ai for character-lens training and, where the service is configured to use it, image and video generation; Higgsfield, where the service is configured to use it, for image and video generation; Runway for a live on-camera conversation with a character, which carries that character's picture and description and, while the call is open, the sound of your voice, streamed so they can answer, and written down as a transcript you keep) to fulfill that specific request, governed by that provider's terms. Your private projects are not read for any other purpose, are not sold, are not shared for advertising, and are not used to train models.

What leaves the service

Five categories only: the AI provider calls above; the apps you have connected yourself (Section 7b), which receive only the prompt and references for a run you asked for; Stripe, for payment processing; your chosen sign-in provider (for example Google or GitHub), when you sign in with it; and the infrastructure that hosts the service. Beyond that, data is disclosed only if the law genuinely requires it. Content you deliberately publish or share (Community work, an exported podcast RSS feed, a shared media link) is available to whoever you shared it with: media links use long unguessable names, and anyone holding the full URL can access that file.

Your own API keys

Keys you paste - a writing provider's key, or the Oxen.ai key used to train a lens - are stored only in your browser and are never written to server storage; they pass through the server solely to make the request you asked for. A browser is not a vault: anything able to run code on that device can read them, so use a narrowly scoped key and remove it when you are done.

A connected app is different, and deliberately so. When you connect an app under Section 7b by signing in to it, the token that sign-in returns is kept on your account on the server - otherwise the connection would not survive closing the tab. It is never shown back to you in full, it is used for nothing but calling that app on your instruction, and disconnecting in Account deletes it.

Retention, deletion and portability

Deleting a project removes it from the active store. You can export complete backups of your projects at any time (the backup file format is yours to keep and reimport). To delete your account, contact support@shootingdraft.com: your projects and personal data are removed within 30 days of the request, except records legally required to be kept for payments and accounting.

Security

Passwords are stored hashed, sessions use HttpOnly cookies, sign-up confirms your address before the account is usable, media URLs on the hosted service are capability-named (long and unguessable), and API keys you mint can carry an expiry. Two-step sign-in (an authenticator app) is available under Account → Account security, and turning it on or off is yours to decide. Tokens for connected apps are held on your account and never displayed in full; keys you paste yourself stay in your browser, which is the weaker place of the two - see Your own API keys above.

No online service can promise perfect security; if a breach affecting your data is discovered, you will be notified as required by applicable law, and the aim is promptly regardless.

Your rights

Wherever you live, you can ask what data is held about you, get a copy (the in-app backup export gives you your creative work; contact support@shootingdraft.com for account and billing records), correct it, or have it deleted. Residents of the EU/EEA, UK, California and similar jurisdictions have these as statutory rights (access, portability, correction, erasure, and no discrimination for exercising them); the service honors them for everyone. Contact support@shootingdraft.com to exercise any of them.

Children

The service is not directed to children under 13, and accounts for children under 13 are not knowingly kept. If you believe a child under 13 has an account, contact support@shootingdraft.com and it will be removed.

Changes

Material changes to this policy will be reflected on this page with a new date.

Community Guidelines (Acceptable Use)

The Community exists for creative work: scripts, worlds, boards, films. Published content must not include: content that sexualizes minors in any form; credible threats, harassment, or incitement of violence against real people or groups; other people's private information (doxxing); content you don't have rights to share; deceptive impersonation of a real person; malware or attempts to exploit viewers or the service. Fictional violence, horror, and mature themes are part of storytelling and are welcome within these limits.

Reporting and enforcement. Every published work carries a Report control. Reports are reviewed by a human; content that breaks these rules is removed, and removed work cannot be republished. Repeat or egregious violations end the account. Rate limits apply to publishing, forking, and reporting to keep the gallery honest.

DMCA / Copyright

If you believe published content infringes your copyright, send a notice containing: (1) identification of the copyrighted work, (2) the URL or title of the infringing material, (3) your contact information, (4) a good-faith statement that the use is unauthorized, (5) a statement under penalty of perjury that the notice is accurate and you are authorized to act, and (6) your physical or electronic signature. Send it to support@shootingdraft.com. Infringing content will be removed expeditiously, and repeat infringers' accounts terminated. Counter-notices follow the same address.

Shooting Draft LLC · 400 N Tampa St, Ste 1550 #523488, Tampa, FL 33602, USA · support@shootingdraft.com
Shooting Draft · from first draft to final frame