Metadata only · never messages

For your team

Your manager just installed Sonar.
Here’s what it sees, and what it doesn’t.

Finding out a tool is reading your work feels weird, we get it. The short version: Sonar reads patterns, not words. Meeting transcripts only happen when your admin and the meeting host both opt in — you'll see when the bot joins. Four buttons that actually work.

What your manager actually sees

One row in the brief. That’s the whole product.

No second dashboard, no HR export, no “just for the admin” view. The card below is the entire surface your manager has on you.

You · this morning’s briefExample
Gone quiet · 5 days

Out of the pattern, suddenly.

Your usual week: 80–120 messages, 6–10 PR reviews. The last 5 days: 4 messages, no reviews, no PTO marked. Worth checking in.

What this row contains

A label, a few numbers, and one suggested question your manager could ask. No screenshots of your messages, no transcripts, no quotes.

If anything else showed up about you, that would be a bug.

The actual data

What we read. What we don’t.

The same list lives on /privacy with the legal phrasing. This is the friend version.

What we read

  • When you sent stuff

    Timestamps on messages and PRs. Never what you actually wrote.

  • Which channels you're in

    The channel name is hashed before it leaves Slack. We see #chan-7e4f, not #deploy-issues.

  • PR events

    Open / merge / review counts. Not your code, not your commit messages.

  • Calendar shape

    Meeting count and length. Never event titles or notes.

  • Message shape

    Whether it's short or long, has a question mark, lives in a thread. Yes or no, that's all.

What we don’t

  • What you typed

    Slack messages, ever. The text gets dropped before it hits our database.

  • Your code

    Diffs, commits, issue bodies — we see the events, not the words.

  • Meeting topics

    Event titles and descriptions are off by default. The meeting bot is opt-in twice — admin enables it, then the meeting host invites it; the bot announces itself when it joins.

  • Your DMs

    We don't even ask Slack for the permission. Sonar literally cannot read them.

Your buttons

Four things you can do at /me.

No emailing your admin, no support tickets. Click, it happens.

Pause

Stops Sonar reading your data. Effective in under a minute. No email to your admin.

Export

Download everything Sonar has on you. JSON file, same data your manager can see.

Delete

Wipe it. 30-day grace in case you change your mind, then gone everywhere.

Push back

A signal feels wrong about you? Tell us. A real human reads it, not an algorithm.

Honest note from the founder

Hey — if you’re reading this because your manager just told you about Sonar, I get the reaction. “Tool that watches my work” is a no for me too. So I built this one assuming you’d google it.

Reading message text would’ve made the product better in some ways and unshippable in the only way that matters — you knowing your messages are read. So we don’t. The Pause button at /me actually pauses. Those four buttons aren’t a customer-service workaround — they’re the product.

If anything on this page stops being true, that’s a bug in the product. Not the page. Email me directly if you find one.

— Yash · founder · privacy@sonarwork.com

Got a specific question?

privacy@sonarwork.com →

Ready when you are

Your manager will get a brief about you. You get the same view.

The data is about you. The buttons are yours. The opt-out is one click, not a process.

No card · Cancel any time