Here is what TeamPredict reads, and what stays your job.

The LinkedIn signals come from public profiles only.

LinkedIn tracking only reads public profile signals: a new headline or title, an Open to Work badge, fresh skills, a profile refresh. TeamPredict never contacts, messages, or notifies the people you track, and it does not tell them they are being monitored.

The risk score is a prioritization signal, not a verdict. A high score is a reason to start a supportive conversation, never proof that someone is leaving.

Telling your team is your job, and the rules depend on where you operate.

TeamPredict notifies nobody, anywhere in the product: LinkedIn tracking never contacts the employees you track, and Slack team health sends no message either, because it holds no permission to post in your workspace. Telling your team about Slack team health is your job.

Notice and consent rules vary by country, state, and role, and you as the employer are responsible for having a lawful basis and meeting the obligations that apply to your team. You are the data controller. See our Privacy Policy for the data we process and your responsibilities as the data controller.

Slack team health is optional and off until an admin turns it on.

Before it counts a single week, an admin has to confirm in the product that your company has already told its workforce, and we record who confirmed it, when, and the exact wording. We do not verify that confirmation and cannot. Only after it is on record is their history read, up to the last 12 months of their message counts in the selected channels, and there is no opt-out.

The confirmation is recorded, not verified: it is the employer’s statement, not our check. If your admin confirms and nobody was told, the counting still runs, and that is on the employer. TeamPredict holds no permission to post in your workspace and cannot message anyone in it, which is why telling your team is yours to do.

The full detail, including how far back it reads and who sees the numbers, is on the Slack team health page.

Five limits on Slack team health have no setting.

Each one is a permission the product does not request or a field it does not store. There is no plan, no toggle, and no support request that turns any of them on.

• It never reads message text.

  Not the message, not the thread, not the reactions, not a permalink. One integer per person per week is stored, and nothing else.

• It never reads or sends direct messages.

  TeamPredict holds no DM permission at all, and no permission to post anywhere in your workspace. It cannot read a DM and it cannot write one.

• It never uses Slack’s Discovery API.

  The export API that can pull a whole workspace, including rooms nobody in it has joined, is not requested and not used.

• It never records where or when.

  A count does not carry the channel it came from, the person it was aimed at, or the hour it happened. It is a weekly total and that is all.

• It never keeps a count past 18 months.

  A weekly row is deleted 18 months after the week it covers, so the table stays a rolling 18 months rather than a permanent behavioural record. Switching the feature off deletes them all.

What it does do: it reports named individuals to your admins, it reads the private channels your authorizing admin is already in and has selected, it reaches back up to a year into what those people already posted, and it gives the people it counts no choice and no message. Telling them is yours to do, and your confirmation that you did is recorded rather than checked. You remain the data controller.

The legal terms live in two other documents.

The Privacy Policy lists every kind of data we process and how long we keep it, and the Terms set out the rest of the agreement.