Privacy Policy

What Sonar is

Sonar is a content platform for founders, operators and executives. It drafts, schedules and measures LinkedIn and X content on your behalf, using information you provide and accounts you explicitly connect. Use of the service is governed by the Terms of Service.

Who is responsible for your data

The controller is V Group (FZE), trading as Distilled, a free zone company registered in the United Arab Emirates, at Block B - B36 - 158, SRTIP, Sharjah, United Arab Emirates. For anything in this policy, including a request about your own data, write to hello@meetsonar.co. We have no establishment in the European Union or the United Kingdom; if you are there, write to the same address and we will answer you directly.

What we collect

• Account: your name and email, and how you signed in (email and password, or LinkedIn or X). Passwords are handled by our authentication provider and never stored by us in readable form.
• What you create: the posts, drafts, notes, documents, recordings, dictated and typed answers you enter, and the intelligence Sonar builds from them.
• Your own public profile: when you give Sonar your LinkedIn profile address, it reads your public profile (headline, about, experience, education, photo) and your recent public posts, through a research provider, to learn your voice and pre-fill your brief. If you give it your website, it reads that once for the same reason.
• Connected accounts: when you explicitly connect LinkedIn, X, Google (Calendar and Meet), Slack, Microsoft 365 (Outlook and Teams), Zoom, Notion, Fireflies, Granola, or Wispr Flow, we store the access tokens needed to provide the feature you enabled, and the data you asked Sonar to read from them. Some sources also accept an API key you paste instead; either way the credential stays server-side, encrypted, is used only to read what that source is connected for, and is deleted when you disconnect. Two of these have a boundary you choose at connect time: with Slack you pick the specific conversations and Sonar reads only those, including direct messages if you pick them; with Notion you pick the pages you grant, and Sonar sees nothing else in your workspace.
• Public content about other people: to build your watchlist, your niche snapshot and a shared library of well-performing public posts, Sonar reads posts and articles that people published publicly. What that covers is set out under People who never signed up, below. It never uses your login to do so and never reads anything behind one.
• Payment: if you subscribe, our payment processor collects your card details directly. Sonar never sees or stores your full card number.
• Usage: product analytics and masked session replay, described below.

The Sonar for LinkedIn browser extension

The extension reads the analytics numbers already visible to you on your own LinkedIn analytics pages (post impressions, engagements, profile views, search appearances, followers, and audience demographics) while you browse them in your own logged-in session, and sends those numbers to your own Sonar workspace. It reads nothing else, visits nothing on your behalf, and performs no actions on your account.

• Data collected: your own analytics numbers, and the pairing token that links the extension to your workspace.
• Where it goes: only to the Sonar workspace the token belongs to. Never to anyone else.
• Local storage: the pairing token and last-sync time, kept in your browser's extension storage, which your browser may sync across your own signed-in devices.
• No sale, no third-party transfer, no advertising use, no credit or lending use.
• Removal: uninstall the extension and, if you wish, regenerate the token in Sonar to revoke the old one.

How we use it

We use your information only to provide and improve Sonar: to learn your writing voice, draft and schedule content, surface what is happening in your niche, and measure how your content performs. We do not sell personal data. The only advertising use is the ad measurement described under Cookies, which you can switch off.

Emails. We email you about your account and your use of Sonar: when posts are ready, when your access is about to end, a monthly recap of your numbers, a nudge if you have not finished setting up, and a short note when Sonar changes in a way that affects how you use it. Each of those carries an unsubscribe link that turns them off. A separate monthly round-up of what is new goes only to people who switch it on in Settings. Some service messages are sent even if you unsubscribe, because you need them to use what you pay for: emails about your account, sign-in and billing, and the email that tells you a post you scheduled failed to publish.

Dictation.When you use the microphone to dictate, your browser's own speech recognition turns your voice into text. In Chrome and some other browsers that recognition runs on the browser maker's servers (Google, for Chrome) under their terms; Sonar receives only the text.

