How Starlings handles your data
Envisioning makes Starlings. In this notice, “we” means Envisioning.
Updated 3 November 2026.
Workspaces and who decides
Each organization that uses Starlings gets its own workspace. A workspace is a separate deployment with its own databases and file storage. Workspaces do not share records.
Envisioning uses Starlings for its own work, in a separate workspace.
The organization that runs a workspace decides who joins it and what goes in it. For that data the organization is the controller, and we process it for them. For the Envisioning workspace, and for anything you send through this site, Envisioning is the controller.
What we collect and why
- Members. Members sign in with Google. We receive your name, email address, Google account ID and profile picture. We use them to sign you in and to show colleagues who you are. You can replace or remove the picture.
- Devices and presence. We keep a list of the devices you signed in on and when each was last active, so you can sign a lost device out. Colleagues in your workspace can see whether you are online and when you were last active. They never see where you are.
- Profile details. A job title, pronouns, time zone or working hours, if you add them. Colleagues in your workspace can see them.
- Workspace records. The messages, tasks, projects, documents, decisions and notes that members write. We store them so the workspace works.
- Connected services. When a member connects Google Calendar, GitHub, Slack, Granola or their own Claude, we exchange data with that service as the member asked. We store Google Calendar access encrypted.
- Google user data. Starlings’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We never sell it, and we never use it to train AI models. Read the policy
- Guests. Guests join a call without an account. A guest gives a name and an email address, and we keep both with the record of the call. A third-party notetaker gives a name only.
- Join pages. While you are on a join page, the host can see that someone is there, the name you typed, and your approximate city and country, taken from your network connection. The host does not see your email address until you ask to join. This disappears about a minute after you leave.
- This site. This site counts visits with Plausible, which sets no cookies and keeps no personal data. It runs no advertising trackers. It remembers your light or dark setting in your browser. If you send the early-access form, we keep your answers and email you a copy. We use your network address to limit abuse of the form, and we do not store it with your answers.
- Logs. Our servers log errors. The logs hold no access tokens, transcript text, message text or full email addresses.
Calls
- Starlings does not record the audio, video or screen share of a call.
- Speech-to-text runs on the device that hosts the call. The audio stays in that device’s memory and is discarded once it is text. Only the text leaves the device: who spoke, in which language, when, and what they said.
- We keep the transcript and the notes written from it, so people with access can read them after the call. We do not email them to anyone.
- Guests wait in a waiting room until the host lets them in. Nobody gets the call’s audio or video before that.
- If the host lets a third-party notetaker in, that service may record what it receives, under its own terms. Starlings marks it in the call, and the host can refuse notetakers.
- With the Mac app, a member can also transcribe a call held on another service, such as Zoom or Teams. The audio then stays in temporary files on that Mac until the transcript is saved, and is deleted after. The audio never leaves the Mac. Starlings does not tell the other people in that call, so the member must.
Who processes data for us
These companies process data on our behalf. Some of them apply only when a workspace turns a feature on.
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Cloudflare | Runs Starlings and this site: servers, databases, file storage and queues. Its Workers AI writes notes when Claude is not used, and suggests tasks during a call. | Everything a workspace stores. Transcript text, for notes and task suggestions. | In the workspace’s data region. See Where data is stored. |
| LiveKit | Carries live audio, video and screen share. Recording is off. | Live media for the length of the call, and display names. | Unknown. We have not confirmed a region yet. |
| Member sign-in. Google Calendar, when a member connects it. | Member identity. The calendar events a member creates or reads in Starlings. | Unknown. | |
| Anthropic | Writes meeting notes with Claude. Turns text a member sends into calendar events. A member’s own Claude, when the member connects it. | Transcript text and speaker names, and the title of the calendar event a recorded meeting matches. The text a member sends. What a member asks their Claude to read. | Stores data in the United States. Claude can run in any region. |
| Postmark | Sends email: your copy of the early-access form, and alerts to our operators. | Your email address and your answers. | United States. |
| GitHub | Issues and pull requests, when a workspace links repositories. | What a member reads or writes there. | Unknown. |
| Slack | Imports the channels a workspace maps to its projects, when the workspace connects Slack. | The messages in those channels. | Unknown. |
| Granola | Imports the meeting notes a member chooses, when the member connects Granola. | Those notes and their transcripts. | United States. |
| TypeSafe AI | Suggests where an imported Granola note belongs, through Cloudflare Workers AI or Vercel AI Gateway. | The note’s title, participant names and email domains, its text and the start of its transcript. | Unknown. |
| Plausible | Counts visits to this site, and use of the Envisioning workspace. Sets no cookies. | The page name and the site you came from. Your network address and browser, which Plausible turns into a daily count and does not store. | Germany. |
| Open-Meteo | Weather in the calendar, when a member names a city. | A rounded location and a time zone. No identity or calendar data. | Europe and North America. |
| Envisioning Core | Envisioning’s own CRM. The Envisioning workspace only. | A record of each call: summary, transcript, and the names and email addresses of the people in it. | Unknown. |
Under their terms, Anthropic and Cloudflare do not train their models on this content. No cloud service ever receives the audio of a call.
Where data is stored
- Each workspace has a data region, the EU or the US, chosen when it is created.
- In the EU region, we store messages, calls, transcripts, quick notes and daily backups in the EU. The Envisioning workspace is still moving its calls and quick notes to the EU.
- Workspaces created from now on store files and profile pictures in the EU. Older workspaces are moving theirs.
- In the US region, we place messages, calls, transcripts, quick notes, files, workspace databases and daily backups in the United States. Cloudflare treats this placement as a preference and does not guarantee it.
- In the EU region, workspace databases are placed in western Europe. Sign-in and signup are placed there too, and serve every workspace from there, whatever its region. Cloudflare treats this placement as a preference and does not guarantee it.
- Our servers run on Cloudflare’s network around the world, close to each user. Workers AI runs on that network too.
- Postmark, Anthropic and Granola store data in the United States. LiveKit may route live media outside the EU.
- Where data leaves the EU, it does so under each provider’s data protection terms.
How long we keep it
- Live audio and video
- Not stored.
- Audio on the host device
- In memory only, discarded once it is text. A call transcribed from another service is kept in temporary files on the Mac until its transcript is saved, then deleted.
- Transcripts, notes and workspace records
- Kept until someone deletes them. There is no automatic expiry yet.
- Messages
- Kept until the author withdraws them. There is no automatic expiry yet.
- Waiting room requests
- End with the call.
- Join-page presence
- About a minute.
- Sign-in
- A session lasts 8 hours. A device stays signed in until it is signed out or unused for 60 days.
- Daily backups
- Expire after 30 days. Something you delete can stay in a backup until then.
- What a connected Claude asked
- 90 days.
- Error reports
- 30 days. They hold no names, email addresses or content.
- Early-access answers
- Kept until you ask us to delete them.
Your rights
You can ask to see, correct, export or delete your data, to limit how we use it, or to object to it. You can withdraw any consent you gave.
Some of this you can do yourself today:
- Copy or download any transcript you can read, as Markdown or plain text.
- As host, delete lines from a transcript or correct a speaker’s name.
- Withdraw a message you wrote.
- Remove your profile picture, delete your quick notes, disconnect Google Calendar and sign out any of your devices.
Exporting a whole workspace and deleting a whole workspace are planned and not built yet. Until then, write to us and we do it by hand.
If your data is in a workspace another organization runs, that organization decides on your request. Send it to them, or to us and we pass it on.
You can also complain to a data protection authority: the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon), or the authority where you live or work.
Legal basis
- Members. To provide Starlings under the agreement with their organization, and our legitimate interest in keeping it secure.
- Guests. To provide the call you asked to join.
- Transcripts and notes. The workspace’s legitimate interest in a record of its calls.
- Envisioning’s own records. Envisioning keeps a record of who it met and when, as ordinary business records (legitimate interest).
- Early-access answers. Your request, as a step before an agreement.
This notice follows Brazil’s LGPD and the EU GDPR. You can complain to Brazil’s data protection authority (ANPD), or to the supervisory authority where you live in the EU.
Changes to this notice
When Starlings changes how it handles data, we update this page and the date at the top.
Contact
Starlings is provided by Envisioning OÜ, Pärnu mnt 10, 10148 Tallinn, Estonia. VAT number EE101979991.
Envisioning’s privacy contact is Michell Zappa, our data protection officer (encarregado) under the LGPD.