Privacy & security
What the Angada GitHub App can access, how your code is used, and how to report an issue.
What the GitHub App can do
The Angada GitHub App requests three permissions:
| Permission | Level | Used for |
|---|---|---|
| Contents | Read | Reading diffs for review and wiki generation |
| Metadata | Read | Repo, branch, and PR structure |
| Pull requests | Write | Posting review checks and findings |
That's the whole list. No admin rights over your repositories, no write access to code.
What the Slack connection can do
Angada joins your Slack workspace through the standard OAuth consent screen you approve during setup. It posts messages — living PR cards, digests, reports, nudges — into the channels you route to. One Angada Workspace connects to exactly one Slack workspace.
How your code is used
Your code is read to produce the things you asked for: review findings on pull requests, and wiki pages for your repositories. Those outputs go back to your Workspace and nowhere else.
For the complete picture, read the legal and security pages on the marketing site:
Your privacy choices
Angada asks for three optional choices. Each is independent, and recording and analytics are off until you opt in. Existing accounts keep their saved product-update preference:
- Onboarding session recording: records your onboarding pages only, with inputs masked. It starts only after you opt in.
- Optional product analytics: browser usage analytics, separate from recording and from the processing needed to run your account.
- Product updates: marketing emails.
You choose during onboarding, and "Continue with choices off" is always available. To change a choice later, go to Settings → Profile → Privacy and save. Turning off analytics or recording stops capture straight away. If your choices can't be loaded, nothing is captured.
Reporting a security issue
Email [email protected] with the details. Report suspected vulnerabilities privately, not in public issue trackers — we'll respond and work the fix with you.