Current operational status of Release Assurance and the security commitments we make to every customer.
Last updated: April 17, 2026
Live status across the services your team relies on.
We treat your data, your credentials, and your Salesforce org as if they were our own. Here is what that means in practice.
Security is built into every layer of the service, reviewed continuously, and prioritized above new-feature work when the two conflict.
Your data is logically isolated from every other customer at every layer — storage, query, and access control — with automated regression tests guarding that boundary.
Access to production systems is tightly scoped. Only a small set of authorized personnel can reach customer-affecting infrastructure, and every access path is logged.
All customer data is encrypted in transit with TLS and encrypted at rest. Secrets and credentials are stored in a dedicated secret-management service.
We use short-lived, tokenized access to your Salesforce org and never retain long-lived refresh tokens. Access tokens are kept in memory only.
We collect only what is needed to run the service. Test artifacts are retained for the shortest period that still supports your debugging and compliance needs.
Monitoring, alerting, and automated health checks run 24/7 across multiple regions. On-call engineers are paged within minutes of any customer-impacting degradation.
When something goes wrong, we tell you. Confirmed customer-impacting incidents are disclosed to affected tenants within 72 hours.
A summary of the security controls we operate today. The exact implementation details are kept private, but every item below is enforced in production.
Past 90 days.
Questions about security or a live issue? Reach us directly at security@ReleaseAssurance.com. For full technical detail on our security posture, see our Security page.