SQUYR PLATFORM · ONE TRUST ROOT

One platform.
Three capabilities.
Everything bilateral.

PHI Shield, Email Shield, and SSN Shield all share the same Ed25519 bilateral keypair and SHA-256 hash-chained audit log. One compliance posture. One onboarding. Three surfaces.

PHI Shield → Email Shield → SSN Shield →

Shared trust root · Ed25519 bilateral

PHI Shield

● LIVE

Email Shield

Pre-send DLP + bilateral encryption

● IN DEV

SSN Shield

Zero-knowledge SSN verification

● PATENT-PENDING

Ed25519 Keypair · shared trust root

◉

PHI Shield

● LIVE

Bilateral encrypted health data exchange. Patient identifiers hashed client-side, encrypted before transmission — raw PHI never crosses the wire. Both organizations hold one key each; no master key, no intermediary plaintext exposure.

HOW IT WORKS

FIPS 140-2 · RFC 8032 · RFC 5869

Bilateral key exchange

SHA-256 client-side hashing, Ed25519 signature on every bundle, HKDF-SHA256 key derivation combining both parties' master material. No plaintext crosses the wire.

COMPLIANCE

HIPAA Safe Harbor · BAA Required

BAA-gated PHI storage

All PHI tables gated behind signed Business Associate Agreements. Access requires authenticated org membership and active BAA on file. No exceptions.

AUDIT

Append-only · Cryptographically verifiable

SHA-256 hash-chain ledger

Every transmission, receipt, and verification logged in an append-only hash-chained audit log. Each entry includes SHA-256 of the previous — tampering breaks the chain.

See live demo → Request pilot →

✉

Email Shield

● LIVE

Pre-send DLP + bilateral Ed25519 encryption on every email, attachment, and SMS. PHI, PII, SSN, patient ID — detected, redacted, and sealed before transmission. Both keys required to unlock. Encryption happens on your server — no raw PHI ever leaves.

DLP FIRST

Pre-send · Atomic pipeline · No gaps

Pre-send scan

Every outgoing email, attachment, and SMS automatically scanned for sensitive information before transmission. SSN, patient ID, account numbers — intercepted and sealed before send.

ENCRYPTION

AES-256-GCM · Both keys required

Bilateral keys

Emails and attachments sealed with Ed25519 bilateral encryption. Both keys required to unlock. Recipient verifies authenticity before decryption. No PHI leaves unencrypted.

CHANNELS

Email + SMS · One compliance policy

Email + SMS

Same atomic pipeline applied to both email and SMS. One compliance policy covers both wires. Same Ed25519 trust root, same audit chain.

Open in portal ↗ Learn more →

◈

SSN Shield

● PATENT-PENDING PATENT-PENDING

Zero-knowledge SSN verification. The SSN is never transmitted, never stored, never on your infrastructure. You get a yes/no answer and an Ed25519 cryptographic proof — that's all.

PROTOCOL

Ed25519 signed proof only · Patent-pending

SSN never transmitted

Your company sends a verification challenge. The identity holder's server computes a yes/no locally, signs it with Ed25519, and transmits only the proof. You receive a yes/no — the number was never in transit.

RESULT

Verify once · Store proof · Never hold

No storage risk

Your infrastructure never receives the SSN. You store the yes/no and the Ed25519 proof. When you need to re-verify, you run the challenge again. The number is never on your servers.

APPLICATIONS

Zero direct competitors

Banking, healthcare, background checks

Every industry that currently transmits SSNs to third-party IDV vendors — banking, healthcare credentialing, employment screening, insurance underwriting. This is not encryption. This is elimination.

Request early access → See related demo →

PATENT PROTECTION

U.S. Patent Application Filed — Bilateral SSN Verification System

The bilateral SSN Shield protocol — our system for verifying Social Security numbers without transmitting them — is covered by a patent application filed with the USPTO. The system uses zero-knowledge proof to confirm SSN validity while keeping the SSN itself encrypted end-to-end.

PATENT PENDING

One platform.Three capabilities.Everything bilateral.

One platform.
Three capabilities.
Everything bilateral.