# Privacy and your data

> What DemoVexa keeps on your computer, what it sends to Claude and ElevenLabs, where your keys live, and how to move your data folder.

Source: https://demovexa.com/docs/settings/privacy-and-data

DemoVexa runs on your own computer. Your projects, voiceovers and videos stay there, and only what's needed to write and voice a video is sent to the AI services you connect. This page explains what goes where.

## What stays on your computer

Everything DemoVexa makes is stored on your computer:

- Your projects: briefs, scripts, scene plans, posts and covers.
- Voiceovers, uploaded photos and clips, and rendered videos.
- The database, your preferences and your backups.

Your app's code folder stays where it is. DemoVexa only reads it; nothing in the folder is changed. Rendering happens on your computer too.

## What's sent, and to whom

| Sent to | What | Why |
|---|---|---|
| Claude (Anthropic) | The relevant parts of your app's code and docs, and the project it's working on, such as your brief and script | To plan, write and build your videos |
| ElevenLabs | The script text | To make the voiceover |
| Your product's website | A normal visit to the public site | Only when you use **Import → From the website** in a workspace's Brand tab, to fetch your logo, colours and fonts |

For an Event Recap, Claude also looks at your photos and clips to build the storyboard.

Claude is reached through your own Claude login or Anthropic API key, and ElevenLabs through your own API key.

> [!NOTE]
> With **My Claude login**, Claude can read your app's code while it writes the brief. With an API key it works from your how-to guides. Either way, the build itself reads your code to recreate the screens.

## Your DemoVexa account

Your online account at [app.demovexa.com](https://app.demovexa.com) stores your account details, your plan and your usage: a record of the videos and renders you make, so it can count them against your allowance. Your code, scripts, voiceovers and videos aren't stored there.

## Where your keys are kept

Your Claude and ElevenLabs keys are stored in your operating system's password store, under the name "DemoVexa":

| System | Password store |
|---|---|
| macOS | Keychain |
| Windows | Credential Manager |
| Linux | The keyring (Secret Service) |

If the computer has no password store, DemoVexa keeps the keys in a private file in the data folder that only your user account can read.

Keys are only sent to Anthropic and ElevenLabs, and the app never shows them in full again after you save them. The studio's keys are shared by every workspace; a workspace with its own keys keeps them separately and uses them first.

Your preferences, such as how Claude runs, the model and the default voice, are saved in a settings file in the data folder.

## The data folder

The data folder holds everything DemoVexa makes. It's the `data` folder inside DemoVexa's app-data folder (see [Where your data lives](/docs/getting-started/install#where-your-data-lives)). It contains:

- The database (your workspaces, projects, scripts and so on)
- Uploads
- Voiceovers
- Renders
- Covers
- Stills
- Logs
- Your preferences
- Backups

The code and audio for each animated video are written into the `engine` folder next to the data folder, in DemoVexa's app-data folder (see [Where your data lives](/docs/getting-started/install#where-your-data-lives)).

To open the folder, go to **Settings → Database** and click **Show in folder**.

### Move the data folder

The desktop app always keeps its data in its app-data folder. To save space on your main drive, export finished projects ([Export project](/docs/more/export-import)) and remove them from DemoVexa, or move rendered videos elsewhere after downloading them.

## Who can open DemoVexa

DemoVexa only listens on your own computer, so nobody else on your network can open it. Each person who uses DemoVexa installs the app and signs in with their own account.

## Related

- [Backups](/docs/settings/backups)
- [Settings](/docs/settings/settings)
- [Your account and computers](/docs/account/sign-in)