Security Architecture & Isolation
OmniPhoto provides an enterprise-ready, confidential image editing experience by decoupling modern photo editing from cloud compute servers.
WASM Linear Memory
Execution occurs within a single, isolated WebAssembly linear memory buffer protected by the browser virtual machine.
Zero Server Ingress
No photo ingestion endpoints or backend databases exist. Your images never cross the network boundary.
Hardened CSP
Strict Content-Security-Policy headers block unauthorized third-party scripts, object plugins, and untrusted network sockets.
Technical Security Breakdown
1. Local File API & Memory Lifecycle
When you drag a file into OmniPhoto, the browser File System API passes binary data directly into the WASM heap. Pixel calculations and convolution kernels process data inside client RAM. When the tab is closed, all document state is purged from memory by standard browser garbage collection.
2. Hardware Acceleration Shaders
GPU acceleration is mediated through standard WebGL2 and WebGPU graphics APIs. Shaders operate strictly on texture coordinates within the canvas bounding box, preventing unauthorized screen scraping or cross-origin canvas leakage.
3. Compliance for Confidential & Medical Imagery
Because OmniPhoto does not store, transmit, or process files on remote infrastructure, using OmniPhoto is compliant with HIPAA, GDPR, and enterprise confidentiality requirements for sensitive imagery that cannot be uploaded to third-party cloud servers.