Privacy Policy

TeamPredict (“TeamPredict,” “we,” “us,” or “our”) provides a B2B software service that helps employers identify early signals of employee resignation risk. It does this by analyzing publicly available LinkedIn profile activity and, where a customer switches on our Slack team health feature, by counting how many messages each of that customer’s employees posts in Slack each week. This Privacy Policy explains what data we collect, how we use it, the legal framework that applies, and the choices and rights available to data subjects. The service is operated by Sensei Capital LLC.

For data about our customers’ own account users (for example, the HR or People team members who sign in to TeamPredict), we act as a data controller.

For data about the employees that a customer chooses to track (“Monitored Individuals”), the customer is the data controller and TeamPredict acts as a data processor that processes that data only on the customer’s documented instructions. The customer is responsible for establishing a lawful basis for monitoring and for providing any notices required by applicable law.

• Account data. Name, work email, company name, and authentication details for users who create a TeamPredict account.
• Billing data. Subscription, plan, and payment metadata. Card details are handled directly by our payment processor (Stripe); we do not store full card numbers.
• Monitored Individual profile data. Publicly available LinkedIn profile information for the individuals a customer chooses to track, such as name, headline, current and past roles, employer, location, skills, and changes to these fields over time. This profile data is obtained through a third-party LinkedIn data API (provided via RapidAPI), not by TeamPredict logging into LinkedIn on a customer’s behalf.
• Derived analysis. Resignation-risk scores, flags, and summaries that we generate from the profile data described above.
• Slack message counts. Where a customer enables Slack team health, we collect one number per person per week for the people in that customer’s Slack workspace: how many messages they posted that week in the channels the customer selected. Those channels are the workspace’s public channels, plus any private channels the customer’s authorizing admin is already a member of and has selected. These counts are not limited to the weeks after the feature was switched on. Once an admin at the customer has confirmed to us that the customer has told its workforce (see Section 5), and only then, we read those people’s message history in those channels backwards and reduce it to the same weekly counts, covering up to the preceding 12 months. How far back that reaches in practice depends on the customer’s Slack plan, because Slack serves a free workspace roughly 90 days of channel history and paid plans more; we record the oldest week we actually reached and report that, and we do not fill in weeks Slack did not serve. Alongside each count we store the person’s Slack user id, their Slack display name, and their department where they match someone on the customer’s roster, and we derive a usual level from their trailing weeks and how far below it they currently sit. Each counted person is reported by name to the admins of that customer’s TeamPredict organization. Message content is never collected. We do not read, store, or log the text of any message, thread, or reaction, we keep no permalinks, and a count does not record which channel a message was posted in or at what time of day.
• Slack credentials. The Slack bot token issued when a workspace is connected and, where private-channel counting is authorized, the personal Slack user token of the admin who authorized it. Both are encrypted at rest. A user token reaches only the channels its own owner can already read.
• Usage and device data. Standard log data such as IP address, browser type, and product interactions, used to operate and secure the service.
• Product analytics and session activity. To understand how our website and app are used and to improve them, we record pages viewed, buttons and links clicked, and feature usage, along with a first-party analytics identifier. We also capture session replays: recordings of on-screen interactions (clicks, navigation, scrolling) with keystrokes and form-field contents masked. This is processed by our analytics provider, Mixpanel.
• Advertising measurement. When you reach us from one of our ads, we record that the visit came from that ad and whether it led to a free-trial signup, so we can measure what our advertising achieves. This uses Google Analytics and Google Ads. If you start a free trial, your email address is converted into an irreversible code (a one-way hash) in your own browser and only that code is sent to Google, so Google can tell that a signup came from an ad without us handing over your email address itself. We do not sell personal information.

We use data to:

• Provide the core service: analyzing public LinkedIn profile signals to produce resignation-risk insights for our customers.
• Where a customer enables Slack team health, count each person’s weekly Slack messages in the selected channels, including up to the 12 months preceding the date the customer asked for that history, and show those counts, their usual level, and their current trend by name to that customer’s TeamPredict admins. Slack counts are reported on their own and are not an input to the resignation-risk score.
• Send product communications, including risk alert emails when a tracked employee’s resignation risk spikes and a recurring digest email summarizing risk flags.
• Process payments and manage subscriptions.
• Secure, maintain, debug, and improve the service, and comply with legal obligations.

The purpose of processing Monitored Individual data is resignation-risk analysis and, where the customer has enabled it, Slack team health reporting, in each case as instructed by the customer.

Where data protection laws such as the GDPR or UK GDPR apply, processing of Monitored Individual data is carried out on behalf of the customer, who is the controller and is responsible for identifying the appropriate lawful basis (for example, a legitimate interest assessment) and for meeting transparency and notice obligations to its workforce. For our own controller processing (account and billing data), our bases include performance of a contract and our legitimate interests in operating and securing the service.

