Privacy Policy
Version 2026-08-29.command4-v1 · Effective 2026-08-29
Information handled
The active product handles the minimum Google identity and server authorization data needed to verify the Owner, plus Owner-created settings, research context, reports, alerts, and audit metadata required by enabled capabilities.
Why it is used
Information is used to authorize the Owner, protect private routes, preserve governed research state, diagnose reliability, and record security-relevant changes. Fixture evidence is kept separate from provider and operational calibration evidence.
Access and disclosure
Owner-scoped content is not made public. Hosting, identity, and security processors may handle the minimum information necessary for their services. Provider credentials remain server-only and must never appear in browser content or evidence.
Retention and requests
Retention, export, deletion, backup-removal, and processor-erasure claims remain subject to verified implementation and applicable obligations. The support page records the current contact limitation without pretending a request was completed.
Security and boundaries
NovaBastion uses Google identity, exact Owner authorization, revision checks, protected caching, audit records, and data minimization. No system can guarantee absolute security.
External operation
No external launch geography or multi-user admission is authorized. The historical policy constants remain versioned evidence only and do not activate applicant collection.