At Prewind, we take your privacy, security, and safety seriously.

We adhere to Privacy by Design principles and embrace a Safety by Design approach, ensuring safeguards are integrated into everything we do, from how we design our products to how we deliver our services.

Your data, your choice

Integrating diverse data sources can enrich insights and help build optimal suggestions. Users nevertheless retain control over which data sources to integrate. Types of data we access include: Communication applications,

No unnecessary data retention

Personal data is kept only for as long as necessary to fulfill the purposes outlined in Prewind’s privacy policy statement or as required by law. The specific retention periods for each type of data may vary and will be reviewed periodically to ensure compliance with relevant regulations and industry standards.

Integration, not new monitoring

Rather than conducting additional monitoring, Prewind integrates your existing data sources. We exclusively utilize data derived from tools you already use every day.

What types of data do you access?

Communication applications such as Public Slack channels and MS Teams channels and discussions
- Many people collaborate on platforms like Slack or MS Teams at work. By studying how they communicate, we can suggest better ways to work together. This data helps us see how different parts of the company work together, but we only keep basic information like who sent a message, when, and who they talked to – we don't read the messages themselves."
Calendar meetings on platforms like Google and Outlook
- By analyzing patterns of communication, we discover employee collaboration patterns. This enables us to give better recommendations to employees. When we put it all together, we see how the company fits together, like who works with whom across teams and the business as a whole. We only store who's in a meeting and when, but we don't keep what the meeting's about or any private calendar info.
Project management tools including Linear and Jira
- These applications provide crucial insights into workplace collaboration and project progress. By integrating their data, we understand team interactions, task completion rates, and productivity. We keep our focus to ticket data, such as status, lead time, owner, and contributors. Title, description and other text content in tickets is analyzed for keywords, but the ticket content is not stored.
Business metrics in CRM tools like Hubspot and Salesforce
- CRM platforms offer insights into customer interactions and sales pipelines. We analyze sales opportunities, including ownership, value, and cycle time, to gauge pipeline health—a critical success measure. Combining this data with collaboration patterns yields unique insights, like the impact of specific team members on meeting outcomes.

Can we add just some data sources?

Yes, customers can control what data to include. Our hypothesis is that incorporating additional data sources will enhance the accuracy of the model and its recommendations.

Does this infringe on our employees’ privacy?

No, all of the data Prewind handles already exists on different platforms and is accessible and usable by the employer and employees. By bringing together this pre-existing data, our platform enables users to view a more comprehensive picture of their information all at once.

Do you store Patient Health Information?

No. We do not access, utilize, or retain any patient health information. Even if such data exists within a customer's CRM or Project Management system, we configure integrations to ensure no access or storage of this information occurs.

Does this impact employee behavior

Yes, ideally. We aim to identify key drivers of organizational success and guide leaders and teams to focus their efforts where they can make the greatest positive impact.

For instance:

When an employee understands responsiveness in Slack counts as increasing the strength of a relationship, they can become more responsive. We believe this is a positive outcome.
When a customer service rep knows their contribution impacts project management ticket flow, they may be inclined to make higher quality tickets.
When a product manager knows their participation is noted in sales deal flow, they know that preparing for calls is important.

Who uses the system? Leaders or everyone?

Our goal is to ensure that our product benefits all members of an organization. One way is by offering automated suggestions aimed at creating positive impacts, such as generating customized discussion points for 1-1 meetings. Initially, these features and visibility are developed for admin users, such as CEOs and other executives.

Do we have to tell employees and how do we tell them?

Yes, we root for transparency in every direction. It’s a good idea to tell employees that you’re analyzing data in the CRM, Project Management solution, Slack, Calendars, and possibly other tools. You’re probably already doing this by analyzing sales results in CRM, for example. It’s also a good idea to tell the employees you’re piloting Prewind for advanced cross-platform analytics.

What conclusions can you make from the data?

"Instead of giving definite 'good' or 'bad' labels, we focus on asking the right questions and sparking helpful discussions. We also keep an eye out for any potential issues by looking at how people work together across different tools. By putting together all this info, we build a big picture of how the organization operates. Plus, we track how teams and individuals are doing and think about any risks involved. And to make our product even better, we're using a Graph Neural Network, an advanced AI model, to predict how work will turn out based on what's been done."

Where is your official documentation?

Privacy Policy: https://teamspective.com/privacy-policy/
Information Security Policy: https://teamspective.com/information-security-policy
Data Processing agreement: https://teamspective.com/dpa/