CASCADE TRUST
Security
We take reasonable steps to protect accounts and release information.
Effective and last updated: 7 October 2026
Protecting access
Cascade uses secure connections and authenticated access. Access to your apps and releases is intended for authorized users and trusted release workflows. We work to keep sensitive information out of public pages and limit access to the people who need it. No service can promise complete security.
Protecting credentials
Sensitive release credentials should stay in secure services such as GitHub Secrets where applicable to your setup. Cascade does not intentionally display secret values in the user interface. Do not paste passwords, signing keys or other credentials into support messages, app descriptions or public content. Check logs before sharing them.
Your part
Protect your Cascade account and the repositories and store accounts you connect. Use strong passwords, keep access limited to trusted people and use additional account protection where available. Review the permissions you grant to integrations. If a credential is exposed, replace or revoke it in the service that manages it.
Need help?
If you notice unexpected account activity or find a genuine security issue, contact us using the address below. Describe what you observed and how to reproduce it without sharing secrets or another person’s private information. Do not access someone else’s account or disrupt the service while investigating. We will review the report and respond as appropriate.
Contact Cascade
For questions, privacy requests or security reports, email cascadeciofficial@gmail.com. Avoid sending passwords, signing keys or provider credentials.