Schema gate
Unknown fields and unsafe values fail validation before durable ingestion.
Security by contract
Observe AI operations without collecting AI content.
SignalOps is designed around bounded operational facts. Security controls sit at schema validation, identity, tenant authorization, storage, and credential lifecycle boundaries.
Digest-only keys
Managed ingest secrets appear once; only SHA-256 digests and safe prefixes persist.
Tenant isolation
Operator membership is revalidated against durable storage near every protected read and mutation.
Deny-by-default data plane
Browser roles have no direct grants to SignalOps tables or administrative RPCs.
Data SignalOps accepts
- Opaque operation and attempt identifiers
- Normalized provider route and logical model keys
- Lifecycle timestamps and bounded durations
- Normalized failure taxonomy and retryability
- Reported or estimated cost with explicit provenance
- Environment, service, release, and region keys
Data the contract excludes
- Prompts, completions, transcripts, or embeddings
- Generated media, input media, or arbitrary URLs
- Customer names, email addresses, or application user IDs
- Provider API keys or customer ingest credentials
- Raw provider errors, stack traces, or free-form logs
- Nested arbitrary metadata or unbounded attributes
Current public-beta assurance status
SignalOps currently does not claim SOC 2 certification, ISO 27001 certification, HIPAA eligibility, or a contractual 99.9% SLA. Those require independent scope, controls, evidence, legal terms, and completed audits. The product does enforce HTTPS in production, HSTS, CSP, same-origin mutation checks, signed HttpOnly operator sessions, rate limits, bounded payloads, audit events, retention jobs, and revocable tenant credentials.
To report a security issue, use the contact channel and mark the request as security-related. Do not include production secrets or customer content.