Security and data.
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. 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
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
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, never the public internet
- Contract
- One package of Zod 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. Mac and iOS releases are notarized from a tag, and the Mac app checks for its own update
- Sign-in
- Google, your company’s accounts only. The Worker encrypts refresh tokens; the device keeps a session and its own device id
How Starlings is built.
Every service Starlings runs on, and what data moves between them. Video goes directly between participants. The transcript goes to a Worker that never sees video. The full diagram, down to the bucket and the queue, is on feature status.
In the meeting
The devices a person is looking at.
- The hosting device
- One owner device opens the room, admits guests, and writes the transcript on its own hardware.
- The browser
- Guests join at
/room/<slug>with no account; a signed-in member gets the five surfaces too. It never hosts.
Media
Audio and video, end to end, never recorded.
- LiveKit CloudLiveKit
- Carries audio, video and screen between the people in the room. Nothing is recorded, and no stream is stored.
The control plane
One Cloudflare Worker. Text only — it never sees a stream.
- Starlings control planeCloudflare
- One Worker: the door, the routes, and the SPA in front of them. It holds text and never media.
What it keeps
Room state, the words, the ledger, the files.
- Starlings storeCloudflare
- The ledger, the tokens, the files and the job queue behind the Worker. Text and files — no media bucket.
The rest of the company
Services Starlings reads and writes on a member's behalf.
- CoreEnvisioning
- The CRM. Subjects, tasks and interactions, read and written over HMAC — a meeting is filed on the project it belongs to.
- DocsEnvisioning
- Where documents and their comments live. Every read goes through the Starlings Worker; the browser never holds a Docs token. Docs calls back over a service binding to tell the workspace when a guest views a shared link.
- KeepEnvisioning
- Where client credentials live. Starlings reads what a member may see, over a service binding.
- Google WorkspaceGoogle
- Both halves of Google: who is one of us at sign-in, and the owner's day once they attach a calendar.
- Starlings sign-inEnvisioning
- Google sign-in and Google consent on the auth host, for a workspace that binds it (hq first). The workspace starts an attempt and redeems its one-time code over a service binding, then sets its own session. It also holds the Starlings GitHub App's key, and mints a GitHub token for each workspace's own installation over the GITHUB binding.
- The operator consoleEnvisioning
- The product across every workspace on the ops host, for the platform operator behind Cloudflare Access. Provisioning adds each new workspace to it.
- The models
- Where the writing happens: the notes after a meeting, a forwarded mail read into events, suggested tasks and filing.
- AgentsVercel
- Peers with no device. Each is one row in the roster; a hand-off is signed, and an unanswered one is reset every five minutes.
- Connectors
- Every outside source that writes meetings into Starlings. One card each on
/admin/connectors; the next one is a card, not a page. - PostmarkPostmark
- Outbound mail — invitations and the notices a guest gets — sent from the contact address.
What runs between them
- The hosting device ↔ LiveKit CloudAudio, video and screen · WebRTCNever: A recording. Nothing is written to disk, here or anywhere.
- The browser ↔ LiveKit CloudAudio, video and screen · WebRTCNever: A recording, and never a stream before the owner has admitted you.
- The hosting device ↔ Starlings control planeTranscript text, summaries, admissions and room state · HTTPSNever: Audio, video, or the screen. The words leave; the sound does not.
- The browser ↔ Starlings control planeThe knock, admission status, chat, and every workspace read · WebSocket
- Starlings control plane → LiveKit CloudA media token, minted only once the owner has admitted the guest · HTTPSNever: Media. No stream passes through the Worker.
- Starlings control plane ↔ Starlings storeRoom state, the words, the ledger, the files, the jobs · Cloudflare binding
- Starlings control plane ↔ CoreThe meeting, its notes and its tasks, filed on a subject · HTTPS
- Starlings control plane ↔ DocsDocuments and comments, on the member's behalf · Cloudflare bindingNever: A Docs token into the browser. The Worker keeps its own, per owner.
- Starlings control plane ↔ Google WorkspaceThe owner's day, and the meetings scheduled from Starlings · HTTPS
- Connectors ↔ Starlings control planeMeetings from outside sources — a webhook in, a paced job pulling history · HTTPS
- Starlings control plane ↔ The modelsTranscript text to write the notes from, and a mail to read into events · HTTPSNever: Audio. A model reads the words the device wrote, never the sound.
- Agents ↔ Starlings control planeA signed hand-off out, the agent's answer back · HTTPSNever: A seat in the room. An agent has no device and no media.
- Starlings control plane ↔ KeepThe credentials a member may see · Cloudflare binding
Each claim below has a test behind it.
Each line names the automated test that checks it. Remove or rename a test and the build stops until this page changes too. The release queue runs all of them before a change ships.
Checked for Starlings 7.6.9.
Who gets in
Every route that serves members checks a named permission. A route that checks a session without one fails the build.
Checked byrefuses every session-gated route without a sessionservices/control-plane/test/route-gates.test.ts
A removed person cannot sign in again or renew a session.
Checked byrefuses to renew somebody who has been revokedservices/control-plane/test/auth-cookies.test.tsrefuses a revoked person with 403 oauth_failed, as renewal doesservices/control-plane/test/auth-cookies.test.ts
The server checks every sign-in against the workspace's own domains. Narrowing the Google account picker does not change who gets in.
Checked byaccepts either domain and nothing elseservices/control-plane/test/identity-domains.test.tsnarrows the account chooser to one domain without narrowing the gateservices/control-plane/test/identity-domains.test.ts
An outside address gets in only with an open invitation. A revoked or expired invitation admits nobody.
Checked byadmits nobody on a revoked or a lapsed invitationservices/control-plane/test/invitations.test.tsgives no session to an address the workspace does not admitservices/control-plane/test/email-sign-in.test.ts
Only an admin can remove a person, and no admin can demote or lock out the workspace owner.
Checked byneeds an admin to revoke anyoneservices/control-plane/test/admin.test.tscannot demote, revoke, or lock out a root adminservices/control-plane/test/admin.test.ts
One firm, one instance
Each firm gets its own server and its own database. Only the front door that routes requests is shared.
Checked bythe env block has the keys of env.hq, and its own resourcesscripts/provision-workspace.test.mjs
Sign-in reads a workspace's address from its configuration, never from the request. One workspace cannot start a sign-in for another.
Checked byreads the origin only from props, and only an origin this Worker servesservices/control-plane/test/central-auth.test.tsrefuses a caller that names an origin of its own, and binds the attempt to the props originservices/control-plane/test/central-auth.test.tsan AUTH binding that names another workspace is refusedscripts/check-production-config.test.mjs
A sign-in code works once, even when two requests race. The identity is encrypted at rest and never appears in a URL.
Checked byredeems exactly once under concurrency; the identity is sealed at rest and never in a URLservices/control-plane/test/central-auth.test.ts
A call pass lets a person join, speak and listen in one room of their own workspace for two hours. It cannot record and cannot moderate.
Checked bysigns a participant token for a room under the caller's prefix, with the fixed grantsservices/control-plane/test/livekit-broker.test.tsrefuses a room of another workspace, of Envisioning, or the bare prefixservices/control-plane/test/livekit-broker.test.ts
Where data lives
An EU workspace keeps its meetings, transcripts and notes in Cloudflare's EU jurisdiction. Production refuses to start with any other setting.
Checked bytakes the EU path for a workspace set to eu, without reading the move tableservices/control-plane/test/do-jurisdiction.test.tsrefuses an unknown value in productionservices/control-plane/test/do-jurisdiction.test.tsthrows in production when jurisdictions are not availableservices/control-plane/test/do-jurisdiction.test.ts
Access tokens for connected services are encrypted at rest. The database holds neither the token nor the address it belongs to.
Checked byis sealed at rest: the store holds no token and no addressservices/control-plane/test/core-pat-shared.test.ts
Browser protections
Every answer forces HTTPS, refuses to be framed, blocks content sniffing and sends no referrer.
Checked byforces HTTPS, denies framing, blocks sniffing and sends no referrerservices/control-plane/test/security-headers.test.ts
Only the workspace's own web address may send a signed-in request from a browser.
Checked byallows credentials only from the workspace's own originservices/control-plane/test/security-headers.test.ts
Backups and records
Every room, conversation and notebook is backed up each day, and the tests restore one.
Checked byplans the day once, after 03:00 UTC, as one job per room, thread and personservices/control-plane/test/backups.test.tsgives back a room with its meetings and transcript linesservices/control-plane/test/backups.test.ts
Admin actions write an audit record, kept for two years.
Checked byinvites each address once with a role, renews a second invite, and audits itservices/control-plane/test/invitations.test.tsdrops audit rows older than 2 years and keeps the restservices/control-plane/test/retention.test.ts
Usage events are deleted after 13 months.
Checked bydrops usage events older than 13 months and keeps the restservices/control-plane/test/retention.test.ts
How code reaches production
A deploy stops when the production configuration breaks any rule on this page.
Checked bythe checked-in configs passscripts/check-production-config.test.mjs
What we inherit from vendors
Hosting, databases and storage run on Cloudflare, which holds SOC 2 Type II and ISO 27001.
Sign-in uses Google, which holds SOC 2 Type II and ISO 27001.
Calls run on LiveKit. Its compliance reports are on its trust center.
Meeting notes are written by Claude from Anthropic. Its compliance reports are on its trust center.