Privacy Policy
This page describes how the Orbyt workspace handles internal account information, workflow data, and connector-imported context.
Information We Collect
Orbyt collects account details such as name, work email, role, and team assignment. When the workspace is used, it also stores operational records created inside the product, including backlog items, tasks, defects, releases, pods, governance settings, and internal documentation.
How We Use Information
We use this information to provide authenticated access, support workflow routing, enforce role-based permissions, maintain delivery records, improve operational visibility, and keep internal collaboration features working as intended.
Connector and Integration Data
If connectors are enabled, Orbyt may process imported metadata and content from approved integrations such as email, chat, calendar, meetings, and files. Imported records are used as internal operational context and evidence within the product and are not intended for public distribution.
Internal Access and Governance
Access to information is governed by internal roles and access groups. Users can only view or edit data that their assigned permissions allow. Administrative users may manage access policies, user roles, and system settings.
Data Retention
Operational records are retained for as long as needed to support internal delivery tracking, auditability, governance, and system maintenance, unless your organization requires a different retention schedule.
Security
We use authentication, permission controls, and system-level safeguards intended to protect internal records from unauthorized access. No system is perfect, so organizations should also follow their own credential, device, and access management policies.
Contact
If your organization needs changes to this policy or wants a more specific legal review, contact the internal administrator or product owner responsible for the Orbyt deployment.