What Sonar reads, what it keeps, and who sees it.

The timing of work, not the work itself. From each tool Sonar takes the events it needs: that a message was posted, that a pull request was reviewed, that a meeting took place.

• Slack: Timing and participants of messages.
• GitHub: Pull request, review and merge cadence.
• Google Calendar: Meeting times and lengths.
• Linear: Ticket movement and cycle time. Built, and switched on when you ask.

One source is enough to start, and this is not the whole list. More are built, and we turn them on for your workspace when you ask.

• The text of any message, in any tool
• Code, diffs and commit messages
• The words in pull requests, reviews, issues and comments
• Meeting titles, descriptions, locations and notes
• The text of documents, pages and tickets
• Direct messages in Slack, including group direct messages

How that holds. Slack and GitHub send each event with the words in it. The moment an event arrives, Sonar keeps only the fields listed in section 03 and drops the rest, before anything is saved. From a Slack message it keeps how long the text was and who it @-mentioned, then drops the text. Nothing later in Sonar can read words that were never saved.

The one exception. The meeting notetaker records and transcribes the meetings it joins. It is off unless your company turns it on, it is invited to each meeting separately, and anyone in the meeting can say no. The privacy policy has the details.

• The person themselves. Every activity record Sonar holds about them, and the signals about them, on their own page. They can download all of it. The one thing they do not see is the leadership-only signals below.
• Their manager. The signals about the people who report directly to them, with the activity behind each one. Never the leadership-only signals.
• Leadership only. Manager health, Team retention risk, Stretch candidate, Onboarding drift and Team collaboration gap are for oversight above the manager. The person a signal is about never sees it, and their direct manager does not see it in their brief or team view.
• No one else. Sonar never sells your data. The companies that help run Sonar, and what each one does, are listed in the privacy policy.

On a schedule. Activity records and the raw events behind them are deleted after 90 days, for everyone, without anyone asking.

When someone asks. A person asks from their own page. Their manager, or a workspace owner or admin, can approve it at once. Nobody can refuse it: if no one acts, it happens on its own after 30 days. The person can cancel until then.

What goes. Their activity records and the raw events behind them, every signal about them, the history Sonar used to learn their usual week, their time-off records, their 1:1 notes and their account. Sonar keeps a record that the deletion happened, not the data.

Pausing works the same way. The person asks, and collection about them stops once their manager or an owner or admin approves. They can resume whenever they like, without asking.

1. Day 0. You connect your tools. Twenty minutes to set up.
2. History. Google Calendar brings some with it: Sonar reads the last 60 days of meetings and the next 30. Slack and GitHub start from the moment you connect. Sonar does not go back through older messages or pull requests.
3. Days 1 to 14. No brief yet. Sonar is learning what a normal week looks like for each person, before it compares anything to it.
4. Day 15. The first brief arrives, and one arrives every weekday morning after that.

Some signals compare a person with their own usual pattern. Those need more history than two weeks, so some start later than the first brief.