MATHEMATICAL DISCLAIMER OF LIABILITY

THE PLATFORM, WEBPAGES, SCRIPTS, AND DATABASES ARE PROVIDED STRICTLY ON AN **"AS IS"** AND **"AS AVAILABLE"** BASIS, WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

The Operator does not warrant that:

• Sockets and databases will operate uninterrupted, error-free, or fully immune from network disruptions, DNS hijacks, or latency.
• The compilation of browser-compiled WebAssembly or client JS will run with 100% compatibility across all device hardware, sandboxes, and browser configurations.
• Cryptographic protocols (X25519, ML-KEM-768, AES-GCM) are immune to future quantum decryption schemes.

By utilizing the Service, you acknowledge and accept the following cryptographic and operational risks:

• Self-Custody Risk: There is no server-side backup of private keys. If your terminal device is damaged, lost, or wiped, your secure sessions are mathematically lost forever.
• Inactivity Erasure Risk: Anonymous account sessions that remain completely inactive for 7 consecutive days are permanently wiped from the database relays by a background scheduler. All conversation payloads, chat indexes, reported abuse data, and associated public identity keys are erased and are 100% unrecoverable.
• Local Session Timeout Risk: E2EE private keys stored in the browser sandbox memory are destroyed after 5 minutes of total user inactivity (warning displays at 2 minutes and 30 seconds), terminating dynamic WebSocket sockets.
• Local Security Risk: The E2EE security is contingent upon the security of your device operating system. If your device has local malware, hardware keyloggers, screen recording scripts, or unauthorized browser add-ons, your chats can be compromised at the terminal level.
• Quantum Vulnerability: Standard public-key cryptography (like X25519) faces decryption risks from future quantum computers. While we implement Kyber/ML-KEM-768, this hybrid post-quantum protocol is experimental.
• Disappearing Messages Recipient Retention Disclaimer: While E2EE disappearing messages are permanently and securely deleted from active server storage, the Operator cannot control or prevent the recipient from making physical screenshots, taking photos of their screen with secondary cameras, or copying cleartext payloads before deletion occurs.
• One-Sided Clear Chat Preservation Disclaimer: Executing "Clear Chat" is strictly a client-initiated selective deletion for the initiator's account index. It will not delete or alter E2EE records held in custody by the conversation recipient's profile without their explicit command.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE OPERATOR, DEVELOPERS, CREATORS, OR CONTRIBUTORS OF **blackbox1to1** BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, PUNITIVE, OR EXEMPLARY DAMAGES (INCLUDING LOSS OF PROFITS, REVENUE, OR DATA; CORRUPTION OF ENCRYPTION KEYS; LOSS OF PASSWORDS; OR COMPUTER FAILURES) ARISING OUT OF THE PLATFORM.

IN ALL CIRCUMSTANCES, THE MAXIMUM MONETARY LIABILITY OF THE OPERATOR ARISING OUT OF OR IN CONNECTION WITH THE SOFTWARE, ROUTING TRANSIT, OR WEBPAGES SHALL BE ABSOLUTELY CAPPED AT **$100.00 USD** (OR THE TOTAL AMOUNT YOU PAID TO THE OPERATOR IN THE PRECEDING 12 MONTHS, WHICHEVER IS GREATER).

We will cooperate fully with valid law enforcement subpoenas, court orders, or search warrants issued by competent legal authorities.

Because our database contains only salted SHA-256 blind indexes and AES-GCM ciphertexts:

• We are **mathematically unable** to comply with decryption directives.
• We do **not** possess persistent IP connection logs or cleartext email lists.
• We will deliver only the raw database blobs (salted hashes, ciphertexts, and public ratchet keys) as they exist, without any decryption capacity.

To report phishing, impersonation, or platform abuse, you can send an email with cryptographic logs or screenshots to the Operator.

The Operator will investigate and, if verified, block the offender's blind hash index from routing.