Web-first information
This page is the current public explanation. The PDF is an optional secondary download.
Guardian uses server-derived tenancy, approved integrations and customer-safe records while the public website remains isolated from Guardian operational systems.
The website explains the platform without connecting to Guardian databases or customer data. Guardian access, entitlement and integration status are enforced within the authenticated platform.
This page is the current public explanation. The PDF is an optional secondary download.
Included capability, allowances and separately priced activity are identified before activation.
Exact scope, configuration and service commitments are confirmed in the applicable package schedule or proposal.
Customer and provider authority is derived server-side rather than from browser-controlled identifiers.
Licensed modules and applicable visibility rules determine which operational experiences are available.
Vendor technologies remain connectors and sources rather than being presented as separate customer products.
Views exclude raw payloads, credentials, internal identifiers and unsafe implementation detail.
Unavailable, unconfigured and no-data states remain explicit instead of being represented as zero.
The public CMS uses its own database and media storage and never queries Guardian operational systems.
Regional hosting, data residency, subprocessors, retention and service commitments are published only where separately verified and approved.
A public integration name does not imply unrestricted data access, complete coverage or availability to every package.
We will confirm the relevant package, included allowances, additional modules and any separately scoped Damocles services.