TERMS OF USE & PRIVACY NOTICE · UPDATED 24 SEPTEMBER 2026
1. Eligibility and agreement
Anony Bean is an experimental, ephemeral communication service for adults aged 18 or older. By selecting ACCEPT & ENTER, you confirm that you meet this requirement and agree to these terms and the processing described below. If you disagree, do not enter or use the service.
2. Your content and conduct
You remain responsible for the messages and files you submit, your interactions, and compliance with applicable law. Submit only content you have the right and consent to share. Illegal content, child sexual exploitation, threats, harassment, doxxing, non-consensual intimate material, fraud, malicious files and attempts to disrupt or bypass service safeguards are prohibited. Do not share your own or another person’s contact details, real name, address or other identifying information. You authorize only the temporary processing and delivery necessary to operate your session; you retain your rights in your content.
3. Safety filtering, enforcement and termination
Public timeline posts and comments, and room names, are checked before publication for recognized contact details and social-media references, including platform names, handles and links. This rule helps protect people from unwanted contact, off-platform targeting and exposure of identifying information. The filter recognizes patterns in text; it may not detect every reference. Encrypted room messages and files cannot be inspected by the relay and do not trigger automatic contact-based room dissolution. Use report and block controls for abuse. Inactivity and game mechanics can also remove participants. Admins may remove reported live content or end an active session. Chat identities are temporary, so a block applies to the current connection and may not persist if someone reconnects with a new identity. We may limit actions or end access when reasonably necessary to operate, secure or enforce the service or comply with law. Do not rely on the service for storage, emergency assistance or critical communications.
4. Information processed and purposes
The relay temporarily processes random session identities, room membership, encrypted messages and files, reactions, votes, activity timestamps, game state and rate-limit counters to deliver chat and enforce room rules. Room and timeline state use application memory and are not stored in the BEAN ledger. A random anonymous voting key is saved in browser local storage to prevent duplicate timeline upvotes after reloads and across tabs; it contains no messages or contact details. Optional BEAN activation creates a separate persistent account with a random account ID, a SHA-256 lookup digest, a salted scrypt recovery verifier and a balance ledger in the relay database. Your browser generates the 256-bit recovery key; the service does not store the key itself. BEAN account records contain no chat identity, message, email or phone number. The session token stays in tab memory while you navigate and is cleared when signed out, reloaded or closed; it expires after 12 hours. If you opt in, the relay temporarily associates your BEAN account ID with your live socket to validate room rewards or purchases. Ledger entries include amount, reward or purchase type and transaction time. Idempotency data also retains the room ID and expiry for room extensions, and the room ID, creation time and invite-key hash for a premium-room purchase; it is used to safely retry that purchase and contains no chat content. A short-lived in-memory map associates a premium-room request with its temporary room until it closes or the relay restarts. You can delete the BEAN account from its wallet page; deleting it removes its account and ledger records. Clearing browser site data removes the timeline voting key but does not delete a BEAN account. The application does not implement advertising analytics or tracking cookies.
BEAN credits
BEAN is an optional, cryptographically protected, off-chain Anony Bean site credit recorded in a server-side ledger. Its cryptography protects wallet access and account sessions; BEAN itself is not a blockchain cryptocurrency or on-chain token. It is not money, an investment, a deposit or a promise of profit. BEAN has no public sale, cash redemption, external wallet or transfer feature. Once per UTC day, an Open Table room with at least three active sessions can award 9 BEAN to its host and 3 to each other participating wallet. The relay checks only that the same sessions remained active for 90 seconds and each sent at least one encrypted message; it does not inspect message content or prove that sessions represent different people. Spend 8 BEAN to extend a temporary secret room by 15 minutes, up to two hours total; keep an empty public-room link alive for 15 minutes; or add 15 minutes of idle grace to the current roulette match. Spend 15 BEAN to create a private two-session room with a separate invite key. Share its link and key with one person outside the site. The room expires after 30 minutes and closes for both participants when either leaves. It uses the Anony Bean relay and end-to-end encryption; it is not a direct peer-to-peer network connection. Credits do not expire. The browser creates a cryptographically random 256-bit recovery key, shown once. The service stores a SHA-256 lookup digest and salted verifier, not the key itself. If you lose the key, the account cannot be recovered; if another person obtains it, they may access the balance.
5. Recipients, hosting and network metadata
Content is delivered to other participants in your room through a central relay, without direct peer-to-peer connections. The room access key controls entry and is separate from device encryption keys. Room text, attachment names and bytes, and vault payloads are encrypted on participant devices; the relay receives ciphertext. Only devices present at sending can decrypt; new members do not receive encrypted history. Vault DECRYPT is a shared delivery gate, not threshold cryptography: the relay could release the encrypted payload early to its original recipients. The /ghost and /redact commands are display effects, not additional encryption. Public channels are open to new members, who can read future messages. Public timeline content, room names, identities, membership, timing, sizes, reactions and game actions remain visible to the relay. Device keys are exchanged through the relay. Until two devices’ codes are checked against each other, participants rely on the relay to provide the expected keys. Private keys remain in browser memory and are replaced on reconnect, with no key backup or recovery. Olm Double Ratchet discards processed message keys, providing forward secrecy for those keys. Live plaintext, keys for pending files or vault drops, and limited out-of-order message keys can still exist in device memory. Compromised devices or delivered application code can expose content. The application does not intentionally log client IP addresses or publish them to participants. Network connections nevertheless expose connection metadata to infrastructure providers. Hosting, proxy, security and network-provider processing depends on the deployed configuration and their policies and may occur outside your country. Application memory-only behavior is not a promise that third parties retain no records. The operator has a dashboard of aggregate counts only - how many sessions are open, how many connections were made today, how many rooms exist - computed in memory. No address, identifier or per-person record is created or kept for it.
5a. Encryption design and device trust
Room text, attachment names and file bytes are encrypted in participant browsers using the documented Anony Bean protocol v3 before they are sent through the relay. The relay receives ciphertext and does not receive room decryption keys. Device public keys are exchanged through the relay, so until the devices’ codes are checked against each other, participants rely on the relay to provide the expected keys. Until device codes are compared, participants rely on the relay to provide the expected keys. This application-specific protocol has automated tests but has not had an independent cryptographic audit. Browser-delivered code, the browser, device and extensions are part of the trust boundary and can expose content if compromised or changed. The relay can see room membership, public device keys, message timing and ciphertext sizes. Public timeline content remains readable to the service. Hosting and network providers may process connection metadata under their own configurations and policies. Expiry timers remove app references on a best-effort basis; recipients can retain copies, and app expiry does not guarantee forensic erasure.
6. Retention and deletion
Public timeline thoughts expire after 15 minutes. Comments expire after five minutes or with their parent thought, whichever comes first. Timeline content remains available until expiry even if its author disconnects. Room messages and ordinary completed files normally expire after 60 seconds; system prompts can have shorter lifetimes. Sealed vault drops expire after two minutes unless unlocked, and revealed vault content expires after ten seconds. Unfinished uploads expire after 30 seconds. Secret-room metadata and key hashes remain in memory for up to 30 minutes from creation, including while empty; expiry closes the room and revokes access. Empty secret rooms clear their chat content. Active room state lasts until departure, room closure or process termination; built-in empty channels can remain available. Expiration timers are best effort and can be delayed by runtime scheduling. We remove application references and clear file buffers where implemented, but do not promise forensic erasure. Recipients may capture, download or retain content outside our control.
6a. Safety reports and image processing
You can block a bean for your current connection and report live content to admin. Blocking hides their content from you; it does not hide your content from them, and a new session identity can bypass it. A report contains the reason, relevant content and session identifiers, and a readable copy of selected text only when you choose to include it. For encrypted messages this copy is supplied by the reporter and is not independently authenticated by admin. Files and images are not copied into reports. Reports remain in relay memory for up to 24 hours or until review or process restart, whichever comes first. This is separate from ordinary message expiry. Admin can remove content or end an active session; reports do not automatically punish users. For follow-up contact support@anonybean.site without sending illegal imagery. Support email creates a separate record held by email providers; it is not subject to chat expiry. Supported photo uploads are decoded on the sender’s device before encryption and re-encoded as still WebP images up to 2048 pixels per side, with original metadata and filenames removed. Animated images use their first frame. This cannot remove identifying information visible in the picture or sanitize metadata in other file types.
7. Privacy choices and limits
You can decline entry and leave at any time. Share no information you need to keep confidential. Ephemeral messages, invite keys and the tab privacy shield cannot guarantee anonymity, prevent recognition or block recording. No transmission or security measure is infallible. Rights to access, correct, delete or complain about personal information depend on applicable law; these terms do not remove those rights. We cannot reconstruct expired content or reliably link an anonymous session to a person after its identifiers are gone.
8. No warranties
To the fullest extent permitted by applicable law, the service is provided “as is” and “as available”, without express or implied warranties, including merchantability, fitness for a particular purpose and non-infringement. We do not warrant uninterrupted access, error-free operation, the accuracy or legality of user content, complete filtering, confidentiality, anonymity or recovery of expired data. Other users act independently and their content is not endorsed by the service.
9. Limitation of liability
To the fullest extent permitted by applicable law, the service operator and its personnel will not be liable for indirect, incidental, special, consequential or punitive losses, or loss of profits, data, goodwill or opportunity arising from use of or inability to use the service, user conduct, disclosed content, interruption or deletion, even if such losses were foreseeable. Nothing in these terms excludes or limits liability that cannot lawfully be excluded or limited, including mandatory consumer or privacy rights and liability for fraud, wilful misconduct or gross negligence where such exclusions are prohibited. Your legal rights prevail over any conflicting term.
10. Responsibility for third-party claims
To the extent permitted by applicable law, you agree to indemnify the operator against reasonable third-party claims, damages and costs caused by your unlawful content, infringement of another person’s rights or material breach of these terms. This does not apply to the extent a claim results from the operator’s own fault or non-excludable legal duties.
11. Changes and interpretation
Material changes to these terms or data practices should be presented before renewed acceptance; continued use is not a substitute for consent where fresh consent is required by law. If a provision is unenforceable, the remaining provisions continue only to the extent lawful. No provision restricts non-waivable rights, access to regulators or remedies required by applicable law.
12. Contact
For support, privacy questions or reports, contact anonybeanadmin at support@anonybean.site.