Mergify respects our customers' privacy, and keeping our customers' data protected at all times is our highest priority.
This security policy provides a high-level overview of the security practices put in place to achieve that objective.
Have questions or feedback? Feel free to reach out to us at email@example.com
All of our services run in the cloud. We don't host or run our own routers, load balancers, DNS servers, or physical servers.
Security Assessments and Compliance
Mergify is part of the GitHub Marketplace. To this end, Mergify security has been reviewed by the GitHub security team.
Encryption in transit
All data sent to or from our infrastructure is encrypted in transit via industry best-practices using Transport Layer Security (TLS).
Encryption at rest
All our user data (including tokens) is encrypted using battled-proofed encryption algorithms in the database.
We back up all our critical assets and regularly attempt to restore the backup to guarantee a fast recovery in case of disaster. All our backups are encrypted.
Application Security Monitoring
We use technologies to monitor exceptions, logs, and detect anomalies in our applications.
We collect and store logs to provide an audit trail of our applications' activities.
Our development process follows security best practices and frameworks. We use the following best practices to ensure the highest level of protection in our software:
Developers participate in regular security training to learn about common vulnerabilities and threats;
We review our code for security vulnerabilities;
We regularly update our dependencies and make sure none of them has known vulnerabilities;
We monitor application components (dependencies) for known vulnerabilities.
As part of our commitment to working with security researchers to make our platform safer, Mergify operates a bug bounty program to reward those who find and report bugs in our platform.
We encourage everyone that practices responsible disclosure and comply with our policies and terms of service to participate in our bug bounty program.
Please avoid automated testing and only perform security testing with your own data. Please do not disclose any information regarding the vulnerabilities until we fix them. Rewards are done at our discretion, depending on the criticality of the vulnerability reported.
You can report vulnerabilities by contacting firstname.lastname@example.org. Please include a proof of concept. We will respond as quickly as possible to your submission and won't take legal actions if you follow the rules.
- Cross-Site Scripting (XSS)
- Open redirect
- Cross-site Request Forgery (CSRF)
- Command/File/URL inclusion
- Authentication issues
- Code execution
- Code or database injections
- Account/email enumerations
- Denial of Service (DoS)
- Attacks that could harm the reliability/integrity of our business
- Spam attacks
- Clickjacking on pages without authentication or sensitive state changes
- Mixed content warnings
- Lack of DNSSEC
- Content spoofing
- Text injection
- Timing attacks
- Social engineering
- Insecure cookies for non-sensitive cookies or 3rd party cookies
- Vulnerabilities requiring exceedingly unlikely user interaction
- Exploits that require physical access to a user's machine
We provide authentication through GitHub only and rely on their security to protect our users.
All payment instrument processing is safely outsourced to Paddle, which is certified as PCI DSS SAQ A Compliant. We don't collect any payment information and are therefore not subject to PCI obligations.
Our strict internal procedure prevents any employee or administrator from gaining access to user data. Limited exceptions can be made for customer support.
Our employees sign a Non-Disclosure and Confidentiality Agreement to protect our customers' sensitive information.