Security & Cryptography

QuantC is engineered around a mathematically verifiable zero-knowledge security model. Every byte of personal data is encrypted on your device before leaving your browser. Below are the cryptographic protocols and technical standards protecting your transfers.

1. Zero-Knowledge Cryptography & Server Blindness

Traditional cloud providers retain administrative access or private encryption keys, allowing automated crawlers, corporate systems, or third parties to inspect file contents. QuantC enforces total server blindness:

  • On-Device Execution: All cryptographic operations are executed entirely inside the client’s browser sandbox via the native W3C Web Cryptography API (crypto.subtle).
  • No Key Transmission: Passwords, raw keys, and plaintexts never touch our signaling or relay servers. Even if our infrastructure were physically audited, no user file could be decrypted without the sender's password.

2. Key Derivation: PBKDF2 with SHA-512 (200,000+ Iterations)

To resist offline dictionary attacks and specialized GPU brute-force cracking, QuantC derives strong 256-bit symmetric keys using high-iteration password-based key derivation:

  • HMAC-SHA-512: Utilizes 512-bit pseudorandom hashing for maximum collision resistance.
  • 200,000+ Iteration Work Factor: Enforces computational cost that makes automated dictionary attacks economically and mathematically impractical.
  • Cryptographic Salt: Every session generates a unique, cryptographically random 128-bit salt (via crypto.getRandomValues) to prevent rainbow table attacks.

3. Authenticated Encryption: AES-256-GCM

QuantC uses Galois/Counter Mode (GCM) authenticated encryption, providing both confidentiality and cryptographic integrity verification:

  • Unique Initialization Vectors (IV): Every individual chunk receives a cryptographically unique 96-bit IV, ensuring that identical file blocks never produce identical ciphertexts.
  • 128-Bit Authentication Tags (AAD): Each ciphertext block carries an authentication tag bound to session metadata (chunk index, total chunks, session ID). Any network alteration, byte injection, or chunk re-ordering triggers immediate rejection.

4. WebRTC SCTP Protocol for Local Share

Our Local Share protocol utilizes direct device-to-device transport without cloud mediation:

  • DTLS-SRTP Security: All peer-to-peer data channels are secured with Datagram Transport Layer Security (DTLS) with self-signed certificate fingerprint exchange.
  • Optical QR Authentication: The initial signaling exchange is mediated via visual QR code scanning, eliminating man-in-the-middle (MITM) risks on shared public Wi-Fi networks.
  • Memory-Bounded Pipeline: High-speed sliding windows process incoming slabs in RAM without writing temporary unencrypted fragments to disk.

5. Ephemeral Lifecycles & 48-Hour Permanent Purging

Data minimization is our core operating principle:

  • 48-Hour Auto-Purge: All remote encrypted file shards and transfer metadata are permanently deleted 48 hours after upload. Purged data cannot be recovered by any party.
  • Zero Tracking Cookies: QuantC does not use persistent tracking cookies, fingerprinting pixels, or third-party behavioral profiling.