Reduce what the platform must be trusted with.
Security starts with the architecture: sensitive content should not need to be exposed to the delivery service simply because it is moving between two people.
Zero-knowledge does not mean “zero metadata.”
A delivery service still needs limited operational information to route and manage a delivery. ShareWStyle uses “zero-knowledge” specifically to describe the content boundary: the platform is designed not to receive plaintext document content or the content-decryption key.
Access links are treated honestly.
The current design uses bearer-link security: the complete delivery link is treated as a secret. Anyone who possesses the full link can access the delivery while it remains valid.
Higher-assurance recipient-verification approaches are part of the future direction, but ShareWStyle does not advertise those as available today.
Security claims should stay narrower than the engineering.
ShareWStyle will distinguish between architectural principles, behavior that has been privately validated, and functionality that remains under development. The public website will not turn an internal test result into a production guarantee.
No production compliance claim.
ShareWStyle is not currently making a production HIPAA, legal-compliance, certification, or regulatory claim. Security-focused architecture can reduce risk without eliminating the responsibilities that apply to a production service.