---
title: Phasoric | Private Exchange Hub
description: Exchange sensitive files through independent enrollment, browser-held keys, simultaneous release, local decryption, and signed receipts.
canonical_url: https://phasoric.com/private-exchange
markdown_url: https://phasoric.com/private-exchange.md
---
Private Exchange Hub

# Commit first. Reveal together.

Exchange confidential files without giving either participant an early look, or giving the organizer either private decryption key.

[Open Exchange Hub](/app/vault-exchange?target=private-exchange) [Read the security guide](/guides/private-exchange)

An account is required to organize an exchange. Invited participants enroll through their individual claim links.

Private exchange Encrypted before upload

**Participant A**Independent enrollment

Browser-held key

Package committed

Atomic release

**Participant B**Independent enrollment

Browser-held key

Package committed

No early retrieval

Local decryption

Signed receipt chain

A mutual commitment protocol

## Four clear stages. No trust theater.

The exchange boundary is visible from invitation through receipt export, so both participants know what is fixed and when retrieval becomes possible.

1.  01
    
    ### Invite each participant separately
    
    Set the participants, deadline, and file policy. Each person receives a distinct invitation they can revisit through the exchange deadline.
    
2.  02
    
    ### Create keys in each browser
    
    Each participant enrolls independently. Their browser creates the private key and keeps it out of the organizer’s hands.
    
3.  03
    
    ### Encrypt, review, and commit
    
    The file and optional access code are encrypted before upload. Once committed, a package cannot be swapped for another.
    
4.  04
    
    ### Reveal both packages together
    
    Neither side can retrieve early. The second commitment releases both encrypted packages, which are verified and decrypted locally.
    

Stays out of Phasoric’s hands

## The secrets required for the exchange.

-   Participant private decryption keys
-   Plaintext files
-   Packaged passwords or access codes
-   Finished participant bearer credentials

Phasoric coordinates

## The shared state that makes the exchange fair.

-   Participant names, email addresses, and public keys
-   The selected exchange policy and deadline
-   Encrypted packages, integrity hashes, and lifecycle state
-   A signed, exportable receipt chain

Built for consequential handoffs

## Use it when sequence matters as much as secrecy.

Private Exchange is designed for two-party, one-package-each workflows. It is not a general collaboration folder, identity-verification service, or recoverable key escrow.

### Reciprocal disclosures

Exchange two confidential disclosures without letting one participant inspect the other submission first.

### Sealed proposals

Hold both proposals behind the same commitment boundary until each party has deposited its final package.

### Protected document swaps

Require a password-protected PDF and carry the access code inside the locally encrypted package.

### Time-bounded handoffs

Set an expiration window, track lifecycle state, and export a portable receipt bundle before cleanup.

Policy choices

## Set the file boundary before anyone commits.

### General exchange

Use broader file types with the same independent enrollment, local encryption, atomic release, and receipt protocol.

### Protected PDF

Require a PDF, a password that opens it, and an explicit final commitment confirmation in the participant browser.

## The important limits are part of the product.

-   **Identity:** an invitation email is not proof of who opened it. Verify identity independently when the exchange is consequential.
-   **Recovery:** keep the original invitation private and use it to return from any supported browser until the exchange expires.
-   **Cancellation:** after enrollment begins, unilateral organizer cancellation is restricted; committed exchanges require mutual cancellation or expiration.
-   **Policy evidence:** protected-PDF checks run in the participant browser because the server cannot decrypt the file.

[Review the complete process and threat boundaries](/guides/private-exchange)

Ready when both sides are

## Create the exchange. Let the protocol enforce the order.

Invite two participants, choose a policy and deadline, then follow every enrollment, commitment, release, and receipt from one hub.

[Open Exchange Hub](/app/vault-exchange?target=private-exchange) [Explore privacy architecture](/privacy)