AI processing

Sonar generates content using a third-party AI provider, Anthropic's Claude. To draft in your voice, the relevant parts of your content, your settings and the material Sonar has gathered are sent to that provider to produce a response. Under Anthropic's commercial terms, your inputs and outputs are not used to train their models; Anthropic may keep them for a limited period for safety and abuse monitoring, as its terms describe, and then deletes them. Data received from Google Workspace APIs is never used, transferred, or sold to create, train, or improve any foundational or generalized AI or machine learning model, in line with the Limited Use requirements described under Google user data below.

The other people in your sources

Meetings, messages and calendars involve other people: colleagues, clients, candidates. When you connect a source, their names and words pass through the same short extraction as yours, including being sent to our AI provider, so Sonar can find the moments in your week worth writing about. What is kept from a read is a short moment: a title, an angle, one line of detail, up to three short specifics quoted from the source (a number, a step, a phrase), and the name of the meeting, channel or page it came from, which can itself contain a name.

Sonar is instructed never to name those people in a draft: it writes the role or the relationship instead, and the step that extracts moments follows the same instruction. You review every draft before it goes anywhere. By connecting a source you confirm you are allowed to, for example under your employer's policies, as the Terms of Service say. Anyone whose words Sonar processed through your account can write to hello@meetsonar.co, and we will help you find and delete the moments concerned.

Google user data

If you connect Google, Sonar requests only read-only access, and only to what the feature you switched on requires:

• Google Calendar (calendar.events.readonly): Sonar reads the titles, times, and attendee names of your own calendar events from the last seven days, once a week, to suggest post-worthy moments from your real working week. This is the narrowest Calendar scope that permits reading events; Sonar does not request access to manage calendars or to list the calendars on your account.
• Google Meet (meetings.space.readonly): if you separately switch on Meet transcripts, Sonar reads transcripts of your own recent Meet conferences for the same purpose, and to learn how you phrase things from sentences you yourself spoke.

