SUMMIT PROTOCOL

The identity layer underneath the platform.

THIIC is Summit's proprietary bilateral cryptographic protocol for healthcare identity exchange. Production-deployed. Patent-pending. Built specifically to enable data partnerships without vendor middleware.

LIVE · Production deployed EXTERNAL AUDIT IN PROGRESS
Records Resolved15.3M+
Match Rate94%
Resolution Time< 90s
PII TransitZero
Key ExchangeBilateral
Patent StatusPending
PROTOCOL PROPERTIES

Six properties that define THIIC.

Property · 01

No Middleware

THIIC resolves identity between Summit and any partner directly — no LiveRamp, no Acxiom, no identity graph, no vendor in the middle. The bilateral key exchange happens only between Summit and the partner.

Property · 02

No Per-Record Fees

Traditional identity resolution vendors charge per-record match fees. THIIC eliminates per-record fees by making the resolution a platform capability, not a vendor service. The license covers the resolution layer.

Property · 03

No Holding-Co Ownership

LiveRamp, Acxiom, and most identity resolution vendors are owned by holding companies. Summit's THIIC is independent — no holding company owns the identity graph, no conflicts of interest, no data sharing obligations to third parties.

Property · 04

Bilateral Key Derivation

Neither party derives the shared key alone. Summit and the partner each contribute entropy to a bilateral key that only the two parties can derive. No single party can produce the matching hash without the other.

Property · 05

Built for Healthcare

THIIC is built specifically for healthcare identity use cases. The protocol accounts for PHI-adjacent data models, HIPAA Safe Harbor de-identification standards, and BAA compliance requirements that generic identity vendors don't address.

Property · 06

Standard Primitives Only

THIIC uses standard cryptographic primitives — no proprietary algorithms, no black-box implementations. AES-256-GCM, SHA-256, ECDH — all standard, all auditable, all implementable by any party with standard cryptographic libraries.

THE 8-STEP PROTOCOL

How THIIC resolves identity without PII transit.

THIIC uses bilateral key derivation to match partner CRM data against Summit's cohort without transmitting any raw PII. The eight steps below describe the full resolution flow.

01SENDER
NORMALIZE
Partner normalizes CRM identifiers (email, phone, address) to a canonical format per THIIC specification.
02SENDER
HASH
Normalized identifiers hashed with SHA-256. No raw PII leaves the partner environment.
03BILATERAL
DERIVE
Both parties derive a shared bilateral key via ECDH key exchange. Neither party holds the key alone.
04SENDER
WRAP
Sender wraps the hashed identifiers using the bilateral key derived in step 3.
05SENDER
SIGN
Sender signs the wrapped bundle with Ed25519 — commits to the payload with sender-only signature.
06BILATERAL
TRANSMIT
Signed, wrapped bundle transmitted to Summit. Contains no raw PII — only SHA-256 hashes wrapped with bilateral key.
07RECIPIENT
VERIFY
Summit verifies sender signature on the bundle, confirms sender authenticity before processing.
08RECIPIENT
UNWRAP
Summit unwraps bundle with bilateral key and resolves against 15.3M cohort. Returns match rate + cohort flags only.
THREAT MODEL

What happens if either party is breached.

Breach Scenario · 01

Summit is breached

Partner Safe. THIIC's bilateral architecture means a breach of Summit's systems yields wrapped hashes — not raw PII, not the bilateral key, not resolution capability. Partners' data is not exposed through a Summit breach.

● PARTNER SAFE
Breach Scenario · 02

Partner is breached

Summit Safe. A breach of a partner's CRM yields wrapped hashes from that partner's sessions — not raw PII, not the bilateral key, not the ability to derive Summit's resolution. Summit's data is not exposed through a partner breach.

● SUMMIT SAFE
Breach Scenario · 03

Bundle is intercepted in transit

No Recovery. A bundled, signed, wrapped payload intercepted in transit cannot be unwrapped without the bilateral key. No PII recovery, no cohort access, no resolution capability. The bundle is inert.

● NO RECOVERY
Breach Scenario · 04

Both parties breached

In the unlikely case both Summit and a partner are breached, bilateral key exposure is theoretically possible. In this scenario, both parties coordinate on key rotation immediately. See the THIIC whitepaper for full mitigation protocols.

● SEE WHITEPAPER
WHERE THIIC FITS

THIIC works alongside existing infrastructure — it doesn't replace it.

Alongside · Clean Rooms

Not a clean room replacement

THIIC resolves identity for campaign activation — it doesn't perform the aggregate analytics that clean rooms handle. Use clean rooms for analysis, use THIIC for activation.

Alongside · Identity Graphs

Not an identity graph replacement

Identity graphs map cross-device and cross-channel identity. THIIC resolves against Summit's condition-confirmed cohort specifically. Use identity graphs for cross-channel matching, use THIIC for Summit cohort resolution.

Alongside · Activation Platforms

Not an activation replacement

THIIC resolves who the patient is. The activation platform determines where they see the ad. THIIC feeds the activation layer — it doesn't compete with DSPs, SSPs, or media buying platforms.

COMPLIANCE + AUDIT

THIIC is built for prosecution-grade audit.

Every resolution operation in THIIC is logged immutably. The audit trail is designed for prosecution-grade requirements — every operation timestamped, every key derivation recorded, every signature verified. For pharma brands with strict compliance requirements, THIIC's audit log is the documentation trail that stands up in regulatory review.

Audit LogAppend-OnlyHash-chained append-only log. No deletions, no modifications. Every resolution operation logged with timestamp, parties involved, and operation type.
Key Derivation AuditBilateralEvery key derivation event logged on both sides of the bilateral exchange. Both parties can independently verify the derivation event occurred.
Signature VerificationEd25519Every payload signed with Ed25519. Sender non-repudiation: partners cannot deny signing. Summit cannot forge a sender signature.
INTEGRATE WITH THIIC

THIIC is production-deployed. The integration is available now.

THIIC is built into Summit Exchange. Any brand or partner with a Summit license can use THIIC for identity resolution. For clean-room partners, DSP integrations, or data partnership structures, contact Summit to discuss the integration architecture.

If you're a DSP partner

THIIC can integrate with The Trade Desk, DeepIntent, and other DSPs for audience-matched activation. Discuss integration specs with Summit's engineering team.

If you're a clean room partner

THIIC works alongside AWS Clean Rooms, Snowflake, and other clean room platforms. Use clean rooms for aggregate analysis, THIIC for Summit cohort activation.

If you're a data partnership

THIIC's bilateral architecture enables data partnerships where neither party transmits raw PII. Summit is open to data partnership structures where THIIC enables both parties to participate without raw data transit.

Visit thiic.com ↗
thiic.com · Patent-pending · Production-deployed