Privacy & Data Architecture
Privacy implementation follows functional requirements. CloudConvert must retain files to support async API polling: their isolated containers and 24h deletion policy are excellent for general use, but the file does exist on disk during processing. Endless Forge processes files in volatile memory streams. There is no async retrieval because we never persist the file: once the WebSocket or HTTP request closes, the data leaves RAM entirely.
If you're converting a sensitive database dump, private key file, or proprietary schema, EF's architectural inability to retain data offers stronger compliance guarantees than a time-based deletion policy.

