TOVIO never asks you for feedback

No prompts, no surveys, no pop-ups — and where the report links actually point.

Written By Dustin

Last updated About 3 hours ago

TOVIO software will not interrupt you to ask for feedback. No pop-up, no survey, no in-product rating, no nag scheduled after your tenth commit, and nothing that reports back on its own. This is a written rule rather than a current preference.

There is one place TOVIO asks anything at all. The last line of tovio quickstart — a tutorial you ran deliberately — prints a dimmed question about what was confusing, and a link. It is treated as a hint like any other, so turning hints off turns it off too, and it is the end of a tutorial rather than an interruption of your work.

What that means in practice

  • A feedback link appears only where you went looking for one: the help footer, the documentation link printed on an error, and that one tutorial line.
  • Machine-readable output never carries it. --json and --quiet gain no feedback text, ever — a script's output is a contract, not a place to advertise.
  • There is no in-product survey mechanism and no net-promoter prompt, and neither is planned before general availability.

Every feedback link a TOVIO binary, extension, or app prints or opens points at a TOVIO-owned address — tovio.dev/feedback, or tovio.dev/errors/ followed by the error code. No TOVIO program embeds the portal's host name. That is what makes the channel replaceable: the destination is one reviewed entry in the project's published product data, and when it is unset every surface renders no link at all rather than breaking.

The portal itself is a link out, not an embed. No portal script, iframe, font, or cookie runs on a TOVIO-owned page; following a link is the only thing that takes you to the vendor.

Very little, and all of it deliberately treated as public: the surface you were using, the error code, the documentation page, and the TOVIO version. Never a file path, a repository or lane name, a change identifier, the error's title or cause, or anything identifying you. What the feedback portal collects, in the privacy collection, documents this in full.

The one question that is ever asked

Design partners occasionally get a plain email with a single question, described in The design partner program. It arrives as email rather than inside the product, it is written and counted by hand, and not answering it costs you nothing. There is no survey tool behind it and no in-product equivalent.