Security

Controls begin with a deliberate scope.

Angada reads repository content and pull-request context for the repositories your workspace connects, then returns review, documentation, or coordination output to the surfaces you configure.

What to review before connecting.

The right security conversation is specific to your repositories, workspace, and enabled products. We’ll answer questions at [email protected].

Repository scope

Choose which GitHub repositories are connected. Review and Wiki use the source context required for the product flow you enable.

Output scope

Review output is posted back to the pull-request workflow; Wiki output stays in generated documentation; coordination can route to configured Slack destinations.

Workspace controls

Access, product availability, and integration settings are governed by the connected workspace and its enabled entitlements.

A security conversation for your team.

Contact us for AI processing, retention, and security review details that matter to your team.

AI processing

AI Review and AI Wiki process repository content to produce findings or documentation. Contact us for the processing details that apply to your workspace.

Connected services

GitHub and Slack remain third-party services with their own terms. Read our published Privacy Policy and contact us for AI-processing details.

Questions welcome

Email [email protected] for repository scope, AI processing, access, or security review questions.