Last updated: August 13, 2026. This policy details how Ciwrl Technologies LLC d/b/a Spctre handles telemetry, rule configurations, and operational audit trails for autonomous agent systems.
Spctre (operated by Ciwrl Technologies LLC d/b/a Spctre) is a control plane for policy enforcement. To author, simulate, and verify policy decisions, we process the minimum necessary operational metadata:
We collect profile data including your email, name, organization name, and workspace configurations required to manage administrative access, SAML/SCIM settings, and API authentication.
When you author and compile policy rules, we store the policy source code, environment scopes, change histories, pull requests, reviewer credentials, and cryptographic bundle hashes.
For each evaluated decision, we record the agent's identity, target connector (e.g., Stripe, GitHub), requested action (e.g., refund.create), system environment, policy decision outcome, and execution latency. Configured evidence integrations also retain the submitted source event with its mapping version alongside the canonical governance record.
Spctre stores the governance context required by the integration you configure. Generic evidence integrations retain submitted source events alongside mapped governance records, so use mappings and redaction to limit sensitive data before submission.
Local policy evaluation keeps decisions close to your runtime. Gateway and evidence integrations send the data required for the governance and audit workflow you configure.
Our gateway supports standard regex-based redaction patterns, ensuring that identifiers (such as credit cards or SSNs) present in tool names or transaction arguments are masked prior to being logged.
Spctre uses operational data exclusively to deliver, maintain, and optimize the policy control plane. This includes:
Historical event headers are processed to simulate how a proposed policy modification would have changed decisions in the past, allowing you to dry-run rules safely.
Durable chains of custody are created to let compliance officers inspect which policy bundles allowed or blocked an action, when review requests were resolved, and by whom.
Calculating execution latencies, rate-limit thresholds, and workspace volume stats to guarantee that Spctre gateways meet the high-availability demands of autonomous system architectures.