Sharing that audits itself.

What "secure" means here

"Secure sharing" in most products means TLS in transit and at-rest encryption on the storage provider. SkyeConnex's sharing inherits the full Sovereignty by Architecture stack:

• The shared file is still RS(5,2) sharded across providers. A recipient downloading via a share link triggers the same client-side reconstruction path as a primary user. Plaintext never assembles on the server.
• The DEK is wrapped for each authorised recipient. Revoking a share doesn't just hide it — it terminates the recipient's ability to derive a working key.
• Every action is in the audit log. Shares created, viewed, downloaded, revoked. Signed JSON exportable, CSV streamable.

Outlook and Gmail add-ins

Two operations land directly inside email: Save attachment to SkyeConnex (encrypted upload from your inbox into the sovereignty envelope) and Insert SkyeConnex share link (one-click secure share into the email body). Manifest.xml ready for AppSource and Google Workspace Marketplace submission.

Reliability is a protocol, not a bandwidth trick

Large-file sharing inherits the five-endpoint chunked upload protocol — Init, Put, Status, Complete, Cancel — so an interrupted upload from a recipient (or sender) on a flaky connection resumes from where it left off. This is the operational answer every regulated buyer asks when comparing against MASV-class transfer.

What happens to recipients who don't have a SkyeConnex account

External recipients click a share link, optionally authenticate (password and/or identity capture), and the client-side reconstruction path runs entirely in their browser. They don't need to sign up; they don't see any of your other files; they don't gain any platform privilege. The shared file is reconstructed for them, frame-by-frame, from the same Reed-Solomon shards. Plaintext exists briefly in their browser memory for the read, then is released.

This is meaningfully different from "share a Dropbox link" because the underlying topology hasn't changed for sharing. The recipient is going through the same sovereign reconstruction path your own users go through — just authorised for one file, with an audit-captured identity.

Revocation in practice

Revoking a share invalidates the recipient's ability to derive a working wrap key for that file. Any further read attempt returns a 401 with a clear error. The recipient might retain a previously-downloaded local copy — no cloud-storage product can recover that — but no future fetches succeed. The revocation is timestamped, signed, and audit-logged.

For higher-assurance sharing, expiry-on-time and expiry-on-views can be combined. A document shared "for 48 hours, max 3 views" enforces both bounds independently, with revocation triggered the moment either threshold is hit.

Audit log queries for compliance

The audit log is event-typed and indexed for compliance queries. "Who has accessed contract X in the last 6 months?" returns a streaming CSV. "Which external recipients accessed any document tagged 'Project Alpha'?" returns a filtered set with identity, time, IP, and access duration. Append-only chain integrity prevents tampering; ML-DSA-87 signatures make exports cryptographically credible to external reviewers.

Practical patterns

Legal discovery exchange

Documents shared with opposing counsel under negotiated terms. Time-bound, view-limited, identity-captured. The audit log produces the discovery record automatically.

Clinical study coordinator access

Coordinators at partner institutions access study materials under TCPS2 / REB rules. External identity capture creates the institutional record the REB requires.

M&A due-diligence rooms

Buyer's analysts get scoped access to a subset of company data with view limits and IP-capture. Sellers retain full audit visibility. Post-deal-close, all access is revoked atomically.

Government-to-vendor document transfer

Government department shares classified-handling documents with a cleared vendor. Geo-policy ensures shards remain in-jurisdiction; recipient identity is captured and signed. Audit log produces the procurement record.