What the feedback portal collects

When a TOVIO surface offers a link to the feedback portal, that link may carry at most four things:

• The surface you were using — CLI, VS Code, JetBrains, Desktop, and so on (the from parameter).
• The error code, if you were looking at one (code).
• The documentation page address, if you came from one (page).
• The version of that surface — the extension version for an editor, the CLI version for the CLI (v). Not a repository or format version.

A binary or extension emits at most the first, second, and fourth of those. The page value is added by a link on the documentation or marketing site, which is the only place a documentation address is known.

What it never carries

No title, no cause, no file path, no repository name, no identity. The values are checked, not just the keys — an allowlist of names alone would let free text ride out through code or v. The error code must match the catalog shape TVO-AREA-NNN; the page value must point at one of the two TOVIO-owned sites. Anything failing those checks is dropped silently rather than forwarded.

Those four values are deliberately treated as public. The vendor does not document whether post metadata is visible to other visitors, so the allowlist is sized small enough that the answer does not matter.

The link points at TOVIO, not at the vendor

Every link goes to a TOVIO-owned address on the marketing site. No TOVIO binary or extension contains the portal's hostname — only the marketing and documentation sites know where the page forwards, and they read that from reviewed product data. The page tells you which host you are about to visit before you continue.

Links are user-initiated

A binary prints or opens that address only when you ask for it: a help footer, the documentation link on an error, the closing line of a tutorial you invoked. Machine-readable output — --json and --quiet — never gains feedback text.

What the portal itself holds

The portal is a hosted third-party service, and this part is not covered by the guarantees above. Signing in creates a contact record there. What you post is what you typed, and TOVIO staff can see your posts, votes, comments, and the sign-in identity you chose. Sign-in and posting are voluntary; nothing in TOVIO requires either.

AI features are on, selectively, and here is which

Some of the vendor's AI features are deliberately enabled, and your content passes through the vendor's AI providers for those:

• Duplicate suggestions on the feedback boards.
• Reply drafting for operator responses — a person reviews every draft before it posts.
• Help-center answers, over these articles.

The AI agent on the ticket channel is switched off initially and reconsidered later. Which processing is not user-configurable, and which providers receive content for each enabled feature, is asked of the vendor in writing and re-checked on a standing schedule. The providers are named on the supplier review page rather than here, because that page is the record.

A caveat worth stating

The portal collects personal data while the privacy notice covering it is still a draft awaiting legal review. That is a known, recorded gap, not an oversight — treat the notice as disclosure of intent rather than as an approved policy.

Never paste repository content, and never report a vulnerability there

The feedback boards are public and operated by a third party. Describe the behaviour instead of pasting contents, paths, diffs, tokens, keys, or other people's data. Security vulnerabilities go to the private channel named on the security page, never to a board.