OPENData and privacy
Where your footage lives, what crosses the process boundary, and what is never collected.
OpenScene's privacy properties are structural rather than a setting you have to find and switch on.
What is never collected
- No account. There is nothing to sign up for
- No telemetry. No analytics, crash reporting, or usage tracking
- No background network calls. The app talks to a provider only when you ask it to, using a provider you connected
Where your data lives
Projects are folders you choose. Assets, chat history, and generated results are written inside them. App-managed projects and window recordings live under Electron user data, and recordings can be redirected with VIDEO_TOOL_RECORDINGS_DIR.
The process boundary
The renderer talks to the main process through one narrow typed window.videoTool bridge. Raw ipcRenderer, filesystem paths, FFmpeg arguments, API keys, and OAuth tokens stay outside it. A picked reference image, for example, crosses as bytes and never as a path.
| Stays in the main process | Reaches the interface |
|---|---|
| Filesystem paths | Asset identifiers and metadata |
| FFmpeg arguments | Export progress and result state |
| API keys and OAuth tokens | Whether a provider is connected |
Capture is scoped
Window capture grants access to the single source you select, recorded to a local WebM file. Full-screen capture and microphone or system-audio mixing are not in the recorder yet.
Removal
Removing a project unregisters it from the list — a folder you chose is never deleted recursively. Conversations can be deleted individually. What you delete is gone locally, because there was never a server copy.
What providers receive
A provider only ever receives what you ask the agent or a studio to send it: prompt text, a script, sampled frames when you ask about footage, or a reference image you picked. Your project folder is not indexed or uploaded.