Open Protocol

Squyr

Bilateral Cryptographic Data Exchange

A clean-room-native primitive for pharma audience data partnerships.

Download Whitepaper ↗ Contact the team ↗

What Is Squyr?

The problem with the
current data ecosystem

Most healthcare audience data is built from surveillance — patient behavior tracked across apps, websites, and third-party data brokers without meaningful consent or clinical verification. Brands who rely on it face two compounding risks: regulatory exposure and audience quality degradation as privacy regulations tighten and third-party cookie availability contracts.

Current State
Consent: buried in terms of service, never clinically verified
Identity: probabilistic device graph, no clinical anchor
Measurement: modeled conversions, no Rx linkage
Patient control: opt-out buried in privacy policy
Compliance path: post-hoc legal review, reactive
Surveillance-based approach
Squyr
Consent: clinically verified at pharmacy point-of-care
Identity: encrypted ID graph anchored to Rx event
Measurement: cohort Rx lift with HIPAA-compliant loopback
Patient control: real-time dashboard, granular scope controls
Compliance path: built-in from day one, auditable architecture
Consent-anchored approach

How Squyr Works

Consent at the pharmacy,
compliance across the chain

01
Patient
Consent at Pharmacy
Patient consents at point-of-care pharmacy touchpoint — verified by pharmacist, scoped to specific data use, time-bounded with automatic expiration.
02
Squyr Network
Encrypted ID Graph
Patient matched to de-identified Rx data via encrypted ID graph. No PII exchanged — only hashed, role-restricted identifiers across the chain.
03
Brand
Campaign Activation
Brand targets consented patient cohort via Summit Audience Segments. Cross-channel frequency capped. Converted patients suppressed from further targeting.
04
Summit
Measurement Loopback
HIPAA-compliant cohort-level Rx lift reported to brand. Patient never re-identified. Brand receives aggregate incrementality and channel attribution data.

Who Benefits

A better data ecosystem
for every stakeholder

Patients
Visibility and control
Visibility and control over how their de-identified Rx data is used. Granular consent scope, real-time dashboard, and automatic expiration. No opaque data brokers.
Pharmacy Networks
New revenue stream
New revenue stream from consent-anchored data infrastructure. Patient relationship strengthened through transparency. Competitive differentiation as privacy regulations tighten.
Healthcare Brands
Compliant audience intelligence
Compliant, measurable path to prescription-stage audience intelligence. Audit-ready data lineage. Risk reduction as third-party data sources contract.

Bilateral Architecture

Brand brings their data. Summit brings ours.
We find the overlap. Nobody loses control.

Squyr runs the bilateral exchange under the hood — the brand's PHI never leaves their environment, Summit's data never leaves Summit's environment. Hashes exchange. Overlap surfaces. Both parties see the matched cohort size and identifier references; neither sees the other's underlying data.

Brand Side
Local hashing in brand environment
Hash · sign · transmit one-way · verify Summit signatures · receive matched IDs.
Brand's data never left brand environment.
Squyr Protocol
< 90 second exchange
Hash · encrypt · sign · transmit · verify · unwrap.
Bilateral · Auditable · Hash-chain verified
Summit Side
Local hashing in Summit environment
Receive · verify · respond signed · compute overlap · receive matched IDs.
Summit's data never left Summit's environment.