Security Architecture & Vulnerability Disclosure

IPasteIt implements true zero-knowledge client-side encryption for password-protected pastes. • Key Derivation: Passphrases undergo PBKDF2 (100,000 iterations of SHA-256) or Argon2id with a unique 16-byte random salt generated via crypto.getRandomValues(). • Cipher: Payloads are encrypted client-side using AES-GCM with a 256-bit key and 12-byte initialization vector (IV). • Verification Tag: An HMAC authentication tag verifies ciphertext integrity prior to decryption. The plaintext password and unencrypted payload never leave the client's browser.

Burn-After-Reading pastes are protected with atomic row locking (FOR UPDATE) in PostgreSQL. The moment the first successful read transaction completes, the record is immediately erased. Expired records are hard-purged via continuous edge vacuum routines.

We welcome responsible security research from the global developer and infosec community. If you discover a potential vulnerability in our web application, API, or infrastructure: • Submit an encrypted report with reproducible proof-of-concept steps to security@ipasteit.bond. • Provide a reasonable window (minimum 14 business days) for remediation prior to public disclosure. • Do not access, mutate, or exfiltrate customer or anonymous user data during testing. • Do not perform disruptive denial-of-service (DDoS) testing against production edge nodes.

Our security policy and contact endpoints are mirrored per RFC 9116 at: https://ipasteit.bond/.well-known/security.txt Direct Encrypted Security Dispatch: security@ipasteit.bond Emergency Abuse Team: abuse@ipasteit.bond