AssureRun / Trust & clarity
Security & data handling
A clear boundary before any access is discussed.
Public demonstration boundary
The public Guard experience uses synthetic workflows, evidence and metrics. No credentials, account registration or customer production connection are requested in the demonstration.
Before a real pilot
Real customer data remains on hold. A real pilot is subject to security approval, approved scope and an agreed access boundary. A synthetic demonstration is not evidence that all real-world integrations are ready.
Minimized evidence by design
The proposed approach uses only evidence needed for an agreed outcome contract, such as pseudonymous event keys, states, timestamps and acknowledgements. Actual categories, retention and access must be documented for each approved pilot.
Monitoring and remediation
The proposed initial scope is read-only monitoring of 1–3 non-critical workflows. Remediation, replay or other changes require separate explicit approval.
Assurance limitations
We do not claim certification, independent security endorsement or guaranteed failure prevention. Independent assessment is pending. Hosting providers may retain operational request metadata outside application-level controls; provider-specific retention must be confirmed before a real pilot.
Report a concern
Contact pilot@assurerun.com with a concise description. Do not include secrets or real customer payloads, and do not test private or third-party systems without permission.