Listening

Listening brings what people say about your product — in reviews, forums, search results, and support email — into Torno as Signals. Every connector uses an official source, and public content lands quarantined with its provenance attached.

Connectors

Connector credentials are write-only: entered once, encrypted, and never readable again through any surface.

Compliance posture

Torno connects to official APIs and licensed feeds. There is no scraping path, and no automated outreach or DM feature — these are permanent product boundaries, not gaps waiting for a release. Support email earns owned trust only after provider signature and sender-authentication checks pass; mail that fails them is held for human review rather than guessed about.

Quarantine and provenance

Public content is untrusted by definition. Everything a connector collects normalizes through the same quarantine boundary as every other Signal: text in constrained fields, provenance and sample-size metadata recorded, author identity minimized. Insights and Hypotheses derived from it carry the untrusted-derived label downstream.

Subscriptions per Loop

Each Loop subscribes to the sources, keywords, and topics it cares about, with matching rules it controls. Preview shows what a subscription would likely match before you commit to it. Backfilling history is explicit and audited. Mute rules and duplicate collapsing keep the inbox quiet without rewriting the underlying evidence.

Sync and health

Every connector reports an explicit state — idle, queued, running, rate-limited, degraded, or paused — plus cursor position, retry backoff, and a batch history you can inspect. When a provider throttles or fails, the connector says so instead of quietly falling behind.

Active validation

When passive listening is thin — pre-product, or a niche audience — a Loop can run active validation: a waitlist or fake-door test launched as a normal Change with exposure. Templates enforce launch-readiness checks (with reasoned waivers), attach curated benchmark ranges with their source and basis, and produce readouts that separate sample size, conversion, benchmark comparison, and below-threshold or no-data outcomes. A validation run concludes into a Loop Decision like any other evidence.

Honest notes

The connectors above are implemented, and each one shows its live verification status in the product: sync state, last successful batch, provider health. Torno does not claim that every provider integration is production-proven across every account and edge case; the per-connector status surface is where you check yours.