Limited data collection
Rapid RUSLE is designed around the stormwater workflow it supports: account details, project metadata, RUSLE inputs, calculation outputs, inspection scheduling records, generated reports, and operational logs.
Trust and security
Last updated: June 2026
Rapid RUSLE keeps customer data focused on the workflow it supports: RUSLE inputs, project metadata, inspection scheduling records, and calculation or report outputs. This page summarizes the current trust posture for buyers, reviewers, and implementation teams.
Rapid RUSLE is designed around the stormwater workflow it supports: account details, project metadata, RUSLE inputs, calculation outputs, inspection scheduling records, generated reports, and operational logs.
The product supports preparation, review, and documentation. It does not replace qualified professional judgment, permit obligations, or project specific verification.
Application traffic uses HTTPS with security headers including HSTS, content security policy, frame protection, and content type protection.
Production access is limited to approved technical operators. Secrets are kept out of source control and administrative access is kept separate from customer accounts.
Customer project data is retained while an account is active. Export or deletion requests can be handled by written request, subject to legal and operational constraints.
If a security issue occurs, we identify and contain the issue, preserve relevant evidence, assess customer impact, remediate the cause, notify affected customers when appropriate, and document the follow up actions.
Rapid RUSLE uses a small set of infrastructure and product vendors to operate the service. The exact vendor list can change as product capabilities evolve, but the current categories include:
These answers are intentionally conservative. We would rather be clear about the current posture than overstate controls that have not been formally audited.
Not at this stage. Rapid RUSLE is taking a practical security first approach while enterprise requirements are validated. If SOC 2 becomes required for a customer deployment, we are prepared to scope that path with a compliance platform and independent auditor.
Not in the current self serve product. If an enterprise buyer requires SSO, it can be scoped as part of an enterprise deployment.
Core RUSLE calculations are deterministic and reviewable. Rapid RUSLE does not rely on customer project data to train AI models. If AI assisted features are added, we will document what data is sent, to whom, for what purpose, and whether it is retained or used for training.
Yes, by written request. Self serve account export and deletion capabilities may vary by product area, so support can help route requests and confirm the practical steps for a specific account.
For enterprise deployments, we can provide a practical trust review, confirm required controls, and scope any buyer specific assurance needs before rollout.
Contact Rapid RUSLE