Skip to main content
All CollectionsPrivacy and Security
Akooda Privacy Principles
Akooda Privacy Principles
Akooda avatar
Written by Akooda
Updated over a year ago

If you happen to read our Integration Principles you know that we have a zero-compromise policy when it comes to our customer data’s security and privacy. This is no less true to our ethical guarantee when it comes to employee data.

Below are the key principles that guide each of our product decisions.

If you have any questions, please don’t hesitate to reach out to our support team at [email protected].

Transparency on Visibility

Any organization has its own set of rules and expectations around the different tools in which we communicate, and Akooda respects that. In some tools, public communication is the default (e.g. Jira or Github), and in others, private communication is the default (Emails).

In Akooda, we respect the differences of each tool, and never bypass existing permissions. You and your organization are the only ones who control the publicity of your data based on the media in which you communicate; Akooda adheres to these settings from the very first step.

By integrating apps with Akooda, the public footprint in your organization is made more accessible and visible. This allows you to reap countless benefits such as inclusion in cross-team initiatives, improved collaboration, and ease of search. Our focus as a company is forever on positive impact.

Private interactions are only featured either as part of aggregated proxy metrics or in a more descriptive personalized view shown only to their direct collaborators - as noted in our next three central principles.

Data Collection

Akooda is not and cannot be utilized to be an employee monitoring software. Every attribute collected and shown in the platform is done so with the employees’ privacy in mind and from work-only tools. We do not track time spent by individuals across apps, and we do not process direct messages.

What we do keep is:

  • Topic/subject which is the start of public conversations, the title of the ticket, name of a branch, etc.

  • List of topics recognized, as part of a collection opted-in by the Akooda account admin and are shared across the organization

  • List of internal/external people active in the interactions, opted-in by the Akooda account admin, and are shared across the organization

  • Pointers (links)to the apps that Akooda integrates with, that are accessible to anyone with a valid user such that they have the right permissions

Proxy Metrics

Unlike performance trackers which use time trackers, we utilize multiple data points to assess Akooda proxy metrics such as the volume of an individual's activity in interaction and its potential significance. Our databases don’t contain any raw data on a per-employee level.

In time, these metrics are used to drive insights and trigger push notifications to the right individual based on their position in the organization and the people/topic they interact with. These metrics are non-indicative and cannot be directly correlated with performance/velocity - and thus are non-intrusive and not selective.

Personalized Views

Akooda never bypasses existing permissions. If certain interactions in specific apps are only visible to a finite list of people, the same group of people will be able to see and access those in Akooda.

We identify these types of features as “Personalized Views” and you can expect to see these labels and matching lock icons throughout the platform whenever the display is restricted by user access controls.

Your security settings remain with you, at all times, regardless of Akooda.

Did this answer your question?