Current pilot posture
Security & data handling
RightBounds is being validated with a deliberately narrow access model. Early Review Capacity Audits are designed to work from historical, exported or read-only evidence wherever practical.
Minimum access
Initial audits do not require production write access. Teams can begin with public repositories or redacted exports. Private repository access should be read-only where feasible, and the exact access requested is agreed before a pilot starts.
Source code
Do not submit source code through the website pilot form. Source and data-retention terms for any private pilot material are agreed explicitly before transfer.
Secrets
Never send production secrets, API keys, credentials or authentication material through the website or an initial outreach message.
Data minimisation
The goal is to use the least evidence necessary to understand task intent, agent actions, changed artefacts, verification performed, human review and known outcomes.
Vulnerability reporting
If you believe you have found a security issue affecting this website or an agreed pilot workflow, email security@rightbounds.com. Do not include credentials, live customer data or exploit material in the first message; we will arrange an appropriate channel.
CURRENT STAGE
RightBounds is currently an early-stage pilot product. Security architecture and controls will evolve before any broader self-service deployment.
Start with non-confidential context.
The pilot form asks about workflow shape—not source code.