Security
Trust starts with a boundary the system cannot quietly reinterpret.
GLoops is an early product. This page states the operating posture we use for design-partner work without claiming certifications or controls we have not earned.
Operating posture
- Least authority: pilots receive only the systems, actions, spend, and time window required for the agreed workflow.
- Fail-closed execution: missing or ambiguous authority stops consequential work instead of widening the grant.
- Independent review: consequential delivery and authority claims require a reviewer separate from the implementation path.
- Inspectable records: material decisions and outcomes produce evidence and receipts suitable for audit by the customer.
- Separate publication: customer context is not public proof. Publication requires an explicit client-safe decision.
- Revocation: authority can be narrowed or withdrawn when evidence, conditions, or customer direction change.
Data and access
Pilot-specific access, retention, systems, identities, and deletion expectations are documented before work begins. GLoops does not ask for unbounded credentials as a condition of a pilot.
Responsible disclosure
Send a concise description, affected surface, reproduction details, and potential impact tohello@gloops.ai. Please avoid including secrets or personal data in the initial message. We will acknowledge a credible report and coordinate a safe next step.