What is kept where

Which of your things stay on your Mac, which are kept on the service, and which only pass through it.

Showreel Studio makes films on your Mac and keeps on the service only what you share, record in the cloud or set for your organisation.

On your Mac

Your projects: storyboards, the steps that drive your app, footage, voice-overs, films, decks, kits of your own, app profiles, and the documents you add to an app's About page. They stay in the project folder unless you share them.
Your sign-in, in ~/.showreel/auth.json, readable only by your user account.
Settings and caches, in ~/.showreel/: the service in use, the kits and audience rules fetched from it, the last licence check, and a count of the commands you have run.
Signed-in app sessions from showreel signin, so films can record your app signed in.

On the service

Your account: your email, organisation, role, and when you were last here. With single sign-on, the identifier your company's sign-in gives you.
Your sign-ins: for each one, when and how you signed in, when it was last used, and the browser or app it came from. Kept 31 days. See Sign-ins and tokens.
Your organisation: its name, email domain (and whether it is verified), settings, invitations and licence key, and its single sign-on settings with the client secret sealed.
The activity log: who changed the organisation, and when. See Activity log.
What you share or record in the cloud: the film's cuts, frames, verify report, subtitles, transcript and storyboard, and its log, comments and review verdicts.
Published links and their views. See How views are counted.
Organisation kits and audience rules that an owner or admin set.
Own voices: the sealed voice key and the two recordings made to create it. See Own voices and consent.
The organisation's Claude API key, if one was added, sealed (encrypted).
Freshness results: which films were checked, which lines changed, and who checked.
Usage: a row for each call that did work, with its kind, when, who, and details such as the film's name. See Your usage.
The service's logs: each request, when, how it went and the internet address it came from, kept 30 days to run the service and find faults.

What passes through

To write, voice or render for you, your Mac sends the service what it needs: the material a storyboard or deck is written from, a document you add to an app's About page, the words to be read, and a kit of your own to render titles and decks. The service uses them for that call and does not keep them. While it waits for an answer written in Claude Code, it holds what it needs to finish the job, for up to two hours. When Claude in Claude Code reads a PDF you add to an app's About page, the PDF is not sent at all: Claude reads it on your Mac.

For a cloud recording, a Google Cloud token and your app's sign-in travel sealed. They are handed to the recorder once when it starts, then deleted, and never stored with the recording's files.

What sealed means

Keys and secrets kept on the service are sealed, meaning encrypted with AES-256-GCM. The keys that seal them are held apart from the data, and can be changed without anything being lost.

Other companies

Google makes voice-overs, Gemini writing and own voices, on your organisation's own Google Cloud project.
Anthropic writes when your organisation has added its Claude API key, on your Anthropic account. In Claude Code, writing happens on each person's own Claude plan.