Orbit's install screen said it never sends your prompts. It was sending them
The manifest every installer agrees to promises Orbit "never sends prompts, queries, tool arguments". orbit_route_task posted your typed request to Orbit's server as part of a friction signal, and had done since the signal shipped. Redaction strips identifiers, not content, so a question about your own campaign travelled intact beside a persistent install id. That call is gone, and because deleting it only protects installs that update, the receiving server now reads the field and throws it away for every client, including every copy still on 0.32.0 or earlier. The rest of this release is the same shape: PRIVACY.md was never in the bundle at all, a consent audit was issuing passes to forms it had never actually checked, and a setup check could say blocked and go ahead in the same breath. 0.33.1 followed 0.33.0 by eighteen hours because the re-review found three false or vacuous claims inside the work written to stop false claims — including one of these fixes that had only been applied to one of the two surfaces it ships on.
What shipped
•Privacy fix — orbit_route_task no longer sends your request text. A request that matched no skill used to emit a friction signal carrying the request itself. On-device redaction strips emails, URLs, paths and key-shaped tokens; it does not strip the sentence you typed. The call is deleted, and the collector now discards the field for every event from every client, so an install that never updates stops sending it too. The signal was worth little anyway: the scoring floor meant it only ever fired on first-run gibberish, never on the failure that matters, which is a confident wrong route.
•PRIVACY.md now ships inside the .mcpb. It was absent from the bundle entirely — the only privacy file an installer received was an 816-byte page about image generation, so the whole in-product disclosure was one settings string, and that string was the one making the false claim. manifest.privacy_policies is set. PRIVACY.md also now documents the friction event, which existed and was undocumented.
•Correction — the IP-address line in PRIVACY.md said more than Orbit can back. It read "the receiving server does not log it". Orbit's application never reads or stores an IP and the telemetry table has no column for one, but the request arrives through hosting and edge infrastructure that keeps ordinary short-lived access logs, the way every HTTP service does. The page now says both halves, and says plainly that nothing correlates those logs to your install id.
•Bug fix — orbit_gdpr_consent_audit was issuing consent passes it had never earned. The kind parameter was a free string, so "signup" — the word the tool's own description used — was silently accepted, while the two rules gated on the exact value "signup_page" never ran. A signup form with no marketing opt-in checkbox came back with passes and no finding. It is a fixed set of values now. If you audited a signup page before this release, run it again.
•Bug fix — orbit_check_setup could report copy generation as blocked with an empty list of blocking issues and guidance telling you to proceed. Status and the list were derived from different conditions, so they could disagree. Status now comes from the list, which means it cannot.
•Behaviour change — orbit_score_subject_line stops advertising a content-emptiness check. It does not implement one; the underlying check is 21 literal patterns. The 0.33.0 fix removed the claim from the server and missed manifest.json, which ships the same descriptions to your client — 0.33.1 removes it from both.
•Setup fix — the install identifier in the README pointed at a registry name that is fully retired. Every version of braze-lifecycle-mcp is deprecated; the name to install is io.github.justinwilliames/orbit-lifecycle-mcp. The guide count in the same file is corrected to 99.