What happens before your question arrives, explained in 1 minute

6 steps that start the moment you press the Send button

You type a question into a question box and press the Send button. The screen shows "Sending...", and a few seconds later it changes to "Question sent!" That's all users see, but during those few seconds, several processes are running behind the scenes.

This article sorts the typical mechanisms widely used in anonymous question services into 6 steps and explains them with everyday analogies, so you can follow along even without technical knowledge. Which mechanisms a service combines, and how, differs from service to service, but knowing the rough flow gives you a picture of what's happening behind the scenes. Learning how a question box's safety is maintained should help you use it with peace of mind.

Steps 1 and 2: the computational puzzle and the dummy field check

Step 1 is Proof of Work (a computational puzzle). The moment you press the Send button, your browser starts solving a computational puzzle in the background. It's like answering "a simple quiz to prove you're human" at the entrance of an amusement park. For a human, the calculation is over in an instant, but when a bot tries to fake a huge number of tickets, it has to solve the quiz for each one, so the cost of faking them shoots up.

Your browser does this calculation automatically, so you don't need to do anything. When the calculation is done, the proof (evidence that "I solved the puzzle") is sent to the server along with your question data.

Step 2 is the honeypot field check. The question form has a hidden dummy input field that humans can't see. Because humans can't see this field, they don't type anything into it, but bots automatically fill in every field on a form, so they put a value in the dummy field too. The server checks whether the dummy field has a value, and if it does, it judges the post to be from a bot and rejects it.

It's like putting a clear seal on a letter's envelope. A real mail carrier doesn't notice the seal and delivers the letter as it is, but someone who tries to open the letter and tamper with its contents breaks the seal, so the tampering is detected.

Steps 3 and 4: checking how often you post and what you wrote

Step 3 is rate limiting (limits on how often you can post). The server checks how often posts come from your IP address. If there are more posts than the limit within a short time, the extra ones are rejected. It's like a restaurant entrance controlling how fast people come in. It doesn't affect regular customers, but it stops a nuisance group trying to rush in 100 at a time.

The limit is set at a level that normal use will hardly ever reach, so you'll almost never get caught by it.

Step 4 is filtering (content screening). In question boxes with the filtering feature turned on, the content of questions is screened automatically. Questions that contain abuse, threats, or sexual expressions get a warning mark.

It's like putting a letter's contents through an X-ray check. It checks for anything dangerous inside, but it doesn't read and censor what the letter says. It only checks mechanically whether the text matches certain patterns. Even if a question gets a warning mark, it isn't deleted. The final decision is left to the owner.

Steps 5 and 6: saving and notification

Step 5 is saving the data. A question that passes every check is saved in the database. At this point, as stated in the privacy policy, the sender's IP address is encrypted before it's saved. To prevent misuse, the sender's IP address is shown to the owner of the question box, but it's never disclosed to any third party other than the owner.

It's like keeping a record locked in a safe. It isn't left where anyone can see what's inside. Instead, it's shown only to a designated person (in this case, the owner of the question box), and only within defined limits.

You don't need to log in to send a question, so your name and email address never reach the owner or the Q drop team. The full picture of what information is collected is published in the "Information We Collect" section of the privacy policy.

Step 6 is notifying the owner. Once the question is saved, it appears as a new question in the owner's dashboard. When the owner opens the dashboard, your question is in the list. The owner reads the question and decides whether to answer it, skip it, or delete it.

What the 6 steps protect

These 6 steps protect 3 things.

First, they protect the owner of the question box. Spam from bots, floods of aggressive posts, and excessive load on the server are all threats. Mechanisms like Proof of Work, the honeypot, and rate limiting stop these threats in several layers.

Second, they protect the sender's privacy. You don't need a name or account registration to send a question, and the person you're asking is never notified of who you are. Your IP address is encrypted before it's saved and isn't disclosed to any third party other than the owner. The connection is encrypted with HTTPS, so third parties can't intercept the content of your question either.

Third, they protect the health of the service as a whole. Filtering puts a warning on inappropriate posts so that the owner can deal with them properly. Rate limiting keeps the server stable so that every user can use the service comfortably.

All of these steps run automatically in the background, so neither the person sending the question nor the person receiving it needs to do anything special. All you do is press the Send button, and behind the scenes, several mechanisms protect you and the owner.