Your data

What Alyn can and cannot see.

The first question every leader asks is what this thing reads. Here is the whole answer, in the order people ask it, so you can forward this page to whoever has to approve the install.

The short version

Alyn does not read your message history. Its signal comes from short weekly check-ins that each person approves before anything is shared. No data files, no silent monitoring, and nothing is reported up that the person doing the work did not sign off on.

What Alyn sees

  • The weekly check-in each person writes and approves.
  • The company priorities leadership has set, which you enter when the workspace is configured.
  • Which team a check-in belongs to, so drift can be read by team and by goal.

What Alyn does not see

  • Your message history, in channels or in DMs.
  • Anything a person wrote and chose not to approve.
  • Files, documents, or attachments.
  • Activity captured in the background. There is no passive collection anywhere in the product.

Who sees what

The weekly read goes to the leader who owns the priorities. It carries what the team approved, aggregated against the goals, and the blind spot when a stated priority has no team reporting on it. A person's individual check-in is theirs; the read is about whether the work is moving toward the plan, not about how any one person is performing.

The distinction matters more than it sounds. An instrument people have to be protected from produces numbers nobody will act on. Alyn is built so nobody needs protecting from it.

We were wary of anything reading Slack. The person doing the work approving what gets shared is what got it past my team.

VP Operations

What your team controls

Each person approves their own check-in before it is shared, every week. Approval is the mechanism, not a setting someone can flip on their behalf. If a person skips a week, nothing is inferred from the silence; the read simply shows that a team has gone quiet, which is itself a signal worth seeing.

Where Alyn runs

Alyn runs in Slack today, installed as an app in your workspace, and it goes only where you install it. Microsoft Teams is next, and it lands before a pilot started today would finish. If your evaluation depends on Teams specifically, say so in the first call and we will be straight with you about timing.

Still in design-partner pilots. Alyn is early and says so. If your security review needs documentation we have not published yet, ask for it directly and you will get a straight answer about what exists today and what does not. hello@alyn.app

The formal policies

How information from this website and from forms is collected, used, and retained is covered in the privacy policy, and the terms of use are here. This page describes the product; those describe the agreement.

Questions your security team would ask?

Bring them to the first call. Twenty-five minutes, and we would rather answer them early than have them surface halfway through a pilot.

Book 25 minutes hello@alyn.app