# Security and data

> Where a Starlings workspace keeps its data, who can see it, and what Starlings never keeps.

Starlings keeps your team’s work in your own workspace, apart from every other team’s. Here is where it lives, who can see it, and what Starlings never keeps.

### Your data stays yours

Starlings keeps your workspace’s records, documents and transcripts in its own storage, and you can take them with you.

- **Where**: [Cloudflare](https://www.cloudflare.com/). Docs and records too
- **Who else**: Nobody else holds a copy. Starlings doesn’t store audio or video
- **Backed up**: Starlings copies every room and conversation to an EU bucket each day and keeps each copy thirty days. Each one restores on its own
- **Separate**: Each workspace’s data is kept apart from every other workspace’s
- **Export**: Download transcripts and notes as plain Markdown files at any time

### Secrets

Client credentials, sealed on your device. The server cannot read them.

- **Unlock**: Touch ID, Face ID, or a passphrase. Locks after fifteen idle minutes
- **Share**: Per vault, with an audit trail
- **Where**: Mac and iPhone. On the web, a vault says to open it there: a browser never holds the keys
- **Agents**: An agent asks in a thread for one item. A member approves on Mac or iPhone, for fifteen minutes unless they choose longer
- **Works on**: Mac, iPhone and iPad

### Security

Every entry point checks who you are. Starlings trusts no request because of where it came from.

- **Hosts**: Only a Google account from your company can host, proven by Google itself. A room belongs to its owner by configuration, never by a submitted name or link
- **Guests**: Ask to join, and hold a secret until the host admits you. No media flows before that, and the host has to be live within the last thirty seconds
- **Keys**: A room key lasts two hours and opens one room. Sessions last eight hours. Logs never hold keys, transcripts, emails, or lobby secrets
- **Devices**: Settings lists every Mac and phone signed in to your account, by name. Sign one out from anywhere and Starlings refuses its next request. A session stays on its device and never goes into a backup
- **Captions**: Starlings shows captions only from the verified host. Reactions are an enum, so a guest cannot put text on your screen
- **Agents**: Never hold a session. They come through one signed endpoint, rate limited, and Starlings logs every call
- **Browser**: Strict content policy, no framing, no referrer. Shared files render in a sandbox with no scripts

More: [The full privacy and security contract](https://starlingshq.com/privacy)

### Privacy

Starlings keeps the text of a call and the minimum about each person.

- **Speech**: The host's Mac or iPhone transcribes it in memory and discards the audio as it goes. Only finished text leaves
- **Notes**: A model writes them from the transcript text. The model providers do not train on it
- **Who sees notes**: People who were in the call, inside Starlings. Starlings never emails a transcript
- **Where**: Cloudflare. Direct messages are stored only in the EU
- **Logs**: Never hold a token, a transcript, a message, an email address, or a lobby secret

More: [The full privacy contract](https://starlingshq.com/privacy)

### The building blocks

Starlings is the app. Records, documents and the vault are separate services, each with its own store and key.

- **One sign-in**: You sign in to Starlings. Starlings confirms who you are to each service. The service gives your device its own key. Starlings never keeps it
- **Direct**: After that, your Mac or phone talks to the service itself. Each service enforces its own rules, once
- **Self-describing**: Each service says what it holds and what you may do. Starlings shows only that
- **Separate keys**: A key for Docs does not open Keep. Revoke one and the others still work
- **Extensible**: A new service needs a store, a key, a package, and an entry point in Starlings. The tabs do not change

### Technology

Media on LiveKit, transcription on the host's device, everything else on one Cloudflare Worker.

- **Rooms**: A Durable Object holds each room: who is waiting, who is in, whose hand is up. LiveKit only ever sees a signed two-hour key
- **Agent activity**: Admin shows handoffs, runtime acceptance or refusal, finalized replies observed by Starlings, and watchdog resets. Runtime model costs are not included
- **Transcript pipeline**: The host device posts finished text to the Worker. A queue turns it into the transcript, the summary, and a record on the project, with retries and a dead letter an admin can replay. The Worker counts failures and daily model spend and sends an alert by email
- **Services**: Records, Docs and Keep are separate services. Starlings reaches them over [service bindings](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/), never the public internet
- **Contract**: One package of [Zod](https://zod.dev/) schemas defines every wire shape. The Swift clients read the same fixtures, so the three clients cannot drift
- **Ships**: Every push to main deploys the web app and the Worker through [Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/). Mac and iOS releases are [notarized](https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution) from a tag, and the Mac app checks for its own update
- **Sign-in**: [Google](https://developers.google.com/identity), your company’s accounts only. The Worker encrypts refresh tokens; the device keeps a session and its own device id

## More

- [Privacy](https://starlingshq.com/privacy): What Starlings collects, where it is stored, who processes it and how long it is kept. Starlings does not record the audio, video or screen share of a call.

---

Canonical page: https://starlingshq.com/security
