Security
Security Measures
Why trusting FlyCI?
To protect your data, FlyCI employs several security measures:
- Your jobs, when using FlyCI Wingman, run in an environment determined by the GitHub runner of your choice
- Your code and data is never saved on our servers after a workflow is completed
- All communication is encrypted
- Our DB has encryption at rest
- Access to our servers is strictly controlled and audited
Data Isolation and Protection
FlyCI Wingman operates within an in the GitHub runner of your choice, ensuring that your code remains secure during failure analysis. The LLM used by FlyCI Wingman is hosted by a third-party AI service, maintaining data privacy. The LLM analyzes the failure log. No additional code or data is shared except if explicitly required by the LLM to complete the analysis.
Data Storage After Workflow Completion
We do not store any of your data after a workflow is completed. This includes your code and secrets. Any data used by FlyCI Wingman is destroyed.
Log Retention for FlyCI Wingman
We retain metadata logs containing information about the analysis done by FlyCI Wingman. The logs do not store any personal or sensitive data. It is the base on which we measure our performance and improve our services over time.
Are FlyCI services SOC2 Compliant?
FlyCI services are not SOC2 compliant yet, but we plan to start working on it. Please, email us at contact@flyci.net in case of interest.
How can I report a security vulnerability?
For details on how to report security issues, please refer to our security.txt