Privacy Policy

Shatachandra Shield ("the Platform", "we", "us", or "our") is committed to absolute privacy boundaries for operators and organizations deploying our post-quantum cryptographic appliance components. This document defines the policies governing metadata ingestion, storage isolation, and zero-knowledge packet processing across our 3-tier gateway architecture.

1. Scope of Information Collection

Our data collection loop is strictly limited to metadata parameters necessary to authorize, route, and sustain active secure console terminal sessions and gateway validation tokens:

• Operator Account Registry Data: Legal name, authorized operator email addresses, and encrypted unique identifier strings (UID) provisioned upon system registration.
• Cryptographic Gateway Token Attributes: Generated authentication token hashes, access tier tracking variables, token activation dates, and 14-day calendar expiration timestamps.
• Telemetry & Benchmark Metadata: Anonymized runtime node telemetry, including hardware AVX2 handshaking latency measurements, payload encapsulation speeds, and Strict Avalanche Criterion (SAC) diffusion statistics used exclusively for telemetry performance audits.

2. Data Isolation & Technical Infrastructure

To avoid single-point data vulnerabilities, our platform architecture utilizes strictly isolated cloud and server layers:

• Authentication & Identity Layers: Handled natively by Google Firebase Authentication frameworks. Passwords and credentials are fully salted and hashed on Google infrastructure and are never accessible to platform operators.
• Database Record Management: Account configurations, registration profiles, and token metadata parameters are written to Google Cloud Firestore document databases protected by granular security rules.
• Gateway API Daemon: Real-time PQC encryption handshakes and socket processing are hosted on dedicated, hardened AWS EC2 instances running FIPS 203 ML-KEM engines over isolated local Unix Domain Sockets.
• Static Frontend Delivery: Public web interfaces, documentation, and client assets are distributed globally via Firebase Hosting's secure CDN edge network.

3. Zero Inbound Payload Inspection Policy

Shatachandra Shield operates as a pass-through, zero-knowledge architectural gateway. Our Layer 4 and Layer 5 daemons process cryptographic key encapsulation and symmetric session derivation locally over Unix domain sockets (`/tmp/shatachandra_l4.sock`) without ever inspecting, storing, logging, or mirroring customer application payloads.

4. Data Retention & Sandbox Expiration Architecture

Evaluation environment lifecycle rules are strictly enforced by automated backend tasks. Evaluation token rows, access mapping parameters, and temporary terminal variables automatically expire exactly 14 calendar days (336 hours) following initial creation. Expired trial keys are permanently locked and cannot be revived or repurposed.

5. Information Sharing & Third-Party Disclosure

We do not lease, trade, sell, or monetize operator profile metadata or connection logs to corporate marketing firms, analytical tracking networks, or third-party brokers. Data is shared exclusively with our trusted infrastructure subprocessors (Amazon Web Services and Google Firebase) strictly to maintain gateway uptime and authentication security.

6. Operator Rights & Complete Data Erasure

Operators reserve the right to audit their registered account configuration metadata. You may execute a complete system data erasure request at any time. Upon formal request validation, all records linking your real identity to your Firestore profile document will be permanently scrubbed from our active registries within 7 business days.

← Return to System Console