oNabu operates on Google Cloud Platform and Microsoft Azure, ensuring secure data storage and processing.
Data Processing & Retention
oNabu does not store sensitive company information and processes data only when explicitly authorized by administrators.
Jira Integration: If an administrator enables access, oNabu reads task management data, processes it to generate reports, and does not store any sensitive company data.
Meeting Integration: If an administrator enables access, oNabu joins scheduled Zoom, Google Meet, or Microsoft Teams meetings, processes meeting discussions, and deletes all meeting data after reports are generated.
All reports and insights are shared only with the company's authorized users.
Personally Identifiable Information (PII)
oNabu does not require personally identifiable information beyond what is necessary for user authentication.
Only an email address is required for login.
Name, surname, and phone number are optional fields.
Administrators have full control over what data oNabu can access.
Jira Access: oNabu’s access is determined by the administrator and is limited to the data that Jira permissions allow, but it does not provide additional project- or user-level restrictions beyond what is configured in Jira.
Meeting Access: Teams can enable or disable meeting participation based on company policies.
oNabu does not require admin-level access to company systems.
Jira Integration & Permissions
oNabu requires read-only access to specific Jira data necessary for Agile insights. It does not modify any Jira data.
Permissions include: - Boards & Backlogs – Project boards, backlog items, and sprint configurations. - Issues & Tasks – Issue types, comments, attachments, worklogs, and status tracking. - Project & Sprint Data – Project structures, versions, security settings, and sprint data. - User & Team Info – Team roles, assignments, and workload distribution for Agile insights.
