What we collect
RunProof uses account details, incident records, runbook metadata, evidence packets, and approval decisions to provide the product experience. We avoid collecting data that is not needed for those workflows.
Privacy
Privacy built around operational trust.
RunProof is designed to handle incident context with restraint: collect what the product needs, preserve the approval trail, and keep production control visible.
How we use data
Product data is used to authenticate users, prepare evidence-backed recommendations, display audit history, and improve reliability. We do not sell customer operational data.
Operational records
Evidence packets and approvals are retained so teams can review what happened, who approved an action, and why a production step was allowed or blocked.
Access controls
Every console route requires an authenticated session. Access is not partitioned per user or per workspace: any signed-in account can read all incidents, runs, and audit entries in the deployment. Grant accounts only to people who should see all of it.
Data requests
Customers can request export or deletion of account-linked data where legal, security, and audit obligations allow it.
Contact
For privacy questions, contact the project maintainers through the repository or the support channel configured for your deployment.