Security and Data Protection
Engammo is built with security as a foundational requirement, not an afterthought. We protect your data with encryption, minimal access permissions, and infrastructure that meets enterprise compliance standards. Here is exactly how we handle your data.
Security Principles
Minimal Access
Engammo requests the minimum GitHub permissions needed to function. We require read-only access to pull requests, issues, and repository metadata. We do not request write access to your repositories, and we do not access source code files directly. You can review our permission scope during GitHub App installation and revoke access at any time.
No Source Code Storage
Engammo processes pull request diffs in memory during AI analysis and does not persist your source code to disk or database. Only the generated release note content and PR metadata (title, labels, timestamps, author) are stored. This means that even in the event of a data breach, your source code is not at risk.
Encrypted Infrastructure
All data is encrypted in transit using TLS 1.2+ and at rest using AES-256 encryption. Our infrastructure runs on industry-leading cloud providers with SOC 2, ISO 27001, and SOC 3 certifications. Database backups are encrypted and stored in geographically redundant locations.
Authentication and Access Control
User authentication is handled through GitHub OAuth, ensuring that credentials are never stored by Engammo. Enterprise customers can configure SAML-based SSO through their identity provider. All API keys are hashed and can be revoked instantly. Role-based access control limits what each team member can do within the platform.
Data Handling Practices
What Data We Collect
- Pull request titles, descriptions, labels, and timestamps
- Commit messages associated with merged pull requests
- PR diff data (processed in memory, not stored)
- GitHub user profile information (name, email, avatar)
- Repository metadata (name, owner, default branch)
- Generated release note content
What Data We Do Not Collect
- Source code files or repository contents
- Private keys, tokens, or secrets from your codebase
- Data from repositories not selected during installation
- CI/CD pipeline data or deployment artifacts
- Browser cookies or tracking data beyond basic analytics
GitHub Access Scope
A complete breakdown of the GitHub permissions Engammo requests and why each is needed.
pull_requests:readRead pull request data including titles, descriptions, labels, diffs, and merge status. This is the core permission that enables release note generation.
issues:readRead linked issues referenced in pull requests to provide additional context for AI-generated summaries.
metadata:readRead repository metadata including name, owner, default branch, and tag information for tag-based release note generation.
webhooksReceive real-time webhook events when pull requests are merged, enabling instant release note generation.
Infrastructure Security
Application Hosting
Engammo runs on a modern cloud infrastructure with auto-scaling, load balancing, and multi-region availability. Application servers are containerized and deployed using immutable infrastructure patterns, meaning each deployment is a fresh, verified instance.
Database Security
Databases are encrypted at rest and in transit. Access is restricted to application servers through network-level controls (VPC, security groups). Database credentials are rotated regularly and managed through a secrets management service. Automated backups run daily with 30-day retention.
Monitoring and Incident Response
We monitor application health, error rates, and security events in real time. Automated alerts trigger our on-call team for anomalies. Our incident response process includes detection, containment, eradication, recovery, and post-incident review. Customers are notified of security incidents that affect their data.
Network Security
All external traffic is encrypted with TLS 1.2 or higher. Internal service-to-service communication uses mutual TLS. We use a web application firewall (WAF) to protect against common web attacks. DDoS protection is provided at the infrastructure level.
Compliance
SOC 2 Type II
Our infrastructure and processes meet SOC 2 Type II compliance standards, verified through regular third-party audits covering security, availability, and confidentiality.
GDPR Compliance
We comply with GDPR requirements for data handling. Users can request data export or deletion at any time. We do not sell personal data to third parties.
Data Processing Agreement
Enterprise customers can execute a Data Processing Agreement (DPA) that defines how we handle your organization's data, sub-processors, and data transfer mechanisms.
Vulnerability Disclosure
We maintain a responsible disclosure policy. Security researchers can report vulnerabilities to [email protected]. We acknowledge reports within 48 hours and provide status updates throughout the resolution process.
Related Pages
Frequently Asked Questions
Does Engammo store my source code?
No. Engammo processes PR diff data in memory during AI analysis and does not persist your source code to any storage system. Only generated release note content and PR metadata (title, labels, timestamps) are stored in our database.
What GitHub permissions does Engammo require?
Engammo requires read-only access to pull requests, issues, and repository metadata, plus webhook permissions to receive merge events. We do not request write access to your repositories. You can review the full permission scope during GitHub App installation.
Is Engammo SOC 2 compliant?
Yes. Our infrastructure and processes meet SOC 2 Type II compliance standards. We undergo regular third-party audits that verify our security, availability, and confidentiality controls. Enterprise customers can request a copy of our latest audit report.
How can I report a security vulnerability?
Send vulnerability reports to [email protected]. We acknowledge all reports within 48 hours and provide regular status updates during the resolution process. We follow a coordinated disclosure model and appreciate the work of security researchers.
Can I use Engammo with private repositories?
Yes. Engammo works with both public and private repositories. The GitHub App installation controls which repositories Engammo can access. We apply the same security practices regardless of repository visibility.
How is data encrypted?
All data is encrypted in transit using TLS 1.2+ and at rest using AES-256 encryption. Database backups are also encrypted. API keys are stored as cryptographic hashes, not in plaintext.
Does Engammo support SSO?
Yes. Enterprise plan customers can configure SAML-based single sign-on through their identity provider. We support Okta, Azure AD, Google Workspace, and other SAML 2.0 compliant providers.
Can I request deletion of my data?
Yes. You can request a complete deletion of your data by contacting [email protected]. We will remove all stored data including release notes, PR metadata, and account information within 30 days of the request.
Does Engammo share data with third parties?
We do not sell or share your data with third parties for marketing purposes. We use a limited set of sub-processors for infrastructure (cloud hosting, database) and application services (email delivery). Enterprise customers can request a list of current sub-processors.
How do I revoke Engammo's access to my GitHub repositories?
You can revoke access at any time from your GitHub organization settings. Navigate to Settings > Installed GitHub Apps, find Engammo, and click "Configure" to remove repository access or uninstall the app entirely.
Trusted by engineering teams
Start generating automated release notes with enterprise-grade security. Free for up to 5 repositories.