What we keep.Calendar text and meeting transcripts, from every connected source, are processed in memory to extract short, story-shaped moments, and the raw text is then discarded. What we store is those moments (as described in the section above, including up to three short quoted specifics and the meeting's title as its source), plus a short receipt of what was read: the titles of the meetings, notes, or pages processed in the last sync, so you can check our work. You can see that receipt on each source's row in Settings under Connected sources, and delete moments from Home or in Settings under Intelligence, Moments, where you can also set them to delete themselves after a period you choose. Disconnecting a source deletes both its stored access token and its receipt, and deleting your account removes every stored moment along with the rest of your workspace, immediately. Turning a source off inside Sonar keeps the moments already mined until you delete them. Removing Sonar from Zoom's own side (Zoom App Marketplace, Manage, Added Apps, Remove) goes further: Zoom notifies us and we delete the Zoom tokens, the receipt, and every moment derived from your Zoom transcripts.

Who we share it with. We do not sell Google user data, and we do not transfer it to advertisers, data brokers, or any third party for their own purposes. It is disclosed only to the providers that operate Sonar on our instructions: Supabase (database and storage, where the moments are held), Vercel (application hosting), Anthropic (AI processing, where relevant text is sent to generate your drafts and is not used for model training under their API terms), and Loops (email delivery, which receives the titles of moments and the opening of drafts included in the emails Sonar sends you). We may also disclose data if legally required, or to you.

Limited Use. Sonar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we do not use, transfer, or sell Google user data, whether raw, aggregated, or derived, to create, train, or improve any foundational or generalized artificial intelligence or machine learning model. Google user data is used only to provide the features you switched on inside Sonar.

Revoking access. You can disconnect Google at any time in Settings under Connected sources. Disconnecting revokes our access token with Google immediately, and you can also remove access from your Google account permissions page.

How we protect your data

Sensitive data, including anything read from a connected account, is protected by these measures:

• Encrypted in transit and at rest: all traffic runs over HTTPS/TLS, and our database and file storage are encrypted at rest by our infrastructure provider.
• Isolated per workspace: every table enforces database-level row security, so data is readable only by members of the workspace that owns it. This is enforced by the database itself, not only by application code.
• Connection tokens are server-only and encrypted: the tokens for connected accounts are stored in a table that browser-side credentials are explicitly denied access to, are encrypted a second time with a key held outside the database, and are never sent to the browser. Disconnecting always deletes our copy, and for the providers that offer a revocation endpoint (Google, Slack, Zoom, X, Notion, Granola, Fireflies, and Wispr Flow where its server offers one) we also revoke the grant at the provider. Microsoft, LinkedIn and Fathom offer no such endpoint on the tiers we use, so for those you can additionally remove Sonar from your own account settings at the provider.
• Minimised by design: every source we read is granted read-only access, and we request the narrowest scope that runs the feature you switched on. The one exception is publishing: if you connect LinkedIn or X to let Sonar post for you, that connection carries permission to publish as you, and only that.
• Restricted access: administrative access to production systems is limited to the people who operate Sonar, protected by two-factor authentication, and used only to run and support the service.

Service providers

We rely on a small set of providers to run Sonar, each handling only what its function requires: database and authentication, hosting, AI generation, payment processing, email delivery, product analytics, public-content research, and our own internal team notifications. They act on our instructions and are not permitted to use your data for their own purposes. Every one is named, with what it receives and where, on the sub-processors page.

Product analytics and session replay

To understand how Sonar is used and to improve it, we use product analytics, including session replay inside the app. Once you sign in, analytics knows your email address so we can help you when you report a problem. Replays are recorded with all text and form inputs masked, so we can see how the interface is navigated but never the content you write, draft, or connect. Analytics records which buttons are used, not the words on them, and inside the app it keeps only the page, never the text a link carries. We do not sell this data or use it for advertising.

Cookies

Strictly necessary: the cookie that keeps you signed in, the one that remembers your theme, and the one that records your answer to the cookie banner so we do not ask again. These are set without asking, because the service cannot work without them.

Analytics:our analytics provider's cookie and browser storage, which count page views and show where people give up; cookieless page-view counts from our hosting provider; and our own first-visit cookie, kept for 90 days, which remembers which campaign or ad link brought you (the campaign tags and the ad networks' click identifiers in that link) so we can tell which of our marketing works.

Advertising measurement:the Meta Pixel, the LinkedIn Insight Tag and the Google Ads tag, which tell Meta, LinkedIn and Google when someone who saw one of our ads visits our website, starts to sign up, or finishes setting up an account, so we can see which ads work and show them to people likely to find Sonar useful. They set Meta's, LinkedIn's and Google's own cookies. They run only on our public website, the sign-in page and account setup, never inside the app where your content is. When this is on and you finish setting up your account, or later subscribe, our server also tells Meta that this happened, with your email address scrambled (hashed), your IP address and your browser type, so Meta can match it to an ad; that message follows your current choice.

Your choice: in the EU, the UK and Switzerland, analytics and advertising measurement are each off until you accept them on the banner, and accepting analytics alone does not turn advertising on. Elsewhere both are on by default, except that advertising measurement stays off if your browser sends the Global Privacy Control signal. Anywhere, Cookie settings turns either off and withdraws an acceptance at any time.

Cookie settings

Why we are allowed to use it

Where the GDPR or the UK GDPR applies, each thing we do rests on one of these grounds.

• To run the service you signed up for. Your account, your workspace, the drafts, reading the sources you connected, and the service emails that go with them. Performance of our contract with you.
• Analytics and advertising measurement. Consent, each asked for separately before anything is set, and withdrawable at any time.
• Emails about how you use Sonar and how it changes. Our legitimate interest in helping our customers get value from what they pay for, with an unsubscribe link in every one.
• Keeping the service safe and working. Security, fraud prevention, and fixing faults. Our legitimate interests, weighed against your rights.
• Other people in your sources, and publicly posted material. Your legitimate interest, and ours, in writing about your own working week and researching your market, where those interests are not overridden by the rights of the people concerned. That is why names never reach a draft and quoted material is kept short.
• Records we are required to keep. Tax and accounting obligations. A legal obligation.

