Skip to content
Hussh
Connect MCP

Trusted Connections — Generalized Social Graph

Public concept overview of Hussh's privacy-first, directional social graph architecture for agentic trust and recipient-scoped interactions.

Concept

TL;DR: Trusted Connections is Hussh's directional, app-wide social graph that allows users to designate trusted contacts for secure location sharing, check-ins, and emergency SOS alerts without storing plaintext coordinates or exposing personal networks to the server.

Status as of 2026-07-10: see body.

Relations

Introduction to Trusted Connections

Trusted Connections is a first-class, platform-wide directional social graph in the Hussh ecosystem. It elevates the concept of contact-trust from a simple, isolated feature (like SOS alerts or location tracking) into an extensible system-level relationship layer.

Unlike traditional social networks that require bidirectional approval, Trusted Connections operates on a directional model ("follow" or "designate"). This design mirrors real-world trust structures: you designate emergency contacts or allow trusted friends to see your status, but their designation of you remains independent.

Privacy by Design

True to Hussh's core zero-knowledge tenets, the Trusted Connections graph is engineered to protect user metadata and personal networks:

  • Decoupled Social Map: The network graph does not leak communication history or raw data.
  • Recipient-Scoped Credentials: Trust edges authorize the minting of device-to-device capability tokens (HCTs) that govern temporary access.
  • No Coordinate Leakage: Location sharing and check-ins that utilize Trusted Connections remain client-encrypted. The server merely acts as a secure, blind post office routing encrypted location envelopes to designated contacts.

Relationship Layer Governance

The central Hussh One agent holds exclusive authority over relationship modifications. Users manage their trust list naturally through natural language chat or voice commands (e.g., "Add Alice to my trusted connections"). The agent resolves identities against the secure platform directory, preventing free-text guessing or raw phone-number exposure, and maintains graph hygiene under strict privacy policies.

Sources