At Sike Insights, we take data privacy very seriously.

<aside> 🔢 Learn about our encryption standards and how we protect our customers.

</aside>

Get the following information in an easily shareable PDF:

How We Use Data.pdf

Kona Data Privacy_Security Checklist - Sheet1.pdf

How we use data, an overview

What will Kona be able to view?

• View workspace members' basic info on Slack: We need to be able to see each Slack member ID and link it to that person’s personality. [Beta only]
• View email addresses: If a user allows us to store their email IDs, we also store this information in case we need to reach out for feedback.
• Read all public channel messages: We analyze all messages sent in public channels on Slack to generate Kona profiles. We need to have access to this information but none of it is ever logged or stored.
• View messages in DMs/private channels Kona has been added to: Some users prefer to use Kona in private channels or DMs. Users must invite Kona to each private channel or DM in order for Kona to access this information.

What will Kona be able to do?

• Send messages to relevant channel members and store responses: We ask survey questions about work style preferences to each member of the channel(s) to which Kona has been invited. We store user responses to our questions.
• Perform actions in your workspace: Kona can perform quick-actions with slash-commands.

Third-party Services

• IBM Watson: We use IBM Watson’s Personality Insights API in order to get personality data on each member of the team. Watson does not store any information we send to them to improve their service. Here is a note from their API documentation:

  

• Segment/MixPanel: We use Segment and MixPanel to track usage statistics so we can understand how and when our product is being used.

How is data used?

When you install Kona to your Slack workspace, Slack sends an access token to our server, hosted on an Elastic Compute Cloud (EC2) instance using Amazon Web Services. We use this token to authenticate and obtain access to relevant information such as channel members and public channel conversations.

Messages sent on all public channels are sent to our server, where we analyze them using IBM Watson’s Personality Insights service. Messages are never read by a human being or stored in our servers. Only the personality data returned to us by this service is stored in a DynamoDB database.

We also send a few questions to each member of the channel(s) to which Kona has been invited. The responses to these are stored in the DynamoDB database as well.

When a user runs a /kona- command, the personality data from the database is used to generate the relevant insights on our server, which get sent to them in Slack.