Sonar connects to every source read-only and asks for the narrowest permission that runs the feature you switched on. It reads the last seven days about once a week, keeps the short moments it found and discards the raw text. Your workspace is isolated by row-level security in the database, traffic and storage are encrypted, connection tokens never reach the browser, and no meeting bot ever joins a call. It holds no SOC 2 or ISO certification; what it has is this list and a privacy policy that states each item.

What does Sonar read from my calendar?

From Google Calendar: events on your primary calendar from the last seven days, up to 60, through one permission, calendar.events.readonly. For each meeting it reads the day, the title, who was there and the first 200 characters of the description. Only meetings with two or more people who did not decline count; solo blocks and all-day entries are skipped. It never reads another calendar, anything older than a week, or your email, and it cannot create, change or delete an event.

Does Sonar keep my meeting transcripts?

No. Transcript text, like calendar text and message text, is processed transiently and discarded after a short extraction pass. What is stored is the derived moments (a title, an angle, one line of detail and the source) and a receipt of what was read: up to five titles on the source's row in Settings. Where a source records calls, Sonar downloads the transcript file and never the video or audio.

Does a Sonar bot join my meetings?

No. Sonar never dials into a call and is never visible to the other participants. Every transcript it reads is read after the fact through the vendor's own API: Google Meet's, Zoom's cloud recordings, or the notetaker you already use, such as Granola, Fireflies or Wispr Flow.

Who can see my data, and where is it stored?

Only the members of your workspace, which for a solo founder is you. Every table enforces row-level security scoped to the workspace, so the database itself refuses a read from anyone else. Data is stored on Supabase in Singapore (ap-southeast-1), encrypted at rest, and the application runs on Vercel in the same region. Drafting sends the relevant text to Anthropic's Claude to produce a response; under the provider's API terms it is not used to train their models.

How do I delete what Sonar has?

Three ways, all yours. Delete any moment, every moment from one source, or all of them in Settings under Intelligence, Moments, or set a retention rule of 30 days, 90 days or a year and Sonar sweeps every day. Turn a source off with one switch and its tokens and receipt go at once. Delete your account in Settings and every file, every row in the workspace and the sign-in account itself are removed immediately.

Security

Is Sonar safe? What it reads, and what it keeps.

Sonar connects to every source read-only, reads the last seven days about once a week, keeps the moments it found and discards the raw text. No bot joins your calls. The moments are yours to delete, private people never reach a draft, and deleting your account erases everything at once.

Start free The privacy policy

What Sonar reads

Every source, read-only.

Each source is granted the narrowest read permission that runs it, and each read covers the last seven days. Here is the permission and the read, source by source.

Google Calendar
Events on your primary calendar from the last seven days, up to 60: the day, the title, who was there and the first 200 characters of the description. Only meetings with two or more people who did not decline; solo blocks and all-day entries are skipped.
calendar.events.readonly, verified by Google
Google Meet
Transcripts of your own Meet calls from the last seven days, up to five, through Google's Meet API. A separate switch on the same Google connection, off by default.
meetings.space.readonly, verified by Google
Slack
The channels, group messages and direct messages you pick, last seven days. Nothing is read before you pick, and it connects as you, so it can only see what you can already see. No bot joins your workspace.
A user token with read-only history scopes; no write scope
Granola
Your last seven days of meeting notes, up to five, for the moments. For your voice, only the transcript lines Granola attributes to you.
One-click connect or a pasted API key; read calls only
Fathom
Coming
Transcripts of your last seven days of Fathom-recorded calls, up to five, whichever meeting tool the call was on.
Fathom's public_api scope, or a pasted key
Built and waiting on Fathom to switch the app on for everyone.
Fireflies
Transcripts of your own Fireflies-recorded meetings from the last seven days, up to five.
One-click connect or a pasted API key; read calls only
Wispr Flow
Your Notetaker summaries, notes and transcripts from the last seven days. Your dictations are never read; Wispr does not expose them.
One-click connect; read calls only
Notion
The pages you grant on Notion's consent screen, as edited in the last seven days. Sonar sees nothing else in your Notion workspace.
A user-level grant limited to the pages you pick
Zoom
Transcripts of your own cloud recordings from the last seven days, up to five. The transcript file only; the video and audio stay on Zoom.
Cloud recording read scopes; app reviewed and published by Zoom
Microsoft 365
Coming
Your Outlook calendar's week, read like Google Calendar, plus Teams transcripts as a separate ask that your Microsoft admin approves once.
Calendars.Read and OnlineMeetings.Read; transcripts need OnlineMeetingTranscript.Read.All
Built and waiting on Microsoft's publisher check before other companies can connect it.

The one grant that is not read-only is publishing. If you connect LinkedIn or X, that connection can publish as you; the X connection also reads your own posts and the public posts of the people you watch. Neither reads private messages, and nothing is published from either except a post you scheduled or pressed Post on. Each source's own page is on Integrations; the Google Calendar guide and the Zoom guide each walk one read end to end.

What it keeps

What stays is the moment.

The week is assembled into one transient block, mined in a single pass for the moments worth saying, and discarded. What is stored is the short derived moments and a receipt of what was read.

Kept

