Understand the protected boundary
Security Submission and Data Use
Clarify responsibilities before deciding to leak.
Protect the source, start with yourself.
Nobody is automatically given the responsibility to keep your confidential information just because you choose to be anonymous.We will still handle your data with caution, but cannot replace you in eliminating existing identification risks before sending, nor do we promise absolute confidentiality that is impossible to achieve.
Break the content's association with yourself personally.
Keep it safe by checking the content for any personal information before sharing. Names, accounts, document numbers, watermarks, authors, times, locations, background images, and details known only to a few can all lead back to you. Only provide necessary samples; cropping, scanning, or deleting metadata cannot guarantee the removal of all traces. Don't completely entrust the source protection to strangers, technology, or platforms.
Anonymous Reporting Should Be a Last Resort
Don’t use media’s time lightly to handle personal interests or grudges with anonymous reporting. Before reporting for personal interests or public interest, please evaluate other appropriate paths, organize verifiable facts, evidence, and background.
Receiving a tip is not a promise to use or publish it
All tips require additional verification. Responsible media will cross-verify through other credible sources, evidence, or verified methods, evaluate public interest against source risk, and then publish verified content in an appropriate manner. Anonymous is not a reason to avoid explaining and verifying responsibilities; submitting does not guarantee reporting, acquisition, or handling disputes on your behalf.
Email and Telegram Both reveal a contact identity
When you communicate via email, the recipient knows your email address. When we communicate via Telegram, we know your Telegram ID and may see your publicly visible account information. Using pseudonyms does not automatically remove account associations.
The Telegram conversation with this bot is not end-to-end encrypted. Telegram technically can obtain the content; building your own bot API doesn't change this boundary. Sensitive attachments should be encrypted on your device before submitting them as files. Sensitive background explanations should also be placed in the encrypted file, not in the chat text or file name.
File encryption will still leave account, contact time, and file size information. If you use a password to encrypt, please use another trusted end-to-end encryption pipe to deliver the password; do not send the password with the attachment to Telegram.
Email Basics and Security Guide
Understand the differences in email addresses, recipients, carbon copies, and blind carbon copies, as well as the address, IP, time, software, and conversation link clues in the email's raw code, and recognize open-source solutions that can parse EML and TXT files locally.
age Self-Encrypt and Submit
The site's recipient public key comes from its server key pair. Verify it through a trusted, independent channel before use. The private key is kept on the server, so the platform can decrypt submissions. This is not end-to-end encryption that prevents the server from reading the contents.
- Clean your identifying information on your device, only prepare samples and background information that you are willing to share.
- Verify the recipient's public key, place the sample and sensitive notes in the original file, and encrypt it locally. You can also add your own public key to allow yourself to decrypt.
- Using a general file name to send the ciphertext. Retain the original ciphertext submitted to enable SHA-256 queries; re-encrypting usually changes the digest.
- Platform fully validates and decrypts the ciphertext using server keys, checks format against initial scan on the machine, passes then stores encrypted in a isolated zone; fails to decrypt or initial scan fails, does not save. Passing the scan does not mean security, content must be isolated for review.
Select file, select Zuola Inbox key, encrypt locally before confirming submission →
age Official Tool and Documentation · Telegram's cloud chat data processing guide
Anonymity depends on several choices
Private mode reduces local browsing records, does not hide the source IP to websites. A VPN changes the exit and increases trust in service providers.Tor Browser Anonymous and Fingerprint Protection, but cannot guarantee absolute anonymity.
Understand the connection first, then choose the entry.
Tor Network and This Site’s Onion Entry
What does Tor protect?
Tor routes connections through several relays, reducing the chance that one network observer can directly link your origin and destination. Tor Browser also reduces some browser fingerprint differences. It is not the same as private browsing and cannot guarantee complete anonymity.
Use HTTPS for Tor browsing to HTTPS websites through exit nodes; using HTTPS is still important. For visiting .onion sites, connections stay within the Tor network without using exit nodes to return to regular websites. Websites generally cannot see your real IP, but the content you actively provide can still be seen by websites.
What Tor cannot handle?
It cannot remove the author, location, time, watermarks, or clues from the document. It also cannot repair a compromised device. Logging in with a named account, providing contact information, or writing about identifiable experiences may still expose your identity. Please handle the source clues first before deciding to send.
This site's Onion entry does not require login, does not establish visitor tracking or fingerprint, does not connect to general website accounts or Telegram identities. Uses a short-lived cookie required for form security, with a fixed marker that skips pre-played brand animations for all users, and the content and attachments are still processed by the same backend, meaning that the transmission encryption is not understood as content that this site cannot access.
One anonymous entry, two memory methods
https://zuo.in/box Is a convenient short URL, readable as "zuo in box", which redirects to the full Tor Onion address starting with "inbox" below; both lead to the same anonymous inbox entry. The short URL itself is a regular HTTPS website, please open it in the Tor Browser first. Directly inputting the full Tor Onion address can skip the step of accessing the short URL service.
http://inbox2ln6xdy4k64atu7vekoutsa2p2a4utuhzxzjgma2w3pnps553id.onion/
How to Access and Submit
- Ready browser.從 Tor Browser 官方網站取得瀏覽器,開啟後完成 Tor 網路連線。
- Verify the address.Enter complete Onion address in Tor Browser, or open zuo.in/box and confirm you end up at the same address. Most browsers won't automatically establish a Tor connection by clicking on a shortened URL.
- Read safety instructions first, then prepare sample.Login required to post, up to three attachments per post, totaling strictly less than 10 MB (10,000,000 bytes); images per file max 5 MB. Provide necessary crop or mask samples for selling data.
- Submit only after it is clearly sent.Calculate SHA-256 locally, compare with server; known samples are only established as references, each submission remains an independent case. This process requires JavaScript; files, summaries, or drafts will not be saved to the browser storage.
- Keep the same sample.Later, select the original file on the lookup page. Only its digest is sent to retrieve the sample status and reply deliberately made public by the administrator. Anyone with the same sample may see these replies. This is not a private case inbox, and anonymous text-only tips have no sample-based lookup.
This site's Onion address currently uses HTTP, and the connection from the browser to the Tor server is still encrypted and verified by Tor. Attachment encryption on disk does not equal end-to-end encryption from the source to the administrator. There are traffic and capacity limits for the entry; if busy or transmission is interrupted, please keep the original file and try again later to avoid continuous re-sending.
Check the documents first before deciding to share
Cropping may not eliminate watermarks, numbering, content clues, or metadata. Photos or screenshots may contain invisible blind watermarks. Some methods use Fast Fourier Transform (FFT) to hide information in the frequency components of the image. Consider scanning the screen or printing and then scanning to reduce the chance of identifying some original blind watermarks. Scanning cannot guarantee removing the blind watermarks, and you should also be aware of the metadata and background of the new photo. Provide necessary samples for the first time. Attachments will be encrypted and isolated saved; the platform can read the submitted content, but it does not claim to be end-to-end encrypted.
File Summary is a limited query entry.
Other holders may know that the platform has received the same sample. The progress and replies chosen by the administrator to be public are displayed on the page, but the original content, contact information, or payment information are not shown.
Login, Contact, and External Services
Google Login is used to verify identity; whether submissions are associated with an account depends on the identity you choose. Login itself does not imply consent to receive emails. Voluntarily leaving contact information means you agree to be contacted according to your specified preferences. The website uses Cloudflare to handle connections and Google to verify login.
Data Retention and Formal Openness.
Current version is a prototype, not enabled for auto-deletion. Before formal inbox, must confirm retention, backup, deletion, and operational policies. This site's first-party revisit analysis and optional auxiliary fingerprint follow the footer status and privacy policy; no third-party analysis scripts used. Named submissions, confirmed by you, will be temporarily saved in the current page's text draft for recovery upon login. This version does not provide security scores or guarantee anonymity.
Understand the basics first, then use the tool.
Tools can assist in understanding and checking leads, cannot replace risk judgment, and does not provide anonymity or security guarantees.
Check what the photos reveal.
Don’t upload photos. Check GPS, timestamp, device model, author, and editor information in the browser for any potential leaks. Photos and results won’t be included in the analysis.
email parsing and file encryption
Read emails and understand encryption limits before choosing the appropriate tool. These independent tools only handle files in the browser, no upload, no inclusion in access analysis.
RAW Email local parser → · age Self-Encrypt → · age Self-Decrypt →
Check what this browser reveals to the website server.
Browser privacy checking is now a separate tool. It explains your device, language, time zone, display and privacy preferences in plain language. Basic checks and the advanced fingerprint demonstration run locally. You may separately request the exit IP and approximate location seen by this site. The tool is excluded from visit analytics.