Privacy

Overview

STORII keeps very little. Your projects, your keys and your files stay in your browser. STORII's server knows only that you signed in. Video requests and key checks pass through STORII's server on their way to the service, carrying your key for that one call; the server keeps nothing from them and writes nothing about them. Picture, voice and assistant requests go straight from your browser to that service with your key and do not pass through STORII's server. Every request is listed under What leaves your browser, and you start each one yourself.

What we collect

On STORII's server: your email address, a single-use sign-in link record, a session record, and counters that limit how often a link can be requested, kept against a scrambled form of the network address.

Not on the server: your projects, scripts, pictures, voices, notes, estimates, keys and exported copies.

STORII loads nothing from anyone else's address. Its fonts and pictures come from STORII itself. Your browser talks to STORII's own address, and to a provider's address only in the cases listed under What leaves your browser.

How we use it

To let you in and to keep the sign-in page from being abused. Nothing else. We do not sell it and we do not share it.

Making music sends your description to ElevenLabs, with your key, only after you confirm. Steps marked not connected in the guide do not send anything anywhere yet. When one is connected, this page will say what its provider receives before you can use it.

What leaves your browser

Nothing is sent to a provider in the background. A request leaves your browser for a provider only when you press the button named below, using your own key for that provider. The one small addition is the key check: when you save or test a key on the Keys screen, STORII makes one status read of that provider with that key, which makes nothing and is not charged, so the row can say whether the key is accepted.

Video generation (Higgsfield). When you press Submit a round at the Spend gate, STORII sends Higgsfield the prompt for each scene, the model and length you chose, and, for a scene that uses locked library assets with a picture, those pictures as references (each is uploaded to Higgsfield first and sent as a link), with your Higgsfield key as your credential. STORII says how many pictures go with the run as it sends it, and nothing is uploaded before you type GO and submit. When you press Get estimate with your Higgsfield key saved, STORII sends the model, resolution and length of each shot, and no prompt text, to ask Higgsfield for its price. STORII also reads your balance and the status of each take from Higgsfield. When a take lands, your browser fetches the finished clip from the address Higgsfield gives it and keeps it on this device. The charge is on your Higgsfield account.

Pictures (Google Gemini). When you press Generate on a picture, STORII sends Google your prompt and any reference picture you attached, with your Gemini key. The charge is on your Google account.

Radio play voice (ElevenLabs). On Radio play, when you press Confirm and generate, STORII sends ElevenLabs the spoken lines of that scene as text, which voice you chose for each speaker, and the voice model. Your ElevenLabs key goes with the request as your credential. The confirm step shows the number of characters first. The charge is on your ElevenLabs account.

Suggest with STORII (Anthropic). A Suggest with STORII chip, when you press it, sends Anthropic the text you are working on in that field, including a scene you imported from your script, and fixed instructions, with your Anthropic key. The app shows the model and its ceiling before every call, and nothing is saved from the answer until you accept it. The charge is on your Anthropic account.

Match the mood (Anthropic). On Radio play, when you choose Match the mood of the scene and press Confirm and match, STORII sends Anthropic the text of that scene and fixed instructions, with your Anthropic key. It uses the answer to fill in a mood and a short direction, which you can change. The confirm step shows the most it can cost first. The charge is on your Anthropic account.

Saved voice ids. A voice id you save on Radio play is kept on this device only, with the name you gave it. It is not in your project file, and it is sent to ElevenLabs only as the voice for a line when you confirm a radio play.

Ask in Help (Anthropic). When you press Send in Ask, STORII sends Anthropic the question you typed, together with fixed instructions and a fixed set of facts about STORII (taken from the FAQ text), and your Anthropic key as your credential. Nothing is sent while you type. STORII does not save your question or the answer. It keeps one line on your device with the model, the token counts and the estimated cost. The charge is on your Anthropic account.

Not sent, in any case: the rest of your script, recordings and pictures, your project file, the lines in the Status tab, your other keys, and your passphrase.

Like any web request, each of these also carries your network address and the usual details a browser adds, including the address of STORII's site. It does not say which screen you were on. What a provider does with a request is set by your own agreement with that provider, not by this page.

Cloud render (STORII's render service). When you pick a format marked cloud on Deliver, tick the box that names the files, and press Render in the cloud, your browser sends the picture and sound files of the locked cut, with the cut itself (the timeline, which carries the subtitle cues and their speaker names, your notes on clips, the clip names and the project name, and no other script text), straight to STORII's own render store on Microsoft Azure under a short-lived address made for that one render. STORII's server issues that address after your sign-in check and starts the render; it never receives the files itself and they never pass through the service that holds your keys. The render runs on a worker that reads only that render's folder. The finished film is fetched by your browser, and the files are deleted when it has arrived, or after two days at the latest. Nothing is sent in the background and nothing is sent for a device format.

Accounts and sign-in

You sign in with an email link. The cookie that keeps you signed in is HttpOnly (scripts cannot read it), Secure (sent only over a secure connection), SameSite Lax, limited to STORII, and lasts 7 days. Signing in controls access. It does not copy your projects anywhere.

STORII's offline helper never keeps copies of sign-in or account responses.

Retention

Projects live in your browser until you remove them or clear your site data. Exported copies live wherever you saved them. Sign-in records are kept only to run sign-in, and StableState has not yet set how long. This section will state the period once it has.

Security

Keys you add are locked on your device with a key derived from your passphrase (PBKDF2 with SHA-256) and stored encrypted (AES-GCM, 256-bit). The passphrase is not stored. After you unlock once, this browser keeps the unlocked key (not the passphrase, and not readable as text) until you lock, remove your keys or clear site data. STORII's server has no place to store a key. A key leaves your device only as the credential in a request to its own provider, in the cases listed under What leaves your browser. For video requests and key checks it passes through STORII's server for that one call, and is not kept or logged there.

Your choices

Sign out from Settings, on one device or on all. Remove a project inside STORII or clear your browser's site data. Export a copy first if you want to keep it. A way to ask for your sign-in records to be removed is not set up yet in this build.

Contact

Questions about this policy or your data: contact@stablestateit.com.

Last updated 1 November 2026.