Do Not Sell or Share My Personal Information
Nothing here to opt out of.
Sonarwork does not sell or share personal information, and never has. There is no buyer, no ad product, and no revenue line that would make building one worth it.

Where the money comes from.
Subscriptions, paid by the workspace whose data Sonarwork holds. That is the whole list.
Workspace subscriptions
All of it
Sale of personal information
$0
Advertising and ad targeting
$0
Data brokerage or enrichment
$0
Every company that touches it, and what it sees.
Service providers · barred from their own use
Does
Claude is the AI model that writes your morning brief, summarizes meetings and answers the questions you ask Sonic. We never send the contents of any message — only the structural facts (who, when, how often). Emails, phone numbers, and risky phrases are stripped before anything reaches the model. Anthropic's business terms say it does not train its models on data sent through its API by default.
Can see
- Activity metadata: timestamps and event types — never message content
- Signal summaries written in plain English (e.g. 'PR open 9 days, no review')
- First names and job titles for personalization
- Meeting transcripts — only from meetings the meeting notetaker joins, and it joins none yet
Does
Listed because Sonarwork can be set to use an OpenAI model to write the morning brief, summarize meetings and answer the questions you ask Sonic. In production Sonarwork uses Anthropic Claude, and sends nothing to OpenAI unless Sonarwork switches this on. If it is switched on, the same rules apply as above: never message content, and emails, phone numbers and risky phrases are stripped first. OpenAI's published API terms say data sent through the API is not used to train its models unless the customer opts in, and that it keeps API request logs for up to 30 days for abuse monitoring.
Can see
- Activity metadata: timestamps and event types — never message content
- Signal summaries written in plain English (e.g. 'PR open 9 days, no review')
- First names and job titles for personalization
- Meeting transcripts — only from meetings the meeting notetaker joins, and it joins none yet
Does
The database where Sonarwork keeps everything it holds: activity metadata, signals, briefs, accounts and settings. Data exports wait here for seven days and are then deleted.
Can see
- Everything Sonarwork stores about your workspace and its people
- Secrets such as connection tokens, encrypted by Sonarwork before they are stored
Does
Where the Sonarwork website and app actually run. Server logs are kept seven days and never contain message content.
Can see
- Web request logs (page visited, response code, IP — never message content)
Does
Error reports, so we can fix what breaks. Reports carry no IP address and no email. A recording of a sample of browser sessions is kept only for visitors who press "Accept all" on the cookie banner, with every piece of text and every input hidden.
Can see
- Error details: what failed, on which page, in which browser
- Session recordings with all text and inputs hidden — only with cookie consent
Does
Runs Sonarwork's scheduled jobs and its rate limits. It starts each job on time and delivers each brief at its set minute. It counts sign-in attempts and other requests, so nobody can send them at speed, and it briefly holds the secret of a two-step sign-in being set up. It never holds a name, an email address, an IP address or any activity: each counter is stored under a one-way hash of what it counts.
Can see
- Job names and record ids — no names, no emails, no activity
- Rate-limit counters, each stored under a keyed one-way hash of the email address, IP address or account id it counts, never the address itself. A counter for an email or IP address is kept an hour at most, a daily limit for an account a day at most
- For two-step sign-in: the sealed (encrypted) secret while someone sets it up, kept 10 minutes, and a one-time pass after a correct code, kept 2 minutes
Does
Transactional + opt-in email delivery for morning briefs, invitations, and export-ready notifications. Bounces + complaints feed our suppression list.
Can see
- Recipient email address and first name
- Email subject and body (the brief itself)
- Delivery status — arrived, bounced, or marked spam
Does
Billing and subscription management. Your card number goes directly to Stripe — Sonarwork never sees it, stores it, or has access to it.
Can see
- Your organization name and billing email
- Subscription plan and seat count
- Invoice amounts and payment status
Does
Product analytics, so we can see which features are used (for example "first brief sent" or "integration connected"). In the browser it runs only after a visitor presses "Accept all" on the cookie banner, records which pages are opened and the events Sonarwork sends on purpose, and never records the text on a page or what anyone typed.
Can see
- Event names — what action was taken, not what was said (e.g. 'first brief sent')
- Org ID and user ID — no email, no name
- Structural properties — integration type, seat count
- In the browser, with consent only: the address of the page opened, browser type, shortened IP address
Does
Speech-to-text for the meeting notetaker. Used only when an admin has turned the notetaker on and the people from your workspace in the meeting have said yes, and the notetaker joins no meeting yet. Audio is streamed to Deepgram, transcribed, and discarded after we receive the text.
Can see
- Meeting audio (only from meetings the meeting notetaker joins, and it joins none yet)
- Resulting transcript (returned to Sonarwork; not retained by Deepgram beyond their stated processing window)
Does
Object storage for short-lived encrypted notetaker audio. Buckets are private; only Sonarwork can read them.
Can see
- Encrypted audio blobs (deleted after transcription completes)
Sonarwork also reads from the tools your workspace connects — Slack, GitHub, Google Calendar, Outlook and any others you add. Your company chose these tools and agreed terms with them directly. Sonarwork sends back to them only into your own workspace. It sends three things: a manager’s brief as a Slack message, when that manager chooses Slack delivery; a Slack alert to a person’s manager when one of that person’s signals turns urgent, which is on unless the manager turns off “Tell me right away” in Settings, Notifications; and, on the calendar of the person who acted in Sonarwork, the meetings they add in Sonarwork, and their approved time off and working from home.
Service-provider transfers are excluded from the CCPA definition of a sale: each one is contractually barred from using the data for its own purposes, including model training. The same list, with links to each company’s policy, is published at /privacy#subprocessors.
The statutory answer.
Cal. Civ. Code §§ 1798.120 · .121 · .130 · .140
What a sale means
Disclosing personal information to a third party for money or other valuable consideration (§1798.140(ad)). No third party has ever paid us, in money or in kind, for anything about your team. Sonarwork does not sell or share personal information.
Never occurred
What sharing means
Disclosure for cross-context behavioral advertising (§1798.140(ah)). Sonarwork runs no ad business, buys no inventory, and embeds no ad trackers in the product or on this site. That is why there is no opt-out switch on this page: an opt-out would imply something is running that you could stop.
No ad business exists
Service providers
The companies above are service providers under §1798.140(ag). They handle the data only to perform the contracted service and are contractually prohibited from using it for their own purposes. Integrations you connect are data sources, not subprocessors. Sonarwork reads from them. Inside your own workspace it sends back only three things: a manager’s brief in Slack, a Slack alert to a person’s manager when one of that person’s signals turns urgent, and events on a person’s own calendar.
11, all published
Your other rights
- Know what we have collected about you in the last 12 months — the data export at /me. Your 1:1 notes and your answers to calendar invitations are not in the export yet: email privacy@sonarwork.com for them.
- Delete it — ask your workspace owner, named on your data page at /me. Only the owner can delete a person’s data in Sonarwork, and it happens straight away.
- Correct it — your profile is editable; signal-level disputes go through /me/disputes.
- Limit use of sensitive personal information — Sonarwork collects none as defined by §1798.140(ae): no government ID, no precise geolocation, no biometrics, no health data, no race, ethnicity or religion. There is nothing to limit.
- Non-discrimination — we will never deny service, charge differently, or give you a worse product for using any of these rights.
Live in the product
Authorized agents
You may use an authorized agent to submit a request for you. We will ask the agent for written authorization signed by you, and may verify your identity directly. Email privacy@sonarwork.com to start.
Written authorization
How we answer
We acknowledge a request within 10 business days and substantively respond within 45 days, as §1798.130(a)(2) requires. For someone with an active Sonarwork account, signing in is enough to verify identity; without one, we may ask you to confirm an email address that matches data we hold.
45 days, in writing
Send one line. We answer in writing.
No portal, no form, no identity hoops. Your work email is enough to find the account.
Last updated . The full privacy policy is at /privacy.