For Slack team health, telling the workforce is the customer’s job and not ours. TeamPredict sends no message to anyone. It holds no Slack permission to post, so it cannot notify a counted person even if it wanted to, and it does not contact them by any other route either. What the product does instead is refuse to read anything until an admin at the customer confirms, inside the product, that the customer has already told its workforce through its own channels: that their weekly message counts in the selected channels are being recorded and shown by name to admins at their employer, that up to the preceding 12 months of those counts may be read, and that they cannot opt out. We record which of the customer’s TeamPredict users confirmed it, the date and time, and the exact wording they agreed to. Until that record exists, nothing about any person in that workspace is read or stored, this week or last year.

That confirmation is the customer’s claim and not proof of anything. We do not verify it, we have no way to verify it, and we do not know whether any particular person was in fact told. If a customer confirms and has told nobody, the counting still runs, and answering for that gap falls to the customer as controller. Nor is any of this a consent request: there is no setting anywhere in the product that lets a counted person decline or stop the counting, and only their employer can switch the feature off. If consent is the lawful basis a customer needs, this feature does not establish it.

We use the following third-party sub-processors to deliver the service. Each is engaged under terms requiring appropriate safeguards:

• Stripe. Payment processing and subscription billing.
• Resend. Transactional and digest email delivery.
• Amazon Web Services (S3). Data storage and hosting infrastructure.
• Anthropic. AI processing used to generate risk analysis and summaries.
• RapidAPI. Third-party LinkedIn profile data API used to retrieve public profile information.
• Slack. Workspace API used, for customers who enable Slack team health, to read the message activity of the selected channels. We hold no permission to post in a customer’s workspace and send nothing to anyone in it.
• Mixpanel. Product analytics and session replay used to measure and improve how our website and app are used.
• Google. Google Analytics for website reporting, and Google Ads for measuring which advertising leads to a free-trial signup.

We retain account and billing data for as long as a customer maintains an active account and as required to meet legal, accounting, or reporting obligations. Monitored Individual profile data and derived analysis are retained while the customer continues to track the individual; when tracking stops or an account is closed, we delete or de-identify the associated data within a commercially reasonable period, subject to backups and legal requirements.

Slack weekly message counts are deleted 18 months after the week they cover, so what exists at any moment is a rolling 18 months rather than a permanent record. That window covers a backfilled year of history plus roughly six months of ongoing weeks before the oldest weeks begin falling off the back. Switching Slack team health off deletes that customer’s counts outright and withdraws the confirmation described in Section 5 with them, so nothing is counted again until an admin confirms afresh.

If a customer’s subscription or trial ends without the account being closed, we may continue the daily refresh of that customer’s tracked roster for up to 60 days so the customer can reactivate without losing continuity. During this window the customer receives no monitoring alerts (at most a few summary emails containing aggregate counts, never individual names), and monitoring stops entirely when the window ends. A customer can ask us to stop the refresh and delete the associated data sooner at any time using the contact details below.

Depending on your jurisdiction, you may have rights to access, correct, delete, or restrict processing of your personal data, to object to processing, and to data portability. Because we process Monitored Individual data on behalf of our customers, a Monitored Individual exercising rights with respect to that data should generally direct their request to the customer (the controller); we will assist the customer in responding. You can also contact us using the details below and we will route your request appropriately.

Slack team health has no opt-out. A counted person cannot stop the counting from inside TeamPredict, and we will not stop it on their instruction, because the customer is the controller and the decision is theirs. A request to stop being counted has to go to their employer.

We use technical and organizational measures designed to protect data, including encryption in transit, access controls, and least-privilege practices for our infrastructure. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

Our application uses strictly necessary, functional cookies to keep you signed in and to maintain your session. We also use first-party analytics cookies set by our analytics provider (Mixpanel) to measure product usage and to connect a visit to our marketing site (teampredict.ai) with subsequent use of the app across our subdomains.

We also set first-party advertising-measurement cookies through Google Analytics and Google Ads. These record that a visit arrived from one of our ads so we can tell which advertising leads to a free-trial signup. We do not sell personal information.

You can control cookies through your browser settings, and we honor the browser “Do Not Track” signal for our own product analytics. Disabling functional cookies may prevent you from signing in.

Data may be processed in countries other than where you are located, including the United States. Where required, we rely on appropriate transfer mechanisms for such processing.

We may update this Privacy Policy from time to time. Material changes will be reflected by updating the “Last updated” date above.

For privacy questions or requests, contact us at privacy@teampredict.ai. Postal address: Sensei Capital LLC, 2013 Live Oak Blvd, Saint Cloud, Florida 34771.