The moments: a title, an angle, one line of detail, the kind (a decision, a win, a lesson, a number, a conflict, a story) and the source they came from.
A receipt of each read on the source's row in Settings: how many meetings, notes or pages, and up to five of their titles, so you can check the work.
The tokens that let next week's read run without asking again, stored server-side only.
Your drafts, your posts, your Intelligence Pack and your own post history, in your private workspace.

Never kept

Transcript text, message text and calendar text. All of it is processed transiently and discarded after a short extraction pass.
Video or audio. Where a source records calls, Sonar downloads the transcript file and leaves the recording where it is.
The attendee list. Names ride the week's text into the read so a 1:1 can be told from a team review, and leave with it.
Anything from a Slack conversation or a Notion page you did not pick.

Your controls

Delete any moment, every moment from one source, or all of them, in Settings under Intelligence, Moments.
Set a retention rule, 30 days, 90 days, 1 year or keep forever, and Sonar sweeps every day.
Turn a source off with one switch. Its tokens and its receipt go at once; the moments already mined stay until you delete them.
Delete your account and everything goes, immediately.

How it is built

What holds it together.

No bot joins your calls.: Sonar never dials into a meeting. Where it reads a transcript, it reads it after the call through the vendor's own API: Google Meet's, Zoom's cloud recordings, or the notetaker you already use. Nothing about Sonar is visible to the other people on the call.
Encrypted in transit and at rest.: All traffic runs over HTTPS. The database and the file storage are encrypted at rest by the infrastructure provider, Supabase.
Isolated per workspace, by the database.: Every table enforces row-level security scoped to the workspace that owns the row, so data is readable only by that workspace's members. The database itself enforces it; the application code is a second gate.
Tokens never reach the browser.: The tokens for connected accounts live in a table the browser-side credentials are explicitly denied access to, and are used only by server code. Disconnecting deletes our copy, and where the provider offers a revocation endpoint (Google, Slack, Zoom, X, Notion, Granola, Fireflies) the grant is revoked there too.
Hosted in Singapore.: The application runs on Vercel in the Singapore region (sin1) and the database on Supabase in ap-southeast-1, Singapore as well.
No public model learns from you.: Drafting uses a third-party AI provider, Anthropic's Claude. Under the provider's API terms your inputs and outputs are not used to train its models, and data from Google Workspace APIs is never used to create, train or improve any generalised AI model.
Private people never reach a draft.: A colleague, a client, a candidate, anyone in your meetings or messages, is written as a role or a relationship in the moment and in the post. Named stays named only for public figures, the employers and clients your own profile cites, and anyone you name yourself in a request. The rule sits in the instructions every draft is produced under, and the miner that extracts moments follows the same rule.
Restricted access.: Administrative access to production is limited to the people who operate Sonar, protected by two-factor authentication, and used only to run and support the service.
Deleting your account erases everything.: Delete my account, under Settings, removes every stored file, the workspace and every table that hangs off it, and the sign-in account itself, immediately. Nothing waits for a request to be processed.
The extension reads only your own numbers.: Sonar for LinkedIn reads the analytics already on your own LinkedIn analytics pages while you browse them, sends them to your workspace, and reads nothing else. It visits nothing on your behalf and performs no actions on your account.

Sonar does not hold a SOC 2 report or an ISO 27001 certificate today. What it has is the list above, and a policy that says the same things in more detail: the privacy policy. Who makes Sonar is on the about page.

Reporting a problem

Found something? Tell us.

Security reports go to hello@meetdistilled.com, the address published in this site's security.txt. Any other question about a source or your data goes to support, answered within one business day.

FAQ

The questions people ask first.

Sonar connects to every source read-only and asks for the narrowest permission that runs the feature you switched on. It reads the last seven days about once a week, keeps the short moments it found and discards the raw text. Your workspace is isolated by row-level security in the database, traffic and storage are encrypted, connection tokens never reach the browser, and no meeting bot ever joins a call. It holds no SOC 2 or ISO certification; what it has is this list and a privacy policy that states each item.
From Google Calendar: events on your primary calendar from the last seven days, up to 60, through one permission, calendar.events.readonly. For each meeting it reads the day, the title, who was there and the first 200 characters of the description. Only meetings with two or more people who did not decline count; solo blocks and all-day entries are skipped. It never reads another calendar, anything older than a week, or your email, and it cannot create, change or delete an event.
Only the members of your workspace, which for a solo founder is you. Every table enforces row-level security scoped to the workspace, so the database itself refuses a read from anyone else. Data is stored on Supabase in Singapore (ap-southeast-1), encrypted at rest, and the application runs on Vercel in the same region. Drafting sends the relevant text to Anthropic's Claude to produce a response; under the provider's API terms it is not used to train their models.
Three ways, all yours. Delete any moment, every moment from one source, or all of them in Settings under Intelligence, Moments, or set a retention rule of 30 days, 90 days or a year and Sonar sweeps every day. Turn a source off with one switch and its tokens and receipt go at once. Delete your account in Settings and every file, every row in the workspace and the sign-in account itself are removed immediately.

Read-only in. Your approval out.

Start with Google Calendar, the lightest ask, and add the rooms where the real conversations happen when you are ready.

Start free See the integrations

Is Sonar safe? What it reads, and what it keeps.

Every source, read-only.

Google Calendar

Google Meet

Slack

Granola

Fathom

Fireflies

Wispr Flow

Notion

Zoom

Microsoft 365