VegaCrypt LogoVegaCrypt
Cryptographic Specification & Protocol

How VegaCrypt Works:
Client-Side Zero-Knowledge

Traditional file transfers upload your documents unencrypted and rely on server-side promises. VegaCrypt mathematically ensures that servers only receive ciphertext, keeping your secrets unreadable to everyone except your intended recipient.

How it works

Three steps.
Zero-knowledge.

Start with a Free account. No tracking, no complexity — just secure file transfer in seconds.

01

Upload Your File

Select a file, message, audio or video with your Free account. Choose your encryption method and set custom expiry.

02

Get a Unique Link

Receive a one-time encrypted link and optional password. Share it with your recipient via any channel.

03

Auto-Destroyed

Transfers expire automatically after your configured lifetime, or burn immediately upon first access if enabled. No recovery possible.

01

Web Crypto API

All encryption operations execute inside the browser sandbox using hardware-accelerated Web Cryptography API primitives.

02

Key Segregation

Decryption key fragments never touch HTTP request bodies or query strings, isolated exclusively in URL hash anchors (`#`).

03

Cryptographic Purge

Ciphertext blocks are purged immediately upon expiry or first access. Without decryption keys, stored blobs are mathematically unrecoverable.

Encryption

You choose how
your data is protected.

Three encryption methods — maximum privacy or maximum convenience. All use AES-256-GCM.

E2EE · Recommended

Client-Side Encryption

Your file is encrypted in the browser before it ever reaches our servers. We literally cannot read it — even if we wanted to.

AES-256-GCM + PBKDF2 (100k iterations)
Zero-knowledge architecture
Password required for access
HIPAA, GDPR, ISO 27001 ready
Server breach = zero data exposed
Split Key · No Password

Dual-Key Link

Encrypted in the browser before upload. Access requires the full link plus an email verification code — no shared password to invent or pass in a second channel.

AES-256-GCM + HKDF from both key halves
Client Secret in link fragment + Server Secret after OTP
Inbox-bound access — no shared transfer password
Recipient needs no EMP or VegaCrypt account
HIPAA, GDPR, ISO 27001 ready
Server stores ciphertext only — cannot read content
Vault · EMP

Vault Encryption (EMP)

Content is encrypted in the browser for the recipient's public key before upload. We store ciphertext only — we cannot read it.

AES-256-GCM + X25519 envelope; EMP unlocked with Argon2id
Zero-knowledge architecture (EMP never sent to the server)
EMP required for recipient access (not a per-drop password)
Email link + Encrypted Inbox for registered recipients
HIPAA, GDPR, ISO 27001 ready
Server breach = zero plaintext exposed
Security Architecture

Multi-layered protection
by design.

Every transfer is encrypted, isolated, and automatically destroyed after access — leaving no recoverable trace.

Encrypted Before Upload

  • AES-256-GCM local encryption
  • Client-side key generation
  • Ciphertext-only storage
  • No plaintext data on servers

Privacy by Design

  • Strict data minimization
  • Encrypted database entries
  • No advertising trackers
  • GDPR & HIPAA compliant architecture

Self-Destruct Logic

  • One-time download links
  • Custom expiration timers (1h–30d)
  • Instant memory wipe
  • No recovery possible

Controlled Access

  • Multi-factor link access
  • Brute-force protection (5 attempts)
  • Global CDN isolation
  • Custom password layer

Need a custom security review?

Review our protocol specifications with your security and compliance team, or request an enterprise security architecture briefing.