People who never signed up

This is the part most policies leave out, so it is stated plainly. When you add someone to your watchlist, when Sonar suggests people to watch, or when it looks at what is performing in your niche, it reads what those people published publicly on LinkedIn or X. It stores the post text and its public engagement counts, the author's name, headline, profile address and public profile picture, their public follower count over time, and Sonar's own analysis of why a post worked. Well-performing public posts are also kept in a library that every Sonar workspace can browse. That is personal data about someone who is not our user, and we hold it so workspaces can see what their market is publishing.

We never scrape anything behind a login, we never collect private profile details or contact details, and we never build a profile of a private individual beyond what they chose to publish. If you are one of those people and you want your posts removed from our systems, write to hello@meetsonar.co and we will remove them, including from the shared library, and act on any later copy you point us to. You can ask this without giving a reason.

Where your data goes

Our database and our application servers are in Singapore. AI processing, payments, email delivery, product analytics and public-content research run with providers in the United States and the European Union, and we operate Sonar from the United Arab Emirates. If you are in the EU, the UK or Switzerland, that means your data is transferred outside your region. Where that transfer needs a safeguard, we rely on the European Commission's Standard Contractual Clauses, or the UK Addendum to them, in our agreements with those providers. The current list of providers is on the sub-processors page, and it is kept current rather than written once.

Your rights over your data

Wherever you are, you can ask us to show you what we hold, correct it, give you a copy of it, or delete it. You can correct most of it, and delete your whole account, yourself inside Sonar; for a copy of your data, write to hello@meetsonar.co and we will send it within one month. If the GDPR or the UK GDPR applies to you, you also have the right to object to processing we base on legitimate interests, to ask us to restrict it, and to withdraw a consent you gave, which is as simple as the banner that asked for it. Withdrawing consent does not undo what was done while it was in force.

If you live in a US state with a privacy law (California, for example): we do not sell personal data. The advertising measurement described under Cookies can count as “sharing” under some of those laws, and you can opt out of it with Cookie settings or by sending the Global Privacy Control signal. We do not treat you differently for using any of these rights.

We answer verified requests within one month. If you think we have handled your data badly, please tell us first so we can fix it, and know that you can also complain to your national data protection authority, or to the Information Commissioner's Office in the UK, without going through us.

How long we keep it

• Your workspace: for as long as your account exists. Moments from your sources stay until you delete them, or until the retention period you set in Settings under Intelligence, Moments.
• When you disconnect a source: its token and its receipt are deleted at once, and revoked at the provider where the provider allows it.
• When you delete your account (Settings, Account and plan): a paid plan is cancelled, every connected account is revoked, and your workspace, every file and the sign-in account are deleted immediately. Two things stay: your email address with our email provider, marked so you are never emailed again, and your usage history in our product analytics. Write to hello@meetsonar.co and we will erase those too. Database backups roll off within seven days.
• Billing records: kept by our payment processor for as long as tax and accounting law requires.
• Public content about other people: kept while it is useful for the watchlist, the niche snapshot or the shared library, and removed on request as described above.

Children

Sonar is a professional tool for adults and is not directed to anyone under 18. We do not knowingly collect data from children.

Changes to this policy

We may update this policy as Sonar evolves. When we make a material change, we will update the effective date above and tell you in the product or by email before it takes effect.

Contact

Questions, requests about your data, or deletion: hello@meetsonar.co, or by post to V Group (FZE), Block B - B36 - 158, SRTIP, Sharjah, United Arab Emirates. Hours and response times are on the support page.