Skip to content
Hussh
Connect MCP

Enterprise CRM Registry

User-controlled enterprise data integration platform under PCHP governance, utilizing secure local-only mappings and zero-knowledge record storage.

Concept

TL;DR: The Enterprise CRM Registry enables secure, user-authorized data synchronization between corporate CRM platforms and the personal operating layer (One). Governed by PCHP consent receipts and mapping fields on-device via Gemini models, it eliminates corporate data siloing and guarantees complete user sovereignty.

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

Relations

High-Level Capabilities & Value

The Enterprise CRM Registry bridges the gap between organizational Customer Relationship Management (CRM) databases and user-centric personal intelligence. Traditionally, enterprise integrations require a centralized backend database that silently mirrors, indexes, and analyzes corporate records. This creates significant security and privacy liabilities.

The Hussh CRM Registry architecture shifts the integration paradigm. It treats enterprise CRMs as secure, federated, and user-consented data sources. Users authorize access dynamically through the One Dashboard under strict cryptographic rules.

Key Architectural Pillars

  1. Consent-Bounded Ingress: Connected systems cannot read or write data unless they possess a cryptographically signed PCHP consent receipt. These receipts explicitly declare which fields are shared, for what purpose, and the exact expiration window.
  2. On-Device Schema Mapping: Instead of exposing raw data to centralized cloud processors, Hussh uses the local-first crm_schema_mapper (driven by lightweight models like gemini-3.5-flash) to align enterprise fields with the user's personal knowledge model.
  3. Zero-Knowledge Record Storage: No raw CRM records are stored or mirrored on Hussh's central servers. Postgres holds only normalized metadata and cached field catalogues. Actual customer data is resolved and rendered on-device, remaining ephemeral and client-contained.
  4. Single-Owner Bindings: Enterprise CRM lookup uses only the authenticated user's server-verified email and phone number. An individual can only resolve their own records; anonymous or ambiguous queries are rejected, preventing cross-tenant data leaks.

Sources