Security Architecture

Client-Side Cryptography

All encryption and decryption happens on your device using the Web Crypto API. The plaintext never leaves your browser. We use AES-256-GCM, a military-grade authenticated encryption standard, to ensure both confidentiality and integrity.

Key Management

Your encryption keys are stored in the URL fragment (the part after the #). Browsers do not send fragments to the server during requests. This means even if our database or servers were compromised, your data remains secure as we never had the keys to begin with.

Secondary Protection (PBKDF2)

When you choose to add a password, we utilize PBKDF2 (Password-Based Key Derivation Function 2) with 100,000 iterations and a unique salt for every paste. This protects against brute-force attacks and ensures your password effectively strengthens the encryption key.

Network Security

• Strong Content Security Policy (CSP) headers to prevent XSS.
• HSTS (HTTP Strict Transport Security) for forced HTTPS.
• X-Frame-Options to prevent clickjacking.
• Strict Rate Limiting powered by Upstash Redis.