What happens when Navōn refuses a request, and why it answers in the conversation

Every filtered tool has to say no sometimes. What matters is how. A child who types a question and gets a red error box learns that the tool is broken, or that they did something terrible, and neither is true. A parent who sees a bare "blocked" has no idea why. In Navōn a refusal is part of the conversation, and this post walks through what that means in practice.

Where a request can be stopped

A message passes through several checks before any model writes a word, and the answer is checked again afterwards. Roughly in order:

• Allowed hours. If the account has time limits and it is outside them, the request stops here.
• Any file you attached. A file that cannot be read, or whose contents fail the check, is refused, and so is one that cannot be extracted properly, rather than being passed along unseen.
• The blocked-topics list. A parent, a school, or an adult for their own account can list topics to keep out. A message that matches one is stopped before any model runs.
• The safety check on the question itself, against the standard that applies to that account.
• The safety check on the answer, once the model has written it.

Because all of this runs on the server and not on the device, it is the same on a school Chromebook and a phone at home. We explain why that matters in our post on server-side and device filtering.

What you see when it says no

The refusal shows up in the thread, in the place the answer would have been. It is saved in the history like any other turn, so a parent or the person themselves can later see what was actually said. It is not a pop-up, and it is not lost when the page is refreshed.

The wording depends on who is asking. An adult gets a plain reason and, where there is one, an alternative: that the request falls outside what Navōn covers under its content standards, and what to try instead. A child gets a gentler line that says this is not something we talk about here and invites another question. If the message is in Hebrew or Yiddish, the refusal is written in that language too, not in English.

Under a refusal there is a small line pointing onward. For an adult it links to their filter settings and to Navōn's policies. For a child it says to ask a parent if they think the request should be allowed, because a child cannot change the filter themselves.

Who set the rule matters

When a blocked topic stops a message, the wording says whose rule it is. If a parent or school added the topic, the reply says so. If an adult turned that topic off in their own settings, the reply says that instead and points to Settings, where they can change it. Telling a grown person that someone else had asked Navōn not to discuss something, when the setting was theirs, would simply be untrue.

The exception we made on purpose

A topic list is a blunt tool. A parent who blocks a word like "abuse" or "suicide" means keep that subject away from my child, not refuse my child if they are in trouble and have nobody else to ask. So when a message is a real disclosure of distress, the blocked-topic list does not apply to it, and the response is handled by the distress path rather than a refusal. An ordinary request that merely uses the word is still blocked.

Not every rule refuses

Navōn's content rules carry different settings. Some decline the disallowed part with a short explanation. Others never refuse at all: they shape the answer, so a sensitive subject is handled the way the family or school wants rather than hitting a wall. A small number of rules have no exceptions and are never relaxed. The point of the distinction is that a no should be reserved for the cases that need one.

When the answer is withheld, and when the check could not run

Sometimes the question passes and the answer does not. In that case the text is replaced with a notice that the response was withheld because it did not meet the content guidelines. Nothing is left on screen above the notice.

A different message appears if the safety check itself could not be completed. That case is worded differently on purpose, because telling a student their answer failed the check when in fact it was never checked would be untrue. Navōn fails closed: if the check cannot run, the request is not answered unchecked. Nothing was decided about the question, so you are asked to try again in a moment.

Separate from all of this, an account on a plan with usage limits will sometimes be told it has reached a limit for the day. That is a plan limit with a link to upgrade, not a judgement about the content.

If you think a refusal was wrong

Filters make mistakes in both directions, and we would rather say so. An adult can open Filter settings straight from the refusal and look at the topics and rules in force. A child should ask a parent. If something that should have been stopped was not, our guide on what to do when something gets through the filter covers the steps.