A public security destination, not a hidden enterprise footnote.

Digital Guardian is explicit about what the platform does, what it does not automate, and how operational state is preserved.

Clarity over theater.

Security posture starts with architectural and workflow honesty: public-web discovery only, manual outbound by design, and auditable transition state.

Public-web only discovery

The platform monitors publicly reachable surfaces and does not automate login, paywall bypass, or private-surface access.

Evidence-first auditability

Case transitions, evidence records, containment actions, scan executions, and scheduler ticks remain fully auditable.

Manual outbound by design

Outbound notices and removal workflows stay operator-controlled, reducing automation risk during early enterprise rollout.

Access and operations are membership-scoped.

Workspace memberships, ops-only policy management, and explicit queue access keep the current implementation predictable.

Access

Role-scoped ops entry.

Owner, manager, and operator roles can access the ops flows while viewer access stays read-only or excluded.

Audit

Case and scheduler state stay persisted.

Evidence, containment actions, scheduler ticks, and creator scan executions are preserved for later review.