Data boundary
Tenant scoped
Organization records remain attached to the correct workspace.
Privacy
Privacy practices for project data.
Understand what information the platform handles, how organization data is separated, and how access is controlled during normal operation.
Tenant-scoped organization records
Role-based access controls
Responsible operational retention
Privacy
Privacy principle
Tenant-scoped data and role-limited access.
We process only the information required for safe software operations and keep tenant data separated.
Privacy framework
Organization information is handled within clear operational boundaries.
The platform processes the information required to run software development workflows while separating tenant data, controlling access, and maintaining accountability for sensitive actions.
Access model
Role controlled
Permissions are validated before protected data is returned.
Accountability
Audit aware
Sensitive actions can be retained for operational review.
01
Information handled by the platform
The platform stores account details, organization profiles, member roles, project configurations, code repositories, deployment settings, audit records, and client deliverables needed to operate software delivery workflows.
02
How information is used
Data is used to authenticate users, separate organization tenants, authorize team actions, run development workflows, manage deployments, and provide client or stakeholder access.
03
Organization tenant responsibility
Each organization is responsible for entering accurate project details, team members, access controls, and deliverables and for assigning appropriate roles to its members.
04
Access controls
Access is based on authenticated accounts, active organization membership, platform roles, and server-side permission checks. Organization domains resolve to the matching tenant before protected data is loaded.
05
Operational retention
Audit and project records may be retained for accountability, reporting, dispute resolution, and operational recovery according to the deployment operator's retention policy.
06
Support requests
Support may ask for organization name, account email, tenant or domain details, error messages, and workflow context to diagnose issues without requesting passwords.
Privacy and operational responsibility
Organizations remain responsible for the accuracy and appropriate use of the data they enter.
Deployment operators should define retention periods, backup practices, support procedures, and access-review policies that match their legal and operational requirements.